Hi Andy!
Can you explain what's causing the message you are reffering to (The
client was unable to obtain a snapshot of the file system. The operation
will continue without snapshot support)?
If TSM wasn't able to obtain a snapshot, a user would like to know
why...
Also, it's only issued for a few files and directories, not for all...
Thanks for your reply!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: donderdag 18 januari 2007 15:38
To: [email protected]
Subject: Re: Return code 650?

Hi Eric,

I realize the message appears to be confusing, but the explanation is
all there, in the text immediately following the 650.

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
ager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <[email protected]> wrote on 01/18/2007
05:39:03 AM:

> Hi *SM-ers!
> Today I encountered some warnings during the backup of my pc.
> For several files and directories I see the following messages in the
> dsmerror.log:
>
> ANS1327W The snapshot operation for 'C:\AUTOEXEC.BAT' failed with 
> error
> code: 650.
> The client was unable to obtain a snapshot of the file system. The 
> operation will continue without snapshot support.
>
> I cannot find the meaning of return code 650. It's not a (documented) 
> TSM API return code (source dsmrc.sh) nor is it a (documented) Win32 
> return code...
> Thank you very much in advance!
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
>
> **********************************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain 
> confidential and privileged material intended for the addressee only. 
> If you are not the addressee, you are notified that no part of the 
> e-mail or any attachment may be disclosed, copied or distributed, and 
> that any other action related to this e-mail or attachment is strictly

> prohibited, and may be unlawful. If you have received this e-mail by 
> error, please notify the sender immediately by return e-mail, and 
> delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its

> subsidiaries and/or its employees shall not be liable for the 
> incorrect or incomplete transmission of this e-mail or any 
> attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal 
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with 
> registered number 33014286
> **********************************************************************


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286 
**********************************************************************

Reply via email to