Use these tips to fix the Windows system state backup issues

Performing system state backup of a Windows system using higher version Tivoli Storage Manager client can cause various problems if it is sending backup to lower version Tivoli Storage Manager server. The cause of these different symptoms are all related to the difference in the backup method used by the 6.2 client and the extra processing required by the server.

This problem applies to newer versions of the Windows operating system due to the number of objects contained in the backup of the system state. Windows 2008, Windows Vista, Windows 7 and most likely later versions of Windows when they come out are affected by this issue. These problems include:

• Extended backup time.

• Extended time for inventory expiration.

• Recovery log filling up quickly due to slower writing of "dirty pages" to the data base volumes.

• Higher CPU utilization by the Tivoli Storage Manager server.

Also Read: What is System State Backup and why do we need it ?

Troubleshooting Tips

• Create a new backup window for the system state backups so they are not running during the normal backup window and also not during other times the server may experience heavy usage.

• Use policy settings to limit the number of versions for system state backups. The greater the number of versions being kept the greater the amount of processing that needs to be performed by the Tivoli Storage Manager server.

• Limit the frequency that system state backups are performed.

• Create new Tivoli Storage Manager server instances to balance the workload.

• Use the TESTFLAG POORSMANINCR as documented in APAR IC68962. That will cause more data to be processed during the system state backup, however, it will significantly reduce the CPU required for the processing. If the client level is 6.2.3 or higher the testflag has been replaced with the client option SYSTEMSTATEBACKUPMETHOD which can be set to FULL to always do a full system state backup or to OPPORTUNISTIC to only perform the full system state backup if a component in that system state has changed. Since it is likely that something has changed the option setting FULL is recommended.

The long term solution is to migrate to a 6.x version of the Tivoli Storage Manager server where the data base operations required to support the newer method of the system state backup can be performed more efficiently.

Also Read: Different types of Image Backups

Syntax

                            .-PROGressive---.   
>>-SYSTEMSTATEBACKUPMethod--+---------------+------------------><
                            +-OPPortunistic-+   
                            '-FULL----------'   

Parameters

PROGressive

With the PROGressive method, the system writer portion of the system state data is backed up using the progressive incremental backup method. That is, if system writer files have not changed since the last system state backup, they are not included in this backup. Only the changed system writer files are backed up. This is the default system state backup method. This type of system state backup uses the least network bandwidth and Tivoli Storage Manager server storage, but it increases the amount of Tivoli Storage Manager database processing required to keep track of the changes.

OPPortunistic

With the OPPortunistic method, if any system writer files have changed since the last system state backup, all system writer files are backed up. This method, like the PROGressive method, also uses the least network bandwidth and Tivoli Storage Manager server storage if system writer files have not changed since the last system state backup. If any system writer files have changed since the last system state backup then the system writer is backed up in full, which uses more network bandwidth and Tivoli Storage Manager server storage. With the OPPortunistic method, the amount of Tivoli Storage Manager database processing that occurs is less than that caused by the PROGressive method.

FULL

When FULL is specified, all system writer files are backed up, even if they have not changed since the last system state backup. This type of system state backup uses the most network bandwidth and Tivoli Storage Manager server storage because all system writer files are backed up during each system state backup operation. However, this system state backup method causes little Tivoli Storage Manager database processing.

Examples
Options file:

SYSTEMSTATEBACKUPMETHOD FULL

SYSTEMSTATEBACKUPMETHOD OPPORTUNISTIC

Command line:

backup systemstate -SYSTEMSTATEBACKUPMETHOD=FULL