You need to move vRanger to a different machine.
Follow the steps below:
Install Requirements
Microsoft SQL Server Management Studio Express
http://www.microsoft.com/download/en/details.aspx?id=8961
vRanger Latest full installer
https://support.quest.com/Search/SearchDownloads.aspx?ActiveTab=1
vRanger .asc license
https://support.quest.com/LicenseKey.aspx
Install Setup
1. Install vRanger on your new server with all the default settings including the SQL express bundled with the product
2. Install the Microsoft SQL Server Management Studio Express on the new server
3. Install Microsoft SQL Server Management Studio Express on your old vRanger server
Backup of old vRanger Database
See the Microsoft article for the instruction on backing up your database.
http://msdn.microsoft.com/en-us/library/ms187510.aspx
1. Backup your vRangerPro database
Restore of old vRanger Database
See the Microsoft article for the instruction on restoring your database.
http://msdn.microsoft.com/en-us/library/ms188312.aspx
1. Restore the old vRangerPro Database over the new vRangerPro Database using the Option to Overwrite Existing database
,
Reconnect to restored vRanger database
1. Go to start, programs, Quest Software, vRanger Backup & Replication, vRanger Database
2. Click Next
3. Select Install/Upgrade on an existing SQL Server 2005/2008
4. Use Server Authentication of Windows (unless you are installing in enterprise SQL)
5. Click Next
6. Select Verify
7. Ok
8. Click Next
9. Click Next
10. Click Yes to proceed
11. Click Automatic Setup
12. Click Next
13. Click Finish
Verify Services, start vRanger, and Reconfigure
1. Stop the vRanger services
a. Stop vRanger API Service first
b. Stop vRanger FLR Service second
c. Stop vRanger Service
2. Start the vRanger services third
a. Start vRanger Service first
b. Start vRanger FLR Service second
c. Start vRanger API Service third
3. Start vRanger
4. Make sure the vRanger configuration is back
5. Reimport your license file if needed
6. If the storage that will be used for the repository has changed update your repository
7. If the repository was changed the jobs needs to modified to use the new repository
