Hi Everyone,
Brief history I'm running Arcserve 2000 on a w2k box. I've had DB corruption before and had to run DBchecks and the keybuild which fixed my problem (word of advice to everyone, don't ever run a keybuild unless you have plenty of time. It ran for 3 days on a 5MB DB before finishing) Well my problem is the DB Pruning job now runs for hours. I have the DB Pruning job schedule to run at 5:00 am everyday for anything older than 30 days. It starts at 5 and is still running at 9. Then it finishes successfully? Has anyone seen this happening to them and is there a fix for it? Does this mean I still have DB corruption?
Thanks in advance.
Brief history I'm running Arcserve 2000 on a w2k box. I've had DB corruption before and had to run DBchecks and the keybuild which fixed my problem (word of advice to everyone, don't ever run a keybuild unless you have plenty of time. It ran for 3 days on a 5MB DB before finishing) Well my problem is the DB Pruning job now runs for hours. I have the DB Pruning job schedule to run at 5:00 am everyday for anything older than 30 days. It starts at 5 and is still running at 9. Then it finishes successfully? Has anyone seen this happening to them and is there a fix for it? Does this mean I still have DB corruption?
Thanks in advance.