How can you save all your Retrospect scripts, etc., if you upgrade your operating system

[dmataras]

I am running Retrospect 6.0 on a Windows 98 machine, in a peer-to-peer network.

I use this Windows 98, and the Retrospect 6.0 that is running on it, to backup this machine itself, but also 8 client machines. 6 of these clients run Win 98; 1 runs Win 95; and 1 runs Windows 2000 Pro. Think of the main machine, the one that is running Retrospect 6.0, as the "backups machine".

 

I would like to UPGRADE the operating system of my "backups machine" from Windows 98 to Windows 2000 Professional.

 

But I have put in a lot of work defining backup sets, volumes, sub-volumes, not to mention 30 or 40 scripts on the Retrospect 6.0.

 

Can I *save* all of these configurations ( backup sets, volumes, sub-volumes, and scripts ) somewhere so that I don't have to re-input all of them.

 

I presume that after I've upgraded to Windows 2000 Pro from Windows 98, I will have to re-install Retrospect 6.0. I don't want to have to re-input all of my configurations, including all those backup scripts, all over again.

 

How can I avoid that?

[AmyJ]

Copy the config60 and config60.bak files on the old machine:

 

C:\Program Files\Dantz\Retrospect

 

to the new machine after installing Retrospect:

C:\Documents and Settings\All Users\Application Data\Retrospect

This is a hidden directory - if you can't find it, configure the computer to show hidden files and folders.

 

Copy your backup set catalogs to the new computer. After copying them, open each catalog individually to ensure that Retrospect is aware of their new location.

 

You may have to edit any scripts that backed up local hard drives - remove the old drives and add the new.