That's an interesting question. The obvious answer is to just run an incremental backup, which will get all the files that are new/changed since the last incremental backup. EMC NetWorker does not do incremental forever, so you'd need to run a full backup now and then, but that could be monthy if your retention is long enough for monthly to make sense. In the old days people worried about the risk for N tapes, the mount time of N tapes, seek time of N tapes and so on.... but in a VTL or B2D world, the number of incrementals is essentially irrelevant. (If asked to recover files as of Friday, NetWorker won't bring back files that were in a Monday full but deleted on Wednesday, and each file is just recoverd once, from whatever backup is appropriate.)
That would seem to meet you need and foist the work off on the backup application.
It backs up files that were not backed up but are more than two days old, of couse. You'd wanted to exclude those (?).
Of course for ultimate control, you could generate a file of exactly what filenames to back up, as part of a kicked-off-from-the-client backup. See the -I flag on save. (Or you could look at pre/post processing for the group on the client, but that is probably more trouble than it's worth if this is all you're doing). Then use your power to exclude all files containg the letter 'Q' if you like.
If you get too fancy, there's a chance you might to trip yourself up on recovery. Think about what you want to recover: "Someone will always request 'Tuesday Files' and I'll never need to recover the whole share" or "Someone might want the whole share back, or a file where I'll know the name but not the date.".
If you're worried about space, EMC has two products that will remove duplication from the back end storage so that it doesn't much matter how many backups you do.
If you take a look at the save command you will see that there are various switches, etc. (Sorry I don't have the CLI manual n front of me). One thing is level and another is date. If you do level, but give no date it actually does a full backup. If you watch NetWorker, what it does is use the date/time stamp of the last backup for an incremental and backs up everything that has changed since that date/time. So, what you need to do is set it up so that it only backs up files that have changed in the last 48 hrs by modifying that date/time stamp.
You could do this in a coupleof ways, but my favourite would be to craete a script file that sits in the nsr directory called something like save48, and that runs the save command you wish. When you create the client, put save48 as the backup command, and you should be sweet.
reitmr
10 Posts
0
April 7th, 2010 15:00
Hello, Dave.
That's an interesting question. The obvious answer is to just run an incremental backup, which will get all the files that are new/changed since the last incremental backup. EMC NetWorker does not do incremental forever, so you'd need to run a full backup now and then, but that could be monthy if your retention is long enough for monthly to make sense. In the old days people worried about the risk for N tapes, the mount time of N tapes, seek time of N tapes and so on.... but in a VTL or B2D world, the number of incrementals is essentially irrelevant. (If asked to recover files as of Friday, NetWorker won't bring back files that were in a Monday full but deleted on Wednesday, and each file is just recoverd once, from whatever backup is appropriate.)
That would seem to meet you need and foist the work off on the backup application.
It backs up files that were not backed up but are more than two days old, of couse. You'd wanted to exclude those (?).
Of course for ultimate control, you could generate a file of exactly what filenames to back up, as part of a kicked-off-from-the-client backup. See the -I flag on save. (Or you could look at pre/post processing for the group on the client, but that is probably more trouble than it's worth if this is all you're doing). Then use your power to exclude all files containg the letter 'Q' if you like.
If you get too fancy, there's a chance you might to trip yourself up on recovery. Think about what you want to recover: "Someone will always request 'Tuesday Files' and I'll never need to recover the whole share" or "Someone might want the whole share back, or a file where I'll know the name but not the date.".
If you're worried about space, EMC has two products that will remove duplication from the back end storage so that it doesn't much matter how many backups you do.
Richard
Siobhan1
49 Posts
0
April 18th, 2010 16:00
If you take a look at the save command you will see that there are various switches, etc. (Sorry I don't have the CLI manual n front of me). One thing is level and another is date. If you do level, but give no date it actually does a full backup. If you watch NetWorker, what it does is use the date/time stamp of the last backup for an incremental and backs up everything that has changed since that date/time. So, what you need to do is set it up so that it only backs up files that have changed in the last 48 hrs by modifying that date/time stamp.
You could do this in a coupleof ways, but my favourite would be to craete a script file that sits in the nsr directory called something like save48, and that runs the save command you wish. When you create the client, put save48 as the backup command, and you should be sweet.
Siobhan