I totally agree, this should have been mentioned in the upgrade notes.
I also ran into this problem, but since We've only been using veeam in a test environment, i just purged all old backups and reinstalled veeam and the DB.

Argh, had I read this thread earlier, just yesterday thrashed two weeks of v3 Backups, because Veeam Backup 4.0 was trying to upgrade a 800GB VBK which exceeded the free space on the backup raid. This *really* should've been noted in the release notes.

After upgrading to the original 4.0.80 and running my first test job, an existing job, it has been "hanging" at the 0 percent complete and "initializing target session". Is it anticipated that this will eventually complete or do I need to restart the server.

I have updated to the latest Backup 4.0 (just downloaded, looks to be the same build file however re-installed over the existing). I still have 2 servers that are stuck on the 0% problem. And after the update are still stuck on this. Should I leave them for the weekend? Or is there a way to force kill the .update process, clear the job and start with a new job?

Upgrade shoud complete pretty fast, no need to leave the jobs hanging for the weekend, it won't help. If you follow the procedure I listed above closely, the upgrade should complete successfully. Or yes, alternatively you can always simply delete the jobs for which automatic VBK storage upgrade failed, and create the new job - if this works for you.

Jeff, if you need any help at all, please do not hesitate to open a support case, and they will assist you. If the job won't stop, I believe you can simply kill veeam manager and agent processes with the task manager. Or, reboot Veeam Backup server. Then, you will be able to delete the job.

I ran into the same issue after I upgraded it to version 4. The job just hung on "Constructing roll back file" for over day. It won't stop or cancel. I end up have to move the old backup files to a different folder and delete the backups in the Veeam console and start the new Full back on the same job. If I need anything from the old backup, I just import them again.

Anyway, Veeam 4 works much better and solved alot of old issues. Some of my job was running only 15MB/s. The same job is running 120MB/s with Veeam 4. Huge improvement. Thanks alot.

jingxi02 wrote:I end up have to move the old backup files to a different folder and delete the backups in the Veeam console and start the new Full back on the same job. If I need anything from the old backup, I just import them again.

Yep, this is exactly what I would do too. Despite major storage changes, Veeam Backup 4.0 can still import backups made by any previous version of Veeam Backup. Glad you are enjoying the new version!