Scheduled Utility Job to Erase B2D Files Independent of Backup Jobs
I have confirmed with Backup Exec Technical Support that there is no way to schedule a job to erase B2D files independent of a backup job.
Why would i need to do this? The answer is that to keep the B2D storage array (Overland REO 9000 in my case) optimized. Backup Exec doesn't erase B2D files until a job needs them or someone goes in and manually erases them. That results in space still being allocated to a B2D file, so the defragmentation utility (Diskeeper) cannot use this space to do its work. If the storage array that contains the B2D files is heavily utilized and little free space exists, Diskeeper cannot do its job effectively and cannot keep up with the ever-changing files created by Backup Exec.
Right now, the solution is to manually go into all media sets, sort by the Overwrite Protection Until column and identify the B2D files that are overwriteable, then select all that are in this status, and perform an Erase job.
There should be a job the could be scheduled to identify and erase B2D files that can run independent of a backup job, so that other system tools like Diskeeper can utilize the space to optimize the volume. I would anticipate scheduling this to run every 8 hours, as I have jobs running around the clock.
Thanks,
Kevin
Comments
I agree as I have a similar
I agree as I have a similar reason for this. In our organization, we are required to hold backups for only 3 weeks and NO MORE than 3 weeks. Hence even though there is plenty of disk space left, we need BackupExec to overwrite the expired backup sets rather than attempt to keep them out there for the longest amount of time possible.
With regular B2D backups, BackupExec seems to do a good job about reusing expired backup sets when you choose that option, but GRT backups complete ignore this option and continue to use new GRT backup sets without erasing expired backup sets, so we have to manually delete the expired GRT backup sets on a weekly basis.
Frustrating.
I have my GRT's going to a
I have my GRT's going to a seperate B2D Folder through a seperate job that just does Exchange and it overwrites the IMG folders just fine. My overwrite protection is set to partial with user prompt and I keep my GRT's for a week before they become overwriteable. I didnt setup any kind of low disk space thresholds or anything like that.
My policy is set to overwrite media and only points to the GRT folder. So my guess is however your backup is configured is the problem.
Prior to doing it this way I had exchange backed up as part or a larger backup and I too had the same issues but after resetting it up the way I listed above its worked wonderfully.
Would you like to reply?
Login or Register to post your comment.