I started down that road. The main problem with that process is amount of
extra space required on both the live machine and the backup. Incremental
recovery of multiple backups is already handled by BackupPC.
Thanks,
GH
From: Adam Goryachev <mailingli...@websitemanagers.com.au>
Organization: Website Managers
Reply-To: "General list for user discussion, questions and support"
<backuppc-users@lists.sourceforge.net>
Date: Friday, August 4, 2017 at 11:33 AM
To: "backuppc-users@lists.sourceforge.net"
<backuppc-users@lists.sourceforge.net>
Subject: Re: [BackupPC-users] DumpPre/DumpPost scripting with $type incr
On 5/8/17 00:39, Greg Harris wrote:
I’m having difficulty wrapping my brain around the DumpPre/DumpPost command on
a backup. I’ve got a database service that I need to shut down, run an
incremental backup, then start the service again. I’ve got it successfully
SSH’ing in and shutting down the service, running the backup, and then
restarting the service. However, how do I use the $type incr command to
specify only incremental backups?
Currently I have:
$Conf{DumpPreUserCmd} = '$sshPath -q -x -l root $host /root/serviceDown';
$Conf{DumpPostUserCmd} = '$sshPath -q -x -l root $host /root/serviceUp';
Problem #2:
I need the incremental to run after the full does, on the same day. I don’t
want the database service to be shut down for the length of time it takes to
run a full backup, so do the full, then run a followup incremental that shuts
down the service. Additionally, I assume that if I do a full once a week that
I need to keep 7 incrementals, rather than the previous 6, correct?
I would suggest that you instead use the prebackup script to:
1) shutdown the DB
2) copy the DB files to some other location
3) start the DB
Then, your incremental and full will both backup the DB, and the DB is only
down for the minimum time required.
Alternate option, configure cron to shutdown DB, do a local copy/backup, start
DB. Then whatever time the backup runs, it will backup the latest copy.
Personally, I choose the second option, and keep two local copies of the DB to
rotate, this way I have a very simple and quick copy to restore from if needed,
plus the backuppc copies if I need something older/etc.
Regards,
Adam
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
