Maarten Boot (CWEU-USERS/CWNL) wrote:

>Hi Bill,
>
>In my case I solved it by creating 28 schedules FULL_01 till FULL28 with a 
>full backup on that day of the month and level 5 once a week and incremental 
>on any other day.
>
>I then assigning a whole server  to a particular day, if they are not to big.
>If they are to big I assign individual savesets of the server to a particular 
>day.
>
>e.g server1 is a small one so is server2 but server3 is big.
>
>FULL_01: server1: All
>FULL_02: server2: All
>FULL_03: server3: C:\
>FULL_04: server3: D:\
>FULL_05: server3: E:\
>
>in this way each server has a full backup once a month (a requirement here) 
>
>I can do this as I plan beforehand that volumes do not become to big for the 
>backup window between 21:00 and 07:00.
>
>I also created a small script that suggests which schedule has the least 
>amount of clients. This helps me balancing the load a bit between days.
>
>Maarten
>
>On Monday 13 March 2006 15:46, Bill Hewitt wrote:
>  
>
>>In an ideal world I would like to split up the full backups of my
>>fileservers such that they back up a few filesystems
>>a night rather than all at one go.
>>Can anybody suggest ways to script this ?
>>One approach is to use the networker scheduling to run a full backup
>>every night and then use nsradmin to change the
>>list of save sets that are going to be backed up on a daily basis i.e.
>>
>>on the fist of the month, generate a list of filesystems to be backed up
>>each night, take 3 filesystems from the to of the list and put them into
>>the savesets attribute for that group on a client
>>remove successfuly backed up filesystems from the list.
>>
>>editing a clients resourses automatically by script isn't that easy if a
>>client is in more than one group as the resorses for that client are
>>repeateded for each group.
>>
>>The second option is not to use the networker scheduling at all, but to
>>run save, or savefs from a script.
>>
>>Do other folk do this kind of thing? If they do, what approach do they
>>use ?
>>
>>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 wit 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
>>    
>>
>
>  
>
our setup is rather bigger than that. I want to do something like

FULL BACKUPS DAY 1

server1:filesystem 1
server1:filesystem 2
server2:filesystem 1
server2:filesystem 2
server3:filesystem 1
server3:filesysem 2
server3:filesystem 3

DAY 2

server1:filesystem 3
server1:filesystem 4
server2:filesystem 3
server2:filesystem 4
server3:filesystem 4
server3:filesysem 5
server3:filesystem 6

DAY 10


server1:filesystem 21
server1:filesystem 22
server2:filesystem 21
server2:filesystem 22
server3:filesystem 31
server3:filesysem 32
server3:filesystem 33


etc etc

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
wit 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