|
![]() |
Overclock.net - Overclocking.net > Specialty Builds > Servers | |
Server Backup Ideas
|
||
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) | ||||||||||||
|
4.0 GHz
![]() |
Ok my company I work for has alot of servers at a datacenter.
Due to recent hd problems with a server we are redoing our backup plan. The previous setup was done by my boss but it didn't perform to what we wanted. What kind of options would we have for backing up terabytes of data off multiple servers besides tape? To give an idea most servers have 1-2TB of data on them.
__________________
Want to get ~25,000PPD folding on your i7 running a Virtual Machine? EVGA 680i FOR SALE i7 920 @ 4.2Ghz ![]() HT off for now, still testing. HEATWARE O o /Ż/___________________________ _\ | BBBBBAHHHHHHHHHHHHHHHHH \_\ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ Ż/
|
||||||||||||
|
|
|
|
|
#2 (permalink) | |||||||||||||
|
Case Modder
![]() |
Hard drives?
Being more precise might allow us to give you some ideas. Do you need raid? Occasional manual backups? You're backing up the entire servers? As in the data on them, or OS + data?
|
|||||||||||||
|
|
|
|
|
#3 (permalink) | ||||||||||||||
|
First Time Build
![]() |
Quote:
__________________
|
||||||||||||||
|
|
|
|
|
#4 (permalink) | ||||||||||||
|
Linux Lobbyist
![]()
Join Date: Jan 2009
Location: London, United Kingdom
Posts: 526
Rep: 57
![]() Unique Rep: 53
Trader Rating: 0
|
Yeah an off-site SAN would be ideal, but "ideal" usually equals "expensive".
__________________@OP For those sized data sets, tape is still probably your best bet, especially since you can move the tapes into a safe, or off-site. Look at tape library systems/software such as IBM's Tivoli. It's certainly pricey, but it works. Alternatively, you could co-locate a back up server at a data centre and spend some cash on a decent Internet up-link. The first full backup would be slow, obviously, but after that, it'd only be differential backups. You *might* be able to a) do a full backup to tape b) "restore" that tape back up to the co-located server c) point your backup software at the co-located server and tell it to do differential backups from that point onwards. That should minimise your traffic needs.
|
||||||||||||
|
|
|
|
|
#5 (permalink) | |||||||||||||||
|
4.0 GHz
![]() |
Quote:
![]() Quote:
Quote:
__________________
Want to get ~25,000PPD folding on your i7 running a Virtual Machine? EVGA 680i FOR SALE i7 920 @ 4.2Ghz ![]() HT off for now, still testing. HEATWARE O o /Ż/___________________________ _\ | BBBBBAHHHHHHHHHHHHHHHHH \_\ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ Ż/
|
|||||||||||||||
|
|
|
|
|
#6 (permalink) | ||||||||||||
|
66MHz
![]() |
I think the solution with the best cost/benefit ratio would be a combination of having a dedicated backup server and tape backups you take offsite.
For the dedicated backup server, if you can't afford sparing bandwidth on the main network give it a separate one with just the other servers (either through a VLAN if you've got the spare ports or with a separate switch). Then for tape backups, alternate between two or three sets of tapes so that one of them is always offsite even during backups.
__________________
For Sale: [Conus] CM Storm Scout, TEC, WC, Laptop, A900, Model M, GPU, Audio, and a ton more!!
|
||||||||||||
|
|
|
|
#7 (permalink) | ||||||||
|
Linux Lobbyist
![]() |
hold on there buddy... let's start with your requirements?
how many servers? how much data per server? what is your required recovery window/time? what is your backup window/time? what is your desired backup frequency for fulls and incrementals? what is your data retention policy? do you require off-site storage for disaster recovery? what does your disaster recovery plan require? what is the ballpark figure for the budget on hardware, software, labor? when you answer those questions, the technical details start making sense. For example, i have one customer who requires a maximum recovery time of 6 hours on a maximum of 3.5TB of data. That means I need a system that can restore about 600GB of data per hour, which is 10GB/min, which is about 171MBytes/sec. this tells me that in a bare metal recovery scenario, I can't accomplish this over a 1Gbps network (which is about 120MB/sec), and I need a I/O subsystem that can sustain about 200MB/sec writes on the bare metal server, and 200MB/sec reads on the backup I/O subsystem. Once you know these numbers, then you start looking for hardware solutions that can accomplish this. Then you start looking at software solutions, etc. This is just a back of the envelope analysis of a bare metal recovery scenario, but you'll need to look into the backup scenarios, single file system recovery scenarios, disaster recovery scenarios, etc. Start by understanding the requirements.... otherwise, later down the road you'll realize all over again that you don't have the backup solution you need.
__________________
|
||||||||
|
|
|
|
|
#8 (permalink) | ||||||||||||||
|
2 + 2 = 5
![]()
Join Date: Nov 2006
Location: In a Chair.
Posts: 34,932
Rep: 4172
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Unique Rep: 1907
Trader Rating: 56
|
Quote:
__________________
To answer most of your questions: (1) a fridge cannot cool a PC (2) 64-bit OS for over 3.4GB (3) If a PCIe card fits, it should work (4) Resolution, not screen size (5) If you have a question, it is not news (6) Report, not respond to Spam (7) Single-Rail/Non-Modular PSUs are not always better than Multi-Rail/Modular
|
||||||||||||||
|
|
|
|
#9 (permalink) | ||||||||||
|
Networking Nut
|
commvault software. We run it on our servers here in the data centers I support. Offsite tape backups are going to be a definite need.
__________________
|
||||||||||
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|