Unsolved
This post is more than 5 years old
2 Intern
•
2K Posts
0
517
November 10th, 2006 08:00
Backup Policy Suggestion
Hi,
I need to configure backups all windows 2003 & NW 7.3.2.
I need to take a full backup everyday on a new tape each saparate for each week day with a retention period of 35 days. I thought I will make a pool for each weekday but then I also do not want a tape used once to be appended again i.e. If I take a backup today, I do not want that the backup next monday gets appended in the same tape. Every backup has to happen on a new tape. One way I know is to mark the tape Read Only at the end of the backups so that it does not get accidentally appended. After 35 days, I would relabel these tapes but that needs too much of manual intervention.
Can anyone suggest a better of doing this?
I need to configure backups all windows 2003 & NW 7.3.2.
I need to take a full backup everyday on a new tape each saparate for each week day with a retention period of 35 days. I thought I will make a pool for each weekday but then I also do not want a tape used once to be appended again i.e. If I take a backup today, I do not want that the backup next monday gets appended in the same tape. Every backup has to happen on a new tape. One way I know is to mark the tape Read Only at the end of the backups so that it does not get accidentally appended. After 35 days, I would relabel these tapes but that needs too much of manual intervention.
Can anyone suggest a better of doing this?
0 events found
No Events found!
vsemaska
194 Posts
1
November 10th, 2006 08:00
We have a similar policy and a similar approach. What we do is use scripts to do this for us so manual intervention is minimal. Our tape library is a HP6060 and I'm running 7.2.2.
1) We have a 'Scratch' pool with 'Recycle to other pools' enabled. All tapes are initialized in that pool.
2) The pool that we use for backups, called Unix, has 'Recycle from other pools' enabled.
3) We have a script that will initialze 1 or more tapes into the Scratch pool. We load the tape library with tapes and run the script.
4) Another script runs in cron about 10 minutes before the start of the nightly backups. Any tapes found in the tape library that are in the 'Unix' pool are marked read-only. It's assumed someone forgot to remove the tapes.
5) When the backups run there will be no tapes available in the 'Unix' pool so Networker takes a tape from the 'Scratch' pool, initializes it into the 'Unix' pool, and then does the backups.
Hope that makes sense.
Vic
amediratta
2 Intern
•
2K Posts
0
November 10th, 2006 10:00
Would it be possible for you to share the scripts or hint some wys developing it. I have not done scripting before.
vsemaska
194 Posts
0
November 10th, 2006 11:00
The scripts are written in Korn shell for RedHat Linux and Tru64 Unix and you appear to be using Windows so they wouldn't be much good. Plus over time we've kept adding little features that make them rather complex. For you I think it'd be better to start by doing the steps manually at the command line and writing down what Networker utilities and their options you'll need to use. Then write the scripts for your environment.
I can suggest that you learn to use nsrjb as best you can since you'll be using that a lot. For example:
nsrjb -I - To do Inventory of the tapes in the jukebox.
nsrjb -o readonly -Y- To mark a tape in the jukebox read only.
nsrjb -L -v -Y -b "Scratch" - To label a tape and put it in the Scratch pool.
nsrjb -o recyclable -Y - To mark a tape recycable.
Forgot to mention that if you use the 'Scatch' pool method that you have to mark the tape 'recyclable' after you initialize them in the Scratch pool. Otherwise Networker won't use them for other pools.
Vic