Thank you James for that answer. As I expected, 2 full backups seems to be needed to exist to be able to have 2 weeks possibility to restore.
But what about this: (F = full, I= incremental. Day 1 to day 13.) F+I+I+I+I+I+I+I+I+I+I+I+I Then merge the oldest incremental with the full one, creating something like this: F+I+F+I+I+I+I+I+I+I+I+I+I+I I can then remove the first F+I without loosing my 2 weeks possibility to restore. Is this possible? I have played around with "run job= level=VirtualFull" and have notice that it always create a full backup last in the chain. Like this F+I+I+I+I+I+I+I+I+I+I+I+I+F. Maybe it exist some parameters so I can control this more? On 12/08/2009 12:12 AM, James Harper wrote: >> Hi. I have a customer that has 287 GB of data that's needs to be >> backuped. The change of this data is probably around 100MB per day. >> The >> customer wants to be able to restore files 2 weeks back in time. How >> do >> I set this up so it requires so little space as possible? >> >> I was thinking about using this new Virtual Backup (Vbackup) feature >> that exist from 3.0 version. >> One full backup and 13 incremental backups will always exist. When a >> new >> incremental backup is added, the oldest incremental is later merged >> with >> the full backup by a script same day. Is this possible? > > It's possible, but while the new vbackup is being synchronised, you will > need the space to hold the full backup you are using as the 'base', and > the virtual full backup you are building, so the space requirements will > be similar to just doing another full backup. 100MB per day isn't much > compared to 287GB so I don't know that the virtual full buys you that > much. > > In my setup which has similar requirements, I run a full backup once a > week and incremental backups every few hours during the day, and retain > the older backups for 15 days. This means I have 2 full backups at any > point in time, and 3 backups for a few days while the expired full > hasn't been overwritten yet. > > I just use a permanently attached USB disk to hold all the backups, so > space isn't really an issue - disks are cheap so more can be added if > required. > > Also, every night I synthesize a virtual full backup to tape to be taken > offsite for DR purposes. > > If this is a Windows system, then bear in mind that the normal VSS > backup of MSSQL Server isn't going to do what you expect when you do an > incremental backup, and even less so if you are doing Virtual Full > backups. > > James > > (btw, USB disks suck these days - the disks are so much faster than USB > can handle that it seems like a waste. I'm starting to use eSATA instead > when possible) > ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
