How to replicate urbackupServer and use the backups of the first one

1

Hi,

I’m trying to replicate urBackupServer. I want to do that because I want to restore an image of my urbackupServer in another lan that it has another urBacupserver.
To do that, I’ve stopped service of my urbackupserver and I copy all the folder(s) in the new urbackupser and then I copy in my new location of backups (e:\backup, not g:\backup like the first one) my backups.
When I’m trying to mount an image it gives me an error:

2026-09-26 01:49:38: ERROR: Error opening VHD file

I suspect that it can be because it store some metadata of the unit or something like that.

Do you know how to resolve it?

Thanks

2

The cause is that UrBackup stores image backups in its database with their full path (e.g. G:\backup\<client>\<backup>\Image_C_....vhdz), while file backups are stored relative to the backup storage path. So after moving to E:\backup, the database still points every image at G:\....

Two ways to fix it:

  1. Easiest: give the new backup drive the same path as before. Change its drive letter to G: in Disk Management (or put the backups in G:\backup), and nothing else needs to change.
  2. Keep E:\backup: set the backup storage path in the new server’s settings to E:\backup. When UrBackup can’t open an image at its stored path during its statistics update, it looks for it under the current storage path and fixes the database entry. That update runs during the nightly cleanup, or you can trigger it right away by running cleanup.bat 0% from the server folder as administrator. (With 0% it won’t delete backups to free space; it only applies your normal retention settings, the same as the nightly cleanup. Without an argument it defaults to freeing 10% of the drive.) Then try mounting again.

One warning: don’t run remove_unknown.bat until the images open correctly. It deletes database entries for images it can’t find and then removes files in the storage folder that aren’t in the database, so running it with the wrong paths could delete your copied images. Since you’re working on a copy, you’re safe to experiment, but keep the original until the new server works.