Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Sun Aug 16, 2009 5:43 am 
Offline
Senior Member
User avatar

Joined: Wed Jan 24, 2007 12:04 am
Posts: 90
Website: http://www.smiffysplace.com
Location: Rural South Australia
Currently re-assessing my internal IT strategy, specifically how I handle my hosting.

At the moment, I have 2 Linodes: a production server in one data centre, with a backup/test server in another.

What I am trying to work out is whether I really need the backup/test server, when:

1) I can do all my testing on local servers (to which my primary Linode is backed up daily.)
2) I am doing less client hosting on my own server - setting up separate Linodes for clients on their own accounts.
3) If something really bad happened to the host my production server is on, I would have to make loads of DNS changes which would take time so:
4) It might be quicker to start from scratch with the replacement host.
5) It could take just as long getting my backup up to speed as doing (4).

What do you think, folks? Dump the backup (can't really see the advantage of it now) and spend the money on upgrading my primary?

Comments on this would be much appreciated. I'm trying to cut costs - time more than financial. One less box to look after is rather attractive, especially with the burden of new ones set up for clients.

Cheers

M


Top
   
 Post subject:
PostPosted: Sun Aug 16, 2009 1:01 pm 
Offline
Senior Member

Joined: Fri May 02, 2008 8:44 pm
Posts: 1121
It depends on what you use your "primary" Linode for. If it's so NOT mission-critical that you can afford a few hours of downtime while you start from scratch and re-upload your 1-day-old backup, by all means dump the backup and save your money. If not, maybe it's worth the extra $20.

DNS changes don't necessarily take long. You could use short TTL values. You could convert as many subdomains as possible to CNAME records, so you only need to change one A entry and everything else just follows. If you manage multiple domains, you can automate the task with the Linode API. Or even better, you can simply switch IP addresses between the broken linode and the new one.

If you want to do the start-from-scratch route, consider my example: I keep a list of every package I installed and every configuration file I customized. I feed it into a home-brewed bash script, along with the firewall entries and the exact rsync command to restore my data from the backup. When I provision a new server, I just upload and run the bash script. 5 minutes + the time it takes to restore the backup, and it's ready.


Top
   
 Post subject:
PostPosted: Tue Sep 08, 2009 1:48 am 
Offline
Senior Member
User avatar

Joined: Wed Jan 24, 2007 12:04 am
Posts: 90
Website: http://www.smiffysplace.com
Location: Rural South Australia
Oops - forgot to say thanks for your response. Sorry.

It pretty well confirmed what I was already thinking.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group