Re: [Bacula-users] Full backup forced if client changes
On Sat, 24 Mar 2012, James Harper wrote: 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? That's definitely going to confuse Bacula. As far as it is concerned you are backing up a separate client with separate storage. I still don't follow this. The client has changed, but everything else (pool, storage, catalog, etc) is the same. I don't see why a full backup is forced, or why bacula should be even slightly confused. Steve -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Full backup forced if client changes
2012/3/24 Steve Thompson s...@vgersoft.com 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? Avoid changing a client's name. You can change IP resolution or switch a dedicated backup client IP to the desired server. If this is a cluster you can use its framework for the job. best regards -- Radosław Korzeniewski rados...@korzeniewski.net -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Full backup forced if client changes
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Full backup forced if client changes
Bacula 5.0.2. For the following example job:
Job {
Name = cbe_home_a
JobDefs = defjob
Pool = Pool_cbe_home_a
Write Bootstrap = /var/lib/bacula/cbe_home_a.bsr
Client = clarke-fd
FileSet = cbe_home_a
Schedule = Saturday3
}
FileSet {
Name = cbe_home_a
Include {
Options {
wilddir = /mnt/cbe/home/a*
}
Options {
exclude = yes
RegexDir = .*
}
Options {
compression = GZIP
sparse = yes
noatime = yes
}
File = /mnt/cbe/home
}
}
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?
Steve
--
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Full backup forced if client changes
Bacula 5.0.2. For the following example job: snip 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? That's definitely going to confuse Bacula. As far as it is concerned you are backing up a separate client with separate storage. You might be able to invent a new name for the client and put it in /etc/hosts and change /etc/hosts when you want to back up via a different host. I'm not sure how that works for the fd-sd connection though. DNS with a very short TTL (eg measured in seconds) might work too, as long as you wait for a bit between changing the DNS entry and starting the backup. James -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
