B2D2T - last x days to backup
Hello,
This is probably really easy for you experts.
I have a 5Tb E: drive on the Backup server. Backupexec 2010 R3 is installed.
There are 20ish individual server backups that run from 16:00 - 04:00 - backing up to their own folder with E:\Backup. (e.g. E:\Backup\SERVER1). This runs fine. Servers are a mix of physical and VM's, but this shouldn't matter.
Backup jobs are set to hold the last 2-3 backup copies of each server on disk for ease of restoration (acknowledged that this retention period is short). So in essence, each servers folder on E: has 3 backup copies Day1, Day2 & Day3. Say the backup for SERVER1 is 40Gb, it only ever uses upto 120Gb on the disk as overwrites take place. This works fine.
I now wast to backup ONLY LAST NIGHTS (Day3) backup copy to tape. Tapes are changed daily and removed from site. It is preferred that FULL backups are taken. I've tried backing up the E: drive using the 'General' setting of 'Backup Method for files = Working set - last accessed in x Days" and set this to 1 day.
My plan was to send just files changed in the last 24 hours to tape. But this isn't happening. Checking the job monitor, the total size of last nights D2D backup was 1.1Tb. So I should only be sending 1.1Tb to tape. what is happening is I am sending the whole E: drive to tape, some 3.3Gb - which fills the tape drive.
Is there a setting for this - or will I have to create a set of subfolders per server (MTWTF) and set some additional backup jobs and BTD locations?
Cheers in advance
Tony
Do not flat file copy disk storage locations it is not a good idea
Please review this for why:
http://www.symantec.com/business/support/index?page=content&id=TECH176061
Run duplicate jobs in a policy linked to the original jobs to disk
Note: duplicate jobs do have advantages - if you flat file copy you have to restore the files to the media server, then sort out any problems relating to the above article then do another restore to the server that originally owned that data. Most types of duplicate job can be restored directly from the duplicate to the original servers/locations