Upgrade from 3.1 - Constructing Rollback File Name

[mdornfeld]

I upgraded from version 3.1 to 4. My first job has 18 (version 3.1) rollback files and a regular vbk file already in the destination folder. Veeam has for the last hour and 30 minutes been "constructing rollback file name". First it grew the wkwms01.vbk file, now it's in the process of growing the wkwms01.vbk.upgrade file. This conversion has so far tripled the size of this backup folder.

1. Is this expected behavior?
2. Should I in the future move the 3.1 version vbk and vrb files to an "old" directory before running the other 4.0 jobs the first time?

Name Size Type Date Modified
wkwms01.vbk 90,391,456 KB VBK File 10/29/2009 10:54 AM
wkwms01.vbk.upgrade 51,058,812 KB UPGRADE File 10/29/2009 11:21 AM
wkwms012009-10-15T230028.vrb 1,341,084 KB VRB File 10/17/2009 12:29 AM
wkwms012009-10-16T230035.vrb 1,866,659 KB VRB File 10/20/2009 12:31 AM
wkwms012009-10-19T230030.vrb 1,759,130 KB VRB File 10/21/2009 12:33 AM
wkwms012009-10-20T230036.vrb 1,614,726 KB VRB File 10/22/2009 12:34 AM
wkwms012009-10-21T230041.vrb 1,473,953 KB VRB File 10/23/2009 12:34 AM
wkwms012009-10-22T230025.vrb 1,217,463 KB VRB File 10/24/2009 12:29 AM
wkwms012009-10-23T230031.vrb 2,177,040 KB VRB File 10/28/2009 12:37 AM
wkwms012009-10-27T230044.vrb 1,596,215 KB VRB File 10/28/2009 1:27 PM
wkwms012009-10-28T120048.vrb 735,103 KB VRB File 10/28/2009 3:25 PM
wkwms012009-10-28T140044.vrb 1,022,624 KB VRB File 10/28/2009 5:24 PM
wkwms012009-10-28T160024.vrb 693,674 KB VRB File 10/28/2009 7:42 PM
wkwms012009-10-28T180029.vrb 618,590 KB VRB File 10/28/2009 9:24 PM
wkwms012009-10-28T200039.vrb 575,290 KB VRB File 10/28/2009 11:35 PM
wkwms012009-10-28T220040.vrb 370,842 KB VRB File 10/29/2009 1:42 AM
wkwms012009-10-29T000039.vrb 845,905 KB VRB File 10/29/2009 5:39 AM
wkwms012009-10-29T040021.vrb 393,322 KB VRB File 10/29/2009 7:23 AM
wkwms012009-10-29T060024.vrb 584,549 KB VRB File 10/29/2009 9:37 AM
wkwms012009-10-29T080025.vrb 8,218 KB VRB File 10/29/2009 9:59 AM

I'll let you know how it gets along...

Thanks,
Matt

[mdornfeld]

Ah. It looks as though this may already be addressed here:
http://www.veeam.com/forums/viewtopic.php?f=2&t=2058

Anton. Does the advice still stand to create new backup jobs, or would it be sufficient just to clear out the destination directory?

Thanks.

[Gostev]

Matt, you can either create new job, or email our support to obtain the fix so that storage upgrade continues successfully. It may take a few hours for support to respond though, next day after major release is always tough day for them obviously...