How to Migrate to a New Server(Vision)
Step by Step guide
This article describes how to move a standard RTA database from an existing server to a new server. If you are wanting to create a test environment of RTA, please refer to the article titled "How to Create a Test System(Vision)".
*Note for SQL and Oracle versions of the software, this article only applies to moving the front end application layer of RTA. If you need to move the database in a SQL version of RTA, please refer to the article titled "How to Migrate to a New Server(SQL)".
- You'll need everyone to log out of RTA. Windows is unable to copy files that are in use, so this is a crucial step. You can validate that no files are open in the fleet directory by going to the Shared Files > Open Files folder in the Management Console on the server.
- Once everyone is out, you'll want to make note of how the current share permissions and security permissions are set up. Taking screen shots here would be a good idea, as you'll need this info to add the proper users/groups back to the folder with the proper permissions.
- At this point you are ready to migrate RTA over. Copy the fleet folder to some type of storage device. This can be a cd, dvd, or thumb drive, depending on the size of the folder. You can also opt to copy the directory directly over the network to the new server if you have the bandwidth to do so. If you copy the contents from a dvd or cd, don't forget that it retains the read-only attribute, so you'd need to reset that through explorer or through command prompt using the attrib -s -h -r * command.
- If you don't plan on running RTA on this machine, you can skip to step 5. Otherwise, you'll need to run the client setup, to ensure the server has all the pieces it needs to run RTA properly. The client setup will install active x controls, fonts, shortcuts, and our report viewer. The client setup.exe can be found in the client folder in the fleet directory. When it asks for a directory just point it back at the fleet directory on the server.
- Next you'll need to set up the share as it was on the other server. If permissions aren't set up correctly, you will increase the probability that you get some type of error when users attempt to run RTA again. Errors like 93/00 are generally the result of incorrect permissions. Call RTA Tech Support if you have issues like this. Users should have full control through the share permissions, and at least modify on the security permissions.
- Now that the server is configured, you'll need to edit the shortcuts on the client PC's so that they now point to the new server and not to the old server. If you have policies set up to control the mapping of drives, you can simply edit the old mapping so it reflects the new server. Otherwise, you'll need to go to each pc and set up the mapping, then edit the shortcuts to change the drive letter. If you are using UNC paths, you'll need to edit each shortcut to point at the new target and start in locations.