Support Home New Sales Website Old Sales Website Contact Us
RDP Support  


RDPWin KB Booking Engine - IRM.Net RDPWin4 & PCI Compliance Search
 
 
 

Index
Updated: 6/27/2013 (RK)
Article ID#: KWin0071

Data Server Replacement / RDP Data Migration



RDP Data Server Replacement / Data Migration Steps
1 Contact RDP Support to schedule a time.
2 Configure the new data server.
3 Install Pervasive on new server.
4 Add default RDP directories to the data server.
5 Download RDP updates to new server.
6 Verify there is a valid backup of all RDP data.
7 Transfer files from backup to new server.
8 Install RDP updates on new server.
9 Login to RDPWin on new server.
10 Rename the resorts file on old server / users must exit RDP.
11 Copy RDP data files to new server.
12 Remove the share on the old RDPNT directory.
13 Map network drive on new server and one 32-bit workstation.
14 Rename resorts file on new server.
15 Uninstall RDPWin client on all workstations.
16 Install RDPWin client on all workstations.
  17   Change drive mapping on workstations.
18 Recreate users.dat file if updating from RDPWin version 2 to RDPWin version 3.
19 Rebuild all Files and Indexes
20 Users login to RDPWin.
21 Update Confirmation Path and Monitor Path to new data server.
22 Configure the IRM.Net server to use the new data server.

Server Migration

1. Contact RDP Support to schedule a time for the Data Migration

It is necessary to contact RDP Support to schedule a time for the data migration, in order to receive assistance from a RDP Support Technician.

  1. Select a time for the data migration during normal business hours. See RDP support hours for more information.

  2. Data migrations are NOT supported during non-business hours.

  3. Expect upwards of 3 hours of down time during the migrations.

  4. Select a time when the property is less busy.

2. Configure the New RDP Data Server

RDP recommends configuring the new RDP server and testing the installation of the RDP programs prior to the data migration. This limits the down time required to transfer the data and helps to make sure the installation goes smoothly.

You are responsible for setting up the new server. This may include configuring DNS/Active Directory, security, installing Windows updates, and other network settings, similar to the configuration of the existing data server.

  1. See RDP Hardware Requirements for more information.
  2. Install Microsoft .Net Framework 4.0.
  3. If the new server will have the same computer name as the old server, set it up as a stand alone workstation. Do not put it on the network yet.  If the new server will have a different name than the existing server, add the server to the network. The server must be in the same domain and subnet as the previous RDP data server.

 3. Install Pervasive on New Server

  • Install Pervasive on the new server.
  • Only Pervasive version 10 and 11 are supported by Pervasive.
  • If upgrading Pervasive, all workstation will also need to be upgraded. Updating the workstations to the new version can be done ahead of time, because Pervasive is backwards compatible. For example, if the current version installed on the existing server and workstations is version 10, but you are upgrading to version 11. Install version 11 on the new data server and all workstations.
  • Installing the Pervasive Server requires the entry of the Pervasive License. This license key is available on the Pervasive Installation Disk. If the Pervasive Installation Disk or License key cannot be found, it may be required to install a temporary license from Pervasive and contact Pervasive directly for licensing information. RDP does not store customer license information.
  • If utilizing the same Pervasive License key from the existing server, install a Pervasive temporary license until the data conversion is complete. Then enter the permanent license key on the new server.
  • See Pervasive Documentation for more information.

4. Add Default RDP Directories to the Data Server

Create the default RDP directories on the new server.

  1. Create a RDPNT folder on the root data drive. If the drive is partitioned, it may be on the D:\ drive.
    • Share the RDPNT folder.
    • All users need Full Permission and Full Security to the RDPNT folder.
    • All workstation will have a mapped drive to the RDPNT folder.
  2. Create a RDP folder under the RDPNT folder on the appropriate drive letter created in step 1 - D:\RDPNT\RDP.
  3. Create a RDPWin Setup folder under the RDP folder - D:\RDPNT\RDP\RDPWinSetup.

5. Download RDP Updates to New Server

Download but do NOT install the latest RDP updates on the new server. See RDP Updates for download instructions.

  1. Download the RDPWin Version 2 or Version 3 update to the D:\RDPNT\RDP\RDPWinSetup folder.
  2. Download the IRM.Net update to the \\<irmserver>\IRMSetup folder.
  3. Download the RDP DOS update to the D:\RDPNT\RDP folder.

6. Verify There is a Valid Backup of All RDP Data

The RDPNT folder should be backed up each night. If a quality backup does not exist, make a copy of the RDPNT folder and all contents, and paste it to another computer on the network.

7. Transfer Files from Backup to New Server

From the backup created in step 6, copy the entire RDPNT folder and all contents to the new server's RDPNT folder location created in step 4. This will be used to test the configuration of the server prior to the actual data migration.

8. Install RDP Updates on New Server

Install all RDP product updates on the new data server. Do NOT update the workstations at this time.

  1. See RDP DOS Update for installation instructions. Note: if the server is 64-bit, the RDP DOS update must be run from the 32-bit workstation that has been mapped to the new server.
  2. See RDPWin Version 3 Update or RDPWin Version 2 Update for installation instructions. Note: When logging into RDPWin for the first time, a program prompts for the Administrator password and the RDPWin path to the data. Enter the correct information.
  3. See RDPWin Monitor Documentation for installation and setup instructions.

9. Login to RDPWin on the New Data Server

Login to RDPWin on the new data server to verify that the installation and checkfiles program completed successfully.

10. Rename the Resorts File on the Old Server / Users Must Exit RDP

All users must exit RDP at this time.

  1. On the old RDP data server, explore to the ..\RDPNT\RDP directory.
  2. Rename Resorts to Resorts_old. This will prevent users from logging into RDP and add modifying data during the transfer.

11. Copy the RDP Data Files to the New Server

Note: If the new server was not added to the domain, due to the old and new server names being the same, add it to the domain at this time.

  1. Copy the RDP data to the new server. Copy the entire ..\RDPNT\RDP folder and all contents from the old server to the new server, overwriting the RDP folder on the new server.
  2. Once the copy is complete, login to RDPWin on the new data server. Allow the Check Files program to complete.

Note: If using RDPWin Version 2 and credit cards are encrypted, please contact RDP Support in order to access/save credit card data on the new RDP server. 

12. Remove the Share on the Old RDPNT Directory

Change the Share Properties on the old RDPNT folder to Do Not Share this Folder by selecting Properties from the right click menu of the folder. This will prevent possible confusion later.

13. Map Network Drive on New Data Server and One 32-bit Workstation

Determine what network drive is currently mapped to the RDPNT folder on the old server. This is usually R:\ or F:\. If the new server is a 64-bit, map one 32-bit workstation to the D:\RDPNT shared folder on the new data server in order to install the RDP DOS update.

14. Rename Resorts File on New Server

On the new server, rename the Resorts_old to Resorts.

15. Uninstall RDPWin Client on All Workstations

Uninstall the RDPWin Client on all workstations. Uninstall from Start --> Control Panel --> Programs and Features on a Windows 7, Vista, or Server 2008, or from Start --> Control Panel --> Add/Remove Programs on a Windows XP or Server 2003. This is required because the ClickOnce installation used to install the RDPWin Client looks at a certain location for the file on the server. Since a new server is installed, the location has changed.

16. Install RDPWin Client on all workstations

Install the RDPWin Client on all workstations. Browse to the RDP Data Server --> RDP folder --> RDPWinClient folder. Run the Setup.exe.

 

17. Change Drive Mapping on Workstations

If the workstation has a mapped drive, change the path to the \\RDPDataServer\RDPNT folder for the mapped drive on each workstation. If the workstations are using the UNC path to the data server, then the c:\Program Files\ResortDataProcessing\RDPWin\RDPWinPath.txt file must be edited with the new path, i.e. \\RDPData\RDPNT\RDP\RDP01.

18. Recreate Users.Dat file if Updating from RDPWin Version 2 to RDPWin Version 3

Due to the credit card encryption changes in RDPWin Version 3, recreate the Users.dat file if updating from Version 2.

  1. Browse to the RDPNT\RDP\RDP01 folder.
  2. Delete the Users.dat file.
  3. Login to RDPWin with the user name Admin with no password. You will be prompted to create a new password. All users will be required to enter a new password the first time they login.

 

19. Rebuild Files & Indexes (All Files)

Rebuild ALL Files and Indexes:

  1. Go to the System Menu --> File Utilities --> Rebuild Files and Indexes
  2. Select All Files
  3. Select Rebuild Files and Indexes under 'Rebuild Options'
  4. Click Process

20. Users Login to RDPWin

Users can now log into RDP. When the users login to RDP, the workstation will automatically update to the new server of RDP.

21. Update Confirmation Path and Monitor Path to New Data Server

Monitor Path Instructions.

  1. Create Text Document with local drive.
  2. Save document as MonitorPath.txt in RDPWin document folder. Example location - C:\Program Files\ResortDataProcessing\RDPWIN
  3. Start RDPWin Monitor, confirm successful start in RDPWin Monitor log.

 

Update each active confirmation to point to the new data server.

  1. In RDPWin, go to the Reporter menu --> Configuration --> click the Confirmation Settings tab.
  2. Double click on a confirmation with the Active checkbox selected.
  3. In the Crystal Report Attachment (PDF or Word) field, change the path of the confirmation to point to the new data server.
  4. Repeat  for each confirmation that is active.

22. Configure the IRM.Net Server to Use the New Data Server

For customers using the IRM.Net or IRM, change the path IRMPath.txt file to point to the new data server.

  1. On the IRM server, browse to C:\Intepub\WWWROOT\IRMNet and locate the IRMPath.txt file.
  2. Edit with Notepad.
  3. Change the path to the UNC path of the data on the new RDP server, i.e. \\RDPData\RDPNT\RDP\RDP01.
  4. Open a web browser and verify the IRM.Net loads properly.
  5. If the new RDP data server name is different than the old server and a custom IRM.Net theme is in use, update the custom folder with the new server name. This folder is located on the IRM.Net server in C:\INETPUB\WWWROOT\IRMNet\Custom.

Call Accounting, Phone Actuator, POS and Other RDP Interfaces

  1. If RDP interfaces are installed, disconnect the mapped drive on each interface computer to the old data server's RDPNT folder.
  2. Remap to the RDPNT folder on the new data server using the same drive letter (i.e. F:\ or R:\).
  3. Verify that the RDP DOS Call Accounting, POS, Phone Actuator, or other interface icons on the desktop have the correct mapped drive to the new data server.
  4. Login to each interface using the correct login name and verify the connection is made to the new data server.

PBAdmin - Less Than Version 6.0 Only

The following configuration steps for users on a version of PBAdmin that is less than version 6.0. Version 6.0 and higher, skip these steps, as they do not apply to higher versions.

  1. On the PBAdmin credit card server, remap to the RPDNT folder on the new data server using the same drive letter (i.e. F:\ or R:\).
  2. Verify that the Start CC (uses LoadPB.bat batch file) and Stop CC Engine (uses UnloadPB.bat batch file) shortcuts are mapped to the new drive. Right click the on the shortcut --> select Properties --> determine if the Target field has the correct path. Occasionally, even if the mapped drives are the same, these files do not load correctly unless LoadPB.bat and UnloadPB.bat shortcuts are created and copied to the desktop.

PBAdmin - Version 6.0

If using PBAdmin version 6.0, the following steps should be completed on the PBAdmin credit card server using the C:\ drive.

  1. On the PBAdmin credit card server, remap to the RPDNT folder on the new data server using the same drive letter (i.e. F:\ or R:\).
  2. Using Notepad, open C:\SDC\PBASE\STARTPB.BAT file.
  3. If RDP was mapped to a different drive than before, change the drive letter on the 3 lines that have f:\rdp\pb\pbfiles to the correct drive letter.
  4. Run STARTPB.bat to make sure two windows are running minimized on the task bar. One file should be named Protobase Comm Director. This running PBDIRECT. The other minimized file is named Protobase Fileserver, which is running PBFSRV.
  5. Run STOPPB.bat and make sure both windows close.

 

 

 
Support Home  RDPWin4 & PCI Compliance Enhancement Requests Open A Web Support Ticket
Training New Sales Website Old Sales Website Contact Us

 Facebook     Twitter      LinkedIn   TODF