Dec 27

IBM Spectrum Protect™ Backup-Archive Client 8.1.4 APARs and 8.1.4.x APARs

Clients Comments Off on IBM Spectrum Protect™ Backup-Archive Client 8.1.4 APARs and 8.1.4.x APARs

Fix Pack 8.1.4

APAR Platforms fixed Description
IT22806 All Unix/Linux 8.1.2 CLIENT’S LANFREE BACK UP FAILS WITH ANS1235E WHEN  THE NODE HAS VALIDATEPROTOCOL SET ALL.
IT22707 All Windows ANS5250E ENCOUNTERED DURING ‘RESTORE SYSTEMSTATE’ IN HARDLINKSWRITE
IT22689 All Platforms UPGRADING BOTH CLIENT AND SERVER TO EITHER 718 OR 812 MAY RESULT IN SSL INITIALIZATION FAILURE WHEN USING MD5 TYPE CERTIFICATES
IT22672 All Unix/Linux ANS1068E ERROR FOR BACKUP IMAGE OF FILESYSTEM CREATED ON DEVICE-MAPPER MULTIPATH DEVICE
IT22660 Windows x64 Hyper-v backup vm with added vhdx can not be restored
IT22556 All Platforms ANS0361I ANR0480W ANR8218W WHEN USING PERFMONTCPSERVERADDRESS
IT22485 All Unix/Linux AUTOMATIC DEPLOYMENT OF BACKUP-ARCHIVE CLIENT MIGHT FAIL ON TARGET MACHINES CONFIGURED FOR SSL/TLS COMMUNICATION
IT22380 All Windows ANS1071E MESSAGE SHOULD REPORT VOLUME MOUNT POINT NAME INSTEAD OF ‘(DRIVE NOT AVAILABLE)’.
IT22377 All AIX
All Linux
UNEXPECTED PATHS FOR FILE(S) IN DSMERROR.LOG FOR FILESET SNAPSHOT BASED BACKUP
IT22374 All Platforms DSMC Q BA QUERYSUMMARY INCORRECT FOR LARGE AVG. FILE SIZE
IT22245 Linux x86
Windows x64
DSMC.EXE MAY CRASH WHEN EXECUTING BACKUP VM WITH IFINCREMENTAL MODE
IT22157 All Platforms SNAPDIFF DOCUMENTATION NEEDS CLARIFICATION FOR IBM SPECTRUM PROTECT BACKUP-ARCHIVE CLIENT PROCESSING OPTION
IT22038 All Platforms CLIENT MAY GIVE “RC 0” WHEN A FILE COULD NOT BE DELETED DURING ARCHIVE PROCESSING WITH “-DELETEFILES” OPTION
IT21994 All Unix/Linux AFTER AN INSTALL FAILURE WRONG CODE IS RECORDED IN THE LOGS TO THE SP SERVER
IT21991 All Platforms EXPECT ANS5294E ERROR MESSAGE, INSTEAD  ANS8007E WHEN TRY TO CONNECT TO 8.1.2 SERVER AS NON-AUTHORIZED USER.
IT21983 All Windows IBM SPECTRUM PROTECT CLIENT CAN CRASH ON WINDOWS IF MICROSOFT SYSTEM PARTITION HAS A PATH NAME EQUAL OR GREATHER THAN 49 CHARS
IT21873 All Unix/Linux DSMADMC MIGHT CRASH WHEN A COMMAND IS SUBMITTED WITH DISPLAYMODE SET TO TABULAR
IT21657 All Windows ANS9999E MESSAGE WITH FILE ACCESS ERROR RETURN CODE 1359 CAUSES AN ANS1999E AND STOPS THE BACKUP
IT21639 All AIX
All Linux
CLIENT INCORRECTLY PROCESSES FILELIST OF IBM SPECTRUM SCALE SNAPSHOTS WITH NESTED MOUNTPOINTS.
IT21512 All Windows DSMCAD.EXE CAN HANG TRYING TO START DSMSVC.EXE DUE TO A HANDLE LEAK
IT21322 Mac AFTER UPGRADE TO 7.1.6.5, THE NEXT INCREMENTAL BACKUP WILL UPDATE ATTRIBUTES ON THE SERVER FOR OBJECTS WITH NO CHANGES.
IT21310 Mac RESTORE OF FILES WITH A SERIES OF NULL VALUES MAY BE CORRUPTED.
IT21291 All Windows AUTHORITATIVE RESTORE OF A CLUSTER NODE USING “RESTORE SYSTEMSTATE CLUSTERDB” COMMAND FAILS WITH ANS5189E
IT21200 All Windows BACKUP OF SYSTEMSTATE CAN ERROR WITH ANS1228E/ANS4987E FOR ‘BCD’  OBJECT IF ‘BCD’ IS IN LOWERCASE
IT21172 All Platforms DEDUBLICATION CACHE NOT RESTORED AUTOMATICALLY IN CASE OF FILE INTEGRITY ERROR
IT21123 All Platforms DSMADMC TABULAR OUTPUT IS NOT PROPERLY ALIGNED WITHIN COLUMNS AND HYPHENATION IS INCORRECT
IT21089 Linux x86 “ANS1592E FAILED TO INITIALIZE SSL PROTOCOL” USING 8.1.0.2 API CLIENT FOR X86_64 LINUX
IT21059 All Unix/Linux A NON-ROOT USER PERFORMING A BACKUP/ARCHIVE OPERATION ON UNIX PLATFORM, CONFIGURED FOR AUTOMATED FAILOVER, RECEIVES ANS1035S
IT21056 All Windows DUPLICATE ANS1899I MESSAGES ARE ISSUED DURING SYSTEM STATE BACKUP
IT21052 Linux zSeries INSTALL OF THE 7.1.4 AND 7.1.6 CLIENTS FOR RHEL 5 ON ZLINUX FAILS LIBRARY DEPENDENCIES.
IT21045 All Windows DSMAGENT CRASHES WHEN PERFORMING VSS BACKUP AGAINST A HIGH NUMBER OF MICROSOFT SQL DATABASE
IT20999 All Linux
All Windows
Solaris
PROCESSOR MODEL IS INCORRECTLY REPORTED BY THE CLIENT FOR INTEL CPUS WITH A VERSION NUMBER
IT20371 All Platforms ABSTRACT: IBM SPECTRUM PROTECT CLIENT MAY HANG DURING PROCESS MGMTCLASS
IT20103 All Windows CLIENT AUTO DEPLOY FAILS DURING THE VC++ PORTION OF THE INSTALLATION
IT19623 All Windows “UNABLE TO OPEN FILE ‘DSMMSINFO.TXT'” MESSAGE WHEN RUNNING “DSMC  Q SYSTEMINFO” ON A “WINDOWS 2016 SERVER CORE”
IT17338 All Platforms CLIENT STOPS A RESTORE OPERATION IF AN “ANS1154E” ERROR IS
ENCOUNTERED IN CLASSIC RESTORE MODE.

written by Bosse

Feb 23

Modified Instructions for Complete Restores of Windows Systems with the TSM Client: Bare Metal Restore (BMR), System State Restore, Windows System Object Restore

Windows VSS Comments Off on Modified Instructions for Complete Restores of Windows Systems with the TSM Client: Bare Metal Restore (BMR), System State Restore, Windows System Object Restore

Technote (troubleshooting)

Problem(Abstract)

The following article provides guidance for complete system restores of Windows 2003, 2003 R2, Vista, 2008, 2008 R2, and Windows 7 systems using the TSM client and system state restore. Systems running Microsoft Windows 8, Windows 2012, and Windows 2012 R2 are also supported for EFI systems. The procedure applies to the restore technique where you are restoring over a running operating system. These procedures should only be followed after less severe recovery techniques such as Microsoft System Restore have been attempted.

Cause

Note: For Windows 2008, 2008 R2, Vista, Windows 7, 2012, 2012 R2, and Windows 8 there is a Automated System Recovery (ASR) support capability available with 6.3.2 and newer client levels. The ASR restore approach is preferred over the approach covered in this document for non-EFI systems. More information on the ASR approach is available via the following links:

A number of fixes have recently been introduced in the TSM client which impact the success of complete system restores.

  • The following or newer client levels for the releases in service are recommended:
    • 6.3.2.4, 6.4.3.x or 7.1.x when using TSM server 6.3.x

Note that not all Windows operating systems discussed below are supported on all TSM client releases currently in service. See the following link for supported levels: Windows Client Requirements

Resolving the problem

Preparation:
In order to perform a complete system restore, a complete backup is needed. The backup must include a complete backup of the system drive, and a backup of the system state. You may also need to backup additional drives besides the system drive if they exist on your system. Generally, this should include any drive containing critical user data or application program files. The following points should be considered:

  1. A scheduled backup of the default all-local domain will include both the system drive and system state.
  2. Care must be taken not to exclude required application files from the system drive backup. The sample options file in the config directory lists suggested include/exclude rules which are known not to interfere with system recovery. The sample options files can be found in the normal installation path. For example, c:\program files\tivoli\tsm\config\dsm.smp.
  3. A number of files on the system drive are automatically excluded from backup based on operating system controls. The “query inclexcl” command can be used to view the rules which will affect which files are automatically excluded during backup. Files which are under Windows system file protection can only be backed up as part of the system and boot files component of system state. They are automatically excluded from normal system drive backup processing.
  4. System recovery time can be greatly reduced by maintaining a volume-level image of the base Windows installation.

Restore Procedure:
The following restore procedure is required when you are restoring your complete operating system over a running operating system. These procedures are not required if you are restoring with Automated System Recovery (ASR). See note #5 for additional details related to ASR.

Preparation steps:

  1. It is strongly recommended that you restore to identical hardware to which the backup was taken from. In virtualized environments there often subtle differences between the original system and the restore target which can cause problems. Here are some common ones to avoid:
    1. Different code levels for the hypervisor.
    2. Different virtual hardware levels.
    3. Different virtual devices assigned to the virtual machine. For example, a different type of virtual disk controller or network adapters, or changes in the number of these devices.
  2. In order to restore, you need a base operating system running with the TSM client installed, and connectivity to the TSM server.
  3. Windows must be installed in the same directory at which it was installed at the time of backup (c:\Windows for example.) The system drive file system must be formatted in the same file system type that existed at the time of backup. For systems previously upgraded from Windows NT4.0, you may have difficulty installing the base OS in the original directory. See notes below for more information.
  4. The system name must be set to match the system name at the time of backup. Unless this is set, the system state component cannot be restored.
  5. If you are recovering a domain controller, do not promote the base operating system to a domain controller prior to running the restore.
  6. Apply the same Windows service pack to the base operating system which was installed at the time of backup. In addition, on Windows 2003 servers, the VSS hotfixes identified in KB940349 and KB934016 need to be installed following any service pack installations.
  7. Partition and format any additional volumes required for recovering the systemstate or additional drives. For example, if you are restoring a domain controller with NTDS files stored on a drive other than C:, you will need to create the additional drives before proceeding with the restore. The new drives need to be of equal or greater capacity, formatted with the same file system type, and mapped to the same drive letter or directory that was used at the time of backup.
  8. Ensure that the Windows default administrative shares exist for all of the drives to be restored. Issue the following Windows command to check this:
    > net share
  9. For restores from a TSM server, you will need a working network connection. Even with local backupset restores, problems have been encountered resolving UNC names on systems where there are no active network connections, so you should have at least one active network connection before attempting the restore.
  10. For Windows 2003 domain controller restores, the option FRSPRIMARYRESTORE can be set to YES prior to performing the systemstate restore. Recovering the first domain controller in a domain is one example where using the option to force an authoritative FRS restore is required. An authoritative SYSVOL restore is not possible when using ASR.
    Note: Performing an authoritative SYSVOL restore is not supported for Windows versions newer than Windows 2003. See APAR IC79919 for additional information.
  11. For Windows 7 and Windows 2008 R2 systems, use regedit to confirm that the registry subkey HKEY_LOCAL_MACHINE->COMPONENTS exists prior to restoring the system state. See APAR IC65386 for more details.

Restore steps (see the additional information section for notes on using the Graphical Users Interfaces):

  1. Restore the system drive. Ignore the request to reboot at the end of the restore and proceed to the next step! Repeat this restore step for all other drives that exist on your system.> dsmc restore c:\* -sub=yes -rep=all
  2. Restore the system state. On Windows 2003, the option frsprimaryrestore yes can be added to the client option file prior to running the following commands if an authoritative sysvol restore for a domain controller is required. If you are restoring a Windows 2008 server running failover cluster services you may need to add the keyword bootable to the restore systemstate command. See below for more information on restoring clustered systems.> dsmc restore systemstate
  3. Reboot

The following example shows a complete sequence of commands for restoring a Windows system using environment variables to avoid fixed drive letters and paths.

> dsmc restore %systemdrive%\* -sub=yes -rep=all
> dsmc restore systemstate

Additional Information
1. There are four files under system file protection which cannot be restored due to a Microsoft Windows limitation with replace on reboot. These files are: ntdll.dll, smss.exe, dtcsetup.exe, and ctl3dv2.dll. If you are restoring over a base Windows image which contains down-level versions of these files versus those contained in your backup image, you may experience system problems following the restore including:
2. When is it necessary to use “Directory Services Restore Mode” (DSRM)? The normal complete system recovery procedure for a domain controller does not require DSRM. The use of DSRM is only required when a server is already active as a domain controller, and recovery of NTDS is prevented when the Active directory services are active. When performing a complete system recovery, do not promote your newly installed base OS to a domain controller prior to performing the restore. The system should automatically become a functioning domain controller as a result of the restore. Alternatively, DSRM is required if your server is already operating as a domain controller, and restore of the active directory is needed to resolve an issue such as accidental deletion of active directory objects. In this scenario, booting to DSRM prevents the NTDS services from starting, allowing a TSM restore of system state including NTDS.

3. Following a domain controller recovery, you may see errors in the Windows event viewer for file replication services which indicate that the server is prevented from becoming a domain controller due to problems with the SYSVOL share. In normal cases, this message will eventually be followed by another message indicating that SYSVOL has been shared and is no longer preventing the server from becoming a domain controller. If this does not happen, manual repairs to the SYSVOL structure may be required. In many cases, the SYSVOL directory structure can be repaired, and FRS will replicate in the correct contents of the SYSVOL. Microsoft article KB315457 provides details on how to rebuild the SYSVOL tree including the junction points which are required before a system can be returned to a domain controller.

http://support.microsoft.com/kb/315457

4. In some situations, special steps are required to force Windows to install into a non-default directory when installing your base operating system. For example, a system which is upgraded from Windows 2000 to Windows 2003 will maintain the operating system files in C:\WINNT. When installing a base Windows 2003 operating system for recovery purposes, Windows will force the installation into the C:\WINDOWS directory by default. A successful restore will not be possible unless the base Windows 2003 operating is forced to install into the C:\WINNT directory instead of C:\WINDOWS. Microsoft article KB235478 provides instructions on how to force Windows to install into a non-default directory.

http://support.microsoft.com/kb/235478

5. An additional recovery feature known as Automated System Recovery (ASR) is available with the TSM client. With ASR you will not be required to perform many of the steps described in this document, including the pre-restore of the SFP catalogs. The TSM restores performed during ASR occur while Windows system file protection is not running. See the links at the beginning of this document for links to additional information on ASR.

6. The procedures listed in this article are not recommended for recovering an operating system to dissimilar hardware. However, in situations where there is no alternative, two methods have provided limited success repairing boot problems following restores to dissimilar hardware. The first technique involves retaining a copy of critical hardware specific files after installing the base operating system and copying these files back after performing the restore, but before rebooting the system. See the following Microsoft article for more discussion on this technique:

http://support.microsoft.com/kb/Q249694

The second technique uses the Windows installation CD repair facility to repair the restored operating system which is failing to boot. This procedure is some times referred to as “upgrade in-place” or “repair installation.” See the following Microsoft articles for more information on this technique:

http://support.microsoft.com/kb/315341

http://support.microsoft.com/kb/816579

7. Tips for recovering NTDS or SYSVOL components to a new location without restoring the entire systemstate.

In certain circumstances, you may desire to restore NTDS or SYSVOL files for a domain controller to an alternate location, and then use Microsoft utilities to recover from these restored files. Tivoli does not provide support for these recovery techniques, but provides these commands for users who have a requirement for recovery of NTDS and/or SYSVOL without a complete systemstate recovery, and have knowledge of the procedures necessary for recovering from the files which have been restored to an alternate location.

WARNING: these restore commands may create junctions in the restore target directory that point back to critical directories on the running system. Do not delete the temporary restore destination using the Windows explorer interface since it is known to also delete the contents at the target of junctions. Instead, we recommend using the Windows rmdir command to remove the temporary directory.

rest "{SERV1\SystemState\NULL\System State\SystemState}\\serv1\e$|\ntds\*" e:\ntdsrest\ -sub=y

Your pathnames for where NTDS and SYSVOL may vary requiring adjustment to these commands. If you are having trouble locating the correct path, you can search for the files with a command like the following:dsmc q b "{SERV1\SystemState\NULL\System State\SystemState}\ntds.dit" -sub=y

8. A systemstate restore may fail with the message ANS1056E Share/network path cannot be resolved. This failure may be caused by the absence of the default administrative shares for drives which need to be accessed during the systemstate restore. You can determine if you have this problem by issuing the Windows command net share to ensure the shares are listed for all drives. In most cases rebooting will restore the missing shares. Alternatively, stopping and starting the Windows server service may also restore these shares.

9. A systemstate restore may fail with the error message ANS1949E Microsoft volume shadow copy snapshot initialization failed. See the following technote for a possible solution to this problem:
http://www.ibm.com/support/docview.wss?&uid=swg21385864

10. Restores of Windows 2008 systems running failover cluster services require a modification to the restore commands described above. Without this modification, the restore systemstate command may fail with the
error:
ANS5211E The cluster service is offline. The cluster service must be online to perform an authoritative cluster database restore operation.

This error is encountered because the clusters services are not running as part of a base Windows operating system. In most recovery cases, other nodes in the cluster are still running, so there is no need to restore the cluster database since it will automatically copy back from the other nodes. In rarer cases, an authoritative restore of the cluster database is needed when other cluster nodes are not present or the cluster database has been corrupted on all nodes.

The non-authoritative restore sequence uses the bootable subkey to avoid ANS5211E:

dsmc restore c:\* -sub=yes -rep=all
dsmc restore systemstate bootable
reboot

Authoritative restore sequence :

dsmc restore c:\* -sub=yes -rep=all
dsmc restore systemstate bootable
reboot
dsmc restore systemstate clusterdb

11. The restore procedures described in this document can also be performed using the graphical user interface with the exception of the steps for performing a pre-restore of the Windows system file protection catalogs.

To restore the system drive:
a) Click “Restore”
b) Expand “File Level”
c) Select the entire drive representing the system drive, for example, \\tsmbldx861\c$ (C:)

d) Click the “Options” button, and select the options for files which already exist “Replace” and “Replace files even if read-only/locked”, then click OK

e) Click “Restore”, and select “Original location”, then click “Restore” again

f) Ignore the request to reboot at the completion of this restore and proceed to the systemstate restore.

To restore the system state:
a) Click “Restore”
b) Select the object “SystemState”, and click “Restore”

12. The following are links to additional information on TSM topics useful for Windows system recovery.

Best practices instructions for a new ASR system recovery approach:

White paper titled “Tivoli Storage Manager Recovery Techniques Using Windows Preinstallation Environment (Windows PE)”
http://www.ibm.com/support/docview.wss?uid=swg27005028

Technote explaining restore location of the Windows event log files for Windows 2003
http://www.ibm.com/support/docview.wss?uid=swg21223228

written by Bosse

Oct 22

System State Backups May Fail On Certain Windows Operating Systems

Windows VSS Comments Off on System State Backups May Fail On Certain Windows Operating Systems

Problem(Abstract)

TSM Client system state backups sometimes fail on Windows 2008 R2, Windows 7, Windows 8, or Windows 2012 operating systems. These backups are performed using Volume Shadow Copy Service, which may fail during this operation. During the operating system installation, a 100 MB System Reserved Partition is typically created, however the VSS operation will fail if this volume is not online. This leads to the system state backup failure.

Symptom

When this problem is encountered the following will appear after the system state backup is invoked:

Backup System State using shadow copy…
ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

System State Backup finished with failures.

ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

After the failure, vssadmin reports that the ASR writer has timed out.

********

In addition to the above error, the error log will contain entries similar to the following:

05/13/2011 11:18:39 ANS5250E An unexpected error was encountered.
TSM function name : BackupComplete()
TSM function : ‘BackupComplete() failed with error VSS_E_BAD_STATE. -2147212543’
TSM return code : -2147212543
TSM file : asrutil.cpp (2416)
05/13/2011 11:18:39 ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

05/13/2011 11:18:40 ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

********

In addition to the errors listed above, the Windows Event Viewer will contain:

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}.
Routine details EndPrepareSnapshots({4fe8f016-cc83-4541-acb1-106e36caba72}) [hr = 0x80070015, The device is not ready.].

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

 

Cause

TSM uses VSS to back up system state, but VSS runs into errors if the 100 MB System Reserved Partition is offline.

One cause for the 100 MB System Reserved Partition to be offline is having the Windows automount capability disabled. There are circumstances where the automount capability must be disabled, but it has been observed that this can result in the partition being offline after the reboot.

 

Environment

Windows Server 2008 R2

Windows 7
Windows Server 2012
Windows 8

 

Diagnosing the problem

To determine if this problem has been encountered during a TSM Client system state backup, perform the following:

  1. Confirm that the operating system is Windows 2008 R2, Windows 7, Windows 8, or Windows 2012.
  2. Check for the errors listed in the Symptoms section above.
  3. Run ‘DISKPART LIST VOLUME’ from a Command Prompt to determine if there is a 100 MB volume that is offline.

Resolving the problem

As mentioned in the Abstract section, this problem occurs because the 100 MB System Reserved Partition is offline. This issue can be resolved by enabling automount and rebooting, which will bring this volume online and keep it online through subsequent reboots. Enabling automount can be done by opening a Command Prompt window and invoking DISKPART:

DISKPART -> automount enable -> exit

Before making this change to enable automount, care should be taken to determine that it was not disabled intentionally. For example, systems acting as VMware vStorage backup servers are required to have automount disabled. If automount needs to stay disabled, a work-around would be to go into DISKPART and set the 100 MB volume online:

DISKPART -> list volume -> select volume 1 -> online volume -> exit

The volume selected should be the 100 MB volume. In the above example it was assumed that ‘list volume’ showed the 100 MB volume to be volume 1. It is important to note that with automount disabled, this will only keep the volume online until the next system reboot.

written by Bosse

Mar 05

Iscsilog.dll is not included in the system state backup files on a Windows Server 2008 R2 SP1-based computer

Windows 2008 Comments Off on Iscsilog.dll is not included in the system state backup files on a Windows Server 2008 R2 SP1-based computer

Error description

  • The TSM client may issue the following warning message during a
    backup of the boot drive (usually C:).
    
      ANS1417W Protected system state file
      'C:\Windows\System32\iscsilog.dll' is backed up
      to the drive file space, not system state file space.
    
    This specific file is protected by Windows Resource Protection
    (WRP) but is not enumerated for backup by the Windows VSS System
    Writer. Since files protected by WRP should be part of the VSS
    System Writer, which is part of system state, TSM issues the
    message.
    
    The problem is introduced when Service Pack 1 (SP1) is applied
    to Windows 2008 R2. The problem is detected by the TSM backup-
    archive client as a result of the system state integrity
    verification enhancement made for APAR IC72446.
    
    Initial Impact: Low
    Platform Affected:
    Windows 2008 R2 Sp1

Fix

http://support.microsoft.com/kb/2680097/en-US

 

written by Bosse

Nov 14

Changing the client GUID on Windows

Windows 2003, Windows 2008 Comments Off on Changing the client GUID on Windows

Question

How do I change the GUID on a Tivoli Storage Manager Backup Archive client?

Answer

GUID is an acronym for Globally Unique IDentifier. The GUIDs are intended to help uniquely identify a particular machine (for reporting purposes), regardless of how many different node names are used on the machine, or which network adapter on the machine is used to connect to the Tivoli Storage Manager server.

In Windows this GUID is stored in the registry under the following location.
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Guid
If it is necessary to remove an old GUID and create a new one the following procedure can be followed.
NOTE: This procedure will require you to modify your Windows Registry. Before doing anything, make sure to backup your registry. This is so you can restore your registry should you accidentally remove something you should not have.

  1. Backup your Windows Registry
  2. Close all client GUI windows and stop all client services
  3. Open the registry and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Guid
  4. Delete/rename the entire GUID folder
  5. Start the client again. This should recreate the GUID folder and a new GUID key

 

written by Bosse

Sep 28

Automated System Recovery backup fails with ANS1468E

Windows VSS Comments Off on Automated System Recovery backup fails with ANS1468E

ASR backups fail stating no files will be backed up.

Symptom

The following is reported in the error log.

ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up.

Resolving the problem

The following Microsoft hotfixes should be applied to resolve this. Please contact Microsoft for additional information on these fixes.

http://support.microsoft.com/kb/934016
http://support.microsoft.com/kb/951568

written by Bosse

Dec 02

.VSS System State restore fails with ANS5250E error 4346(dec) 0x000010fa

Windows VSS Comments Off on .VSS System State restore fails with ANS5250E error 4346(dec) 0x000010fa

Problem(Abstract)

On a Windows 2003 server VSS system state restores may fail if the required Windows VSS patches have not been applied.

Symptom

VSS system state restores fail with the following error logged in the dsmerror.log:

ANS5250E An unexpected error was encountered.
TSM function name : vssRequestor::prepareForRestore
TSM function : QueryInterface(IID_IVssBackupComponentsEx) returned
unknown error 4346(dec) 0x000010fa
TSM return code : 4346
TSM file : vssreq.cpp (7837)

ANS5250E An unexpected error was encountered.
TSM function name : vssPreRestore
TSM function : prepareForRestore() returned ‘4346’
TSM return code : 4346
TSM file : vssrest.cpp (1162)

 

Resolving the problem

In order to perform Systemstate operations on Windows 2003, you first have to apply Windows 2003 SP 2 and the following Windows VSS hotfixes:
http://support.microsoft.com/kb/940349

http://support.microsoft.com/kb/934016

Note that this hotfix is documented as required in order to perform systemstate backup and restore:
http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&uid=swg21197133&loc=en_US&cs=utf-8&lang=en

*NOTES on Windows 2003 requirements:

  • If you plan to back up System State or use Open File Support with the VSS snapshot provider, you must install Service Pack 1 (SP1) or higher Service Pack level, and you must install Microsoft hotfix roll-up packages 934016 (for COM+) and 940349 (for VSS). The hotfix roll-up packages can be found at Microsoft’s support pagehttp://support.microsoft.com.
  • If you plan to use an x64-bit machine, apply the Microsoft hotfix for knowledge base article 908675. The hotfix is included in Service Pack 2 for Microsoft Windows 2003. In case you cannot apply the entire Service Pack this particular hotfix can be provided by Microsoft upon request. See details at http://support.microsoft.com/kb/908675.

written by Bosse

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

Nov 16

Troubleshooting/Testing VSS using DiskShadow on Windows 2008

Windows VSS Comments Off on Troubleshooting/Testing VSS using DiskShadow on Windows 2008
Problem(Abstract)
When diagnosing problems with SystemState backup or Open File Support/Online Image using VSS, it is sometimes useful to test the VSS portion by itself..
 
 
Resolving the problem
With Windows 2008, Microsoft included a tool called DiskShadow.exe that can be used to take snapshots of the system and much more. For the purpose of this technote, we will be limited to performing tests similar to what happens when Tivoli Storage Manager (TSM) performs a SystemState backup, Open File Support backup or an Online Image backup.Obtain Writer Information:When troubleshooting a problem, sometimes it is useful to obtain information about the writers, their status and the metadata.You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadow.out

From the diskshadow prompt, issue the following commands:

reset
list writers
list writers status
list writers metadata
list writers detailled
list providers
exit

The output of all the above commands will be found in c:\diskshadow.out. The output can use useful to see the list of files which are reported by the VSS writers to be included and excluded by the backup.

Test a snapshot of SystemState

When dealing with SystemState backup failures, sometimes the problem is with TSM, sometimes on Windows either with VSS itself or with one of its writers. Testing outside TSM helps determine if the problem is within TSM or outside.

You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadowsys.out

From the diskshadow prompt, issue the following commands:

reset
set verbose on
set option differential
set context volatile
add volume c: (if the system is on more than one disk, specify them separated by a space)
create
exit

The output of all the above commands will be found in c:\diskshadowsys.out. Review this file for errors. Any failure during the create phase indicate a problem either with VSS or one of the writers which should be pursued with Microsoft.

Test a snapshot of a disk for Open File Support or Online Image with snapshot provider to VSS

When dealing with a problem doing an open file support backup or online image backup when VSS is used as the snapshot provider, it is sometimes useful to isolate if the problem is within or outside of TSM. This will perform a snapshot of the disk.

You can start diskshadow and logging all outputs to a file by starting a Command Prompt and launching this command:
diskshadow /l c:\diskshadowsnap.out

From the diskshadow prompt, issue the following commands:

reset
set verbose on
set option differential
set context volatile nowriters
add volume c: (replace c: with the drive letter the snapshot is having problems.)
create
exit

The output of all the above commands will be found in c:\diskshadowsnap.out. Review this file for errors. Any failure during the create phase indicate a problem either with VSS or possibly the disk.

 
 
Related information
DiskShadow Information

written by Bosse

Oct 07

Windows 2003 Volume Shadow Copy Service (VSS) Hotfixes for Systemstate Backup

Windows VSS Comments Off on Windows 2003 Volume Shadow Copy Service (VSS) Hotfixes for Systemstate Backup

Problem(Abstract)

TSM client backups of Windows 2003 system state fail with varying VSS errors

Cause

Microsoft VSS failures

Resolving the problem

This list represents fixes available from Microsoft, listed in historical order, for Windows 2003 systemstate backup problems experienced by 3rd party backup vendors, including Tivoli Storage Manager (TSM).

KB # in bold represents the most current fix that is available. All the below VSS fixes should be reviewed for applicability and requested from Microsoft support.

    KBASE# FIX #
    ————–
    826936 139876
    833167 158865
    867686 188827 (No web link)
    887827 unknown (No web link)

All of the above fixes are rolled into Windows 2003 SP1. Microsoft KBase# 824721 documents the list of fixes included in SP1.

Subsequent to Win2k3 SP1, Microsoft has provided VSS Post SP1 fix packages:

    KBASE# FIX #
    ————–
    891957 unknown
    903234 unknown
    913648 unknown Note: 903234 is a prerequisite for the above patch and replaces 891957.
    915331 unknown
    923628 unknown

All of the above fixes are rolled into Windows 2003 SP2. Microsoft KBase# 914962 documents the list of fixes included in SP2.

Subsequent to Win2k3 SP2, Microsoft has provided VSS Post SP2 fix packages:

    KBASE# FIX #
    ————–
    940349 unknown
    934016 unknown Note: This is a COM+ rollup package required for VSS

Additional KB information from Microsoft:

    951568 – VSS-based backup operations may fail if VSS tracing is enabled on a Windows Server 2003-based computer that has hotfix 940349 applied.

written by Bosse