Bacula-users

Re: [Bacula-users] Full backup forced if client changes

2012-03-25 05:26:21
Subject: Re: [Bacula-users] Full backup forced if client changes
From: Thomas Mueller <thomas AT chaschperli DOT ch>
To: bacula-users AT lists.sourceforge DOT net
Date: Sun, 25 Mar 2012 09:24:03 +0000 (UTC)
Am Sat, 24 Mar 2012 16:52:32 -0400 schrieb Steve Thompson:

> Bacula 5.0.2. For the following example job:
> 
...
> }
> 
> more than one client is available to backup the (shared) storage. If I
> change the name of the client in the Job definition, a full backup
> always occurs the next time a job is run. How do I avoid this?

i would run the bacula-fd (maybe a second instance to not intefere with 
other backups on the node) with the same configuration on every shared 
storage node where you would like to backup the storage and setup an DNS 
entry to point at the desired node.

- Thomas


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>