Unsolved
This post is more than 5 years old
1 Rookie
•
14 Posts
0
1006
July 22nd, 2013 05:00
Managing tapes with NW
Hi
I am new with NW and I have a simple question. Where to start a configuration of backup to tape in my environment: NW 8.01, two tape drives, 20 slots, some sql clients, exchange and file server. What I need is as follows: Tapes are divided into 5 groups of four. It means that all backups should be done on those 4 tapes on friday(full) and incremental or transaction logs from 6 am to 20 pm every hour. I call this 4 tapes a "generation" . On saturday all tapes should be removed and send to a safe place. Another 4 tapes will be inserted for the next week.(second generation). And so on for 5 weeks. At the end of generation 5 the first 4 tapes will be inserted that means all data should be overwritten(a 30 day protection). In this scenario I have a restore for 35 days always available. In case of disaster a maximum of 7 day will be lost. This is the logic that our customer want to implement.
Thanks for any suggestion
Fausto
bingo.1
2.4K Posts
0
July 22nd, 2013 06:00
That means that you stay with one simple browse/retention policy (30 days) and you simply 'control the access' to the tapes. This means that you would only need one pool (you can use 'Default' which is already available). The only manual issues you have to perform are:
- export/eject the written tapes
- import the expired tapes
- relabel the retired tapes.
If you remove the fresh backup tapes on a daily base, this should be enough. Otherwise you must set them to full/readonly to force NW to begin with a new tape.
Let me suggest this configuration sequence:
- hardware (jukebox and devices)
- pool
- group(s)
- clients
goldrake1
1 Rookie
•
14 Posts
0
July 23rd, 2013 02:00
Hi
Thanks for the explanation. I did the configuration of hardware,all tapes
are now labeled with barcodes and members of Default media pool. A test
backup is working. I am a little confused about the Recycle interval under
Media Pool Properties -Default. It is set to 24 hours and can't be
modified. What does it mean? I want the data be protected for 30 day on
those set of tapes (4 tapes for my week-generation). I will remove the
fresh backup tapes one a week. I hope this make sense.
Thanks
Fausto
bingo.1
2.4K Posts
0
July 23rd, 2013 04:00
Most of the default resources cannot be modified at all. This is just a precaution.
Of course you may also use another pool where you my define another value.
The info in the online help is pretty limited. For full details you need the Admin Guide or even better the Command Line Reference (look for "nsr_pool").
"Recycling interval" is new to (me) and NW 8.0. It means that you can define a daily recycle operation which starts at "Recycle start" time. If you do not use it, NW will recycle a recyclable media when he needs it (ensuring the maximum security for your data).
bingo.1
2.4K Posts
0
July 23rd, 2013 06:00
As long as you do not set the "Recycle start" time, NW will not recycle anything in advance.
And do not forget that NW will prevent you from making changed to the pool "Default". If you really want to use that feature
you must use a new pool.
But do not forget - no backup software can restore from a (tape) media which has (accidentally) been overwritten.
goldrake1
1 Rookie
•
14 Posts
0
July 23rd, 2013 06:00
If I use Default media pool and Recycle interval is set to 24:00, can a
restore be done from those tapes?
goldrake1
1 Rookie
•
14 Posts
0
July 25th, 2013 00:00
Hi
I have an exchange 2010 to backup. In a test envirnment works fine, but in
a production i receive an error
NetWorker\nsr\bin\nsrsnap_vss_save.exe:
Original file name: nsrsnap_vss_save.exe
Version: 2.4.1.92
Comments: NetWorker Module for Microsoft Applications (x64)
50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not
specified. Assuming local host: exc01.mydomain.local
50412:nsrsnap_vss_save:nsrsnap_vss_save: Invalid argument: -g is specified
without snap_sessionID
50338:nsrsnap_vss_save:
usage: nsrsnap_vss_save []
50420:nsrsnap_vss_save: options:
50421:nsrsnap_vss_save:
The exchange client configuration is:
NSR_SNAP_TYPE=vss
NSR_EXCH_RETAIN_SNAPSHOTS=yes
NSR_ALT_PATH=f:\mount_dir
NSR_EXCH_CHECK=no
NSR_ESE_UTIL_SEQUENTIAL=False
NSR_ESE_UTIL_THROTTLE=False
NSR_CHECK_JET_ERRORS=none
Backup Type:
Microsoft Exchange Server
Deduplication:
None
Client Direct:
true
Pool:
Tape pool
Remote Access:
@
Browse Policy:
Month
Retention Policy:
Year
Schedule:
Default
Group:
What is wrong? Why I need a snapshot policy? NW should make a snapshot
before a backup starts.Where a snap_sessionID is configured?
Thanks
Fausto
bingo.1
2.4K Posts
0
July 25th, 2013 02:00
Are you sure you added the last message to the right thread? - How does it refer to the 'managing tape' issue?
BTW - NMM internally works with PowerSnap not VSS. Just look add the installed services and you will recognize the additional "NetWorker PowerSnap Service". The mechanism works different and that is why you now must use
- a Snapshot Group
- a Snapshot Policy
- a Snapshot Pool
But you may also use one of your existing pools for that purpose.