Re: Backup completion / BACKUP_END on network FileSpaces?
When performing the backup, do not append '\*' to the end of the share
name (the messages you include in your post suggest that this is what you
Do this: dsmc i \\machinename\sharename
Not this: dsmc i \\machinename\sharename\* -subdir=yes
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
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.
Ted Byrne <ted.byrne AT ADELPHIA DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Please respond to
"ADSM: Dist Stor Manager"
ADSM-L AT VM.MARIST DOT EDU
Backup completion / BACKUP_END on network FileSpaces?
We have two customers that back up remote drives. One client was recently
upgraded to version 184.108.40.206 (from 4.x) and the other is running at
220.127.116.11. Both clients are Win2K servers.
On the client that was upgraded, the backup_end field (Backup Completion
date/time) for that filespace has not changed since the client upgrade
place(03/08). Prior to the upgrade, the completion date/time was updated
with each backup.
On the client that has been at 18.104.22.168, there is no backup completion
date/time showing for the network filespace.
On both clients, messages indicating that the Filespace backup has
completed are logged in dsmsched.log
04/07/2004 02:07:28 Successful incremental backup of
04/08/2004 07:47:50 Successful incremental backup of
Is this a known bug (or WAD behavior) in the 5.x clients? I've searched
the APAR database, Richard's ADSM QuickFacts and adsm.org, but have not
come up with a hit. It's always possible that I may not be using the
search terms to get a match.
Thanks in advance,