And as always Daniel ... you rock. Thanks. This is much simpler than
what I thought it could be.
Can I assume that after --context and before -- (the ...) I can put in
other switches?
--interface, --initstyle, --hostname, etc?
I was just getting ready to try _my method_ on a small guest but this
will be better.
Again thanks,
Rod
--
Daniel Hokka Zakrisson wrote:
Roderick A. Anderson wrote:
I've been all through the Wiki and old docs, searched using Google,
looked through my _OLD_ messages (back to 2003) and still can't come up
with a well defined method to copy a (running if possible) vserver guest
from one system to another.
From my reading I think I need to build the _new_ guest 'mynewone'
using the skeleton method. Then rm all the files in /vserver/mynewone
and follow that with a rsync from the _old_ guest to the _new_ guest.
Unfortunately the vserver docs are from the CTX kernels. A vserver
--help gets a semi-useful help screen. Any newer docs?
What special rsync switches do I need or use to make this process
doable? As in it is a running guest that I'd prefer not taking down
until the actual move I'm sure /proc and maybe /dev could cause problems.
The need for the hot copy is because the _old_ guest has a big pile of
installed perl modules and _other_ software packages. It would be
easier to copy than (re)install them. :-)
The way I'd do it:
export RSYNC_RSH=ssh
vserver <guest> build -m rsync --context ... -- --source
[EMAIL PROTECTED]:/vservers/<guest>/
<make sure it's good, stop the guest on the other host>
rsync -Hazx --numeric-ids [EMAIL PROTECTED]:/vservers/<guest>/
/vservers/<guest>/
vserver <guest> start
--
Daniel Hokka Zakrisson
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
