Bacula-users

[Bacula-users] Full backup forced if client changes

2012-03-24 17:12:21
Subject: [Bacula-users] Full backup forced if client changes
From: Steve Thompson <smt AT vgersoft DOT com>
To: bacula-users AT lists.sourceforge DOT net
Date: Sat, 24 Mar 2012 16:52:32 -0400 (EDT)
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 AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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