As Macina stated (this is a confirm)
when you create multiple instances of the same client there ISNT an
additional licensing requirement. (Legato keepts track of them with the
client id - all of the instances will have the same client id).
The way I would do it is to have mutpliple clients with a few of the
savesets in each of them. I would then have several schedules as well (to
ensure full / incremental /. differential backups) and then off course
either one group with all of the clients in (remember the differentiating
factor is te savesets - i.e. the savesets MUST be different for each client
instance to be in the same group) - or multple groups (I prefer this -
because it is easier for slow people like me to keep track off - and you can
then should you wish - send the date to different pools).
Enjoy !
Riaan
-----Original Message-----
From: David De Maeyer [mailto:ddm AT RUC DOT DK]
Sent: Friday, December 05, 2003 2:43 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] mail server backup issue
Hi again,
Well it costs nothing to try. I will try asap on another server and
check if that works.
Thanks a lot.
Regards,
David
On 5 Dec 2003, at 13:35, Macina, Conrad wrote:
> I'm no expert on Legato licensing, but I believe that creating an
> additional
> client definition for an existing client does not deplete your client
> licenses. If you have a 25 client license and create six clients named
> "mail1", for example, you still only use one client license and have 24
> remaining. At least, that's the way it appears to work with v6.1.3
> Power
> Edition.
>
>
> -----Original Message-----
> From: David De Maeyer [mailto:ddm AT ruc DOT dk]
> Sent: Friday, December 05, 2003 7:24 AM
> To: Legato NetWorker discussion; Conrad Macina
> Subject: Re: [Networker] mail server backup issue
>
>
> Hi Conrad,
>
> Thanks for the answer. As mentioned we were looking in the doc for a
> solution and as a matter of fact we found out that we could make use of
> the Saved Sets to tackle our problem. The only con is that we need
> several client definitions to achieve that and at the moment we don't
> have the necessary license to define new clients. But of course that's
> another "problem".
>
> Thanks again.
> Regards,
>
> David
>
> On 5 Dec 2003, at 13:08, Conrad Macina wrote:
>
>> Here's how I would do it (if I'm understanding the problem statement
>> correctly):
>>
>> 1. Set up Schedules called "Monday Full", "Tuesday Full", etc. You
>> didn't
>> say what you do on the days when you don't do full backups, but you
>> could
>> set the other days to "incr" or "skip", depending on your needs.
>>
>> 2. Then create a client definition for your a-f directories. Set the
>> Schedule to "Monday Full" and under Save sets include
>> /usr/mail/accounts/a
>> through /usr/mail/accounts/f. Create separate clients for g-m and the
>> rest
>> of your directories. All these clients can go in one group, or you can
>> create a separate group for each of them.
>>
>> 3. When the group runs you should get what you want.
>>
>> Conrad Macina
>> Pfizer, Inc.
>>
>>
>> On Thu, 4 Dec 2003 12:38:41 +0100, David De Maeyer <ddm AT RUC DOT DK> wrote:
>>
>>> Hi,
>>>
>>> We use NetWorker 6.1.3 to backup our mail server. Every week we run a
>>> full backup on the mail server (Linux). This is of course synonym of
>>> heavy load on the backup server the day we proceed with the full
>>> backup!
>>>
>>> We were considering splitting the full backup in several smaller
>>> "full"
>>> backups... and by doing so we could balance the load over several
>>> days.
>>>
>>> Taking a full backup of the mail server is basically taking a full
>>> backup of a directory called /usr/mail/accounts (for the example).
>>> The
>>> idea of splitting the backup came naturally because of the
>>> /usr/mail/accounts directory architecture:
>>>
>>> /usr/mail/accounts/a
>>> /usr/mail/accounts/b
>>> /usr/mail/accounts/c
>>> /usr/mail/accounts/d
>>> ...
>>> /usr/mail/accounts/y
>>> /usr/mail/accounts/z
>>>
>>> We would like - for example - to backup a-f accounts on Monday, g-m
>>> on
>>> Tuesday, etc... instead of taking a full backup on Thursday...
>>>
>>> We had a look in the docs but didn't find (yet) any "relevant" topic
>>> to
>>> put some light on that issue.
>>>
>>> Is is possible to define one directive telling the server to only
>>> backup /usr/mail/accounts/a to /usr/mail/accounts/f on Monday?
>>>
>>> Any help would be appreciated!
>>>
>>> server: NetWorker Server 6.1.3 + Solaris 2.8
>>> client: NetWorker Client 6.1.3 + Linux Debian 3.0
>>>
>>> Regards,
>>>
>>> David
>>>
>>>
>>> ___________________________________________________
>>> David De Maeyer
>>> Roskilde University Center
>>> Computer Science Department
>>> Box 260, Hus 42.1
>>> 4000 Roskilde
>>> Denmark
>>> voice (+45) 46 74 38 29 fax (+45) 46 74 30 72
>>>
>>> --
>>> Note: To sign off this list, send a "signoff networker" command via
>>> email
>>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>> http://listmail.temple.edu/archives/networker.html where you can
>>> also view and post messages to the list.
>>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>
>> --
>> Note: To sign off this list, send a "signoff networker" command via
>> email
>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>> http://listmail.temple.edu/archives/networker.html where you can
>> also view and post messages to the list.
>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>
> ___________________________________________________
> David De Maeyer
> Roskilde University Center
> Computer Science Department
> Box 260, Hus 42.1
> 4000 Roskilde
> Denmark
> voice (+45) 46 74 38 29 fax (+45) 46 74 30 72
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
___________________________________________________
David De Maeyer
Roskilde University Center
Computer Science Department
Box 260, Hus 42.1
4000 Roskilde
Denmark
voice (+45) 46 74 38 29 fax (+45) 46 74 30 72
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
