> To me, not clear is the meaning of "existing file".
> Given a file in my backup, foo.avi, with a creation
> and modification date, and a size of 1 Gigabyte.
> Given a file foo.avi (same name) on my harddisk in
> the same location from which the backup has been
> created, with the same creation date as in the
> backup, but later mod-date, and a filesize of only
> 500Kb.
> Now I restore this file to the original location,
> with replace=no - what happens?
Because foo.avi already exists, foo.avi is not restored.
> Does TSM not replace the file, since the "existing
> file" (even though with different size, and different
> modification date - are there any other criteria?) is
> there with the same name and in the same location?
Correct. Because a file already exists with the same name, it is not
restored.
> Or is it replaced, as it is different from the one in
> the backup?
The decision is based solely on the file name. Therefore the content and
attributes of the file have no bearing on the decision.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Tobias Hofmann <tobias.hofmann AT MEDIEN.UNI-WEIMAR DOT DE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/05/2003 09:37
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: How does "replace=no" work?
Hi Andy, all,
On 05.11.2003 16:01, Andrew Raibeck wrote:
> I would recommend that you consult the client manual, which includes a
> reference chapter for client options.
This is from ansbc550.pdf, page 194, obtained from
http://web.urz.uni-heidelberg.de/ADSM/ibmdoc.tsm51/aix/pdf/unixc/ansbc550.pdf
, which I hope to be the correct document for the linux clients version
5.1.1.0:
"The replace option specifies what you want the system to do when it
restores files that already exist on your workstation. This option
applies to the restore, retrieve, and restore backupset commands only.
[...]
All
All existing files are overwritten, including read-only files. If access
to a file is denied, you are prompted to skip or overwrite the file. No
action is taken on the file until there is a response to the prompt.
[This is clear to me. All files will be restored, given they are not
access protected]
Yes
Any existing files are overwritten, except read-only files. If a file is
read-only, you are prompted to overwrite the file or skip it. No action
is taken on the file until there is a response to the prompt. If access
to a file is denied, the file is skipped.
[This is clear to me, too]
No
Existing files are not overwritten. No prompts will display."
> If, after reading the information on REPLACE you still don't understand
> it, let me know what is not clear.
To me, not clear is the meaning of "existing file".
Given a file in my backup, foo.avi, with a creation and modification
date, and a size of 1 Gigabyte.
Given a file foo.avi (same name) on my harddisk in the same location
from which the backup has been created, with the same creation date as
in the backup, but later mod-date, and a filesize of only 500Kb.
Now I restore this file to the original location, with replace=no - what
happens?
Does TSM not replace the file, since the "existing file" (even though
with different size, and different modification date - are there any
other criteria?) is there with the same name and in the same location?
Or is it replaced, as it is different from the one in the backup?
I am sorry to bother you with this, but from the docs it is not clear to
us. Thanks in advance for your time, it is very much appreciated -
Kind regards, tobi...
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
>
>
>
> Tobias Hofmann <tobias.hofmann AT MEDIEN.UNI-WEIMAR DOT DE>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 11/05/2003 07:18
> Please respond to "ADSM: Dist Stor Manager"
>
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: How does "replace=no" work?
>
>
> Ladies, Gentlemen,
>
> following up to my (maybe confused) question yesterday, I think my
> question boils down to this:
>
> How does 'restore ... replace=no' work?
>
> That is, what does it take for a file to not be replaced?
> Is name and location already sufficient?
> Or does the client check for creation/modification date, size, or
> something like md5-hash?
>
> tia for any info on that,
>
> kind regards, tobi... :)
>
>
> --
> ----------------------------------------------------------------------
> Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar
> Professur fuer Graphische Datenverarbeitung Projekt medienquadrat
> SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar
> Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111
> Fon: ++49-(0)3643-58-3780 Fax : -3701
> e-mail: mailto:tobias.hofmann AT medien.uni-weimar DOT de
> ----------------------------------------------------------------------
>
--
----------------------------------------------------------------------
Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar
Professur fuer Graphische Datenverarbeitung Projekt medienquadrat
SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar
Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111
Fon: ++49-(0)3643-58-3780 Fax : -3701
e-mail: mailto:tobias.hofmann AT medien.uni-weimar DOT de
----------------------------------------------------------------------
|
