Hi,
option 0 is the best one however there are financial drawbacks :-) The
whole situation is like this. I have bacula server with two remote SAN
connected drives. SAN does mirroring etc and SAN drives are considered
stable and safe.
I have the backup rotation schema with 1 weekly full backup
Hi,
option 0 is the best one however there are financial drawbacks :-) The
whole situation is like this. I have bacula server with two remote SAN
connected drives. SAN does mirroring etc and SAN drives are considered
stable and safe.
I have the backup rotation schema with 1 weekly full back
My opinion to your ideas:
0) Leave the schema as I submited and buy more disk space for backuping. :-)
1) It is best variant I think. The other advantage is that the full
backup of all clients would take much longer time then 1/7th full and
other differential. Now what to do with Catalog:
You ca
Hi,
thanks for your answer. Your idea sounds good. However if I understand
it correctly, there will be two full backups for the whole day after
full backup. This is what I am trying to avoid as I will be backing up a
lot of clients. So as I see it I have these possibilities:
1) use your
Hi,
I suggest to solve like this:
One Pool only. 8 volumes. Retention time 7 days and few hours. Use time
1 day.
The use will be like this:
first Monday: full backup. volume 1 used and contains the full backup
Tue to Sun: diff backup using volumes 2 to 7 (automaticaly selected or
created by bacu
Hi,
I am implementing simple schema for backing up our data. Data are
backed up to disk. Full backup is performed every Sunday. The next 6
days differential backups are performed.
I want to keep only one Full backup and at maximum 6 daily differences.
The moment new Full backup is made,
