This "problem" sounds impossible,,, kinda like an "Ann Landers" test(?).
If you want to restore file that changed AFTER the latest backup, by
definition, it has not been backed up, yet! I suspect, like other respondents,
that you are really looking for point-in-time restore...
I worked with a customer situation where a drive failure occurred "slowly",
such that the admin's failed to prevent normal-daily-incr from running after
hundreds of thousands of files got vaporized, though the drive was still
operating; the net was to research the logs for the last successful (and
full/good) daily incremental, selecting the date-time of completion for the PIT
parameters.
Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT ayett DOT net (change aye to a for replies)
Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Xavier Merlin
Sent: Thursday, February 20, 2003 4:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: incremental restore
Hello,
Someone wants to restore only the files which have changed after the latest
backup.
The opposite of the -ifnewer option on the restore command, in other words
doing an "incremental restore".
There are possible ways of doing this, like for instance for a unix client:
touch -t some_time_stamp some_ref_file
find -newer some_ref_file > files_to_restore
for each if the files in files_to_restore dsmc restore .....
Are there any other possibilities, preferrably using standard TSM
mechanisms ?
Xavier Merlin
________________________________________________
DISCLAIMER
This e-mail and any attached files are confidential and may be legally
privileged. If you are not the addressee, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this communication is
strictly prohibited. If you have received this transmission in error please
notify KBC immediately and then delete this e-mail.
KBC does not accept liability for the correct and complete transmission of the
information, nor for any delay or interruption of the transmission, nor for
damages arising from the use of or reliance on the information.
All e-mail messages addressed to, received or sent by KBC or KBC employees are
deemed to be professional in nature. Accordingly, the sender or recipient of
these messages agrees that they may be read by other KBC employees than the
official recipient or sender in order to ensure the continuity of work-related
activities and allow supervision thereof.
|
