Error importing config when migrating to new server

[timstumbo]

I setup a new 2012 server today, I'm tying to migrate my config over from a 2008 server. When I go to import the config and select the migrate option it errors out when analyzing the file with "Configuration backup file has unsupported version or corrupted contents". I verified that both versions of the software were the same, 8.0.0.817. I didn't do a SQL backup but instead setup a clean database install with SQL 2012. From what I read you don't need the database backed up as long as you have the configuration.

Thanks for the help.

[foggy]

Right, you do not need to backup the database separately. Please contact technical support directly for assistance with this. Your case ID posted here will be much appreciated.

Also, if there's an ability to perform configuration backup again and then import it, you can try that.

[timstumbo]

I tried to do another backup and I'm still getting the error importing. I will put in a ticket.

[foggy]

Yes, this is the most effective way of addressing issues like this.

[timstumbo]

Case # 00721742

[justin@itvantage.com]

I was also getting this error when moving the Configuration from an old server (Windows Server 2012 Std R2) to a new server (Windows Server 2012 Std R2).
The fix was to move the Configuration backup file from the SMB share on my NAS to a local folder on the new server.

[TitaniumCoder477]

Thanks. This is the 2nd time I had to perform a migration from an interim server to the actual backup server, and once again I got caught by this. Can't restore straight from UNC path oddly enough even if it is your repo. Must copy backup config files locally and restore from there.

[GT-Engineer]

This is still an issue. I figured that this would have been fixed in 3-4 years but it is still an issue or at least do not have the option to restore straight from the backup repository. Copy it locally and it works.

[pklein@prodatec.de]

and still the problem is not solved?!

... copying to local did the job.

greets
patrick

[foggy]

Hi Patrick, we've just checked and this works (and should also work before) as expected - if you specify the remote location, the configuration backup file is automatically copied locally and then imported normally. I recommend contacting support for a closer look at the logs. Thanks!

[FoCTayw0wavh78Qu53wi]

Hi,

We had this problem and we found that in the destination repository the file permission on the file was set to 700 and when it was copied locally on the server Veeam was not able to access the file. If we put the file with 777 permission the file is now valid.

[sandroalves]

Hi,

our server crashed the operating system disk, but the data remains intact at first.

I don't have information on which version was installed, but I believe it was Veeam 10 for sure.

However, when I choose the option to restore the configuration of the JOBs it presented error.

This version that I'm using for sure is more recent.

Thanks.

[Natalia Lupacheva]

Hi Sandro,

moved your post to the existing thread with the discussions on the same error message.
Please provide a support case ID for this issue, as requested when you click New Topic.

Also, please take a look at the soutions above, maybe the permissions or file location trick could help.

Thanks!

[sandroalves]

Hi,

I came back to inform the reason of the problem.

The file was corrupted, because the volume was enabled with deduplication (Windows) and after the re-installation of windows some problem occurred with the files.

Thanks.

[Natalia Lupacheva]

Hi Sandro,

Thank you for sharing the results! Appreciate it.

Thanks!

[davidkillingsworth]

I was also getting this error when moving the Configuration from an old server (Windows Server 2012 Std R2) to a new server (Windows Server 2012 Std R2).
The fix was to move the Configuration backup file from the SMB share on my NAS to a local folder on the new server.

Thanks. This resolved the issue for me when migrating from Windows 2012 R2 server & latest patched Veeam 10 - to Windows 2019 & latest Veeam 10.

[Tonst3r]

Necro'ing this because the "copy the backup to the server and try again" just saved my booty cheeks. I copied it to my local download folder and it worked great.

Since I order through ConnectWise, I have the most useless lack of technical support, so I've been stuck and scared until finally finding this thread.

TY <3