Best backup strategy on short disk capacity

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Best backup strategy on short disk capacity

Jason Voorhees
Hello guys:

I'm running Bacula 7.4.0 to save backup of my Windows fileserver which
has 4 drives (D:, F:, G:, H:) with 7.1 TB of total capacity.

I've ran a full backup during 7 days which occupied 5.8 TB (~20%
compression rate) in a local filesystem with local SATA disks. This
local filesystem is at 80% usage so I don't have enough free space to
run a 2nd full backup. I was planning to run Full + Incremental +
Differential backups like this:

- Full -> 1st sunday
- Differential -> 2nd-5th sunday
- Incremental -> monday-saturday

If my full backup takes 7 days to complete, how should I schedule my
jobs? I created 3 Storage resources which each point to 3 different
directories so I can run a Full+Incremental or Full+Differential jobs
concurrently.

Also, how long should my retention periods should be so I can run a
new full backup without filling my disk up to 100%? I thought my
retention period could be something like 30 days or less (maybe 21
days)... but .... if my last full backup is overwritten by the new
full backup I guess I won't be able to have a valid copy during the
time my new full backup is running (7 days approximately). Am I right?

I hope you can understand how confused I am here.

P.D. I only use bacula to make backups to this Windows fileserver and
the Bacula server, no more clients are backed up.

Thanks in advance for your help.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|

Re: Best backup strategy on short disk capacity

Kern Sibbald
Hello,

You are sort of in an impossible situation.  With the large amount of
data you have and the small backup space, it will be hard to make Bacula
work as it should.

My very strong conviction is that any single backup job that last more
than 10 hours is too long.  If it takes 7 days to backup one machine,
Bacula will not work very well.

At a minimum you should split your Windows backup into four separate
jobs each one backing up a single drive.  Then after completing a full
backup of each drive, you can stagger backups to do a full of the
machine over 4 days (one for each drive).  That will reduce the overall
backup load.  However, if a backup of a single drive takes 2 days, in my
opinion, it will still be too long.

Another, though slightly more complicated way to handle it is to
separate the Fulls as noted above, but when the next Full for a drive
comes do, do a VirtualFull instead of a full.  All the other backups for
that drive can then be  Incrementals.  At least one of the Incrementals
should be with Accurate = yes.  Then as a security measure do another
real Full (per drive) once a year.

About how to handle retention periods: that is too complicated for me to
explain here.  The simplest solution is to get much more disk for use by
Bacula, or you can get a professional support to get help for retention
periods, or ask for help on the list. Reading the "Automated Disk
Backup" chapter may help or "Automatic Volume Recycling" and "Basic
Volume Management".  It is all there, but it is much easier to
understand with help.

Best regards,
Kern

On 06/20/2016 04:49 PM, Jason Voorhees wrote:

> Hello guys:
>
> I'm running Bacula 7.4.0 to save backup of my Windows fileserver which
> has 4 drives (D:, F:, G:, H:) with 7.1 TB of total capacity.
>
> I've ran a full backup during 7 days which occupied 5.8 TB (~20%
> compression rate) in a local filesystem with local SATA disks. This
> local filesystem is at 80% usage so I don't have enough free space to
> run a 2nd full backup. I was planning to run Full + Incremental +
> Differential backups like this:
>
> - Full -> 1st sunday
> - Differential -> 2nd-5th sunday
> - Incremental -> monday-saturday
>
> If my full backup takes 7 days to complete, how should I schedule my
> jobs? I created 3 Storage resources which each point to 3 different
> directories so I can run a Full+Incremental or Full+Differential jobs
> concurrently.
>
> Also, how long should my retention periods should be so I can run a
> new full backup without filling my disk up to 100%? I thought my
> retention period could be something like 30 days or less (maybe 21
> days)... but .... if my last full backup is overwritten by the new
> full backup I guess I won't be able to have a valid copy during the
> time my new full backup is running (7 days approximately). Am I right?
>
> I hope you can understand how confused I am here.
>
> P.D. I only use bacula to make backups to this Windows fileserver and
> the Bacula server, no more clients are backed up.
>
> Thanks in advance for your help.
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports. http://sdm.link/zohomanageengine
> _______________________________________________
> Bacula-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>


------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|

Re: Best backup strategy on short disk capacity

Jason Voorhees
On Tue, Jun 21, 2016 at 7:09 AM, Kern Sibbald <[hidden email]> wrote:

> Hello,
>
> You are sort of in an impossible situation.  With the large amount of data
> you have and the small backup space, it will be hard to make Bacula work as
> it should.
>
> My very strong conviction is that any single backup job that last more than
> 10 hours is too long.  If it takes 7 days to backup one machine, Bacula will
> not work very well.
>
> At a minimum you should split your Windows backup into four separate jobs
> each one backing up a single drive.  Then after completing a full backup of
> each drive, you can stagger backups to do a full of the machine over 4 days
> (one for each drive).  That will reduce the overall backup load.  However,
> if a backup of a single drive takes 2 days, in my opinion, it will still be
> too long.
>
> Another, though slightly more complicated way to handle it is to separate
> the Fulls as noted above, but when the next Full for a drive comes do, do a
> VirtualFull instead of a full.  All the other backups for that drive can
> then be  Incrementals.  At least one of the Incrementals should be with
> Accurate = yes.  Then as a security measure do another real Full (per drive)
> once a year.
>
> About how to handle retention periods: that is too complicated for me to
> explain here.  The simplest solution is to get much more disk for use by
> Bacula, or you can get a professional support to get help for retention
> periods, or ask for help on the list. Reading the "Automated Disk Backup"
> chapter may help or "Automatic Volume Recycling" and "Basic Volume
> Management".  It is all there, but it is much easier to understand with
> help.
>

Thanks again Kern, I'll try to get the best of your recommendation to
decide how to backup this specific client.

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users