[Bacula-users] Handle files that have st_ctime changed often in bacula

2014-12-04 Thread Sieu Truc
Hello,

I have a problem when bacula tried to backup a folder that contains some
files changed often.

For example: i backup the folder /var/samba

And for some reason, some big files in this folder are accessed by other
programs and therefore their attribute chang (st_atime) is changed. As a
consequence of that, bacula backups that file in the following incremental
backup.


The final result is that those such files eat up all of my disk space.

In my opinion, i have 2 ways to solve that problem but i dont know if
they're feasible.
1) Do a full backup, but incremental backup don't include those files .  Is
it possible to create a fileset for a full backup and another fileset for
the incrementals.for that case ?

2) In the fileset, those files will be treated in a different way like the
configuation below:

FileSet {
Name = fs_samba_system

File = /var/samba
Include {
Options {
signature = SHA1
onefs = no
Wildfile = *badFile.pdf
  Exclude = yes
}
}
Include {
File = /var/samba
Options {
WildFile = *badFile.pdf
Signature = SHA1
mtimeonly=yes
}
Options {
Exclude = yes
RegexFile = .*
}
}

} Is it right for what i described above ?

and is there another better solution ?

Thanks in advance,

Truc
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume

2014-11-19 Thread Sieu Truc
Thanks to Ana,

It works without any problem now.

But what do you mean Label Format clauses are strange. Are you sure
whether the same volume is reused ?

Does bacula detect Maximum Volumes greater than 1 so il will automatically
add the number after ?

For ex: monday-2014-11-17001 and monday-2014-11-1700.

Truc

On Tue, Nov 18, 2014 at 7:57 PM, Martin Simmons mar...@lispworks.com
wrote:

 Also, I think those Label Format clauses are strange when used with
 Recycle =
 yes.  The volumes will be labelled forever with the creation date
 (e.g. monday-2014-11-17), not the recycling date.

 __Martin


  On Tue, 18 Nov 2014 13:51:57 -0300, Ana Emília M. Arruda said:
 
  Yes, you are correct. That was exactly what ocurred. If you want a 13
 days
  retention period for your incremental jobs, you will have to configure
  a Maximum
  Volumes of 2. Also, you have different retention periods for incremental
  and full backups (me too). So I would recommend you to have different
 pools
  for your full and incremental backups.
 
  Best regards,
  Ana
 
  On Tue, Nov 18, 2014 at 1:35 PM, Sieu Truc sieut...@gmail.com wrote:
 
   Yes, the actual value is 13, and it caused the problem.
  
   In my opinion,  the first week , bacula created successfully the monday
   incremental backup, and its status was USED but it had to be wait 13
 days.
   During that time, in the second week, bacula tried to write again to
 the
   same volume that is not pruned so it caused the problem. And maybe it
 hangs
   the remain jobs.
  
   Is it right ?
  
   Or do you have any suggestion ?
  
   Truc
  
   On Tue, Nov 18, 2014 at 5:27 PM, Ana Emília M. Arruda 
   emiliaarr...@gmail.com wrote:
  
   Hi Sieu,
  
   If you have changed the volume retention for your volumes in the
 pool
   configuration, this change only is applied to new volumes created.
 For the
   volumes that were already in the catalog, you should run an update
 volume
   through bconsole and change this value there too.
  
   Since you said that you have changed from 6 to 13 days your retention
   periods, I´m supposing maybe this is your problem with  is waiting
 on
   max storage jobs.
  
   Best regards,
   Ana
  
   On Tue, Nov 18, 2014 at 12:39 PM, Sieu Truc sieut...@gmail.com
 wrote:
  
   sorry for my mistake, in the pools.conf, the value of parameter
 Volume
   Retention is all 13 days, not 6 days as above.
  
   Truc
  
   On Tue, Nov 18, 2014 at 4:34 PM, Sieu Truc sieut...@gmail.com
 wrote:
  
   Hello,
  
   I have a schedules.conf like
  
   #
   # Planification des sauvegardes nfs.
   #
   Schedule {
   Name = schedule_intra1
   Run = Level=Incremental Pool=lundi Monday at 22:00
   Run = Level=Incremental Pool=mardi Tuesday at 22:00
   Run = Level=Incremental Pool=mercredi Wednesday at 22:00
   Run = Level=Incremental Pool=jeudi Thursday at 22:00
   Run = Level=Incremental Pool=vendredi Friday at 22:00
   Run = Level=Incremental Pool=samedi Saturday at 22:00
   Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10 w12
 w14
   w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48
 w50 w52
   Sunday at 22:00
   Run = Level=Full Pool=dimanche_impair w01 w03 w05 w07 w09
 w11
   w13 w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45
 w47 w49
   w51 w53 Sunday at 22:00
   }
  
   Schedule {
   Name = schedule_intra2
   Run = Level=Incremental Pool=monday Monday at 22:10
   Run = Level=Incremental Pool=tuesday Tuesday at 22:10
   Run = Level=Incremental Pool=wednesdayi Wednesday at 22:10
   Run = Level=Incremental Pool=thursday Thursday at 22:10
   Run = Level=Incremental Pool=friday Friday at 22:10
   Run = Level=Incremental Pool=saturday Saturday at 22:10
   Run = Level=Full Pool=sunday_even w02 w04 w06 w08 w10 w12
 w14
   w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48
 w50 w52
   Sunday at 22:10
   Run = Level=Full Pool=sunday_odd w01 w03 w05 w07 w09 w11 w13
   w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47
 w49 w51
   w53 Sunday at 22:10
   }
  
  
   And here the definitions of the pools are:
  
   Pool {
   Name = monday
   Pool Type = Backup
   AutoPrune = yes
   Volume Retention = 6 days
   Volume Use Duration = 1 days
   Recycle = yes
   #recyclepool= lundi
   Maximum Volumes = 1
   Recycle Current Volume = yes
   Label Format = monday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
   }
  
   Pool {
   Name = tuesday
   Pool Type = Backup
   AutoPrune = yes
   Volume Retention = 6 days
   Volume Use Duration = 1 days
   Recycle = yes
   #recyclepool= mardi
   Maximum Volumes = 1
   Recycle Current Volume = yes
   Label Format =
 tuesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
   }
   Pool {
   Name = wednesday
   Pool Type = Backup
   AutoPrune = yes
   Volume Retention = 6 days
   Volume Use Duration = 1

[Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume

2014-11-18 Thread Sieu Truc
Hello,

I have a schedules.conf like

#
# Planification des sauvegardes nfs.
#
Schedule {
Name = schedule_intra1
Run = Level=Incremental Pool=lundi Monday at 22:00
Run = Level=Incremental Pool=mardi Tuesday at 22:00
Run = Level=Incremental Pool=mercredi Wednesday at 22:00
Run = Level=Incremental Pool=jeudi Thursday at 22:00
Run = Level=Incremental Pool=vendredi Friday at 22:00
Run = Level=Incremental Pool=samedi Saturday at 22:00
Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10 w12 w14 w16
w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52
Sunday at 22:00
Run = Level=Full Pool=dimanche_impair w01 w03 w05 w07 w09 w11 w13
w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51
w53 Sunday at 22:00
}

Schedule {
Name = schedule_intra2
Run = Level=Incremental Pool=monday Monday at 22:10
Run = Level=Incremental Pool=tuesday Tuesday at 22:10
Run = Level=Incremental Pool=wednesdayi Wednesday at 22:10
Run = Level=Incremental Pool=thursday Thursday at 22:10
Run = Level=Incremental Pool=friday Friday at 22:10
Run = Level=Incremental Pool=saturday Saturday at 22:10
Run = Level=Full Pool=sunday_even w02 w04 w06 w08 w10 w12 w14 w16
w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52
Sunday at 22:10
Run = Level=Full Pool=sunday_odd w01 w03 w05 w07 w09 w11 w13 w15
w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51 w53
Sunday at 22:10
}


And here the definitions of the pools are:

Pool {
Name = monday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= lundi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = monday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}

Pool {
Name = tuesday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= mardi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = tuesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}
Pool {
Name = wednesday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= mercredi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = wednesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}
Pool {
Name = thursday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= jeudi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = thursday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}
Pool {
Name =friday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= vendredi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = friday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}
Pool {
Name = saturday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= samedi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = saturday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}

Pool {
Name = sunday_even
Pool Type = Backup
AutoPrune = yes
Volume Retention = 13 days
Volume Use Duration = 1 days
Recycle = yes
recyclepool= dimanche_pair
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = sunday_even-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}

Pool {
Name = sunday_odd
Pool Type = Backup
AutoPrune = yes
Volume Retention = 13 days
Volume Use Duration = 1 days
Recycle = yes
recyclepool= dimanche_impair
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = sunday_odd-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}

storages.conf
 Storage {
Name = FileStorage
Address = 192.168.56.10
SDPORT = 9103
Password = test
Device = FileStorage
Media Type = File
}

There wasn't any problem in the first week, but since the second week, i
got a lot of messages of is waiting on max storage jobs from almost the
jobs.

Some of them got is waiting for an appendable volume

Can you suggest me what to solve it ?

Truc
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE

Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume

2014-11-18 Thread Sieu Truc
sorry for my mistake, in the pools.conf, the value of parameter Volume
Retention is all 13 days, not 6 days as above.

Truc

On Tue, Nov 18, 2014 at 4:34 PM, Sieu Truc sieut...@gmail.com wrote:

 Hello,

 I have a schedules.conf like

 #
 # Planification des sauvegardes nfs.
 #
 Schedule {
 Name = schedule_intra1
 Run = Level=Incremental Pool=lundi Monday at 22:00
 Run = Level=Incremental Pool=mardi Tuesday at 22:00
 Run = Level=Incremental Pool=mercredi Wednesday at 22:00
 Run = Level=Incremental Pool=jeudi Thursday at 22:00
 Run = Level=Incremental Pool=vendredi Friday at 22:00
 Run = Level=Incremental Pool=samedi Saturday at 22:00
 Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10 w12 w14
 w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52
 Sunday at 22:00
 Run = Level=Full Pool=dimanche_impair w01 w03 w05 w07 w09 w11 w13
 w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51
 w53 Sunday at 22:00
 }

 Schedule {
 Name = schedule_intra2
 Run = Level=Incremental Pool=monday Monday at 22:10
 Run = Level=Incremental Pool=tuesday Tuesday at 22:10
 Run = Level=Incremental Pool=wednesdayi Wednesday at 22:10
 Run = Level=Incremental Pool=thursday Thursday at 22:10
 Run = Level=Incremental Pool=friday Friday at 22:10
 Run = Level=Incremental Pool=saturday Saturday at 22:10
 Run = Level=Full Pool=sunday_even w02 w04 w06 w08 w10 w12 w14 w16
 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52
 Sunday at 22:10
 Run = Level=Full Pool=sunday_odd w01 w03 w05 w07 w09 w11 w13 w15
 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51 w53
 Sunday at 22:10
 }


 And here the definitions of the pools are:

 Pool {
 Name = monday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= lundi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = monday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }

 Pool {
 Name = tuesday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= mardi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = tuesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name = wednesday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= mercredi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = wednesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name = thursday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= jeudi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = thursday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name =friday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= vendredi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = friday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name = saturday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= samedi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = saturday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }

 Pool {
 Name = sunday_even
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 13 days
 Volume Use Duration = 1 days
 Recycle = yes
 recyclepool= dimanche_pair
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format =
 sunday_even-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }

 Pool {
 Name = sunday_odd
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 13 days
 Volume Use Duration = 1 days
 Recycle = yes
 recyclepool= dimanche_impair
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = sunday_odd-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }

 storages.conf
  Storage {
 Name = FileStorage
 Address = 192.168.56.10
 SDPORT = 9103
 Password = test
 Device = FileStorage
 Media Type = File
 }

 There wasn't any problem in the first week, but since the second week, i
 got a lot of messages of is waiting on max storage jobs from almost the
 jobs.

 Some of them got is waiting for an appendable volume

 Can you suggest me what to solve it ?

 Truc

--
Download BIRT iHub F-Type

Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume

2014-11-18 Thread Sieu Truc
Yes, the actual value is 13, and it caused the problem.

In my opinion,  the first week , bacula created successfully the monday
incremental backup, and its status was USED but it had to be wait 13 days.
During that time, in the second week, bacula tried to write again to the
same volume that is not pruned so it caused the problem. And maybe it hangs
the remain jobs.

Is it right ?

Or do you have any suggestion ?

Truc

On Tue, Nov 18, 2014 at 5:27 PM, Ana Emília M. Arruda 
emiliaarr...@gmail.com wrote:

 Hi Sieu,

 If you have changed the volume retention for your volumes in the pool
 configuration, this change only is applied to new volumes created. For the
 volumes that were already in the catalog, you should run an update volume
 through bconsole and change this value there too.

 Since you said that you have changed from 6 to 13 days your retention
 periods, I´m supposing maybe this is your problem with  is waiting on
 max storage jobs.

 Best regards,
 Ana

 On Tue, Nov 18, 2014 at 12:39 PM, Sieu Truc sieut...@gmail.com wrote:

 sorry for my mistake, in the pools.conf, the value of parameter Volume
 Retention is all 13 days, not 6 days as above.

 Truc

 On Tue, Nov 18, 2014 at 4:34 PM, Sieu Truc sieut...@gmail.com wrote:

 Hello,

 I have a schedules.conf like

 #
 # Planification des sauvegardes nfs.
 #
 Schedule {
 Name = schedule_intra1
 Run = Level=Incremental Pool=lundi Monday at 22:00
 Run = Level=Incremental Pool=mardi Tuesday at 22:00
 Run = Level=Incremental Pool=mercredi Wednesday at 22:00
 Run = Level=Incremental Pool=jeudi Thursday at 22:00
 Run = Level=Incremental Pool=vendredi Friday at 22:00
 Run = Level=Incremental Pool=samedi Saturday at 22:00
 Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10 w12 w14
 w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52
 Sunday at 22:00
 Run = Level=Full Pool=dimanche_impair w01 w03 w05 w07 w09 w11
 w13 w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49
 w51 w53 Sunday at 22:00
 }

 Schedule {
 Name = schedule_intra2
 Run = Level=Incremental Pool=monday Monday at 22:10
 Run = Level=Incremental Pool=tuesday Tuesday at 22:10
 Run = Level=Incremental Pool=wednesdayi Wednesday at 22:10
 Run = Level=Incremental Pool=thursday Thursday at 22:10
 Run = Level=Incremental Pool=friday Friday at 22:10
 Run = Level=Incremental Pool=saturday Saturday at 22:10
 Run = Level=Full Pool=sunday_even w02 w04 w06 w08 w10 w12 w14
 w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52
 Sunday at 22:10
 Run = Level=Full Pool=sunday_odd w01 w03 w05 w07 w09 w11 w13 w15
 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51 w53
 Sunday at 22:10
 }


 And here the definitions of the pools are:

 Pool {
 Name = monday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= lundi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = monday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }

 Pool {
 Name = tuesday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= mardi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = tuesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name = wednesday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= mercredi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format =
 wednesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name = thursday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= jeudi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = thursday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name =friday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= vendredi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = friday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }
 Pool {
 Name = saturday
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 6 days
 Volume Use Duration = 1 days
 Recycle = yes
 #recyclepool= samedi
 Maximum Volumes = 1
 Recycle Current Volume = yes
 Label Format = saturday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
 }

 Pool {
 Name = sunday_even
 Pool Type = Backup
 AutoPrune = yes
 Volume Retention = 13 days
 Volume Use Duration = 1 days
 Recycle = yes

Re: [Bacula-users] Recover full backup from the incrementals

2014-10-16 Thread Sieu Truc
Thank for your answer, it gets me more understanding bacula.

But now, if i have 2 full backups like

Schedule {
Name = schedule_test
Run = Level=Incremental Pool=Monday Monday at 22:00
Run = Level=Incremental Pool=Tuesday Tuesday at 22:00
Run = Level=Incremental Pool=Wednesday Wednesday at 22:00
Run = Level=Incremental Pool=Thursday Thursday at 22:00
Run = Level=Incremental Pool=Friday Friday at 22:00
Run = Level=Incremental Pool=Saturday Saturday at 22:00
Run = Level=Full Pool=even_sunday w02 w04 w06 w08 w10 w12 w14 w16 w18
w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50 w52 Sunday
at 22:00
Run = Level=Full Pool=odd_sunday w01 w03 w05 w07 w09 w11 w13 w15 w17
w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51 w53
Sunday at 22:00
}

After 3 week, i have 3 full backups named even_sunday_1, odd_sunday_2 ,
even_sunday_3.
If i lose odd_sunday_2, can i recover it from even_sunday_1 and the
incremental backups during 2 weeks ? The incrementals of the second week
are based on the odd_sunday_2 so can they be applied to even_sunday_1 ?

Thanks in advance,

PHAM Ngoc Truc

On Wed, Oct 15, 2014 at 5:53 PM, Bryn Hughes li...@nashira.ca wrote:

  Really it would come down to what files you needed to restore...

 If the files you need are all in the incremental then Bacula will restore
 them without touching the full backup at all.

 If you need to restore a full filesystem including files that will not
 have changed since the last full, you will possibly loose some data,
 depending on what has changed.

 In the scenario you are talking about (w2 being damaged), you could do a
 full restore of w1 plus the incrementals that depended on it which would
 take you to the end of Saturday, and then you could do a restore of all the
 incrementals going forwards from there.  You would miss any data changed
 after the Saturday incremental run after w1 but before the full w2 was run
 - the first incremental after w2 would have caught any changes after w2.
 So you would loose about a day's worth of data - depending on what type of
 data changes you are dealing with that may or may not be acceptable to
 you.  The restore would be more complex than just saying restore
 everything to the specified date.

 Whether or not this would give you a usable restore point depends heavily
 on your workload - if you are dealing entirely with files that are updated
 in place you would be fine, the end result would be the same as if w2
 wasn't damaged at all.  If you are dealing with something like a busy mail
 server with a bunch of maildirs - a large number of files being created and
 deleted regularly, you would have a mess. You'd be missing a day's worth of
 mail plus you potentially would have 'undeleted' quite a bit of data since
 you would be restoring files that may have been later deleted.

 So the short answer is 'it depends' - this will be true of nearly any
 backup software when using the approach you describe.

 Bryn

 On 14-10-15 03:02 AM, Sieu Truc wrote:

   Hello,

  I have a question about bacula's recovering mechanism.

  I do an full backup every week, and the dailly incremental backups,
 specified in the following configuration :

 Schedule {
 Name = schedule_test
 Run = Level=Incremental Pool=Monday Monday at 22:00
 Run = Level=Incremental Pool=Tuesday Tuesday at 22:00
 Run = Level=Incremental Pool=Wednesday Wednesday at 22:00
 Run = Level=Incremental Pool=Thursday Thursday at 22:00
 Run = Level=Incremental Pool=Friday Friday at 22:00
 Run = Level=Incremental Pool=Saturday Saturday at 22:00
  Run = Level=Full Pool=fullBK Sunday at 22:0
 }

  After 3 weeks, i have 3 full backup named w1,w2,w3 corresponding to each
 week.

  If for some reasons, the backup w2 is damaged, would i lose all the
 incremental backup in the second week from monday to friday ?
  And can i restore the backup w2 with w1 ?

  Thanks,

  PHAM Ngoc Truc


 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.http://p.sf.net/sfu/Zoho



 ___
 Bacula-users mailing 
 listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users




 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.
 http://p.sf.net/sfu/Zoho
 ___
 Bacula-users mailing list
 Bacula-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Recover full backup from the incrementals

2014-10-15 Thread Sieu Truc
Hello,

I have a question about bacula's recovering mechanism.

I do an full backup every week, and the dailly incremental backups,
specified in the following configuration :

Schedule {
Name = schedule_test
Run = Level=Incremental Pool=Monday Monday at 22:00
Run = Level=Incremental Pool=Tuesday Tuesday at 22:00
Run = Level=Incremental Pool=Wednesday Wednesday at 22:00
Run = Level=Incremental Pool=Thursday Thursday at 22:00
Run = Level=Incremental Pool=Friday Friday at 22:00
Run = Level=Incremental Pool=Saturday Saturday at 22:00
 Run = Level=Full Pool=fullBK Sunday at 22:0
}

After 3 weeks, i have 3 full backup named w1,w2,w3 corresponding to each
week.

If for some reasons, the backup w2 is damaged, would i lose all the
incremental backup in the second week from monday to friday ?
And can i restore the backup w2 with w1 ?

Thanks,

PHAM Ngoc Truc
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users