<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">this may do that job..<br><br>http://www.sentex.net/~mwandel/tech/changer.html<br><br><br>cheap dvd dual layer backup ;-)<br><br><br>hehehe<br><br><br>--- On <b>Sun, 15/3/09, Simon Wells <i><swells@computing.dundee.ac.uk></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Simon Wells <swells@computing.dundee.ac.uk><br>Subject: Re: [dundee] ESATA Linux Support<br>To: toxicnaan@yahoo.co.uk, "Tayside Linux User Group" <dundee@lists.lug.org.uk><br>Cc: "Simon Wells" <swells@computing.dundee.ac.uk><br>Date: Sunday, 15 March, 2009, 5:50 PM<br><br><pre>Hi Lee,<br><br>I already have online replication of data both locally and remotely. I already<br>have a NAS running locally but wanted to have a decent offline backup solution.<br>With the questions about eSATA, I was looking
for a way to consolidate all of<br>the various usb drives that I currently use for offline storage into a single<br>unit (so I can avoid the tangle of wires), using off the shelf hdd, and do it<br>reasonably cheaply using fairly standard Linux tools. It looks as though eSATA<br>fits the bill for me at this point.<br><br>It is debatable though as to whether RAID and other forms of online storage<br>constitutes a *backup* system. It goes some way towards enabling you to recover<br>from short term hardware failure but doesn't help when it comes to data<br>corruption where you need to restore from a known good backup.<br><br>Simon<br><br>Dr. Simon Wells<br>=============<br><br>E-mail: swells@computing.dundee.ac.uk<br>IM: sw3lls@yahoo.co.uk<br>Mail: School of Computing,<br> Queen Mother Building,<br> University of Dundee,<br> Dundee, DD1 4HN.<br>WWW: http://quiddity.computing.dundee.ac.uk/swells/blog/<br>Phone: +44 (0)1382 386 526<br>Fax: +44
(0)1382 385 509 (FAO: Simon Wells)<br><br><br><br><br>On 11 Mar 2009, at 00:00, Lee Hughes wrote:<br><br>> I've not used any esata, I *presume* it's looks like a normal sata<br>device, and should use normal sata drivers. I doubt esata uses a different<br>protocol or device driver than normal sata,.<br>> Why would it, the the cable run's 'outside' of your machine.<br>..<br>> (and probably has about 17 different connectors(!) I think..... i may be<br>wrong!! I'm sure<br>> any multiplexing that's going on, is done in hardware (i.e 1 cable, 4<br>disks)<br>> <br>> If things are doom and gloomy on the esata , don't rule out using aoe<br>over gigabit ethernet, give you flexible storage over the network, and combine<br>that with some clever drdb -ing you can add as much fault tollerance as you<br>want.<br>> <br>> http://mike.neir.org/weblog/619 is interesting.<br>> <br>> You don't exactly say what your going to use the storage
for, gigabit<br>ethernet cards and switches are cheap, and you can bond (if your using linux)<br>gigabit together, some people I've heard have got over 300mb/s of read/write<br>performance using this method, and striping aoe over different disk and<br>systems. using drdb would add a layer of fault tollerance to the gig.<br>> If you go this route use PCIE gigabit adapters, not those made in pci<br>format, they are cheaper, but you'll only ever get around half the speed<br>that gigabit ethernet can go, as they just eat all the pci bus bandwidth....<br>> <br>> <br>> <br>> <br>> <br>> <br>> iscsi is interesting, but I just get more success with aoe at the moment<br>in terms of raw performance......<br>> <br>> when you get it out of your head that storage is no longer attached to<br>system, but just<br>> out there on the network somewhere, you can start doing some very clever<br>things.<br>> <br>> you don't need to
bring a server down to add sata storage, just<br>configure it somewhere<br>> else and import it. Hotswap sata driver bays are nice, but expensive.<br>> <br>> Replicate your storage array somewhere else, may to anothe building, now<br>your data<br>> is safe from falling asteriods.<br>> <br>> Using loopback devices, 'partitions' can be simple linux files<br>(all beit large), thus you can<br>> do clever thing with cow's .. mooooo.<br>> <br>> <br>> here some links....check em..<br>> <br>> http://www.drbd.org/<br>> <br>> http://www.linuxjournal.com/article/8149<br>> <br>> http://en.wikipedia.org/wiki/ATA_over_Ethernet<br>> <br>> http://www.mjmwired.net/kernel/Documentation/networking/bonding.txt<br>> <br>> <br>> A guide I wrote on using aoe vblade's with cow's.<br>> <br>> http://www.etherboot.org/wiki/appnotes/cow<br>> <br>> on the other hand, if you want to get a lot of storage, and
want support<br>etc don't forget these people....<br>> <br>> http://www.coraid.com/<br>> <br>> http://www.coraid.com/PRODUCTS/SR2421<br>> <br>> 24 Terrabytes anyone, almost enough space to store azmodie 'film'<br>collection ;-).<br>> <br>> Cheers,<br>> Lee<br>> <br>> --- On Mon, 9/3/09, Simon Wells <swells@computing.dundee.ac.uk><br>wrote:<br>> From: Simon Wells <swells@computing.dundee.ac.uk><br>> Subject: [dundee] ESATA Linux Support<br>> To: "Tayside Linux User Group" <dundee@lists.lug.org.uk><br>> Cc: "Simon Wells" <swells@computing.dundee.ac.uk><br>> Date: Monday, 9 March, 2009, 6:56 PM<br>> <br>> Does anybody have any experience of using eSATA with Linux?<br>> <br>> I have been looking<br>> at something like the following:<br>><br>http://www.amazon.co.uk/EdgeStore-DAS801T-Bay-eSATA-Enclosure/dp/B001H54JWW/ref=cm_cr_pr_sims_t<br>> <br>> My plan would be
to organise it as two separate JBOD arrays, using LVM,<br>and<br>> connected via eSATA. The two arrays will give me some measure of<br>redundancy and<br>> will make backing up my data much simpler. There is also a second remote<br>server<br>> that holds backups and very important data is also archived to DVD.<br>> <br>> At the moment I am using a whole pile of separate external USB drives and<br>want<br>> to simplify the system by getting all of the drives into a single unit. Am<br>I<br>> missing anything? I have not used eSATA with Linux myself and would like<br>to know<br>> if there are any gotchas or things that I should be aware of.<br>> <br>> Thanks,<br>> Simon<br>> <br>> Dr. Simon Wells<br>> =============<br>> <br>> E-mail: swells@computing.dundee.ac.uk<br>> IM: sw3lls@yahoo.co.uk<br>> Mail: School of Computing,<br>> Queen Mother Building,<br>> <br>> University of
Dundee,<br>> Dundee, DD1 4HN.<br>> WWW: http://quiddity.computing.dundee.ac.uk/swells/blog/<br>> Phone: +44 (0)1382 386 526<br>> Fax: +44 (0)1382 385 509 (FAO: Simon Wells)<br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> dundee GNU/Linux Users Group mailing list<br>> dundee@lists.lug.org.uk http://dundee.lug.org.uk<br>> https://mailman.lug.org.uk/mailman/listinfo/dundee<br>> Chat on IRC, #tlug on dundee.lug.org.uk<br>> <br>> _______________________________________________<br>> dundee GNU/Linux Users Group mailing list<br>> dundee@lists.lug.org.uk http://dundee.lug.org.uk<br>> https://mailman.lug.org.uk/mailman/listinfo/dundee<br>> Chat on IRC, #tlug on dundee.lug.org.uk<br><br></pre><pre>_______________________________________________<br>dundee GNU/Linux Users Group mailing list<br>dundee@lists.lug.org.uk
http://dundee.lug.org.uk<br>https://mailman.lug.org.uk/mailman/listinfo/dundee<br>Chat on IRC, #tlug on dundee.lug.org.uk</pre></blockquote></td></tr></table><br>