[server-admins] Relocation checklist (next steps, rsync of ftp files under way)

Jonathan Marsden jmarsden at fastmail.fm
Tue Jan 11 22:37:36 MST 2011


Troy,

On 01/11/2011 09:01 PM, Troy A. Griffitts wrote:

>>> So, I now have steps (1) to (3) done, unless there are more domains than
>>> just those two we need to work with.

> I believe these are the only 2 domains we serve.  So you already know
> all of our 'ftp. www. community. and other entries from the ns ls
> against extremezone?

Yes, already in my new DNS setup.

> What about our MX entries?

Also already in there.

> I believe we also had some flag turned on to prevent spam being aliased
> as coming from *@crosswire.org.  Some setting major providers check, if
> we want to limit all crosswire mail to be originated from our server's
> IP or something or other.  Am I close?

That sounds like an SPF entry, which would go in a TXT record in DNS.
But crosswire.org doesn't have one at the moment.  I'd suggest leaving
that as is for now, and revisiting the idea once the server move is all
done.

>>   (4) Point DNS for each domain to 'my' DNS servers not the current ones
>>   (usually via a web control panel at the registrar for each domain).
>>   either you make these changes, or you tell me the username/pw info for
>>   each domain account and I'll do it.

>> Looks like crosswire.org uses Network Solutions as its registrar, and
>> testallthings.org uses GoDaddy.  Do you have the relevant user/password
>> info for the control panel access to each of them at their respective
>> registrars?

> Getting on this.  Will get back with you when it's done.

Cool.

In the meantime, before I left the office I started copying the latest
backup file from /backup/20110107.tgz and stuck it onto my home PC, as a
"just in case" backup... it copied fine, 1.6GB or so at around
10Mbit/sec (limited by my home Internet connection), but it seems to
only have the raw modules, not the zip files etc.

Next step I can do (sort of beginning step 6, in parallel with 4 and 5)
is to grab all the /home/ftp/pub/* stuff and set it up for public FTP
access on the server which will temporarily "be" ftp.crosswire.org
during the move.

That's about an 8.6GB file transfer -- will your provider be OK with
that?  I'm planning to rsync it (over ssh), so I can repeat the rsync
closer to the move and pick up any changes that happen between now and then.

QUESTION: Do we need to have the contents of /home/ftp/pub/sword/iso
available to download during the move downtime?  Not copying that would
save us 5+GB of bandwidth.  And it all looks rather old to me. For now
I'll exclude /home/ftp/pub/sword/iso and /home/ftp/pub/ichthux -- let me
know if those subdirectories really are important enough to copy over to
the temporary FTP server.

rsync under way :)

Jonathan



More information about the server-admins mailing list