Cannot verify ... Chain incomplete

How do I fix the following Shadow control image manager 5.0.5.15823 errors?

"Cannot consolidate D_VOL-b001-i2423-cd.spi Image chain missing one or more files"

"Cannot verify D_VOL-b001-i2423.spi Chain incomplete"

 

I beleive it relates to how I performed a system restore but would like to continue my incremental backup.

I installed new software on the morning of 18/11/2012. I decided I didn't like the result so did an image restore from the 8am backup of the boot/program disk (C_VOL-b001-i2423.spi) at about 11:37am. I moved the incremental backups after 8am and prior to the restore to another directory during the restore process (booted from CD). On restarting the system, shadowprotect did its slow incremental backup as expected, choosing incremental backup numbers as if 8am to 11:37 never occured as I was intending. Unfortunatley this appears to have confused shadow control managers D_VOL-b001 incremental backup chain.

In hindsight it appears shadow protect wants me to leave incremental backups when doing a restore. I have the moved incremental backups and do not need incremental backups for this period but would like to continue with the current incremental chain (avoiding starting a new base). How do I acheive that?

For reference Directory listing extracts from the active backup directory

17/11/2012  09:30 PM                56 C_VOL-b001-i2421.md5
17/11/2012  09:30 PM         1,283,072 C_VOL-b001-i2421.spi
18/11/2012  12:02 AM                59 C_VOL-b001-i2422-cd.md5
18/11/2012  12:02 AM       133,621,760 C_VOL-b001-i2422-cd.spi
17/11/2012  10:00 PM                56 C_VOL-b001-i2422.md5
17/11/2012  10:00 PM         3,358,208 C_VOL-b001-i2422.spi
18/11/2012  08:00 AM                56 C_VOL-b001-i2423.md5
18/11/2012  08:00 AM       174,238,720 C_VOL-b001-i2423.spi
18/11/2012  11:37 AM                56 C_VOL-b001-i2424.md5
18/11/2012  11:37 AM       134,275,584 C_VOL-b001-i2424.spi
18/11/2012  12:00 PM                56 C_VOL-b001-i2425.md5
18/11/2012  12:00 PM       162,731,008 C_VOL-b001-i2425.spi
18/11/2012  12:30 PM                56 C_VOL-b001-i2426.md5
18/11/2012  12:30 PM         7,783,424 C_VOL-b001-i2426.spi
18/11/2012  01:00 PM                56 C_VOL-b001-i2427.md5
18/11/2012  01:00 PM        28,335,616 C_VOL-b001-i2427.spi
18/11/2012  01:30 PM                56 C_VOL-b001-i2428.md5
18/11/2012  01:30 PM        28,501,504 C_VOL-b001-i2428.spi
18/11/2012  02:00 PM                56 C_VOL-b001-i2429.md5
18/11/2012  02:00 PM       351,278,592 C_VOL-b001-i2429.spi
18/11/2012  02:30 PM                56 C_VOL-b001-i2430.md5
18/11/2012  02:30 PM        21,244,928 C_VOL-b001-i2430.spi
18/11/2012  03:00 PM                56 C_VOL-b001-i2431.md5
18/11/2012  03:00 PM        17,644,032 C_VOL-b001-i2431.spi
18/11/2012  03:30 PM                56 C_VOL-b001-i2432.md5
18/11/2012  03:30 PM         5,284,352 C_VOL-b001-i2432.spi
18/11/2012  04:00 PM                56 C_VOL-b001-i2433.md5
18/11/2012  04:00 PM         1,058,816 C_VOL-b001-i2433.spi
18/11/2012  04:30 PM                56 C_VOL-b001-i2434.md5
18/11/2012  04:30 PM         1,081,344 C_VOL-b001-i2434.spi
18/11/2012  05:00 PM                56 C_VOL-b001-i2435.md5
18/11/2012  05:00 PM           899,072 C_VOL-b001-i2435.spi
18/11/2012  05:30 PM                56 C_VOL-b001-i2436.md5
18/11/2012  05:30 PM         1,170,944 C_VOL-b001-i2436.spi
18/11/2012  06:00 PM                56 C_VOL-b001-i2437.md5
18/11/2012  06:00 PM        15,728,128 C_VOL-b001-i2437.spi
18/11/2012  06:30 PM                56 C_VOL-b001-i2438.md5
18/11/2012  06:30 PM         9,209,856 C_VOL-b001-i2438.spi
18/11/2012  07:00 PM                56 C_VOL-b001-i2439.md5
18/11/2012  07:00 PM         6,345,216 C_VOL-b001-i2439.spi
18/11/2012  07:30 PM                56 C_VOL-b001-i2440.md5
18/11/2012  07:30 PM        82,195,968 C_VOL-b001-i2440.spi
18/11/2012  08:00 PM                56 C_VOL-b001-i2441.md5
18/11/2012  08:00 PM        43,517,952 C_VOL-b001-i2441.spi
18/11/2012  08:30 PM                56 C_VOL-b001-i2442.md5
18/11/2012  08:30 PM        34,076,672 C_VOL-b001-i2442.spi
18/11/2012  09:00 PM                56 C_VOL-b001-i2443.md5
18/11/2012  09:00 PM        15,238,656 C_VOL-b001-i2443.spi
18/11/2012  09:30 PM                56 C_VOL-b001-i2444.md5
18/11/2012  09:30 PM        19,039,232 C_VOL-b001-i2444.spi
19/11/2012  12:02 AM                59 C_VOL-b001-i2445-cd.md5
19/11/2012  12:02 AM       724,895,744 C_VOL-b001-i2445-cd.spi
18/11/2012  10:00 PM                56 C_VOL-b001-i2445.md5
18/11/2012  10:00 PM        19,063,296 C_VOL-b001-i2445.spi

......

17/11/2012  09:30 PM                56 D_VOL-b001-i2420.md5
17/11/2012  09:30 PM             7,680 D_VOL-b001-i2420.spi
18/11/2012  12:02 AM                59 D_VOL-b001-i2421-cd.md5
18/11/2012  12:02 AM       108,505,600 D_VOL-b001-i2421-cd.spi
17/11/2012  10:00 PM                56 D_VOL-b001-i2421.md5
17/11/2012  10:00 PM             7,168 D_VOL-b001-i2421.spi
18/11/2012  08:00 AM                56 D_VOL-b001-i2422.md5
18/11/2012  08:00 AM             7,680 D_VOL-b001-i2422.spi
18/11/2012  11:37 AM                56 D_VOL-b001-i2423.md5
18/11/2012  11:37 AM           609,280 D_VOL-b001-i2423.spi
18/11/2012  12:00 PM                56 D_VOL-b001-i2424.md5
18/11/2012  12:00 PM            21,504 D_VOL-b001-i2424.spi
18/11/2012  12:30 PM                56 D_VOL-b001-i2425.md5
18/11/2012  12:30 PM            13,312 D_VOL-b001-i2425.spi
18/11/2012  01:00 PM                56 D_VOL-b001-i2426.md5
18/11/2012  01:00 PM             7,168 D_VOL-b001-i2426.spi
18/11/2012  01:30 PM                56 D_VOL-b001-i2427.md5
18/11/2012  01:30 PM             7,680 D_VOL-b001-i2427.spi
18/11/2012  02:00 PM                56 D_VOL-b001-i2428.md5
18/11/2012  02:00 PM            45,056 D_VOL-b001-i2428.spi
18/11/2012  02:30 PM                56 D_VOL-b001-i2429.md5
18/11/2012  02:30 PM             7,168 D_VOL-b001-i2429.spi
18/11/2012  03:00 PM                56 D_VOL-b001-i2430.md5
18/11/2012  03:00 PM       731,415,040 D_VOL-b001-i2430.spi
18/11/2012  03:30 PM                56 D_VOL-b001-i2431.md5
18/11/2012  03:30 PM       207,783,424 D_VOL-b001-i2431.spi
18/11/2012  04:00 PM                56 D_VOL-b001-i2432.md5
18/11/2012  04:00 PM             7,168 D_VOL-b001-i2432.spi
18/11/2012  04:30 PM                56 D_VOL-b001-i2433.md5
18/11/2012  04:30 PM             7,168 D_VOL-b001-i2433.spi
18/11/2012  05:00 PM                56 D_VOL-b001-i2434.md5
18/11/2012  05:00 PM             7,680 D_VOL-b001-i2434.spi
18/11/2012  05:30 PM                56 D_VOL-b001-i2435.md5
18/11/2012  05:30 PM             7,168 D_VOL-b001-i2435.spi
18/11/2012  06:00 PM                56 D_VOL-b001-i2436.md5
18/11/2012  06:00 PM             7,168 D_VOL-b001-i2436.spi
18/11/2012  06:30 PM                56 D_VOL-b001-i2437.md5
18/11/2012  06:30 PM             7,168 D_VOL-b001-i2437.spi
18/11/2012  07:00 PM                56 D_VOL-b001-i2438.md5
18/11/2012  07:00 PM             7,168 D_VOL-b001-i2438.spi
18/11/2012  07:30 PM                56 D_VOL-b001-i2439.md5
18/11/2012  07:30 PM             7,680 D_VOL-b001-i2439.spi
18/11/2012  08:00 PM                56 D_VOL-b001-i2440.md5
18/11/2012  08:00 PM             7,168 D_VOL-b001-i2440.spi
18/11/2012  08:30 PM                56 D_VOL-b001-i2441.md5
18/11/2012  08:30 PM             7,168 D_VOL-b001-i2441.spi
18/11/2012  09:00 PM                56 D_VOL-b001-i2442.md5
18/11/2012  09:00 PM             7,168 D_VOL-b001-i2442.spi
18/11/2012  09:30 PM                56 D_VOL-b001-i2443.md5
18/11/2012  09:30 PM             7,168 D_VOL-b001-i2443.spi
18/11/2012  10:00 PM                56 D_VOL-b001-i2444.md5
18/11/2012  10:00 PM             7,680 D_VOL-b001-i2444.spi
19/11/2012  08:01 AM                56 D_VOL-b001-i2445.md5
19/11/2012  08:01 AM             7,680 D_VOL-b001-i2445.spi

Directory listing of moved files

18/11/2012  08:30 AM                56 C_VOL-b001-i2424.md5
18/11/2012  08:30 AM       133,989,888 C_VOL-b001-i2424.spi
18/11/2012  09:00 AM                56 C_VOL-b001-i2425.md5
18/11/2012  09:00 AM       236,755,968 C_VOL-b001-i2425.spi
18/11/2012  09:30 AM                56 C_VOL-b001-i2426.md5
18/11/2012  09:30 AM        20,120,576 C_VOL-b001-i2426.spi
18/11/2012  10:00 AM                56 C_VOL-b001-i2427.md5
18/11/2012  10:00 AM        13,646,336 C_VOL-b001-i2427.spi
18/11/2012  08:30 AM                56 D_VOL-b001-i2423.md5
18/11/2012  08:30 AM         7,085,056 D_VOL-b001-i2423.spi
18/11/2012  09:00 AM                56 D_VOL-b001-i2424.md5
18/11/2012  09:00 AM       120,836,096 D_VOL-b001-i2424.spi
18/11/2012  09:30 AM                56 D_VOL-b001-i2425.md5
18/11/2012  09:30 AM             8,192 D_VOL-b001-i2425.spi
18/11/2012  10:00 AM                56 D_VOL-b001-i2426.md5
18/11/2012  10:00 AM             8,192 D_VOL-b001-i2426.spi

Forums:

Comments

STC-Court

"Cannot verify D_VOL-b001-i2423.spi Chain incomplete"

The "Cannot verify D_VOL-b001-i2423.spi Chain incomplete" error is what you need to focus on.  The other one is coming up because of this.  Before ImageManager can do anything to a file it must verify the image file.  In this case the image is fairly recent so you should be able to get it squared away.

Look in the backup chain for a file called something like "D_VOL-b001.bad.log".  If you see a file like this go ahead and delete it.  If you don't see it, don't worry about it.

Cut/paste the file into a different folder (incrementals folder works well for this).  ImageManager will know that the file was taken out of the folder.  Then, cut/paste it back into the backup directory.  ImageManager will then notice that the file has been put back in and it will force a re-verify on the file.  Once ImageManager has reverified the file then you'll want to run the processing once again.  If the file checks out it should consolidate and you're good to go.

If the file fails once again then something changed with the image file and the .md5 hash isn't matching what was originally created.  If this is the case you will want to remove the file that is failing out (D_VOL-b001-i2423.spi) along with everything below it (sort by name when looking at the files).  Go to ShadowProtect in regards to this server and execute an "incremental" backup (there is a small drop down menu between execute and cancel that will give the option).  ShadowProtect will see that there are files missing and continue to make a self healing incremental file.  Once that file has been created the backup chain will continue from that point forward.  Beware, the file will be quite large so if you're replicating offsite you may need to manually seed the file if it's too big for the outgoing bandwidth.

Let me know if this info helps.

Patch

Cannot verify D_VOL-b001-i2423.spi Chain incomplete

Thankyou for your very helpful reply.

There was no *.bad.* or *.log  file.

Moving D_VOL-b001-i2423.spi to a different folder, restarting, moving D_VOL-b001-i2423.spi back and restarting, did not clear the  "Cannot verify D_VOL-b001-i2423.spi Chain incomplete" error.

Moving D_VOL-b001-i2423.spi and all subsequent files in the D_VOL-b001 chain to a different folder, restarting and running and incremental backup in Shadowprotect did work with resolution of the Imagemanager "Cannot verify D_VOL-b001-i2423.spi Chain incomplete" error. Imagemanager then ran normally again.

STC-Court

So it seems the "self healing

So it seems the "self healing incremental" did it's job.  That's great to hear.  As for what causes this type of thing to happen it's hard to pinpoint.  In most cases it's caused by something on the destination drive or the environment.  This is why we have the verify features built into ImageManager so if something comes up you can figure it out and get things going again as soon as possible.  As always, feel free to post in these forums if you have any questions or need assistance.

dhoengpreth

Chain not complete

I have same problem, but i find file bad.log, and i find some of file inside, should i delete them?

Terms and Conditions of Use - Privacy Policy - Cookies