Note: This version of the VDT (1.1.14) is no longer supported. Feel free to look through the documentation and install it, but we cannot guarantee support for it. The current stable release is 2.0.0.

Restoring a previous VDT configuration

VDT 1.1.13 comes with a new tool designed to simplify upgrades to new VDT versions by automatically restoring configuration settings from the previous VDT installation.

The general idea is that the user installs the new VDT (1.1.13) into a new location, and then runs $VDT_LOCATION/bin/vdt-restore-old-configuration, specifying the location of the old VDT installation. The script then does the following:

Restores all well-known configuration files (e.g. globus-gatekeeper.conf). These files are specified in $VDT_LOCATION/setup/conf_file_list.txt
Searches for any other files that have been manually modified in the old VDT installation. This is done by comparing modification timestamp of each file to installation times as recorded by Pacman.

All restored files are backed up. The file names of the backed up files are specified in vdt-install.log, together with the diffs for each restored file with respect to the file it overwrites. Note: Restoring configuration correctly is tricky! There is a chance that the tool may not get it completely right! Please review vdt-install.log and look over the file diffs to make sure the changes are correct!!!

Here's an example (abridged) of a user restoring the configuration from an old VDT 1.1.12 installation (in /opt/vdt-1.1.12) to the new VDT 1.1.13 installation (in /opt/vdt-1.1.13):

[/opt/vdt-1.1.13]# ./vdt/bin/vdt-restore-old-configuration /opt/vdt-1.1.12
Restroring files...
(see vdt-install.log for details)

/opt/vdt-1.1.12/globus/etc/globus-gatekeeper.conf
/opt/vdt-1.1.12/globus/etc/globus-job-manager.conf
/opt/vdt-1.1.12/globus-rls-server.conf
/vdt-install-test/installs/041/server-client-as-root/globus/etc/gridftp-resource.conf
/vdt-install-test/installs/041/server-client-as-root/globus/etc/grid-info-resour...

Looking for other modified files in old VDT installation....
(you might want to examine these files and propagate changes
into the corresponding files in the new VDT location manually)

/opt/vdt-1.1.12/globus/var/globus-gatekeeper.log
...

[/opt/vdt-1.1.13]#

Notes:

Make sure the $VDT_LOCATION variable is set to point to the new VDT installation before running the script
All configuration files that are overwritten by configuration files from the old installation are backed up. See vdt-install.log for the exact names of the backup files.
When restoring configuration files, VDT replaces all occurences of the old VDT location with the new VDT location
Files in "old VDT location"/MDS24 are copied into "new VDT location"/globus (this is needed by Grid3 installations
You can always edit the $VDT_LOCATION/vdt/setup/conf_file_list.txt to modify which "known" configuration files are searched and where they will be copied to in the new VDT installation.
If you want the new installation to be in the same location (X) as the old installation:

Move the old installation from X somewhere else (Y)
Install the new version into location X
Set VDT_LOCATION = X
Run X/vdt/bin/vdt-restore-old-configuration Y