I think rsync pretty much provides all you need in one tiny command-line to get data from A to B.
But if you want to increase your resilience against failing network connectivity, and make sure you don't delete anything that hasn't been properly copied to your server, I suggest you take a look at datamover: http://www.cisd.ethz.ch/software/Data_Mover
Essentially, it's a daemon written in Java that monitors an outgoing directory. Everythings that is written in there gets safely copied over to a central storage drive. Behind the scenes, they use rsync to do the copying, but it's wrapped in tons of features that improve the reliability of the moving process, like a quiet period before a file gets moved (good for applications that write their output incrementally and sporadically into files), multiple retries on network time-outs, high-water marks, data transformation (e.g. compression) during the move process, etc. It also is very anal about sending you emails for anything that could possibly be a data integrity problem.
We rely on it to store the raw data from scientific experiments. With the proper configuration, your holiday pictures should be just fine.
"Those internal communication mean nothing"
In prosecuting copyright cases, internal communications mean everything. I'm not speaking in the abstract here; incriminating emails were instrumental in the Napster case and some other major copyright cases, going back to the BBS days. It's an all-too-common pattern: publicly, the company claims that it doesn't know that copyrighted information is being shared in an unauthorized manner; their internal emails reveal that they do know this; plausible deniability is destroyed; game over.
This is central to the concepts of contributory infringement and vicarious infringement. The former is when you know infringement is happening but you do nothing to stop it; the latter is when you're ignoring it because there's a financial incentive to do so.
"The point being, is that just because something seems to be illegal - doesn't mean it is, you/we have NO idea if the customer in question has some kind of weird contract with the copyright holder and if they are in violation of it or not - THAT is up to a judge and/or contract attorney to decide, no one else."
Agreed, compliance can be a hassle, and the more customers and activity you have, the bigger your exposure, which is why ISPs, file lockers, Torrent sites and the like must have sufficient staff for compliance with copyright laws, just as they require sufficient staff to ensure compliance with other laws (everything from Sarbanes Oxley to workplace safety). From reading your situation, it's clear that your ISP is one of the "good guys." However, it's not analogous to MU. It wasn't an issue of not being properly staffed to handle takedown requests, or even legitimate concerns that the requests were bogus -- it was deliberately ignoring the requests because their business model required it.
"What is "reasonable"?"
"reasonable person" is a legal construct. Wikipedia explains it pretty well:
http://en.wikipedia.org/wiki/Reasonable_person
"Why? What if it's a bogus DMCA takedown request?"
You've read the indictment, right? It's not even an issue of thinking the takedown requests are bogus (ie. somebody's forging an email from Fox to issue a takedown on Avatar). They ignored takedown requests that they knew to be legitimate on hugely popular files (ie. the latest scene releases) because they were making tons of money. Kim's instructions to his team were to ignore all takedown requests except from the major media companies in the US -- ie. the ones that would actually do something about it if the requests were ignored. They knew exactly what they were doing.
"How can anyone know that account which uploaded the video does not actually hold copyright on it? Yes, question sounds silly, but it is extremely complex. Unless someone else claims the copyright ownership, you can only assume that whoever uploaded it is the copyright owner."
You nailed it with "silly." The courts tend to have a lower threshold for silliness than many people understand. If even the proponent of an argument acknowledges that it's silly, it won't pass the laugh test in court.
You see, the justice system has a very low tolerance for bad actors. If the facts are these:
A reasonable person would understand that "DeEzNuTs" is not the copyright holder for Avatar, and that the film company's distribution strategy does not include posting screener rips to sites known for piracy. Likewise, if MU's defense is that, gosh, they had no idea that DeEzNuTs wasn't actually the copyright holder, they'll be laughed at.
"Yes, of course they were aware about piracy on the site, but what can you realistically do about that except taking down files when they appear in DMCA notice?"
Again, you've nailed it. Respond to copyright claims in good faith, and you're in that safe harbor. That's why it's called a safe harbor. That's why the DMCA hasn't brought down the Internet: the laws are easy to follow. It's nigh on impossible to run a successful service that (a) actively induces piracy and (b) follows the law; each time a Torrent site operator claims that they're "just like a search engine".... they're not. If you avoid the DMCA safe harbor provisions, you're not just like a search engine.
MU ignored the safe harbor previsions, because it would have interfered with the successful execution of their business model.
"There are so many things that need to be properly tested in court, this will certainly be a massive one."
This is all pretty basic stuff. These were all tested in the Grokster decision, the Napster decision, and lots of other P2P-related decisions. Some of this stuff goes back more than a decade.
if the model is basically "we pay if your file is popular", but there is no checking of the actual file, whether the user has actual rights to the file or not, or encouragement of piracy specifically, all that's left is accusing MegaUpload of encouraging popular files.
Note the IF. What you describe is not how MegaUpload operates. If the indictments are to be believed, the operators were caught numerous times encouraging the sharing of content that they knew to be pirated.
You're correct that a truly content-agnostic file storage and sharing site should have nothing to fear. DropBox is safe. The operators of MegaUpload, however, serve as a textbook example of purposely avoiding all the safe harbor opportunities. This isn't because they were stupid -- far from it -- but because this is their very business model.
The legal concept of mens rea -- latin for "guilty mind" -- applies here. The MegaUpload guys, through their actions, have been nailed fair and square. This is their choice. They took the lucrative, but risky, path, of actively courting piracy. Their business model is wholly different than that of DropBox.
"We want to create puppets that pull their own strings." -- Ann Marion "Would this make them Marionettes?" -- Jeff Daiell