Hello all...
I'm running Arcserve BAB v9 (patched SP4)on Windows 2000 Server with an STK L80 with 2 LTO drives.
Has anyone had a problem where the pruning job, prunes last nights backup? I have had this problem intermittently but have not been able to nail down when or why this happens.
I only see that in the Brightstor.log file that the tapes from last night were pruned (occassionaly) even when I've set the pruning to only prune records older than 61 days.
I have more than sufficient disk space for the database and the pruning job starts about an hour before the backup.
Now, I'm sure you all know that CA says that you shouldn't grow your database that big and its not recommended that you increase the default of 30 days but even when I run the database utilities to check the databases (every week) without any errors I might add... I still have this intermittent problem. Maybe they should change the name from VLDB to VSDB (Very Small DataBase?)
CA has been as usual, f'n useless in so much as to tell me to initialize the databases - gee thanks! So now I've had to start from scratch again but with no solution.
Any help would be greatly appreciated.
Carson
I'm running Arcserve BAB v9 (patched SP4)on Windows 2000 Server with an STK L80 with 2 LTO drives.
Has anyone had a problem where the pruning job, prunes last nights backup? I have had this problem intermittently but have not been able to nail down when or why this happens.
I only see that in the Brightstor.log file that the tapes from last night were pruned (occassionaly) even when I've set the pruning to only prune records older than 61 days.
I have more than sufficient disk space for the database and the pruning job starts about an hour before the backup.
Now, I'm sure you all know that CA says that you shouldn't grow your database that big and its not recommended that you increase the default of 30 days but even when I run the database utilities to check the databases (every week) without any errors I might add... I still have this intermittent problem. Maybe they should change the name from VLDB to VSDB (Very Small DataBase?)
CA has been as usual, f'n useless in so much as to tell me to initialize the databases - gee thanks! So now I've had to start from scratch again but with no solution.
Any help would be greatly appreciated.
Carson