Herbert Poetzl wrote:
On Thu, Dec 15, 2005 at 05:57:43PM +0100, Lars Hallberg wrote:
After some interuption I'm back att writing a script to copy / migrate
VServers.
1) One consern. If a VServer is unified, and I copy over it with rsynk
in the host context. Will links be properly broken or do I risk to mess
upp other servers?
should work as long as you do not copy across guests
(in which case it might be necessary to tell rsync
to ignore hard links)
Not sure I follow... if /vserver/foo/bar/foo.txt is a hardlink
(unifide), an I do copy new contents to it in the host context... Vill
the link be broken or the common (unifide) file altered?
2) Diskspace limits is good, so suport for Xid tagging vould be good.
But I don't realy vant to copy the Xid tagging. I want to use the
targets Xid, whatever it is (or no taging if the target dont use it). My
plan A is:
Start a rsynk server on the target host, runing in the target VServers
Xid context - so any files written will be with the 'right' tagging.
Whithout starting the actual VServer. Is this possable?
yes, sounds reasonable .. as all newer guests are
supposed to use static xids, it should be simple to
do something with chcontext on the receiving end
(which will automatically tag the files properly)
Great! What I understand, xid tagging don't work without static xid? So
it is no issu?
another alternative would be to copy over the files,
then re-unify on the destination and tag the non
unified files properly with chxid ...
Yes, but for migrating, I want to minimize the processing between the
stop on the source and the start on the target. So if the rsynk itself
fix the xid tagging automagicly it be great!
Thanks /LaH
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
