Main.RSMServiceHasNotStarted History
Hide minor edits - Show changes to output
February 02, 2005, at 01:53 AM
by
Changed line 24 from:
Click OK. Now whenever your backup runs, the RSM service will be started automatically, so to:
Click OK. Now whenever your backup runs, the RSM service will be started automatically, so it should be running by the time BackupAssist tries to perform a backup.February 02, 2005, at 01:50 AM
by
Changed lines 1-28 from:
Describe RSMServiceHasNotStarted here.to:
!RSM Service Has Not Started
!!Example:
[[<<]] @@[=BackupAssist warning #15000=]@@
[[<<]] @@[=Description: Unable to enumerate libraries=]@@
[[<<]] @@[=Error number: 21=]@@
[[<<]] @@[=Error description: RSM service has not started. The application should wait and retry.=]@@
[[<<]] @@[=Error source: BARSM=]@@
!!Causes and Resolution:
Generally on Windows XP and 2003, the RSM service starts whenever the tape drive is accessed. However, for some tape drives and systems, it can be slow to start, meaning that the tape drive won't respond to BackupAssist and BackupAssist may think that the tape drive is empty or that it cannot communicate with the tape drive.
!!Resolution:
One way of working around this problem is to start the RSM service manually before each backup.
To do this, go into the Advanced tab, and click the link at the top to modify your pre- and post-backup scripts. Then in your pre-backup script, type the following:
@@[=net start ntmssvc=]@@
Click OK. Now whenever your backup runs, the RSM service will be started automatically, so