Date:  Fri, 30 Nov 2007 14:59:48 -0800
From:  "Ken Marcus - Precision Web Hosting, Inc." <kenmarcus (at mark) precisionweb.net>
Subject:  [coba-e:11332] Re: backup
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <043a01c833a4$b66a1dc0$6700a8c0@OfficeKen>
References:  <03a101c8327b$f7f342a0$0101a8c0 (at mark) systemax> <474EF81C.1080708 (at mark) nomealaska.org> <474F1A16.7020808 (at mark) nomealaska.org> <016a01c832cd$da1801b0$6400a8c0 (at mark) HPPAVILION> <474F5D0E.1070704 (at mark) nomealaska.org> <01ed01c832f6$94936390$6400a8c0 (at mark) HPPAVILION> <007c01c83309$b06c02d0$6700a8c0 (at mark) OfficeKen> <8FE1E490-395C-4CE9-81FB-7F49FE73A599 (at mark) iweb.dk>
X-Mail-Count: 11332


René MÍsted wrote:



> On 30/11/2007, at 5.30, Ken Marcus - Precision Web Hosting, Inc. wrote:
>
>> Here is a script that will take a list of sites from a file named 
>> "sitestoadd.txt" and will restore them to a server. Using this  script, 
>> if you have a problem half way through a restore like a  memory leak or 
>> disconnection problem, you won't have to start all  over.  Just log back 
>> in, edit the sitestoadd.txt and start it again.
>
> Couldn't that be handled by restarting cced for every n site?
> Eg. for every 20 site
>


René

Your idea would probably work also.


What happened in my case, is it created every site, but then part way 
through the process every site started giving an error when it tried to 
restore the files.

But when I did them individually with the script then they worked with no 
problem.

The sequence of the normal restore is:
1.  Create all the sites
2. Restore content to all the sites

What I prefer to do is, create the list of sites to restore    with the top 
complainers first.  That way the site is created, the users set up, then the 
content restored. This helps them to stop calling with questions like "My 
site is there but I don't see the pages!!"


----
Ken Marcus
Ecommerce Web Hosting by
Precision Web Hosting, Inc.
http://www.precisionweb.net