Networker 7.2 Diskbackup

[ToBe25]

Hi,

I have installed the Diskbackup Module for Networker 7.2 for Unix. I use normal file typ (not advanced).

I have created 6 Volumes, (2 for FS, 2 for DB and 2 for Archive) I created the pools, the label templates and the clients. Then I labeled the volumes for the pools.

Now I have some questions:

1.) Is there a possibility to limit the disk space which will be used for the backup in the Networker? Can I limit the space by adding a script and using unix tools?

2.)I put the retention and browse policy to 1 week. But it seems the Networker puts different times to the volumes, up to two weeks.

3.)Is there a way to switch to the next volume within a pool. So e.g. when a certain amount of data is reached.

4.)Is it possible for all pools to end up with the same expiration date? Is there a difference if I start the job manually?

Someone mentioned a paper from emc where more details for diskbackup are given (in the admin guide it's really short). I couldn't find this thing... Can someone email it to me?

Thanks

Toby

 

[Rif123]

1) You can set a limit on how much each disk device should use by specifying the default volume capacity on the device resource and relable the media. This only works for file type device, not advanced.

2) Retention works just as with tape. That is, the volume won't be recyclable until all the save sets on the media are recyclable. You can however remove expired save sets with nsrstage command from the disk device. (You can't do that on tapes of course). Try to check what save set has long retention (ie 2 weeks) with mminfo to correct it if it is a problem for you. It could be the index since that inherits the retention from the networker server's client definition.

3) With a file type device you will fill it up when the volume default capacity is reached. After that, NetWorker will continue on another piece of media in the same pool. Don't forget to set Volume Default Capacity for this to work!

4) You don't actually specify retention for the media. The media will be kept for as long as the longest retention of the save sets on the media. When all save sets has expired, the volume will be eligible for recycling. If you run an ad hoc backup, ie start a manual backup, it gets the longest browse/retention for that particular client as defined on the networker server. You can specify another browse/retention when you start the manual backup with the save command though.

All this is well documented in the Admin guide so you should be able to get the info from there. You could also read up on what the differences are for advanced file type device and 'normal' file type device. Usually the adft is a better choice for disk backup in larger scale.

 

[phbeauverd]

1) for Unix the best solution to limit disk space for a pool is to create separate file systems for each BackupToDisk device.