Data base recovery after upgrade to ARCserve 2000

[cweems]

Just a note of thanks to those that have responded to my questions. Thank you. They have answered the questions or lead me in the direction of finding the answer.

Now, my current question. One of my associates upgraded one of our servers from ARCserveIT ver. 6.61, build 834sp2a to ARCserve 2000 Advanced Edition Ver. 7.0, build 1018. He indicated that when he did the upgrade he was not able to restore the old ARCserveIT database. He got some incompatibility error message, can remember exactly. Can anyone tell me if this is the case and I will have to rebuild the whole database from scratch or is there a fix, and or work-around?

Thanks again.

cweems

 

[Guest_imported]

Was in using Raima or VLDB in the older versions? If it was Raima then your trying to recover a different database back into VLDB. If it is sp2a of ARC 6.61, then you should have the convert database utility. If he does then ask him to convert his current database to vldb and then you'll have more of a compatibility. I am not 100% that vldb was introduced in 6.61 sp2a. So check that out.

Also, service pack your ARCserve 2000, its always best practise. Some of the bugs in SP3 have been ironed out so you can implement it rather safely.

guru - brightstor@hotmail.com

 

[vulpine]

In 6.61 SP2A, there is a screen with several option boxes - the very last one reads 'VLDB support'. That box must be checked for your database to convert from RAIMA to VLDB. It takes a long time and will sometimes stop responding and then start up again (so don't kill it while its running). You may look in your ARCserve folder to see if there is another copy of your database. It may have a .141 extension or say something to the effect that it can be deleted. You will have to reinstall the 6.61 version, copy that db folder to it and run it through that service pack (with that option mentioned above) to get it to convert. OR you could just 'Acknowledge and move on', create new jobs and merge the tapes that you do have stored into your new database.