Video Screencast Help

Expired Backup to Disk Jobs

Created: 09 Jun 2014 | 1 comment

I am reasonably new to the backup to disk side of BE and would like to know about Storage pools.

 

For example, if I have 10 disks in the default 'Any disk storage' pool, and point my backups at the 'Any disk storage' so they just use the next available disk, when BE comes to expire jobs after say, 2 weeks, will it just look at the age of any of the backup files and get rid, or will the backup job that relates to the specific backup file on disk expire it's own jobs?

I can't think of any other way of describing this. What i suppose i want to know is, is it a good idea to create different storage pools for your different types of backup.

Thanks for reading

Operating Systems:

Comments 1 CommentJump to latest comment

Colin Weaver's picture

BE looks at the catalog of the backup set which contains the expiry date and if something is expired it then goes to the disk storage device to reclaim (delete) it, we then remove the catalog as well. For most disk storage devices the process to identify expired backup sets happens every 4 hours and is not linked to a backup job at all. There is a slight diffference for Removable Storage (such as RDX) where we only do the check as job requires (at start of each job/backup set) instead of every 4 hours

I would recommend upgrading to BE 2014 as the load balancing within a disk storage pool in BE 2012 is bacically: continue using 1 disk until it is full (probably causing a job failure when it fills). 2014 however gives round robin , least space first and most space first abilities.

As you can't put multiple disk storage devices on one volume to use separate pools for different job types would need a lot of volumes. However really there is no best practice for creating lots of pools vs only 1 pool. That is really down to how you want to manage your backups