Skip to content

Switching between a remote and a local server archive

Moving data from a remote archive to a local archive

  1. Stop the VDog MasterService in the Service Control Manager.
  2. Check if all subordinate processes of the VDog MasterService are also stopped. This ensures that no more processes are accessing the server archive and that you receive a consistent copy.
  3. Change the name of the local server archive to vdServerArchiveOld.
  4. Copy the remote server archive to your local hard disk and rename it to vdServerArchiveRemote. This places the two directories vdServerArchiveOld and vdServerArchiveRemote in your local drive.
  5. Delete all directories from the directory vdServerArchiveRemote whose name begins with "VD$".
  6. Then copy these directories from the directory vdServerArchiveOld to the directory vdServerArchiveRemote.
  7. Open the Server.ini file in the directory ..\vdServerArchive\VD$A\Configuration.
  8. Navigate in the Server.ini file to the entry 5508=Path to the old remote archive and delete the value of the key so that only the entry 5508= remains.
  9. Rename the directory vdServerArchiveRemote to vdServerArchive.
  10. Restart the VDog MasterService.

Moving data from a local archive to a remote archive

  1. Stop the VDog MasterService in the Service Control Manager.
  2. Copy the local server archive to the desired location on the network drive.
  3. Open the Server.ini file in the directory ..\vdServerArchive\VD$A\Configuration.
  4. In the Server.ini file, find the entry that starts with 5508= and set the value to the path of the new directory on the network drive. For example:

    • 5508=\\myNAS\versiondog\vdServerArchive
    • 5508=\\192.168.172.1\versiondog\vdServerArchive

    Note

    You can use either a network name or an IP address in the path.

  5. Delete all directories from the local server archive except the following:

    • All directories with names that include "VD$"
    • VD_TMP_VD
    • vdog agent setup
    • vdog client setup

    These directories contain databases and critical configuration files and must remain on the local server.

  6. Make sure the user account that starts the VDog MasterService has the necessary permissions to access the remote archive on the network drive.

  7. Restart the VDog MasterService.