Tuesday, December 06, 2005

System State Backup Issue

We recently had to rebuild a box (thank goodness it was not production) and found that the system state and objects had not backed up.  Stranger still there was no error stating they failed. In fact the only error was that the LVSA directory was not set and it would not be used during the backup.  Why would a failure to completely setup the LVSA affect the system objects and state? TSM doesn't require the LVSA to back them up.  We checked multiple systems and found this happening on more than one.  The client level we are on is 5.2.4 and higher.  Has anyone else experienced this?  BTW - The backup schedules were showing in the event log as COMPLETED not Failed.


  1. See the following page for an explanation and tech doc on this issue:


    Renaming the filespaces (systemstate and systemservices) allows the next backup to get them. Upgrading the clients to 5.2.3 ASAP is a better choice. Below are a couple of select statements to help identify the clients at risk. Please, no making fun, I am NOT a 'select' statement expert, but these worked for me.

    The first shows filespaces not backed up in last 24 hours, the second shows Windows 2003 clients at lower than TSM 5.2.3, that have accessed the server in the last 10 days (due to decomissioned boxes)

    select NODE_NAME, FILESPACE_NAME, BACKUP_START, BACKUP_END,DELETE_OCCURRED from filespaces where (FILESPACE_NAME='SYSTEM SERVICES' or FILESPACE_NAME='SYSTEM STATE') and cast ((current_timestamp-backup_end)hours as decimal)>24 order by backup_end asc

    select NODE_NAME,CLIENT_VERSION,CLIENT_RELEASE,CLIENT_LEVEL from nodes where CLIENT_OS_LEVEL='5.02' and CLIENT_LEVEL<3 and CLIENT_RELEASE<3 and cast ((current_timestamp-LASTACC_TIME)hours as decimal)<240 order by NODE_NAME

  2. My guess is you get the error on Windows Server 2003 without service pack 1. Am I right?