How big the Arcserve can really be? 1

[BMW]

Hi,

In theory Arcserve2000 database can hold 30+GB of data. But my personal experience is, when it is over 2GB, you start to get corruption problems. For example, if I have a full backup first day, then everything is good. I can see all my files under restore (either by tree or by session). Testing restore some files---great! then next day same backup job run again (same setting, full backup), next day, I can not see some of the files under restore either by tree or by session. Even the good backup on the very first day was gone. At this point the Arcserve database is about 1.5 to 2 GB. I have a 26GB free disk space on my hard drive. My ARcserve 2000 is fully patched. It seems this product is not designed for the big customer? I have tested my theory many many times. I always clean up my database first and then run full backup job. Is there anyone keep your database biger than 2 GB and without any problems?

 

[jimpames]

Hello,
Please use the Arcserve Manager, manager, database to access database manager and click the "summary" record in the left panel. In the lower right panel, look at "database type" it should be "Arcserve VLDB". Your symptoms seem to indicate the RAIMA predecessor to VLDB. Please let me know and I'll try to help you.

Regards, Jim P. Ames
True Data Storage Networks
Arcserve Service
Data Protection and Recovery
212.352.1780

http://www.truedatacorp.com

 

[BMW]

Thank you Jim!

My Arcserve database is VLDB. I was using ArcserveIT 6.61 and upgraded to 2000 long time ago. Now I am still having this database corruption problems. My full backup activity log shows great, not error messages, jobs were finished. The first full backup(after I clean up the database each time)is always good. I can see my backups under restore either by tree or by session. The problem is after that, if I do another full backup (just for testing the theroy I had), the my database get corrupted. I can only see partial of the backups under restore. I have tried the merge method, merge all the tape back into the database, then same thing--still partial. Why first full backup is always great, then problems start from second full backup? I have tested this way, one full backup and then incremental next day. This works great. But it is hard to believe that I can not do two full backup in roll? Something to do with database size, if the database size bigger than 1.5 GB, then there is problem! Any suggestions?

Thanks again!

 

[jimpames]

Please use the following tools to check you database.

http://support.ca.com/techbases/as2000/as2k-1001.html

Regards,
Jim P. Ames
True Data Storage Networks
Arcserve Service
Data Protection and Recovery
212.352.1780

http://www.truedatacorp.com

 

[BMW]

Hi,

I have used keybuild and other command line utilities many many times, can't solve the database corruption problem. Run pruning job with different interval, 30day,15day, 8day and 3day---no help. But every time I clean up the database(the fresh database size is about 2.5MB)then I can get a good full backup, and the most importantly, I can restore files from this backup. From my personal experience, there is relationship between database size and database corruption. The database size can not be bigger than 1.5GB. I would like to see if anybody out there has their database size bigger than 2GB without running into this kind of problem? Any more ideas?

Thanks!

 

[cdav]

I have certainly had this type of problem with the RAIMA databases. I am currently setting servers to use VLDB databases, with the intention of testing the corruption problems. I will let you know how I get on.
cdav

 

[Electro]

Hi BMW,

One thing you may have to do since you "upgraded" is possibly remove and reinstall Arcserve totally. This may be the only way to correct the problems you are having as there appears to be some leftover corruption from the former RAIMA database configuration. The database corruption issue has been one of Arcserves long outstanding issues which they still have not fixed properly.

When you reinstall Arcserve, make sure you backup your Jobs first to an alternate location. Once completed, perform the uninstall / reinstall of Arcserve and choose the VLDB database option. Once you have installed arcserve fresh you can backup the database folder to an alternate location. In the event of a database crash again, you can delete the database folder and then restore the database folder that you backed up. This will save you time in the future of having to completely reinstall Arcserve. We have performed this trick a few times now and it seems to work ok.

Also, remember when performing this procedure to have your engines stopped at this time. Restart the engines once the database folder has been put back into place.


Let me know how you make out.

Thanks!

Darryl Brambilla
EDS Canada
Darryl.Brambilla@eds.com