Cannot validate backup archives on DVD-R. Insert last volume of multi-volume archive.. blah blah blah...
Hi All,
I`ve tried to make recovery disks for several of my pcs with no luck.. I`ve tried ATI Home 2009, 2010, and a demo copy of ATI WS 2010 with the same results..
I boot the machine from the ati recovery media to create the disks, and burn the dvds. In the last case, 3 of them to do a backup of an XPH install on an MSI 1900 all in one touchscreen computer... It creates the three dvds, and asks for the last volume of the multivolume archive to validate it.. This is where the problem starts... The last volume is in the drive, but Acronis cannot see it.. I`ve tried 3 different types of media, HP, Memorex, Sony, *sony I never have problems with except with ATI* and tried this on four different machines, 1 MSI 1900 touchscreen, and three separate MSI 2010 touchscreens, all with slimline dvd burners built in.
I can reboot the machine to the ati recovery media to try and validate the archives again, but still get the same error, no matter what dvd I put in the drive...
The dvdburner i am currently using thats built into the msi 1900 is model number HL-DT-ST DVDRAM GT10N.
I love the acronis software, but when I try to create recovery media on dvd, its never been easy... anybody have any ideas??
Thanks

- Log in to post comments

Its primary in only that its an archived copy that I keep with the machines... The irritating part is that with these machines, I can make an archive on an external drive that passes verification, and then burn to disk like you said, and the disks still have the same freakin problem... cant find last media.... Its like WTF? I`ve burned the discs on the above mentioned machines, and two desktop workstations with the same result... so I really doubt the optical drives or the 3 different brands of media are the issue... ????
Memory has been Memtested overnight, and passes with flying colors...
- Log in to post comments

Hi Eric,
From my understanding, when backups are taken on DVDs, data files get splitted on multiple dics, that is data get spanned across multiple discs, that could be the reason why it keep asking you to insert volume # or the last media. If taken directly, it is good to label the disc and give them volume number. For instance, a single MP3 file can single file can be scattered across 3 -4 discs. So, it is always good to place them on a single location/folder when performing validation or restoring.
- Log in to post comments

But I`ve done this in the past dozens of times on different machines with older builds of acronis, aka TI Echo 8.xx I still use that on my xp machines, to boot from acronis media to create backups to dvd with no problem.. Heck, about half the time it works with home 2009 too, but in this case, for these 4 machines, it refuses to work come hell or high water.... :(
- Log in to post comments

Who knows what Acronis has done that is different between the older versions and the newer versions. Sometimes I don't think that even Acronis knows. It's their standing track record to bring out a new version/build that breaks something that was working in an old version/build.
- Log in to post comments

Hey Acronis tech support,
any ideas here, or silent as always?
So in my pouring through this forum and others the last several days, *what a way to waste days off, let me tell you* It appears that acronis has serious issues with verifying archives, and with theoretical archive corruption that in more than one case I`ve seen acronis technical support state with a high and mighty tone that in no way could their software have corrupted their archives.. This got me thinking...
Does acronis have any sort of parity built into their backup systems, aka like a raid 5 system, lose or scratch one volume of a backup disk, but the system can still recover all your data, albeit at a slower rate with more overhead..?? I would LOVE to have my backups work EVERY time, and would gladly add 1 dvd to my backup set, or add 100 gig to a 1 terabyte backup, if I knew the software worked EVERY, or 99.99% of the time!
- Log in to post comments

Hello all,
Eric, please accept my profound apologies for the delay with the response.
First of all we need to localize the problem, i.e. find out what happened exactly. Could you please copy all the volumes of the created archive to the same folder on the internal hard drive and run the validation?
We are looking forward to hearing back from you at your earliest convenience.
Thank you.
- Log in to post comments

Hi,
copying all volumes to the same internal hard drive end in the same result.. However, creating the volumes over the network and dumping to my server does work..... Some sort of USB and optical drive media problem? All external drives used for this have been checked and rechecked by the mfgr utilities, and pass with flying colors. A couple have even been fully reformatted for curiousities sake...
- Log in to post comments

Hello Eric,
Thank you for posting your question, I will be happy to help. Please accept our apologies for the delay with the response.
We have an appropriate article in our Knowledge base, please see it for more information. This article will help to find the exact reason of the encountered issue.
Please let us know the results, we should be sure that the program runs flawlessly. If the provided information is not clear or if you have any other question do not hesitate to post them and we will be glad to answer.
Thank you.
- Log in to post comments

Eric,
You may not care anymore but I found a workaround that is relatively painless - just time-consuming. Do NOT use the media builder function - therein lies the problem. The agent-ramdisk.dat file that is created contains the bug that gives the volume label error. I'm using the linux backup/recovery server software, version 11639. I copied the 2 files - image.bin and can DVD iso image with this command...
mkisofs -b image.bin -o /
/.iso -R -J
-A "Acronis" -hide-rr-moved -v -d -N -no-emul-boot -boot-load-size 4 -boot-inf
o-table -c boot.cat -graft-points "/boot=/
/boot " /
/boot
This creates a bootable iso image with a new catalog.bin that includes the .tib file. Burn the iso image to DVD and boot your target device from it - if you look under local folders for the archive file, it will be under cd0 or sr0. Then restore as normal.
I agree Acronis seems to be in no hurry to correct this issue, and it's counter-intuitive that NOT making the bootable media is the key to success. But you can get through as long as the backup is made with the same version of the software.atalog.bin, to a linux box. (RHEL 5) Both files must be in a subdirectory named boot - because that is how they come on the original disk. Add the .tib file to the directory, and create
- Log in to post comments