MySQLdump is a good tool, there are others, but usually the whole
process is scripted to fit the local environment.
Just like many mail servers, databases should be quiescent (the server
stopped) while the dump takes place to ensure consistency. If you want
to really minimize the downtime, then us
I have seen some examples of using a local backup script to dumpmysql
to a local dir, then backup that local dir via BPC, but i was hoping
for something a little more robust. I was looking into replacing the
tar commands that pipe back to ssh with a mysqldump command so it
pipes one big sqldump fil
I was planning to make my backend storage box with zfs which as i
understand it support easy expansion to multiple new disks. Then run
either iSCSI or NFS between the backend storage box and the front end
BPC box
On 23 March 2011 21:34, wrote:
> Best to use LVM (over RAID if you like) for future
Brad Alexander wrote:
> Okay, this kind of confuses me. I would like to have the following backup
> strategy:
>
> 6 incrementals (*2)
> 1 weekly (*2)
> 1 yearly (*1)
>
> Currently,
>
> $Conf{FullKeepCnt} = [ 1, 0, 1, 0, 0, 1 ];
>
> I know this isn't right, but it's not what I would anticipate
On 3/25/2011 10:36 AM, Brad Alexander wrote:
> Okay, this kind of confuses me. I would like to have the following
> backup strategy:
>
> 6 incrementals (*2)
> 1 weekly (*2)
> 1 yearly (*1)
>
> Currently,
>
> $Conf{FullKeepCnt} = [ 1, 0, 1, 0, 0, 1 ];
>
> So how should I set up my FullKeepCnt to ke
Okay, this kind of confuses me. I would like to have the following backup
strategy:
6 incrementals (*2)
1 weekly (*2)
1 yearly (*1)
Currently,
$Conf{FullKeepCnt} = [ 1, 0, 1, 0, 0, 1 ];
I know this isn't right, but it's not what I would anticipate seeing. For
instance, one of my backup targets
