FunkiMunki
Technical User
We have Arcserve 11.1 running on a Windows 2000 Server (SP4) with another Windows 2000 Server (SP4) running SQL 2000 holding the Arcserve database.
The prune job doesn't run at all, no errors, just doesn't run. The backup server can communicate fine with the SQL server and has no problems accessing the database - proof of which is the 18GB (we backup a LOT) database that has been created over the last 5 months...
I've contacted Computer Associates tech support and logged a call. They recommended 3 patches that should fix it - Service Pack 1, Discovery Service Security Patch, Device Support Update. I have applied these patches, none fixed the problem. They are currently working on a solution but seem to be taking their time. I've tried contacting them for an update but have been told numerous times their technician would call me back - they never have. This is my first dealing with CA Tech Support and so far I'm not too impressed.
Anyway, I was wondering if anyone here has experienced a similar problem when using SQL as the database store? I don't want to use the VLDB as I think it's awful. Especially at the size of our database.
Any advice is greatly appreciated.
Thanks
The prune job doesn't run at all, no errors, just doesn't run. The backup server can communicate fine with the SQL server and has no problems accessing the database - proof of which is the 18GB (we backup a LOT) database that has been created over the last 5 months...
I've contacted Computer Associates tech support and logged a call. They recommended 3 patches that should fix it - Service Pack 1, Discovery Service Security Patch, Device Support Update. I have applied these patches, none fixed the problem. They are currently working on a solution but seem to be taking their time. I've tried contacting them for an update but have been told numerous times their technician would call me back - they never have. This is my first dealing with CA Tech Support and so far I'm not too impressed.
Anyway, I was wondering if anyone here has experienced a similar problem when using SQL as the database store? I don't want to use the VLDB as I think it's awful. Especially at the size of our database.
Any advice is greatly appreciated.
Thanks