I guess I don't see a problem with wiping out what is already there
before the restore. We do this all the time to do DB restores from our
Production environment to refresh Test/Dev environments. Presumably
you're doing the restore because you're environment is already hosed.
Since you say you can't have ANY files in the directory that weren't on
the backup then the rsync's only advantage is you could look at the
files restored before overwriting what is in the directory you had
originally backed up. It has the big disadvantage of requiring you to
do I/O first for the restore from backup and then for the transfer from
one directory to the other (unless you insure both directories are on
the same filesystem).
Again since you're doing the restore because you're already hosed doing
the rsync would probably not be very helpful - if there was a chance you
could recover from the files already there rather than restoring from
backup you wouldn't be doing the restore in the first place.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin
Piszcz
Sent: Friday, October 19, 2007 4:16 PM
To: peterschmidt AT northwesternmutual DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] "True" restore
On Fri, 19 Oct 2007, peterschmidt AT northwesternmutual DOT com wrote:
> All -
>
> We have an application with a unique backup/restore requirement.
>
> Simply, when a backup is taken - it must be a "true image" of the
> system. Subsequently, when a restore is performed, it must be an
-exact-
> image of the restore - nothing "extra".
>
> In other words, any files on the target which do not belong, (which
were
> not on the target at the time of the backup) cannot remain after the
> restore is performed.
>
> We looked at "TIR" - but there is a bold statement that says "extra"
> files are not removed - so this doesn't appear as though it will work
> for us.
>
> Here are specifics on the app:
>
> It's called "TeamSite", and the vendor has provided very stringent
> instructions (though no tool) as to how "to" and "not to" backup the
> data.
> One would issue a quiesce command "iwfreeze", take a full backup of
the
> system, then issue the "iwfreeze -" to turn the app loose again.
>
> Other than wiping out the data prior to performing a restore from a
full
> backup, we're at a loss to a "better" solution. It appears as though
> this application's DB will become "corrupt" if there are "extra"
files,
> so it's critical that the system be recovered to the exact state it
was
> at the time of queisce.
>
> Does anyone else have any experience with this application? If so -
how
> have you worked around these requirements?
>
> Pete Schmidt
> Northwestern Mutual Life
> </pre><font face=Arial>This e-mail and any attachments may contain
confidential information of Northwestern Mutual. If you are not the
intended recipient of this message, be aware that any disclosure,
copying, distribution or use of this e-mail and any attachments is
prohibited. If you have received this e-mail in error, please notify
Northwestern Mutual immediately by returning it to the sender and delete
all copies from your system. Please be advised that communications
received via the Northwestern Mutual Secure Message Center are secure.
Communications that are not received via the Northwestern Mutual Secure
Message Center may not be secure and could be observed by a third party.
Thank you for your cooperation.</font><pre>
>
Almost sounds like you need to restore it elsewhere and then:
rsync -avu --delete my_restore_data
destination_and_remove_all_files_that_exist
rsync should serve this exact purpose, not sure whether you could do
this
with netbackup though
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply immediately to the
sender that you have received the message in error, and delete it. Thank you.
----------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
