Brett Maton wrote:
Hi,
Question for you guys.
A brief history:
RHEL 4 AS
I have a partition with way to many small files on (Usually around a couple of million) that needs to be backed up, standard
methods mean that a restore is impossibly slow due to the sheer volume of files.
Solution, raw backup /restore of the device. However the partition is permanently being accessed.
Proposed solution is to use software raid mirror. Before backup starts,
break the soft mirror unmount and backup partition
restore soft mirror and let it resync / rebuild itself.
Would the above intentional break/fix of the mirror cause any problems?
Probably. If by "accessed" you mean read-only, you can do this, but if
the data is changing you have a serious problem that the data on the
disk and queued in memory may leave that part on the disk as an
inconsistent data set. If there is a means of backing up a set of files
which are changing other than stopping the updates in a known valid
state, it's not something which I've seen really work in all cases.
DM has some snapshot capabilities, but in fact they have the same
limitation, the data on a partition can be backed up, but unless you can
ensure that the data is in a consistent state when it's frozen, your
backup will have some small possibility of failure. Database programs
have ways to freeze the data to do backups, but if an application
doesn't have a means to force the data on the disk valid, it will only
be a "pretty good" backup.
I suggest looking at things like rsync, which will not solve the
changing data problem, but may do the backup quickly enough to be as
useful as what you propose. Of course a full backup is likely to take a
long time however you do it.
--
Bill Davidsen <[EMAIL PROTECTED]>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
