Moving CostGuard From One PC to Another

Moving CostGuard From One PC to Another

In order to move CostGuard to another PC, you need to do the following:

Back up your data

1. From within CostGuard make a data backup onto a portable drive (File > Backup).

Note: If you’re using the Advantage Remote Server, this option is not available, you will need to back up on your own. There are two ways to do this:

Manual Backup:If you need to make a manual copy of your data and you’re not sure of your data location, then double click the CostGuard.ini file (in the CostGuard startup folder), and under [File Locations] the DATA=  points to the folder.

Using the ADS server. This is a more technical method.

Install CostGuard on the new machine

2. Install CostGuard on new machine. To download, click Trial Version

Activation Codes

3. Activate CostGuard by clicking ‘Receive Permanent Activation’ when CostGuard starts up; in the email, be sure to explain why you’re requesting another permanent activation

Restore your data

4. After activating, from within CostGuard restore the data (File > Restore).

To restore a manual backup carefully copy both CostGuard Shared\Data and CostGuard Shared\System from the old PC to the same place on the new PC.

Data and system files


If you have passwords that you’ve created and want to bring those over then you will need to copy the system folder also. In this case just copy the entire CostGuard Shared Folder.

Data and system files






A more technical way to backup using the Advantage Server Backup

ADS has a backup command line utility called adsbackup, the details of which can be found here: ADS Backup. It’s simple to use and can be run while a database is online.

For a more complex situation when backing up multiple dictionaries. These directions are from Advantage:

I don’t believe there is a parameter to back up several dictionaries at once, but assuming that the current script being run uses some form of cp/copy, one can modify that script to use adsbackup in their place, changing the parameters as necessary. If you’re using free tables, just setup the lines to look as follows:

adsbackup [options] [file mask]

where src path is the location of the free tables being backed up file mask is A file mask similar to “*.adt” or “*.dbf” which will be used to determine what tables should be included in the backup image. The file mask is only allowed when performing a backup of free tables. Multiple masks can be used in a single backup/restore by separating them with a semicolon. For example, “*.adt;*.dbf”.

dest path is a Path to place the backup image in. This path can be UNC ( \\myserver\myshare\mydir ) or a drive letter ( c:\mydir ) if connecting to a Microsoft Windows server. If using drive letters, keep in mind the drive letter must be recognized by the server machine, any drives mapped on the client executing the backup command are irrelevant. Unlike the source path, the destination path can use any drive letter, even one that references a mapped drive. If connecting to a Novel Netware server or a Linux server UNC, paths are recommended.

Alternatively, to backup data dictionaries if you’re using them:

adsbackup [options]

Overall if there is already a script in place which copies or backs up the files, probably the best way to utilize adsbackup would be the modify the existing script with it to make the changes.