Oct 28

Scheduled backups can hang in a firewall environment

Clients Comments Off on Scheduled backups can hang in a firewall environment

Problem(Abstract)

Scheduled backup hangs in a firewall environment after a communication error occurs

Symptom

Scheduled backup hangs

Cause

When a Tivoli Storage Manager (TSM) client and server are configured to use the SESSIONINITIATION SERVERONLY option, this indicates that only the Tivoli Storage Manager server can initiate scheduled backup operations. If a scheduled operation experiences a communication problem and is interrupted, it is possible that the client could become unresponsive, leading to an incomplete or failed backup and missed future scheduled operations.

The issue in this situation is that the Tivoli Storage Manager client does not have the ability to re-establish the lost session due to the firewall and SESSIONINITIATION settings, and the Tivoli Storage Manager server does not currently have functionality to provide for session re-establishment. Because the scheduled event is still IN PROGRESS (as shown by the QUERY EVENT command output), subsequent scheduled backups also will not run, meaning that no scheduled backups from the affected node will run again without intervention.

 

Resolving the problem

This situation will require that the Tivoli Storage Manager client scheduler be halted and restarted, and the DELETE EVENT command will need to be issued on the Tivoli Storage Manager server to reset the scheduled event state for the affected node.

For example, to delete records for events with scheduled start times prior to 08:00 on May 26, 2011 (05/26/2011), and whose startup window has passed, issue the following command:
delete event 05/26/2011 08:00

 

written by Bosse

Oct 28

Data binding to wrong managment class

Versions files and directories Comments Off on Data binding to wrong managment class

Problem(Abstract)

Client data is bound to an incorrect management class even though there is a include statement in place.

Resolving the problem

Different include statements have different effects on the data being backed up.

  • DIRMC management_class1
    This binds all the directory structures to the ‘management_class1’.
  • INCLUDE c:\test\* management_class2
    This binds all the files in the directory \test to ‘management_class2’ which includes files with extensions and files with no extensions.
  • INCLUDE c:\test\*.* management_class3
    This binds all the files in the directory \test that have an extension to management ‘management_class3’ but files with no extensions will still bind to the default management class.

written by Bosse

Oct 03

http://support.microsoft.com/kb/979711/sv

 

written by Bosse