VLDB to SQL

[peeky1323]

Hi,

I am sure this has been asked a millions times but I wanted to know peoples feelings about using SQL server instead of the native VLDB. This would be for ARCserve 11.1. I am having a nightmare with the VLDB. Our database runs at about 8GB. I try to run the maintenance utilities but they take 36 hours to complete which is not acceptable.

I want to change to SQL but wanted to hear peoples comments (whether good or bad).

Cheers,

Matt

 

[davidmichel]

At that size either go to SQL or Enable Catalog Databases.

Catalog DB is enabled via ARCserve Server Admin, Configuration, Database, click the check box.

Than catalog files are saved to a directory on disk. Only summary information is merged into the database. If you need to restore the detailed information is automatically merged into the database.

By the way SP1 for 11.1 is out.

 

[peeky1323]

Thanks, I just installed SP1 to try and resolve a E3717 error on restore. CA support told me it would fix this....but it didn't. I also upgraded the firmare on my drive with no affect.

 

[vschumpy]

SQL is more manageable/scalable - but you'd expect that from an full Enterprise database that costs a fair bit for a licence, as opposed to something you get 'free' with the product On the flip side - SQL will suck up a fair amount of memory and CPU - so you need to make sure it is running on a system that has spare capacity to handle this.

As has already been mentioned - catalog.db is another way out - you only merge the session detail you want - when you need them - the cat files are stored on disk in compressed format (a lot smaller then when they are expanded into the actual DB) and if you need to browse the contents of the tape the merge will ask you if you want to merge the info, and then should automatically merge the already existing file on disk to the database.