On Fri, Jun 11, 2010 at 10:34 AM, Hanno Schlichting <span dir="ltr"><<a href="mailto:hanno@hannosch.eu">hanno@hannosch.eu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Jun 11, 2010 at 3:25 PM, Paul Winkler <<a href="mailto:slinkp@gmail.com">slinkp@gmail.com</a>> wrote:<br>
> I'm preparing to move a zope site from one host to another. We've been<br>
> planning to use repozo backups to copy the filestorage from the old<br>
> host to the new one. I'd like to figure out how to minimize downtime<br>
> while not losing any data. My plan was:<br>
<br>
</div>For moving stuff to a new host where a short downtime is planned<br>
anyways, I would just use rsync.<br>
<br>
1. While the old site is still running, rsync both the Data.fs and<br>
index file to the new host<br>
2. Make sure you don't run any zeopack operation between that point<br>
and the actual switchover<br>
3. You can keep running rsync a couple times shortly before the<br>
downtime to get the most recent state over<br>
4. Shut down the old site<br>
5. Do a final rsync of both the .fs and .fs.index (this should take a<br>
couple seconds or minutes at most)<br>
6. Start the new site, since the index is up-to-date and matches the<br>
Data.fs it should be seconds as well<br>
<br>
I tend to run rsync via "rsync -rP --rsh=ssh". The Data.fs is an<br>
append-only file, so rsync is very efficient at handling it. Only<br>
zeopack rewrites things all across the file and causes a subsequent<br>
rsync to be slow again.<br>
<div class="im"><br></div></blockquote><div><br>Thanks. I'll do a trial run of this today.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> 1) would it be safe to copy the index file from the old host and just<br>
> use that with the filestorage generated by repozo?<br>
<br>
</div>It's save, but it will be ignored and a new index be created, so you<br>
don't gain anything.<br></blockquote><div><br>Hm, ok, so whether you're right or Chris is right, it's not going to work :)<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
But at some point you could upgrade to ZODB 3.10 (currently in beta),<br>
where repozo does save the index file for each backup. It will still<br>
be slower than rsync for this use-case, though.<font color="#888888"><br></font></blockquote><div><br>Roger that. Thanks. <br></div></div>-- <br><a href="http://www.slinkp.com">http://www.slinkp.com</a><br><br>