Re: Size of backed up file does not match size of restored file
2004-06-24 10:16:47
Hi Tim,
This might be APAR IC40702.
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.
"Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/23/2004 14:22
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Size of backed up file does not match size of restored file
Can anyone tell me what TSM uses as the size of file as reported by
scheduled backup (Dsmsched.log) and a command line restore.
We have a case where a file is backed up using a dynamic mgmt class. This
file changes during backup.
The file size as reported by backup is:
06/21/2004 22:51:08 Normal File--> 1,278,222,336 \\xxxxxxxxxxx [Sent]
The file as reported by restore is:
Restoring 1,272,979,456 xxxxxxxxxxxxxxxxxx [Done]
The file restored has a modified date of 06/21/2004 22:34. The backup of
the server started at 06/21/2004 at 22:30. There were no other backups of
this file after this backup. The active file was restored.
So the size of the file as reported by restore does not match the size of
the file as reported by backup.
Thanks,
Tim Rushforth
City of Winnipeg
|
|
|