Video Screencast Help

DLM is getting me down

Created: 25 Feb 2014 • Updated: 25 Feb 2014 | 3 comments

I feel like I'm trapped in a Catch-22 here...

I'm running Backup Exec 2012 in a Windows Server 2008 R2 environment with one 2003 R2 (6 servers total).  I want to run my backups in the following way and with the following resources:

1. Each server: Full Nightly backup to removable HDD, expires after one week from job scheduled start.

2. Each server: Full Weekly backup to removable HDD, expires after four weeks from job scheduled start.

3. Each server: Full Monthly backup to removable HDD, never expires.

The problem is twofold:

1. Expirations happen the planned time after the backup COMPLETES.  This is bad because there is no consistent predictablity as to when the backup expires.  My drives aren't large enough to hold two complete nights of backup sets, so the backup jobs fail on account of insufficient disk space.  I've already added the registry key to allow DLM to remove the most recent expired backup, but I can't see how that will help since the expiration period would happen after the backup jobs already tried to start...

2. The only way around this is to manually delete any backup sets in Windows when I rotate in the next hard drive and ignore the expirations.  I can't imagine this is healthy for my server and it is a royal pain to remember every single time.

Am I missing something obvious here?  Any workarounds or thoughts for my setup?



Operating Systems:

Comments 3 CommentsJump to latest comment

pkh's picture

Have you thought of getting bigger disks or more disks?  Deleting the existing backup set to accommodate the new one is bad because if the new backup is bad, you are left with no backup.

You should not delete backup sets from the disk.  This will leave orphaned entries in the BE console.  You should delete the backup sets from the BE console.  This will also delete the backup sets from the disk.

OJanicki's picture

pkh, thanks very much for your response.

Upgrading to 2 TB disks would work but the cost difference is hard to justify and would be a tough sell.  I'll do that as a last resort.

I am not worried about not having a good backup on the same disk because a different drive is used each night.  I use a nightly rotation of 5 drives, and a weekly rotation of 4 drives, so by the time I need to clear a backup set, the backup is at least a week old anyhow.  Because of this, DLM (which I like in principle) is proving a bit of a hinderance.

Deleting the unneeded backup sets from the console I can do.  But better still, is it possible to script an automated clearing process using the Backup Exec command line tools and Windows Task Scheduler?

pkh's picture

No. This cannot be done because you need to know which backup set to delete