 |
 |
I asked some Computer Center people about this a few years ago (backing up faculty hard drives to another building). They didn't seem too concerned about the traffic. If you look at the utilization graphs, Erickson Hall doesn't seem to go over 5% -- I think you would have to work hard to saturate it. http://mrtg.acns.msu.edu/mrtg/campus.html (not sure what other buildings would be involved, or a quick way to check the backbone(s) between them) If the data possibly includes "sensitive data", it would certainly be best to encrypt and compress it at the source. Historically, PETA and ALF have only hit one building at a time, so copies in two buildings sounds like a good idea to me. On Sep 12, 2006, at 3:00 PM, Laurence Bates wrote: > What is the general thinking about using the campus Ethernet for > infrequent archives of data between buildings? Is the existing > traffic approaching capacity? Is the security risk acceptable? > Should it be restricted to certain hours? How much DR is really > gained by archives that stay on campus?