| Re: Backups [message #10555 is a reply to message #10554] |
Wed, 21 February 2007 17:13  |
Mike Holloway
Messages: 8
Registered: February 2007
|
Junior Member |
|
|
As Kirill pointed out, be sure to also backup the veid.conf file
(mine are in /etc/sysconfig/vz-scripts) as well as the /vz/private
directories.
I use this procedure along with a heartbeat program to have one
server automatically launch a VE when it detects the primary server
is down, works great.
There is no need to re-create the VE (vzctl create) after re-
installing the os and openvz kernel, just restore the veid.conf and /
vz/private directories and then 'vzctl start veid'. The veid.conf
file you backed up already holds the previously assigned IP address
for the VE.
-mike
On Feb 21, 2007, at 11:00 AM, Kirill Korotaev wrote:
> José,
>
> don't forget to backup /vz/conf/<VEID>.conf file also.
> if you do dumps of databases everything else should be quite fine.
>
> anyway, it is better take another machine disconnected from the
> network and
> just check that your backups do work after restore. Just to be 100%
> sure
> in yourself.
>
> Thanks,
> Kirill
>
>> Hi,
>>
>> Im doing every night backups with rdiff-backup, im running rdiff-
>> backup
>> to the directory /vz/private, then im doing backups of each VPS in
>> the HN.
>>
>> Im thinking about a disaster recovery stratregy, if the disk of my HN
>> crash, for example, can I just:
>> Re-install the same OS, install openvz, create the same VPS with the
>> same VID and same IP address and just restore /vz/private/VID/* it
>> will
>> work?
>>
>> rdiff-backup preserves subdirectories, hard links, dev files,
>> permissions, uid/gid ownership, and modification times
>>
>> Im doing dumps of mysql and postgresql, every night. Then I can
>> restore
>> the databases manually. Its not a problem
>>
>
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
