Networker

[Networker] SV: [Networker] SV: [Networker] SV: [Networker] Backup to Adv-file device

2009-01-04 14:16:46
Subject: [Networker] SV: [Networker] SV: [Networker] SV: [Networker] Backup to Adv-file device
From: Ben Deng <BD AT DBC DOT DK>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Sun, 4 Jan 2009 20:13:21 +0100
Thanks Davina and all other who is trying to help,

Using staging to move the oldest savesets to another volume may help, I´ll try 
to implement it if it will not put to much load on the other volumes which are 
under backupstream from other backupgroups.


Regards,
Ben



-----Oprindelig meddelelse-----
Fra: Davina Treiber [mailto:Davina.Treiber AT PeeVRo.co DOT uk] 
Sendt: 2. januar 2009 12:31
Til: EMC NetWorker discussion; Ben Deng
Emne: Re: [Networker] SV: [Networker] SV: [Networker] Backup to Adv-file device

Ben Deng wrote:
> I´ve already went through some of these suggestions and didn´t get a working 
> solution because:
> 
> -Changing my deletescript from 28 days to a shorter day may or may not 
> release spaces to a waiting backupgroup, because the those savesets being 
> deleted isn´t necessary coming from the volume needed. And I´ve already a mix 
> of deletescripts implemented (28 days, 14 days and 7 days). The reason  we 
> decide to use cloning instead of staging  is offsite tape  location policy. 
> Tapes for a weeks backup will be move out of out company and keeping save in 
> outside location.
> 
> -Distribute the backup process is already implemented as far as it can be, 
> the problem is when a volume have only 200GB space left and out Oracle backup 
> needs 300GB, the backup process will stop after the use of 200GB. 200GB is 
> normally adequate for other backup clients, so it will be waist of many GB if 
> I always reserve enough space in all volume for our Oracle DB. I wish 
> Networker have a spacecheck feature before it starts to make backup to a 
> device.
> 
> -We are using Windows 2003 as Networker host and those volumes are located in 
> 2 of our Nexsan Satabeast disksystems. Therefore it will be difficult to make 
> a single volume. Even if we could it will then suffer from performance 
> impact. I´ve already tested it before installing out Networker host.
> 


The solution to your problem is to set up a staging policy for each of
your disk volumes so that when it gets X% full it clears space by
staging some of the oldest save sets to one of the other volumes in the
same pool. This is easily done from the GUI without any need for
scripting. This has the effect of load-balancing your disk volumes if
they get slightly out-of-step. You should still try to configure your
backups so that they distribute over multiple volumes, but this will
sort out the imbalance. It should not result in a large amount of
staging activity.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER