Re: [ADSM-L] VCB Incrementals: Is there a log of what is backed up?
2011-02-16 14:20:19
Danny, are you running the backups on a client-side schedule or a TSM server
prompted schedule? If you are using a client side script, simply redirect the
output from dsmc to a text file by using ">> full_path_and_file_name" at the
end of the dsmc command line in the client side script.
Ray
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Danny Schmanny
Sent: Wednesday, February 16, 2011 11:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] VCB Incrementals: Is there a log of what is backed up?
Greetings All:
When a backup TSM agent is loaded on a backup client, we can see the results of
an incremental backup in a log file that is stored on the client (i.e.
dsmsched.log).
When we run a VCB incremental from the proxy server, there doesn't appear to be
any log on the client of the files backed up (i.e. no dsmsched.log and no other
pertinent log file that I can see). There also does not appear to be any log
on the proxy server of the VCB incremental files being backed on the clients.
How can we determine what is being backed up when VCB incrementals are run from
the proxy server? We would like to determine if we need to exclude certain
files/directories from being backed up. Do we have to resort to using Windows
Explorer on the VM to see what is there? My supervisor does not like that as
an answer and is thinking we are possibly missing a simpler solution.
Any ideas on what we have possibly overlooked would be greatly appreciated.
Thanks.
Danny Schmanny
CONFIDENTIALITY NOTICE: This email and any attachments are for the
exclusive and confidential use of the intended recipient. If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.
|
|
|