ADSM-L

Re: [ADSM-L] Diagnosing "ANS1377W: The client was unable to obtain a snapshot of 'volname'. The operation will continue without snapshot support."

2013-01-08 11:46:52
Subject: Re: [ADSM-L] Diagnosing "ANS1377W: The client was unable to obtain a snapshot of 'volname'. The operation will continue without snapshot support."
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 8 Jan 2013 11:26:43 -0500
Hi Zoltan,

You should be aware that Windows 2003 is not supported with TSM 6.4. TSM
6.3 is the last client version that will support Windows 2003.

As to why the snapshot has issues, I do not know. Are you using the LVSA or
VSS? VSS is recommended. (I'm speaking, of course, about using this with
the TSM 6.3 client). For VSS, the Windows client requirements web page
cites a couple of pre-requisite hotfix roll-up packages that you should
install, 934016 and 940349.

Best regards,

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2013-01-08
11:00:00:

> From: Zoltan Forray <zforray AT VCU DOT EDU>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 2013-01-08 11:14
> Subject: Diagnosing "ANS1377W: The client was unable to obtain a
> snapshot of 'volname'. The operation will continue without snapshot
support."
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Can someone help me figure out why one of my nodes keeps generating these
> errors and how to diagnose/fix whatever is going on.
>
> ANS1377W: The client was unable to obtain a snapshot of 'volname'. The
> operation will continue without snapshot support.
>
> This is a W2K3 server.  Upgraded the client to 6.4,  which seemed to
> resolve a lot if not all of the issues we were having with journal
backups
> on this server.  We have OFS installed, which I figure is the cause of
> these errors since the files that generate these errors are usually
open/in
> use.
>
> Nothing in dsmerror/dsmsched log files to give me more to go on.  Earlier
> when we had "can access these files" errors, it was caused by the AV
> program blocking them.  Once they were removed, those errors stopped.
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>