cluster backup with CSV
We have just set up a Microsoft cluster with a Cluster shared volume. After installing the TSM 8.1.4 client on both cluster nodes, we would like to back up the cluster shared volume but TSM does not see this volume from either node. Is there a way to back this up with TSM or a special configuration so this disk is recognized? Thanks, Mike Michael Hizny Binghamton University
Journal Buffer
Hi, We have set up journaling on a Windows 2012 file server with approximately 5 million files. They files don't change very often and the turnover is small. We are receiving the following error: 02/25/2017 16:52:33 ANS0361I DIAG: ReadFsChangesThread(tid 3264): ReadDirectoryChangesW: Unable to process change notification buffer, the buffer size may be need to be adjusted to avoid this problem in the future. 02/25/2017 16:52:33 ANS0361I DIAG: ReadFsChangesThread(tid 3264): exiting thread. 02/25/2017 16:58:26 ANS0361I DIAG: psFsMonitorThread(tid 3616): Notification buffer overrun for monitored FS 'G:\', journal will be reset. 02/25/2017 16:58:26 ANS0361I DIAG: jnlDbCntrl(): Resetting journal for fs 'G:'. After reading the articles (there are not many) regarding journal buffer over runs, we have changed the parameters as indicated in the IBM article (http://www-01.ibm.com/support/docview.wss?uid=swg21620688) to the following in the jbb.ini file: ; Notification Buffer Size - default 32 Kbytes for files, 16 Kbytes for dirs ; NotifyBufferSize=0x1000 DirNotifyBufferSize=0x1000 JournaledFileSystems=G:\ ; The error is still occurring. We use journaling on several other servers without issue. Does anyone have an idea on what adjustments can be made to alleviate this? We are running version 7.1.6.2 of the client. Thanks, Mike
Journaling question
All, Does anyone know a way to use journaling in TSM on a networked file system. If you go through the wizard, you can select to journal the local file systems, but there is no option to journal network connected file systems. We can back them up by specifying them in the opt file as: DOMAIN "\\xxx.xxx.xxx.xxx\folder1" DOMAIN "\\xxx.xxx.xxx.xxx\folder2"But can you set up and use journaling on them? Thanks, Mike Michael Hizny Binghamton University mhi...@binghamton.edu
TSM SQL question
Hi, We are trying to set up an automated refresh of our test system databases (Microsoft SQL) using the TSM SQL client. Does anyone know if it is possible to automatically do an SQL backup of a production server database and then restore this to a test system server via a command line script? Thanks, Mike *Michael Hizny* *Director of Networking* *Binghamton University*
Re: backup Systemstate error
The application log shows that the TsmVssPlugin reports that the writers
received a backup request. There are entries for the Registry, ASR,
Performance, Comm,, System, Task, etc writers basically saying that they
received a backup request. They are informational. The only one that
shows an error ist he following and it points me back to the TSM log:
VSS processing encountered error 'VSS_E_PROVIDER_VETO' in the Volume
Shadow Copy API 'AddToSnapshotSet'.
For more information, see the IBM Tivoli Storage Manager client error
log.
Michael Hizny
Assistant Director of Networking
Binghamton University
607-777-4739 (office)
607-777-4009 (fax)
mhi...@binghamton.edu
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Loon, EJ van - SPLXM
Sent: Monday, January 21, 2013 9:11 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] backup Systemstate error
Hi Mike!
>From your error messages down below: "initializeSnapshotSet() failed,
check Microsoft Application event log for VSS errors", did you check the
Application even log? What did it say?
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Michael P Hizny
Sent: maandag 21 januari 2013 14:51
To: ADSM-L@VM.MARIST.EDU
Subject: backup Systemstate error
Hi,
We have a windows 2008 R2 server being backup up to a TSM 6.2.2.30 server
using client version 6.4.0. The client was upgraded from 6.3 to try to
fix this problem. We are getting a failure of the systemstate backup. I
have deleted the TSM systemstate file system to try to fix this to no
avail. We have also restarted the server. The rest of the file system
backups run fine. Has anyone seen this before? The backjup domain is set
to all-local. We have also tried taking the systemstate out of the backup
and the results are the same. Here are the logs:
Dsmsched.log:
01/20/2013 18:00:21 --- SCHEDULEREC OBJECT BEGIN NT_SERVER_SCHEDULE
01/20/2013 18:00:00
01/20/2013 18:00:21 Incremental backup of volume '\\sparrow\c$'
01/20/2013 18:00:21 Incremental backup of volume '\\sparrow\e$'
01/20/2013 18:00:21 Incremental backup of volume 'SYSTEMSTATE'
01/20/2013 18:01:06 ANS1959I Removing previous incomplete group '\System
State\0\SystemState' Id:0-145799926
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'ASR' using
shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'This is the
path to the boot BCD store and the boot managers.
All the files in this directory need to be backed up.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select this
volume (\??\Volume{6fe50a41-cff1-11e0-8fb1-806e6f6e6963}) if it is a
critical volume.
Critical volumes are those which ASR must restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select this
volume (C:) if it is a critical volume.
Critical volumes are those which ASR must restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select to
include disk #0 (of signature 0x80) for ASR restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select to
include disk #1 (of signature a35bb97c-c8f9-4cf6-934d-329b30fc20e5) for
ASR restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'COM+ REGDB Writer' component 'COM+
REGDB' using shadow copy.
01/20/2013 18:01:07 Backing up object 'Performance Counters Writer'
component 'Performance Counters' using shadow copy.
01/20/2013 18:01:07 Backing up object 'Registry Writer' component
'Registry' using shadow copy.
01/20/2013 18:01:07 Backing up object 'System Writer' component 'System
Files' using shadow copy.
01/20/2013 18:01:08 Backing up object 'Task Scheduler Writer' component
'Tasks Store' using shadow copy.
01/20/2013 18:01:08 Backing up object 'VSS Metadata Store Writer'
component 'VSS Express Writer Metadata Store' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM global
configuration, including template definitions, file group definitions,
classification properties and rules, file management and report settings
that apply to the entire system' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM
classification module configuration, captured when the module registers
with FSRM' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM
configuration on volume E:\, including its quota configuration, file
screen configuration, and file screen
backup Systemstate error
Hi,
We have a windows 2008 R2 server being backup up to a TSM 6.2.2.30 server
using client version 6.4.0. The client was upgraded from 6.3 to try to
fix this problem. We are getting a failure of the systemstate backup. I
have deleted the TSM systemstate file system to try to fix this to no
avail. We have also restarted the server. The rest of the file system
backups run fine. Has anyone seen this before? The backjup domain is set
to all-local. We have also tried taking the systemstate out of the backup
and the results are the same. Here are the logs:
Dsmsched.log:
01/20/2013 18:00:21 --- SCHEDULEREC OBJECT BEGIN NT_SERVER_SCHEDULE
01/20/2013 18:00:00
01/20/2013 18:00:21 Incremental backup of volume '\\sparrow\c$'
01/20/2013 18:00:21 Incremental backup of volume '\\sparrow\e$'
01/20/2013 18:00:21 Incremental backup of volume 'SYSTEMSTATE'
01/20/2013 18:01:06 ANS1959I Removing previous incomplete group '\System
State\0\SystemState' Id:0-145799926
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'ASR' using
shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'This is the
path to the boot BCD store and the boot managers.
All the files in this directory need to be backed up.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select this
volume (\??\Volume{6fe50a41-cff1-11e0-8fb1-806e6f6e6963}) if it is a
critical volume.
Critical volumes are those which ASR must restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select this
volume (C:) if it is a critical volume.
Critical volumes are those which ASR must restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select to
include disk #0 (of signature 0x80) for ASR restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'ASR Writer' component 'Select to
include disk #1 (of signature a35bb97c-c8f9-4cf6-934d-329b30fc20e5) for
ASR restore.' using shadow copy.
01/20/2013 18:01:07 Backing up object 'COM+ REGDB Writer' component 'COM+
REGDB' using shadow copy.
01/20/2013 18:01:07 Backing up object 'Performance Counters Writer'
component 'Performance Counters' using shadow copy.
01/20/2013 18:01:07 Backing up object 'Registry Writer' component
'Registry' using shadow copy.
01/20/2013 18:01:07 Backing up object 'System Writer' component 'System
Files' using shadow copy.
01/20/2013 18:01:08 Backing up object 'Task Scheduler Writer' component
'Tasks Store' using shadow copy.
01/20/2013 18:01:08 Backing up object 'VSS Metadata Store Writer'
component 'VSS Express Writer Metadata Store' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM global
configuration, including template definitions, file group definitions,
classification properties and rules, file management and report settings
that apply to the entire system' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM
classification module configuration, captured when the module registers
with FSRM' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM
configuration on volume E:\, including its quota configuration, file
screen configuration, and file screen audit logs' using shadow copy.
01/20/2013 18:01:08 Backing up object 'FSRM Writer' component 'FSRM
reports, classification and file management logs repository, including any
scheduled, incident, and on-demand reports and logs' using shadow copy.
01/20/2013 18:01:08 Backing up object 'WMI Writer' component 'Windows
Managment Instrumentation' using shadow copy.
01/20/2013 18:01:15 ANS5283E The operation was unsuccessful.
01/20/2013 18:01:15 ANS1228E Sending of object
'SPARROW\SystemState\NULL\System State\SystemState' failed
01/20/2013 18:01:15 ANS5283E The operation was unsuccessful.
.
.
.
01/20/2013 20:22:54 ANS1512E Scheduled event 'NT_SERVER_SCHEDULE' failed.
Return code = 12.
01/20/2013 20:22:54 Sending results for scheduled event
'NT_SERVER_SCHEDULE'.
01/20/2013 20:22:54 Results sent to server for scheduled event
'NT_SERVER_SCHEDULE'.
Dsmerror.log:
01/20/2013 18:01:15 ANS1327W The snapshot operation for
'SPARROW\SystemState\NULL\System State\SystemState' failed with error
code: -1.
01/20/2013 18:01:15 ANS5250E An unexpected error was encountered.
TSM function name : BaStartSnapshot
TSM function : initializeSnapshotSet() failed, check Microsoft
Application event log for VSS errors
TSM return code : -1
TSM file : ..\..\common\ba\backsnap.cpp (6343)
01/20/2013 18:01:15 ANS5258E Microsoft volume shadow copy snapshot
initialization failed.
01/20/2013 18:01:15 ANS5283E The operation was unsuccessful.
01/20/2013 18:01:15 ANS1327W The snapshot operation for
'SPARROW\SystemState\NULL\System State\SystemState' failed with error
code: -1.
01/20/2013 18:01:15 ANS1228E Sending of object
'SPARROW\SystemState\NULL\System State\SystemState' failed
01/20/2013 18:01:15 ANS5283E The operation
TSM 6.2 Administration Center
We recently upgrade TSM to version 6.2 and have found out that the Administration Center web interface will not work with any newer browsers. It is certified to work with ie 6.0 and Firefox 2.0. Has anyone come up with a work around to get it to work with ie7, 8, or 9? Or Chrome?
