I have NW7.1.3 on Win2K3 SP1. I have do D2D backups and have now added a tape library in order to get the data offsite. I want to be able to create a tape(s) once a week so I have a reference point to go back to if needed. That way when the retention policy removes the data I want NW to know that the data is on a tape offsite. I am leaning towards Indexed Archiving since once I archive the data it does not follow the retention policy and will remain indexed with the client index. Is there a better method to the madness? Am I headed down the right road? Space is not an issue on my disk backups so I am not looking to free that space up.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Archive Module.
- Thread starter bse1969
- Start date
NO - The retention policy does NOT remove the media index entries - this is done only when you recycle/relabel the media. Just check your system. I bet you have a lot of recyclable save sets (and media)?
As this will save you money, how about a drink?
As this will save you money, how about a drink?
- Thread starter
- #3
If that is the case then when I have a client that has a 7 day retention policy. If I go in and look to see what is in the index for that client I only see 7 days worth of backups. So what your saying is that the others are still in the volume. They are just not reference by the index. What is happening when space is being reclaimed? I was under the assumption that it was removing data based on policies?
- Thread starter
- #5
The problem is I need to be able to dump off to tape once a week and the only way I could see doing that would be to set the high and low points, however, the amount of data I backup changes daily so it would be a constant battle. I need to be able to get what I back up offsite on a weekly basis. Only way I could find to do that was through archiving or possibly cloning. The only problem I saw with cloning was that at some point what was on tape would be removed from the index file, while with archive it is not. It may be worth having to run scanner for those once in a while restore where I have to go back a couple of months.
The retention policy defines how long a NW save set must not be overwritten.
If this has passed, and ALL save sets on the media expired, which will set the whole media to the state recyclable, NW MIGHT automatically recycle the media in case he needs it.
But he does not delete the index info before he overwrites the media.
Or think logically ... if NW would delete a recyclable media from the index, how else would it then remember if it needs such media for relabeling?
Or, even more straight, why does NW even want to know remember a recyclable media if it deletes this info from the index right away? Would not be logical, correct?
Just take a minute and test yourself: Set a media to recyclable - it is still there. If not, i'll buy you a drink.
If this has passed, and ALL save sets on the media expired, which will set the whole media to the state recyclable, NW MIGHT automatically recycle the media in case he needs it.
But he does not delete the index info before he overwrites the media.
Or think logically ... if NW would delete a recyclable media from the index, how else would it then remember if it needs such media for relabeling?
Or, even more straight, why does NW even want to know remember a recyclable media if it deletes this info from the index right away? Would not be logical, correct?
Just take a minute and test yourself: Set a media to recyclable - it is still there. If not, i'll buy you a drink.
- Thread starter
- #8
- Status