Moving Profiles to New Server

[dscotl]

I have a number of profiles, including several Glacier jobs, on a server being retired. I want to move the profiles to a new server and want the Glacier job databases to migrate so I keep the mapping of Glacier archive objects to files (files have been copied 1-to-1 from old server to new). It would be costly (time and money) if files were re-uploaded to Glacier.

Can anyone give me advice on best practices? This is a situation that comes up regularly for me.

[superflexible]

Just make a copy of the whole C:\ProgramData\Syncovery folder and copy it to the new machine. You can install Syncovery on the new machine before or after you copy the Syncovery data.

If you want to avoid copying lots of old log files, you can delete them or move them out of C:\ProgramData\Syncovery\Logs before the migration, or just exclude the Logs folder from your copy.

You will see your jobs and the Glacier databases will be there and they will be used.

[dscotl]

I finally had an opportunity to follow these steps precisely and test. Indeed the profiles are copied, Amazon credentials transferred, etc. However, the first time I run one of the Amazon Glacier profiles I am prompted to get (download) the file inventory from Glacier, which takes 3-5 hours. If I decline the inventory it appears the entire store will be re-uploaded. Is this expected behaviour?

In my particular instance performing the inventory is acceptable but I can imagine scenarios where it would be problematic. The time factor could be critical with 3-5 hours for each of many Amazon Glacier profiles.

[superflexible]

Hello,
if the Glacier databases have been copied over, they should be used. You can check the log file to see which database file name was used for the inventory. Maybe a different one from the old machine, for whatever reason. The reason can probably be guessed by comparing the old and new file name.