Hi,
I've read this thread with great interest, but was hoping to pick your collective brains further. I've "inherited" Arcserve and I've noticed loads of *.CAT files in the \ArcserveIT\temp folder - 2.49Gb worth! Yup, I guess my database has issues and would say housekeeping wasn't top of the agenda before. Same old story, can run a merge OK, but cannot drill down the restore tree. Data is present on the tape as I can select the top level box (i.e. all data within the session) and restore it that way, which on some sessions can be as much as 65Gb - I only need a .PST file. Following advice, I've started a database repair and left it a number of hours, but it doesn't appear to do a great deal at all. I've noticed there is a tab option to initialise the database. I've saved my job scripts away and am considering this option as a last resort but first need to know:
a) how long (v. roughly) would a repair and pack take on 2.49Gb of *.CAT files - I don't know how often people perform maintenance......I've previously read "weekly".
b) am I heading in the right direction with the database initialise idea because repair and pack will take eons? What are the issues with this option?
c) I've downloaded Service Pack 2a and was wondering if it's best to init the database and then apply this or just ignore the init and just apply the S.P. right now.
d) If S.P.2a is applied, I need to apply to all target servers as well I guess (?), which also means rebooting each server, impacting system availability?
If S.P.2a doesn't need a reboot post install, then I'll be sorted and will deploy it everywhere!
If you know answers to parts or all, please let me know. If I'm barking up the wrong tree and being a lamer, also please let me know.
Sparkler.