MAXNUMMP changed between TSM server 4.2.2.8 and 5.3.2.0
Hi TSM-ers, yesterday we upgraded our old NSM from TSM 4.2.2.8 to 5.3.2.0. Now I'm seeing the following messages for our ORACLE backups. ANR0539W Transaction failed for session 1268 for node _ORA. This node has exceeded its maximum number of mount points. (SESSION: 1268) The node has MAXNUMMP set to 1. On TSM 4.2.2.8 the session would wait for a mountpoint to be available. On 5.3.2.0 the session is cancelled. Is there anything I can change to make the second session wait for a mountpoint? Kind regards Thomas Rupp
The snapshot operation for 'C:' failed with error code: 114.
Hi *SM-ers!
We keep on struggling with making snapshot work on a Windows 2003 node (TSM
5.3.2.0 client).
The SNAPSHOTCACHESIZE is already set to 50.
The C: has 3.55 GB, D: has 5.04 GB and E: has got 5.90 GB of free space.
If the error codes are equal to the TSM API return codes, then that doesn't
help much either: 114 means Unknown System Error and 663 I cannot even find...
Does anybody know how to find the cause of these errors? I already applied the
Microsoft VSS patch KB891957, to no avail...
Thanks in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
11/15/2005 00:01:10 ANS1959W Removing previous incomplete group '\SYSSTATE'
Id:0-82000483
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group '\WMI'
Id:0-82000485
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group '\EVENTLOG'
Id:0-82000487
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group '\IIS'
Id:0-82000486
11/15/2005 00:01:20 Snapshot cache size adjusted to accommodate insufficient
space:
11/15/2005 00:01:20 Cache volume directory =
c:\tsmlvsacache\Volume{4031eb10-c5dc-11d8-9a5e-806e6f6e6963}\
11/15/2005 00:01:20 Snap volume = c:
11/15/2005 00:11:45 Snapshot cache size adjusted to accommodate insufficient
space:
11/15/2005 00:11:45 Cache volume directory =
e:\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:11:45 Snap volume = e:
11/15/2005 00:35:01 Snapshot cache size adjusted to accommodate insufficient
space:
11/15/2005 00:35:02 Cache volume directory =
e:\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:35:02 Snap volume = e:
11/15/2005 00:36:02 ANS1228E Sending of object '\\kl1011xh\d$' failed
11/15/2005 00:36:02 ANS1327W The snapshot operation for 'D:' failed with error
code: 114.
11/15/2005 00:36:02 ANS4034E Error processing '\\kl1011xh\d$': unknown system
error
11/15/2005 00:36:04 ANS1377W The client was unable to obtain a snapshot of
'\\kl1011xh\d$'. The operation will continue without snapshot support.
11/15/2005 00:38:51 ANS1327W The snapshot operation for 'E:' failed with error
code: 663.
11/15/2005 00:39:01 ANS1400W The snapshot cache location is not valid.
11/15/2005 00:39:01 ANS1377W The client was unable to obtain a snapshot of
'\\kl1011xh\e$'. The operation will continue without snapshot support.
11/15/2005 01:07:19 ANS1327W The snapshot operation for 'E:' failed with error
code: 114.
11/15/2005 01:07:19 ANS1228E Sending of object '\\kl1011xh\e$' failed
11/15/2005 01:07:19 ANS4034E Error processing '\\kl1011xh\e$': unknown system
error
11/15/2005 01:07:20 ANS1377W The client was unable to obtain a snapshot of
'\\kl1011xh\e$'. The operation will continue without snapshot support.
11/15/2005 02:48:22 ANS1228E Sending of object '\\kl1011xh\e$\Install
Base\INSTALL\Footprint_Part_1.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object '\\kl1011xh\e$\Install
Base\INSTALL\Footprint_Part_2.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object '\\kl1011xh\e$\Install
Base\INSTALL' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object '\\kl1011xh\e$\Install
Base\winzip\winzip81.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object '\\kl1011xh\e$\Install
Base\winzip\wzcline.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object '\\kl1011xh\e$\Install
Base\winzip' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object '\\kl1011xh\e$\Install Base'
failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Tasks\eMonitor\Copy of PageViewAllimport.vbs' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Tasks\eMonitor\ebtImport.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Tasks\eMonitor\ebtImport_old.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Tasks\eMonitor\hostMonitor.inc.asp' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Tasks\eMonitor\import.asp' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Tasks\eMonitor\ImportAvailability.vbs' failed
11/15/2005 02:48:23
Re: The snapshot operation for 'C:' failed with error code: 114.
Hi Eric,
For the OFS issues, the message that immediately follows the return code
message explains the return code.
I wonder if you have insufficient free space for the snapshot? The
messages that say the snapshotcachesize was adjusted are probably
indicative of insufficient space. Is it possible for you to monitor the
disk free space while a backup occurs?
For the VSS error messages, have a look at APAR IC43316, which includes
not only a code fix (which is already in 5.3.2), but some additional MS
patches.
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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
05:38:56:
Hi *SM-ers!
We keep on struggling with making snapshot work on a Windows 2003
node (TSM 5.3.2.0 client).
The SNAPSHOTCACHESIZE is already set to 50.
The C: has 3.55 GB, D: has 5.04 GB and E: has got 5.90 GB of free space.
If the error codes are equal to the TSM API return codes, then that
doesn't help much either: 114 means Unknown System Error and 663 I
cannot even find...
Does anybody know how to find the cause of these errors? I already
applied the Microsoft VSS patch KB891957, to no avail...
Thanks in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
11/15/2005 00:01:10 ANS1959W Removing previous incomplete group
'\SYSSTATE' Id:0-82000483
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\WMI' Id:0-82000485
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\EVENTLOG' Id:0-82000487
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\IIS' Id:0-82000486
11/15/2005 00:01:20 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:01:20 Cache volume directory = c:
\tsmlvsacache\Volume{4031eb10-c5dc-11d8-9a5e-806e6f6e6963}\
11/15/2005 00:01:20 Snap volume = c:
11/15/2005 00:11:45 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:11:45 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:11:45 Snap volume = e:
11/15/2005 00:35:01 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:35:02 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:35:02 Snap volume = e:
11/15/2005 00:36:02 ANS1228E Sending of object '\\kl1011xh\d$' failed
11/15/2005 00:36:02 ANS1327W The snapshot operation for 'D:' failed
with error code: 114.
11/15/2005 00:36:02 ANS4034E Error processing '\\kl1011xh\d$':
unknown system error
11/15/2005 00:36:04 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\d$'. The operation will continue without
snapshot support.
11/15/2005 00:38:51 ANS1327W The snapshot operation for 'E:' failed
with error code: 663.
11/15/2005 00:39:01 ANS1400W The snapshot cache location is not valid.
11/15/2005 00:39:01 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 01:07:19 ANS1327W The snapshot operation for 'E:' failed
with error code: 114.
11/15/2005 01:07:19 ANS1228E Sending of object '\\kl1011xh\e$' failed
11/15/2005 01:07:19 ANS4034E Error processing '\\kl1011xh\e$':
unknown system error
11/15/2005 01:07:20 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 02:48:22 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL\Footprint_Part_1.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL\Footprint_Part_2.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\winzip\winzip81.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\winzip\wzcline.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\winzip' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base' failed
11/15/2005 02:48:23
Re: Web seminars this Tue-Wed - TSM Client Backup Topics
I am confused about this webinar. The time posted below says 10CST (11EST). Yet I just went to the website/details and it says it starts at 10:30 EST ? Darrius Plantz [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/14/2005 01:06 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Web seminars this Tue-Wed - TSM Client Backup Topics This is a two part series held over 2 days covering a range of backup options. Presenters will provide useful advice about where to apply each option for each type of backup. Include/exclude list will be discussed different types of backup: Selective, incremental, image, backup sets journal based backup. Audience - TSM Admins. Presenters: David Canan Dave Daun, Advanced Technical Support (ATS) Engineers Call in particulars: Tuesday and Wednesday 15 and 16 November 2005 10:00 CST, 16:00 UK, 17:00 CET Please log in to the eMeeting and Conference Call 5 minutes prior to the scheduled start time. US: 888-857-6932; Intl: 719-457-2604; T/L: 650-0802 Confirmation Code: 9646188 https://www-1.ibm.com/collaboration/webconferences/meetingdetails.jsp?meetingId=B4204A19EEF7586A477AEA08DC5F1089 password: tiv0li (the 0 is a zero) - Yahoo! FareChase - Search multiple travel sites in one click.
Define tape library ?
Hi, Could someone provide me some quick help to get a new tapelibrary configured on my TSM server ? It's a LTO2 tape robot, the drive has SCSI ID4, and the loader has SCSI ID 5 The library in question is this one: http://www-1.ibm.com/support/docview.wss?rs=663uid=swg21116752 As far as I remember, the commands to be used, are something like: define library MYLIB libtype=scsi define drive MYLIB ??? define path pit-tsm TBERG-SUPERLOADER srctype=server desttype=library device=??? Is this the correct way ?? I'm not sure about the entries where I've put ??? - can anyone help ?? ** Mvh/Rgds. Brian Ipsen PROGRESSIVE IT A/S Århusgade 88, 3.sal Tel: +45 3525 5070 DK-2100 København Ø Fax: +45 3525 5090 Denmark Dir. +45 3525 5080 Email:[EMAIL PROTECTED] *** --- This mail was scanned for virus and spam by Progressive IT A/S. ---
Re: The snapshot operation for 'C:' failed with error code: 114.
Hi Andy!
I will ask our Windows guys whether they have tools to monitor free space
during a backup.
I will also advice them to apply the KB833167 and KB867686 patches, if they can
find them (I couldn't because they are not available for download directly).
Thank you very much for now!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 15:22
To: ADSM-L@VM.MARIST.EDU
Subject: Re: The snapshot operation for 'C:' failed with error code:
114.
Hi Eric,
For the OFS issues, the message that immediately follows the return code
message explains the return code.
I wonder if you have insufficient free space for the snapshot? The
messages that say the snapshotcachesize was adjusted are probably
indicative of insufficient space. Is it possible for you to monitor the
disk free space while a backup occurs?
For the VSS error messages, have a look at APAR IC43316, which includes
not only a code fix (which is already in 5.3.2), but some additional MS
patches.
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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
05:38:56:
Hi *SM-ers!
We keep on struggling with making snapshot work on a Windows 2003
node (TSM 5.3.2.0 client).
The SNAPSHOTCACHESIZE is already set to 50.
The C: has 3.55 GB, D: has 5.04 GB and E: has got 5.90 GB of free space.
If the error codes are equal to the TSM API return codes, then that
doesn't help much either: 114 means Unknown System Error and 663 I
cannot even find...
Does anybody know how to find the cause of these errors? I already
applied the Microsoft VSS patch KB891957, to no avail...
Thanks in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
11/15/2005 00:01:10 ANS1959W Removing previous incomplete group
'\SYSSTATE' Id:0-82000483
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\WMI' Id:0-82000485
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\EVENTLOG' Id:0-82000487
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\IIS' Id:0-82000486
11/15/2005 00:01:20 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:01:20 Cache volume directory = c:
\tsmlvsacache\Volume{4031eb10-c5dc-11d8-9a5e-806e6f6e6963}\
11/15/2005 00:01:20 Snap volume = c:
11/15/2005 00:11:45 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:11:45 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:11:45 Snap volume = e:
11/15/2005 00:35:01 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:35:02 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:35:02 Snap volume = e:
11/15/2005 00:36:02 ANS1228E Sending of object '\\kl1011xh\d$' failed
11/15/2005 00:36:02 ANS1327W The snapshot operation for 'D:' failed
with error code: 114.
11/15/2005 00:36:02 ANS4034E Error processing '\\kl1011xh\d$':
unknown system error
11/15/2005 00:36:04 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\d$'. The operation will continue without
snapshot support.
11/15/2005 00:38:51 ANS1327W The snapshot operation for 'E:' failed
with error code: 663.
11/15/2005 00:39:01 ANS1400W The snapshot cache location is not valid.
11/15/2005 00:39:01 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 01:07:19 ANS1327W The snapshot operation for 'E:' failed
with error code: 114.
11/15/2005 01:07:19 ANS1228E Sending of object '\\kl1011xh\e$' failed
11/15/2005 01:07:19 ANS4034E Error processing '\\kl1011xh\e$':
unknown system error
11/15/2005 01:07:20 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 02:48:22 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL\Footprint_Part_1.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL\Footprint_Part_2.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install
Re: Define tape library ?
DEFINE LIBRARY XX LIBTYPE=SCSI SHARED=YES AUTOLABEL=YES DEFINE PATH servername libraryname SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=lb3.1.0.5 ONLINE=YES DEFINE DRIVE libraryname DRIVE01 ELEMENT=257 ONLINE=Yes DEFINE PATH servername DRIVE01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3584LIB DEVICE=mt0.2.0.5 ONLINE=YES DEFINE DEVCLASS 3584CL DEVTYPE=LTO FORMAT=ULTRIUMC MOUNTLIMIT=DRIVES MOUNTWAIT=10 MOUNTRETENTION=10 PREFIX=TSM LIBRARY=librayname WORM=NO Edit library name, drive name etc. to your liking. Device id's and element numbers are to be taken from the OS and library manual. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ipsen - Progressive IT A/S Sent: dinsdag 15 november 2005 15:47 To: ADSM-L@VM.MARIST.EDU Subject: Define tape library ? Hi, Could someone provide me some quick help to get a new tapelibrary configured on my TSM server ? It's a LTO2 tape robot, the drive has SCSI ID4, and the loader has SCSI ID 5 The library in question is this one: http://www-1.ibm.com/support/docview.wss?rs=663uid=swg21116752 As far as I remember, the commands to be used, are something like: define library MYLIB libtype=scsi define drive MYLIB ??? define path pit-tsm TBERG-SUPERLOADER srctype=server desttype=library device=??? Is this the correct way ?? I'm not sure about the entries where I've put ??? - can anyone help ?? ** Mvh/Rgds. Brian Ipsen PROGRESSIVE IT A/S Århusgade 88, 3.sal Tel: +45 3525 5070 DK-2100 København Ø Fax: +45 3525 5090 Denmark Dir. +45 3525 5080 Email:[EMAIL PROTECTED] *** --- This mail was scanned for virus and spam by Progressive IT A/S. ---
Strange problem deleting filespaces
Hi All, I've got a strange problem when I try do delete old filespaces. The scenario: I've made a backup of the old 5.1.1.0 database. On the new system I installed TSM 5.2.6.3 on the new system and restored the database there. So far so good. To start freshly on all clients we decided to delete all the old filespaces and than this: 11/10/05 13:48:55 ANR2017I Administrator ADMIN issued command: DELETE FILESPACE lima 1 t=any data=any namet=fsid wait=no (SESSION: 2669) 11/10/05 13:48:55 ANR0984I Process 63 for DELETE FILESPACE started in the BACKGROUND at 13:48:55. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0800I DELETE FILESPACE / (fsId=1) for node LIMA started as process 63. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0802I DELETE FILESPACE / (fsId=1) (backup/archive data) for node LIMA started. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR2183W imfsdel.c(1838): Transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56980 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05
Re: The snapshot operation for 'C:' failed with error code: 114.
Hi Andy!
APAR IC43316 talks about applying two Microsoft hotfixes: KB833167 and
KB867686. KB833167 is part of Windows 2003 SP1, which is already installed on
this machine, KB867686 is a knowledge base article which doesn't seem to
exist...
We did apply the registry change suggested in this APAR.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 15:22
To: ADSM-L@VM.MARIST.EDU
Subject: Re: The snapshot operation for 'C:' failed with error code:
114.
Hi Eric,
For the OFS issues, the message that immediately follows the return code
message explains the return code.
I wonder if you have insufficient free space for the snapshot? The
messages that say the snapshotcachesize was adjusted are probably
indicative of insufficient space. Is it possible for you to monitor the
disk free space while a backup occurs?
For the VSS error messages, have a look at APAR IC43316, which includes
not only a code fix (which is already in 5.3.2), but some additional MS
patches.
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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
05:38:56:
Hi *SM-ers!
We keep on struggling with making snapshot work on a Windows 2003
node (TSM 5.3.2.0 client).
The SNAPSHOTCACHESIZE is already set to 50.
The C: has 3.55 GB, D: has 5.04 GB and E: has got 5.90 GB of free space.
If the error codes are equal to the TSM API return codes, then that
doesn't help much either: 114 means Unknown System Error and 663 I
cannot even find...
Does anybody know how to find the cause of these errors? I already
applied the Microsoft VSS patch KB891957, to no avail...
Thanks in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
11/15/2005 00:01:10 ANS1959W Removing previous incomplete group
'\SYSSTATE' Id:0-82000483
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\WMI' Id:0-82000485
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\EVENTLOG' Id:0-82000487
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\IIS' Id:0-82000486
11/15/2005 00:01:20 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:01:20 Cache volume directory = c:
\tsmlvsacache\Volume{4031eb10-c5dc-11d8-9a5e-806e6f6e6963}\
11/15/2005 00:01:20 Snap volume = c:
11/15/2005 00:11:45 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:11:45 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:11:45 Snap volume = e:
11/15/2005 00:35:01 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:35:02 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:35:02 Snap volume = e:
11/15/2005 00:36:02 ANS1228E Sending of object '\\kl1011xh\d$' failed
11/15/2005 00:36:02 ANS1327W The snapshot operation for 'D:' failed
with error code: 114.
11/15/2005 00:36:02 ANS4034E Error processing '\\kl1011xh\d$':
unknown system error
11/15/2005 00:36:04 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\d$'. The operation will continue without
snapshot support.
11/15/2005 00:38:51 ANS1327W The snapshot operation for 'E:' failed
with error code: 663.
11/15/2005 00:39:01 ANS1400W The snapshot cache location is not valid.
11/15/2005 00:39:01 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 01:07:19 ANS1327W The snapshot operation for 'E:' failed
with error code: 114.
11/15/2005 01:07:19 ANS1228E Sending of object '\\kl1011xh\e$' failed
11/15/2005 01:07:19 ANS4034E Error processing '\\kl1011xh\e$':
unknown system error
11/15/2005 01:07:20 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 02:48:22 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL\Footprint_Part_1.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL\Footprint_Part_2.exe' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
'\\kl1011xh\e$\Install Base\INSTALL' failed
11/15/2005 02:48:23 ANS1304W An active backup version could not be
found.
11/15/2005 02:48:23 ANS1228E Sending of object
Re: Strange problem deleting filespaces
Hi Richard! You didn't mention it, but I assume the restore was followed by an upgradedb? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard van Denzel [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 16:20 To: ADSM-L@VM.MARIST.EDU Subject: Strange problem deleting filespaces Hi All, I've got a strange problem when I try do delete old filespaces. The scenario: I've made a backup of the old 5.1.1.0 database. On the new system I installed TSM 5.2.6.3 on the new system and restored the database there. So far so good. To start freshly on all clients we decided to delete all the old filespaces and than this: 11/10/05 13:48:55 ANR2017I Administrator ADMIN issued command: DELETE FILESPACE lima 1 t=any data=any namet=fsid wait=no (SESSION: 2669) 11/10/05 13:48:55 ANR0984I Process 63 for DELETE FILESPACE started in the BACKGROUND at 13:48:55. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0800I DELETE FILESPACE / (fsId=1) for node LIMA started as process 63. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0802I DELETE FILESPACE / (fsId=1) (backup/archive data) for node LIMA started. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR2183W imfsdel.c(1838): Transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70
Re: Strange problem deleting filespaces
Richard, If I am understanding you correctly, you have performed the following Database backup to tape of a TSM server version 5.1.1.0 You have then tried to restore this database backup of a TSM server 5.1.1.0 to a TSM server version 5.2.6.3. This is not supported. You can only restore db backups back to a server of the same release that they came from. You have to upgrade the tsm server from 5.1.1.0 to 5.2.6.3 without doing a db restore. What you could do is the following; On your new system, install 5.1.1.0 and restore the db backup to this and then upgrade this new system from 5.1.1.0 to 5.2.6.3. You can then get a feel for how long the upgrade process will take and also do some testing on the new system to see if you have any issues. Apologies if I have not understood your email correctly and you are indeed doing an upgrade. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard van Denzel Sent: 15 November 2005 15:20 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Strange problem deleting filespaces Hi All, I've got a strange problem when I try do delete old filespaces. The scenario: I've made a backup of the old 5.1.1.0 database. On the new system I installed TSM 5.2.6.3 on the new system and restored the database there. So far so good. To start freshly on all clients we decided to delete all the old filespaces and than this: 11/10/05 13:48:55 ANR2017I Administrator ADMIN issued command: DELETE FILESPACE lima 1 t=any data=any namet=fsid wait=no (SESSION: 2669) 11/10/05 13:48:55 ANR0984I Process 63 for DELETE FILESPACE started in the BACKGROUND at 13:48:55. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0800I DELETE FILESPACE / (fsId=1) for node LIMA started as process 63. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0802I DELETE FILESPACE / (fsId=1) (backup/archive data) for node LIMA started. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR2183W imfsdel.c(1838): Transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56973 was aborted. (SESSION: 2669, PROCESS:
Re: Web seminars this Tue-Wed - TSM Client Backup Topics
The seminar conference leader just told me the following: The confirmation code is not the same for the Tuesday 11-15 and Wednesday 11-16 calls: Tuesday: 9646188 Wednesday: 4108624 (dial in numbers are the same for both calls) US: 888-857-6932; Intl: 719-457-2604; T/L: 650-0802 The web url links are different for both days as well: Tuesday: https://www-1.ibm.com/collaboration/webconferences/meetingdetails.jsp?meetingId=B4204A19EEF7586A477AEA08DC5F1089 Wednesday: https://www-1.ibm.com/collaboration/webconferences/meetingdetails.jsp?meetingId=2DF219FCFAB54B55B9DF24D45E75BF2A IF any questions full detail can be found at: http://www.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html look in November section __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: The snapshot operation for 'C:' failed with error code: 114.
Hi Erick,
How about looking at MS article 826936?
This could very well be a problem with VSS. Have a look at the above
article. If that doesn't help, you can contact IBM TSM support, but also
consider contacting MS, as it might take both parties to identify the
issue.
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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
08:25:10:
Hi Andy!
APAR IC43316 talks about applying two Microsoft hotfixes: KB833167
and KB867686. KB833167 is part of Windows 2003 SP1, which is already
installed on this machine, KB867686 is a knowledge base article
which doesn't seem to exist...
We did apply the registry change suggested in this APAR.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 15:22
To: ADSM-L@VM.MARIST.EDU
Subject: Re: The snapshot operation for 'C:' failed with error code:
114.
Hi Eric,
For the OFS issues, the message that immediately follows the return code
message explains the return code.
I wonder if you have insufficient free space for the snapshot? The
messages that say the snapshotcachesize was adjusted are probably
indicative of insufficient space. Is it possible for you to monitor the
disk free space while a backup occurs?
For the VSS error messages, have a look at APAR IC43316, which includes
not only a code fix (which is already in 5.3.2), but some additional MS
patches.
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-306.ibm.
com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
05:38:56:
Hi *SM-ers!
We keep on struggling with making snapshot work on a Windows 2003
node (TSM 5.3.2.0 client).
The SNAPSHOTCACHESIZE is already set to 50.
The C: has 3.55 GB, D: has 5.04 GB and E: has got 5.90 GB of free
space.
If the error codes are equal to the TSM API return codes, then that
doesn't help much either: 114 means Unknown System Error and 663 I
cannot even find...
Does anybody know how to find the cause of these errors? I already
applied the Microsoft VSS patch KB891957, to no avail...
Thanks in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
11/15/2005 00:01:10 ANS1959W Removing previous incomplete group
'\SYSSTATE' Id:0-82000483
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\WMI' Id:0-82000485
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\EVENTLOG' Id:0-82000487
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\IIS' Id:0-82000486
11/15/2005 00:01:20 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:01:20 Cache volume directory = c:
\tsmlvsacache\Volume{4031eb10-c5dc-11d8-9a5e-806e6f6e6963}\
11/15/2005 00:01:20 Snap volume = c:
11/15/2005 00:11:45 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:11:45 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:11:45 Snap volume = e:
11/15/2005 00:35:01 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:35:02 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:35:02 Snap volume = e:
11/15/2005 00:36:02 ANS1228E Sending of object '\\kl1011xh\d$' failed
11/15/2005 00:36:02 ANS1327W The snapshot operation for 'D:' failed
with error code: 114.
11/15/2005 00:36:02 ANS4034E Error processing '\\kl1011xh\d$':
unknown system error
11/15/2005 00:36:04 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\d$'. The operation will continue without
snapshot support.
11/15/2005 00:38:51 ANS1327W The snapshot operation for 'E:' failed
with error code: 663.
11/15/2005 00:39:01 ANS1400W The snapshot cache location is not valid.
11/15/2005 00:39:01 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\e$'. The operation will continue without
snapshot support.
11/15/2005 01:07:19 ANS1327W The snapshot operation for 'E:' failed
with error code: 114.
11/15/2005 01:07:19
Re: The snapshot operation for 'C:' failed with error code: 114.
Hi Andy!
Thanks, we will pursue that one too. We also found 891957 which is also VSS
related. I see so many VSS related issues that I have the strange feeling that
VSS is still in the beta stage...
Thank you very much!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 16:49
To: ADSM-L@VM.MARIST.EDU
Subject: Re: The snapshot operation for 'C:' failed with error code:
114.
Hi Erick,
How about looking at MS article 826936?
This could very well be a problem with VSS. Have a look at the above
article. If that doesn't help, you can contact IBM TSM support, but also
consider contacting MS, as it might take both parties to identify the
issue.
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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
08:25:10:
Hi Andy!
APAR IC43316 talks about applying two Microsoft hotfixes: KB833167
and KB867686. KB833167 is part of Windows 2003 SP1, which is already
installed on this machine, KB867686 is a knowledge base article
which doesn't seem to exist...
We did apply the registry change suggested in this APAR.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 15:22
To: ADSM-L@VM.MARIST.EDU
Subject: Re: The snapshot operation for 'C:' failed with error code:
114.
Hi Eric,
For the OFS issues, the message that immediately follows the return code
message explains the return code.
I wonder if you have insufficient free space for the snapshot? The
messages that say the snapshotcachesize was adjusted are probably
indicative of insufficient space. Is it possible for you to monitor the
disk free space while a backup occurs?
For the VSS error messages, have a look at APAR IC43316, which includes
not only a code fix (which is already in 5.3.2), but some additional MS
patches.
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-306.ibm.
com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15
05:38:56:
Hi *SM-ers!
We keep on struggling with making snapshot work on a Windows 2003
node (TSM 5.3.2.0 client).
The SNAPSHOTCACHESIZE is already set to 50.
The C: has 3.55 GB, D: has 5.04 GB and E: has got 5.90 GB of free
space.
If the error codes are equal to the TSM API return codes, then that
doesn't help much either: 114 means Unknown System Error and 663 I
cannot even find...
Does anybody know how to find the cause of these errors? I already
applied the Microsoft VSS patch KB891957, to no avail...
Thanks in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
11/15/2005 00:01:10 ANS1959W Removing previous incomplete group
'\SYSSTATE' Id:0-82000483
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\WMI' Id:0-82000485
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\EVENTLOG' Id:0-82000487
11/15/2005 00:01:18 ANS1959W Removing previous incomplete group
'\IIS' Id:0-82000486
11/15/2005 00:01:20 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:01:20 Cache volume directory = c:
\tsmlvsacache\Volume{4031eb10-c5dc-11d8-9a5e-806e6f6e6963}\
11/15/2005 00:01:20 Snap volume = c:
11/15/2005 00:11:45 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:11:45 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:11:45 Snap volume = e:
11/15/2005 00:35:01 Snapshot cache size adjusted to accommodate
insufficient space:
11/15/2005 00:35:02 Cache volume directory = e:
\tsmlvsacache\Volume{735c0427-f5ce-11d8-9a70-505054503030}\
11/15/2005 00:35:02 Snap volume = e:
11/15/2005 00:36:02 ANS1228E Sending of object '\\kl1011xh\d$' failed
11/15/2005 00:36:02 ANS1327W The snapshot operation for 'D:' failed
with error code: 114.
11/15/2005 00:36:02 ANS4034E Error processing '\\kl1011xh\d$':
unknown system error
11/15/2005 00:36:04 ANS1377W The client was unable to obtain a
snapshot of '\\kl1011xh\d$'. The
Imagebackup questions
Hi, I want to use online imagebackup with BartPE or WinPE for fast recovery of important windows servers and already did some backup restore tests successfully. But I wonder whether it's possible to exclude the pagingfile from c: and to use compression. It seems that compression is ignored and no files are excluded from imagebackup. (Other solutions like ghost do compression and exclude paging file) Can someone help Kind regards Stefan Holzwarth
JR- Backing up same node using diff mgmt class and/or diff schedules
2 SCENARIOS 1) you want to back up certain data on a node with a retention of 10 versions/ 30 days on the same node - you want to back up a couple of datasebases with 2 version/ 14 day retention specs I'm assuming you: set up different Management Classes below a Policy Set and then, in your dsm.opt file, you append the Managment Class name to the end of the include statements specifying which Management Class will manage the retention/versions for those particular files? i.e. include d:\...\* -Mgmtclass_name1 include e:\...\* -Mgmtclass_name2 (?) ___ 2) You want to back up a node 5 days a week, backing up a 'd:' drive directory spec. On the same node, on the weekends, you want to just back up an 'e:' drive directory spec. I could see two schedules - one that runs Monday through Friday, and one that runs Saturday and Sunday. However, if it invokes the same dsm.opt I do no know how to get it to differentiate between what data should be backed up based upon which schedule it is running in. Can you have different dsm option files invoked instead of dsm.opt (say, dsm.weekday and dsm.weekend)? Perhaps a presched that renames the dsm.opt if it is a weekend, invokes a different dsm.opt, and then a post sched that switches it back? Can you have more than 1 nodename for the same server?
TSM Win client DOMAIN statement and unc names
I'm confused: TSM client 5.3.x on Win2K: If I map a network drive as drive F: and add it to my dsm.opt file this way: DOMAIN ALL-LOCAL F: Assuming I have the right permissions, the scheduler will back up F: just fine. When I open the GUI client and do edit- preferences - Backup, I can see F: is in the domain list, and I can select it for backup. If I DONT map a drive letter, but I add that same drive to my dsm.opt file this way: DOMAIN ALL-LOCAL \\host\d$ Assuming I have the right permissions, the scheduler will back up this drive just fine. But when I open the GUI client and do edit - preferences - backup, it isn't in the domain list, and I can't select it from the GUI. Is this WAD? I found in the doc where the unc name is allowed in dsm.opt, but can't find an explanation of the difference in the scheduler and GUI behavior? Thanks Wanda Prather * I/O, I/O, It's all about I/O * -(me)
Re: Define tape library ?
Hi, Well, the OS is Windows Server 2003 ... These OS and library manuals, can they be found on the IBM website for TSM ? I assume, that the parameters you mention are these: DEFINE PATH servername libraryname SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=lb3.1.0.5 ONLINE=YES ^^ DEFINE PATH servername DRIVE01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3584LIB DEVICE=mt0.2.0.5 ONLINE=YES ^ 2nd: The drivetype is LTO2, not LTO - but maybe TSM is able to figure that out itself ? I haven't tried attaching a tape-library before, so I'm quite new to these commands (I've mostly done disk-based storage pools untill now - just testing in small-scale environment). Mvh/Rgds. Brian Ipsen -Original Message- From: Bos, Karel [mailto:[EMAIL PROTECTED] Sent: 15. november 2005 16:12 To: ADSM: Dist Stor Manager Subject: RE: Define tape library ? DEFINE LIBRARY XX LIBTYPE=SCSI SHARED=YES AUTOLABEL=YES DEFINE PATH servername libraryname SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=lb3.1.0.5 ONLINE=YES DEFINE DRIVE libraryname DRIVE01 ELEMENT=257 ONLINE=Yes DEFINE PATH servername DRIVE01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=3584LIB DEVICE=mt0.2.0.5 ONLINE=YES DEFINE DEVCLASS 3584CL DEVTYPE=LTO FORMAT=ULTRIUMC MOUNTLIMIT=DRIVES MOUNTWAIT=10 MOUNTRETENTION=10 PREFIX=TSM LIBRARY=librayname WORM=NO Edit library name, drive name etc. to your liking. Device id's and element numbers are to be taken from the OS and library manual. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ipsen - Progressive IT A/S Sent: dinsdag 15 november 2005 15:47 To: ADSM-L@VM.MARIST.EDU Subject: Define tape library ? Hi, Could someone provide me some quick help to get a new tapelibrary configured on my TSM server ? It's a LTO2 tape robot, the drive has SCSI ID4, and the loader has SCSI ID 5 The library in question is this one: http://www-1.ibm.com/support/docview.wss?rs=663uid=swg21116752 As far as I remember, the commands to be used, are something like: define library MYLIB libtype=scsi define drive MYLIB ??? define path pit-tsm TBERG-SUPERLOADER srctype=server desttype=library device=??? Is this the correct way ?? I'm not sure about the entries where I've put ??? - can anyone help ?? ** Mvh/Rgds. Brian Ipsen PROGRESSIVE IT A/S Århusgade 88, 3.sal Tel: +45 3525 5070 DK-2100 København Ø Fax: +45 3525 5090 Denmark Dir. +45 3525 5080 Email:[EMAIL PROTECTED] *** --- This mail was scanned for virus and spam by Progressive IT A/S. --- --- This mail was scanned for virus and spam by Progressive IT A/S. --- --- This mail was scanned for virus and spam by Progressive IT A/S. ---
Re: TSM Win client DOMAIN statement and unc names
Hi Wanda, I would call this a bug. 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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 ADSM-L@VM.MARIST.EDU wrote on 2005-11-15 15:03:08: I'm confused: TSM client 5.3.x on Win2K: If I map a network drive as drive F: and add it to my dsm.opt file this way: DOMAIN ALL-LOCAL F: Assuming I have the right permissions, the scheduler will back up F:just fine. When I open the GUI client and do edit- preferences - Backup, I can see F: is in the domain list, and I can select it for backup. If I DONT map a drive letter, but I add that same drive to my dsm. opt file this way: DOMAIN ALL-LOCAL \\host\d$ Assuming I have the right permissions, the scheduler will back up this drive just fine. But when I open the GUI client and do edit - preferences - backup, it isn't in the domain list, and I can't select it from the GUI. Is this WAD? I found in the doc where the unc name is allowed in dsm.opt, but can't find an explanation of the difference in the scheduler and GUI behavior? Thanks Wanda Prather * I/O, I/O, It's all about I/O * -(me)
Re: TSM Win client DOMAIN statement and unc names
Andy are you sure? I don't remember seeing UNC paths that have been added to a dsm.opt show up in the GUI ever. I'm wondering if the F: drive shows up in Wanda's case because it is mapped and all mapped drives show up under Network in the GUI. I just mapped a drive without ever putting anything in the dsm.opt and I see it under Network. Further I added it to the dsm.opt and that didn't change the fact that it only showed up under Network. What I'm asking is do you really think adding something to the domain statement, drive letter or UNC, will really have an effect on the GUI? I'm running the V5.2.3 client on WinXP Kyle Andrew Raibeck [EMAIL PROTECTED] wrote: Hi Wanda, I would call this a bug. 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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 wrote on 2005-11-15 15:03:08: I'm confused: TSM client 5.3.x on Win2K: If I map a network drive as drive F: and add it to my dsm.opt file this way: DOMAIN ALL-LOCAL F: Assuming I have the right permissions, the scheduler will back up F:just fine. When I open the GUI client and do edit- preferences - Backup, I can see F: is in the domain list, and I can select it for backup. If I DONT map a drive letter, but I add that same drive to my dsm. opt file this way: DOMAIN ALL-LOCAL \\host\d$ Assuming I have the right permissions, the scheduler will back up this drive just fine. But when I open the GUI client and do edit - preferences - backup, it isn't in the domain list, and I can't select it from the GUI. Is this WAD? I found in the doc where the unc name is allowed in dsm.opt, but can't find an explanation of the difference in the scheduler and GUI behavior? Thanks Wanda Prather * I/O, I/O, It's all about I/O * -(me) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: TSM Win client DOMAIN statement and unc names
Hi Kyle, If the drive letter maps to a network resource, then it makes sense to have it show up under network, whether it's in the domain or not. I think if it is a valid resource to back up at the domain level, it should appear in the GUI. The command line client and the scheduler certainly recognize it when it's in the DOMAIN list. 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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. TSM_User [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2005-11-15 16:16 Please respond to ADSM: Dist Stor Manager To ADSM-L@VM.MARIST.EDU cc Subject Re: TSM Win client DOMAIN statement and unc names Andy are you sure? I don't remember seeing UNC paths that have been added to a dsm.opt show up in the GUI ever. I'm wondering if the F: drive shows up in Wanda's case because it is mapped and all mapped drives show up under Network in the GUI. I just mapped a drive without ever putting anything in the dsm.opt and I see it under Network. Further I added it to the dsm.opt and that didn't change the fact that it only showed up under Network. What I'm asking is do you really think adding something to the domain statement, drive letter or UNC, will really have an effect on the GUI? I'm running the V5.2.3 client on WinXP Kyle Andrew Raibeck [EMAIL PROTECTED] wrote: Hi Wanda, I would call this a bug. 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-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.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 wrote on 2005-11-15 15:03:08: I'm confused: TSM client 5.3.x on Win2K: If I map a network drive as drive F: and add it to my dsm.opt file this way: DOMAIN ALL-LOCAL F: Assuming I have the right permissions, the scheduler will back up F:just fine. When I open the GUI client and do edit- preferences - Backup, I can see F: is in the domain list, and I can select it for backup. If I DONT map a drive letter, but I add that same drive to my dsm. opt file this way: DOMAIN ALL-LOCAL \\host\d$ Assuming I have the right permissions, the scheduler will back up this drive just fine. But when I open the GUI client and do edit - preferences - backup, it isn't in the domain list, and I can't select it from the GUI. Is this WAD? I found in the doc where the unc name is allowed in dsm.opt, but can't find an explanation of the difference in the scheduler and GUI behavior? Thanks Wanda Prather * I/O, I/O, It's all about I/O * -(me) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
