SoylentNews is people
SoylentNews
This is probably one of those topics that gets regurgitated periodically, but it's always good to get some fresh answers.
The small consultancy business I work for wants to set up a new file server with remote backup. In the past we have used a Windows XP file server and plugged in a couple of external USB drives when space runs out. Backups were performed nightly to a USB drive and taken offsite to a trusted employees home.
They are looking to Linux for a new file server (I think more because they found out how much a new Windows file server would be).
I'm not a server guy but I have set up a simple Debian-based web server at work for a specific intranet application, but when I was asked about ideas for the new system the best I could come up with was maybe ssh+rsync (which I have only recently started using myself so I'm no expert by any means). Using Amazon's cloud service has been suggested, as well as the remote being a dedicated machine at a trusted employee's home (probably with a new dedicated line in) or with our local ISP (if they can offer such a service). A new dedicated line out of the office has also been suggested, I think mainly because daily file changes can potentially be quite large (3D CAD models etc). A possible advantage of the remote being nearby is that the initial backup could be using a portable hard drive instead of having to uploading terabytes of data (I guess there is always courier services though).
Anyway, just thought I'd chuck it out there. A lot of you guys probably already set up and/or look after remote backup systems. Even if anyone just has some ideas regarding potential traps/pitfalls would be handy. The company is fairly small (about 20-odd employees) so I don't think they need anything overly elaborate, but all feedback is appreciated.
(Score: 0) by Anonymous Coward on Friday July 11 2014, @07:23PM
use a LAN over wifi (or fiber optics). the wifi (or fiber) is to separate the
electrical circuit.
your "remote" backup site doesn't have to be far. maybe just a few hundred meters and another building.
also this "remote" backup site should be feed by another electrical transformer.
of course an even better solution would be to send it to a grid feed by a completely different
power-plant/generator all together ... but that will prolly involve the (slow) internet transit AND
monthly fees ...
with wifi (or fiber) you get electrical circuit separation. the other building could provide
fire protection and flood protection. what else is there ... ah ... solar flares : )
distance for wifi: curvature of earth line-0f-sight
distance fiber: ~50 km and money (plus paper "work" for putting the physical cable yadayada)!
(Score: 2) by egcagrac0 on Friday July 11 2014, @08:46PM
To what benefit? What risk does that mitigate?
The common problems that I've used backups to recover from are:
It's entirely possible that lightning strikes or ESD are legitimate concerns in your plan, but if that's the case, you should be able to buy lotto tickets as insurance against them.
Worry about the common stuff first, worry about the weird stuff later.
Yes, this building has been struck by lightning. It burned a few holes in the metal roof. It didn't zap the network. We have underground power lines and underground telecom lines; this somewhat reduces our risk of those being points of ingress for lightning attack. Your situation may vary.