5 Jun
2012
5 Jun
'12
3:59 p.m.
On Tue, 2012-06-05 at 09:10 -0400, S P wrote:
Thanks in advance.
(Sent from mobile)
On Jun 5, 2012, at 8:53, Miah Gregory <miah(a)darksilence.net> wrote:
> On Tue, 2012-06-05 at 09:22 +0000, Andy Smith wrote:
>
>> Seems like most people only back up data and configuration though.
>
> I back up the entire disk image personally, the change set between
> backups is generally zero for system binaries etc, plus it provides a
> useful audit tool should any box get hacked.
>
> It also means when restoring that I don't need to worry about whether or
> not the box will restore into a working state or not due to package
> updates or config/running state stored in non-standard locations.
>
> Just my 2p though, I tend to be overly zealous about these things. :)
Miah, would you mind sharing your approach for backing
up the entire
image? I am new to VPS backing up, and am searching for a good
approach.
Nothing particularly exciting I'm afraid. I have a separate backup host
running rsnapshot + ssh/rsync which connects to each machine daily and
rsyncs over the entire filesystem minus a few exclusions.
I'll need to re-test my bare "virtual-metal" restore procedure sometime,
but in essence this is just the same in reverse, boot new vm image, shut
down pretty much every service, rsync everything back over the top of
the running machine, reboot, done.
A few files need tweaking if you're restoring to a VM with non-identical
network addresses and so on, eg. /etc/network/interfaces, /etc/hosts
etc.
--
Regards,
Miah
DSIS - IT Support and Consultancy
0141 4382030
http://www.dsis.co.uk/
DSIS is a trading name of Dark Silence Ltd, registered in Scotland SC341532