ADSM-L

Re: Open File (using lvsa) for windows client 5.3.0.0

2005-02-03 03:30:56
Subject: Re: Open File (using lvsa) for windows client 5.3.0.0
From: Jozef Zatko <zatko AT LOGIN DOT SK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 3 Feb 2005 09:34:07 +0100
Hi Steve,
here is response to your problem I have found on Tivoli support site:


Problem is due to parameters. Disk on which OFS cache is stored MUST be
saved with option "Dynamic" (see option include.fs and/or fileleveltype).
It's mandatory to specify mode "SNAPSHOT" for all others disks (even if
this is the default) when we want to use OFS option.
Hereunder is an example for a valid option file :
PASSWORDACCESS GENERATE
TCPSERVERADDRESS xxxxxxxxxx
SNAPSHOTCACHELOCATION c:\tsmcache\
SNAPSHOTFSIDLEWAIT 0ms
TCPNODELAY YES
DOMAIN C: D:
Include.Fs "C:" FILELEVELTYPE=DYNAMIC
Include.Fs "D:" FILELEVELTYPE=SNAPSHOT SNAPSHOTFSIDLEWAIT=0S

Hope this helps

Ing. Jozef Zatko
Login a.s.
Dlha 2, Stupava
tel.: (421) (2) 60252618



Steve Schaub <Steve.Schaub AT HAWORTH DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/02/2005 09:41 PM

Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Open File (using lvsa) for windows client 5.3.0.0






Anyone out there been successful with this?
I have one Win2k client that needs to backup locked files and so far
have been unsuccessful getting it to work.
I did a clean install of tsm client 5.3.0.0, configured the lvsa, did
the required reboot, but the backup still fails over to non-lvsa
incremental.  I have it running journaled, which works fine, and I can
see that tsm has created /tsmlvsacache directories on both the c: and d:
drives.  I am using remote desktop from xp to access the server,
although I have tried using the web gui as well.  I even tried pointing
the lvsacache dirs to opposite vols in the dsm.opt, but I still get the
following errors.  Any pointers on how to begin to troubleshoot this
would be appreciated.  The only reference a search on IBM turned up is
referencing 5.2 problems, which is supposedly one of the main fixes
included in 5.3.

Thanks in advance.

dsmerror.log
02/02/2005 12:07:34 ANS1327W The snapshot operation for 'D:\*' failed.
Error code: 673.
02/02/2005 12:07:34 ANS1401W The snapshot virtual volume is not
accessible.
02/02/2005 12:07:34 ANS1376W Unable to perform operation using a
point-in-time copy of the filesystem. The backup/archive operation will
continue without snapshot support.
02/02/2005 12:07:38 ANS1327W The snapshot operation for 'C:\*' failed.
Error code: 673.
02/02/2005 12:07:38 ANS1401W The snapshot virtual volume is not
accessible.
02/02/2005 12:07:39 ANS1376W Unable to perform operation using a
point-in-time copy of the filesystem. The backup/archive operation will
continue without snapshot support.

dsm.opt
*====================================================================
* Communication Section
*====================================================================
commmethod             TCPIP
tcpport                1500
tcpserveraddress       10.64.1.43
tcpbuffsize            31
tcpwindowsize          63
largecommbuffers       Yes
httpport               1581
*====================================================================
* Workstation Settings Section
*====================================================================
passwordaccess         generate
managedservices        webclient schedule
errorlogretention      90
schedlogretention      14
passwordaccess         generate
snapshotfsidlewait     1s 100ms
snapshotcachelocation  d:\
include.fs d: snapshotcachelocation=c:\


Steve Schaub
Computer Storage Systems Engineer II
Haworth, Inc
616-393-1457 (desk)
616-886-8821 (cell)
Steve.Schaub AT Haworth DOT com
"Trials are inevitable.  We can curse them and grow bitter, or harvest
them and grow stronger"
ForwardSourceID:NT00056AB2