Article ID: 235469
Article Last Modified on 10/30/2006
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q235469
IN THIS TASK
SUMMARY
This article describes how to restore the Remote Storage Service (RSS) database. This may be useful if:
- It is necessary to completely re-install Windows 2000. After you do so, you must restore the RSS database files before you can recall files from off-line storage.
- The RSS database is damaged.
When you try to obtain access to a file in off-line storage when the RSS service is not installed or able to start, you may receive the following error message:
To restore the RSS database, use the appropriate method:
back to the top
Restore the RSS Database after Completely Re-installing Windows 2000
This procedure assumes that you completely reinstalled Windows 2000, but volumes that contain RSS managed data are still intact.
- Reinstall Windows 2000 to the same drive and folder as the previous failed installation. During Setup, do not add the Remote Storage Service component. If this component was added accidentally or automatically, please remove it and restart your computer.
Note that this is usually C:\Winnt, but if you installed Windows 2000 to a different folder, please see the following article in the Microsoft Knowledge Base:235478 Recover from Failed System Drive with Non-Default %SystemRoot% Folder
- Restore the RSS and RSM (Removable Storage Management) databases. Each time RSS migrates data to tape, these databases are automatically backed up to the media containing the migrated data. It is recommended that the databases on this media be used since they will contain the most recent copy of the RSS database. Use the following procedure to restore the databases:
NOTE: For this procedure to work, Windows 2000 must have been re-installed into the same folder and drive that was previously used. If Windows 2000 is installed to a different folder, the restore operation is not able to return the databases to their original location.- Verify that your tape or storage device is on line and functioning. Start the Computer Management snap-in by right-clicking My Computer, clicking Manage, double-click the Storage branch to expand it, and then click Removable Storage.
- Open the Media pools and look in the Import pool. Locate the most recent tape used to store the RSS migrated files. The default name for RSS media is "RS" appended with the machine name and an incremental number (for example, "RS-MachineX-1"). The media with the highest number contains the most recent backup of the databases. If the RSS media spans two or more tapes, catalog these tapes using Backup (temporarily move these tapes to the NTBackup Media pool) and check the dates of the Remote Storage databases and use the one with the latest date.
- Move this media to the NTbackup Media pool. If the pool does not exist, start Windows 2000 backup (NTbackup.exe) and it is created automatically.
- Use Windows 2000 backup (NTbackup.exe) to catalog the tape to find the latest copy of the RSM and RSS databases. These databases are stored on tape in the %windir%\system32\Ntmsdata and %windir%\system32\RemoteStorage folders. Check the dates of the files to determine the most up-to-date copies.
- Select the most current (NtmsData and RemoteStorage) folders to be restored, make sure that all files below these sub-folders are also selected.
- In the Restore files to box, click alternate location, and then click the drive that contains the Windows folder.
NOTE: This step is very important, and if not performed, the databases are restored to the "RSS Managed Volume" instead of the operating system partition. - Click Start Restore, and then click Advanced. Click Restore Removable Storage Database, click OK, and then click OK.
- After this process finishes, restart your computer.
- Start the Removable Storage Manager Snap-in and verify that the databases have been restored. You can do so by looking to see if all of your media pools are present and all the media are in their appropriate pools.
- Use the Add/Remove Programs tool to add the Remote Storage Server component.
- After your computer restarts, log on, and then using the Computer Management Snap-in, expand the Services And Applications branch, and then click Services. Verify that the following services are stopped:
- Remote Storage Engine
- Remote Storage File
- Remote Storage Media
- At a command prompt, change to the %systemroot%\system32\RemoteStorage\engdb folder, and then verify that this folder is empty by moving the files to another folder.
- Use the Rstore.exe tool (a utility that is installed when the Remote Storage service is installed) to run the following command from the engdb folder:
Rstore %systemroot%\system32\RemoteStorage\engdb.bak
- Using the Computer Management Snap-in, expand the Services And Applications branch, and then click Services. Locate and start the following services:
- Remote Storage Engine
- Remote Storage File
- Remote Storage Media
- Open the Remote Storage snap-in and verify that your managed volumes appear and all settings are correct. You may also want to test by recalling a few of the migrated files before putting the server back into production.
Restore a Damaged RSS Database
To restore a damaged RSS database: NOTE: This procedure assumes the Removable Storage Manager (RSM) database is intact and you are only interested in restoring the RSS database. For detailed information about restoring the RSM database, please see the following article in the Microsoft Knowledge Base:
235032 Problems with a Damaged Removable Storage Manager Database
- Using the Computer Management Snap-in, expand the Services And Applications branch, and then click Services. Verify that the following services are stopped:
- Remote Storage Engine
- Remote Storage File
- Remote Storage Media
- Using Removable Storage Manager, open the Media pools and look in the Remote Storage pool. Locate the most recent tape used to store the RSS migrated files. (The default name for RSS media is "RS" appended with the machine name and an incremental number, for example, RS-MachineX-1. The media with the highest number contains the most recent backup of the databases.)
- Move this media to the NTbackup media pool. If the pool does not exist, start Windows 2000 Backup (NTbackup.exe).
- Using Windows 2000 Backup, catalog the tape to find the latest copy of the RSS database. This database is kept on tape in the %windir%\system32\RemoteStorage folder. Check the dates of the files to find the most up-to-date copies.
If the RSS media spans two or more tapes, catalog these tapes using Backup (temporarly move these tapes to the NTBackup Media pool) and check the dates of the Remote storage databases and use the one with the latest date. - Select the most current RemoteStorage folder to be restored, and make sure that all files under this sub-folder are also selected.
- In the Restore files to box, click alternate location, and then click the drive that contains the Windows folder.
NOTE: This step is very important, and if not performed, the databases are restored to the "RSS Managed Volume" instead of the operating system partition. - After the restoration finishes, change to the following folder from a command prompt:
Make sure this folder is empty by moving any existing files to another folder.
%systemroot%\system32\RemoteStorage\engdb
- Use the Rstore.exe tool (a utility that is installed when the Remote Storage service is installed) to run the following command from the engdb folder:
Rstore %systemroot%\system32\RemoteStorage\engdb.bak
- After this command finishes, place the Remote Storage media used during the NTbackup restoration of the databases back in the RemoteStorage media pool.
- Using the Computer Management Snap-in, expand the Services And Applications branch, and then click Services. Locate and start the following services:
- Remote Storage Engine
- Remote Storage File
- Remote Storage Media
- Open the Remote Storage snap-in and verify that your managed volumes appear and all settings are correct. You may also want to test by recalling a few of the migrated files before putting the server back into production.
Keywords: kbhowto kbhowtomaster kbtool kbui KB235469
