mccleld
ADSM.ORG Senior Member
Hello Team,
An informational post here to help anybody else coming up against this in the future - it is something I've encountered a couple of times now when attempting to install the TSM FastBack client onto a Windows system.
In a nutshell, what looks like a successful client installation isn't, and backups fail as a result with a relatively obscure error. What should be a simple pre-req check in the FastBack installation package hasn't been implemented or isn't currently alerting. In this post, I discuss the error scenario, how to identify it, and a couple of ways to resolve it.
To all intents and purposes a TSM FastBack Client installation appears to complete successfully - the installation asks for a reboot at the end and, when restarted, the client connects successfully to the FastBack Server which can correctly identify its volumes and schedule a backup. Textbook stuff.
However, any attempts to backup of one of the client volumes appears to stall and ultimately fail - the Server's Snapshot Monitor reports an Aborted backup due to:
In the Application Event Log on the FastBack Client side we see the following alert:
At this point, the key thing to verify is whether the XR_VSS service is correctly installed - you can check for its existence in the Services applet. If it's not showing here, then it's likely that it hasn't been able to register properly. The main cause that I've seen is that the Distributed Transaction Coordinator service isn't running and/or is disabled - commonly this gets locked down in corporate standard OS builds. Simple re-enable this service and re-install the TSM FastBack client or manually register the service with the following command:
The XR_VSS service should now appear in the client's Services listing and subsequent backup attempts should be successful (or at least not fail because of this error...).
HTH,
__________
David Mc
London, UK
An informational post here to help anybody else coming up against this in the future - it is something I've encountered a couple of times now when attempting to install the TSM FastBack client onto a Windows system.
In a nutshell, what looks like a successful client installation isn't, and backups fail as a result with a relatively obscure error. What should be a simple pre-req check in the FastBack installation package hasn't been implemented or isn't currently alerting. In this post, I discuss the error scenario, how to identify it, and a couple of ways to resolve it.
To all intents and purposes a TSM FastBack Client installation appears to complete successfully - the installation asks for a reboot at the end and, when restarted, the client connects successfully to the FastBack Server which can correctly identify its volumes and schedule a backup. Textbook stuff.
However, any attempts to backup of one of the client volumes appears to stall and ultimately fail - the Server's Snapshot Monitor reports an Aborted backup due to:
In the Application Event Log on the FastBack Client side we see the following alert:
At this point, the key thing to verify is whether the XR_VSS service is correctly installed - you can check for its existence in the Services applet. If it's not showing here, then it's likely that it hasn't been able to register properly. The main cause that I've seen is that the Distributed Transaction Coordinator service isn't running and/or is disabled - commonly this gets locked down in corporate standard OS builds. Simple re-enable this service and re-install the TSM FastBack client or manually register the service with the following command:
Code:
C:\PROGRA~1\Tivoli\TSM\FastBack\client\REGIST~1.VBS -register XR_VSS C:\PROGRA~1\Tivoli\TSM\FastBack\client\FASTBA~1.DLL FastBack_VSSThe XR_VSS service should now appear in the client's Services listing and subsequent backup attempts should be successful (or at least not fail because of this error...).
HTH,
__________
David Mc
London, UK
