Unsolved
This post is more than 5 years old
18 Posts
0
376
June 15th, 2010 09:00
Diskbackup and Archive retention
Hi all,
I have been tasked with finding the following solution using diskbackup and archiving (although if there is a better option than archiving i'm willing to go for it).
What we want is for our users to ask us to archive something to disk, which they tell us how long they want it to be kept for (due to clients only allowing us to keep data for x amount of time) and that they can restore themselves from disk. (There will only be a handful of users we trust who will be able to complete this part).
So the first part is easy, the PC support team will archive using Diskbackup to disk. Now the problem I am having is the retention. My idea was to create different Archive pools, each with it's own retention policy, however archives don't allow for a retention period.
We want the users to use archives as this makes it very easy for them to restore their own data, as they just type in the archive number given to them from the PC support team and get what they want.
Does anybody know of a way that this can be completed - like said earlier, it doesn't have to be using archives, so long as it's just as easy for the users to get their data back. This does have to go onto disk, and ideally have the data automatically deleted after x weeks\months from when the archive\backup was completed.
Any ideas appreciated.
Marc
coganb
736 Posts
0
June 17th, 2010 01:00
Hi Marc,
I think you're better off not using archiving, but using a standard backup. You can then set the retention date to whatever you want and NetWorker will deal with having this data deleted for you. If you only want a small group to be doing the recover operations, you can give them permissions to do so with the 'Recover local data' privilege which will give them permission to query the indexes and savesets for their own client and not other clients. You can check out the Admin Guide for this (for example, in the 7.6 Administration Guide, it's in the section 'NetWorker Server Management' - 'NetWorker User Groups'). There is also the equivalent 'Backup local data' privilege.
If you're worried that these recover operations will be too complicated for the users who are not familiar with NetWorker, you could write a few simple scripts that would allow them to, for example, run the mminfo command for them once they give the path or ssid as a parameter and then run the recover command for them when they've chosen what they want. It shoudn't be too complicated to script and there'd be less manual intervention for you long-term than having to to delete old stuff manually. If you only have a few users doing this, you could probably also get away with providing them with some written instructions on exactly what they need to do to recover - it's really not that complicated.
-Bobby