search for: fireproof

OK. I'm getting out the fireproof suit because it's coming and my hackles have been raised by a number of comments on the list of late. Disclaimer: No disrespect intended to the individuals of any *specific* thread. I'm a little frustrated over energy wasted on pedantic top/bottom posting crap rather than understanding...

...rsions of rails, I''d have to remember to re-modify ActiveRecord. What''s really brittle, though, is my brain. This is my first RoR app, and parts of rails (convention over config, built-in ORM and testing) I immediately loved. But some stuff seems like it would be, well, [puts on fireproof suit] easier in Java. I''m still sort of waiting for it all to come together in my mind. Anyways, apologies for being a dunce. Any guidance on how to best handle the abstract base class question would be much appreciated. John http://fryolator.com -------------- next part --------------...

...ily automated moving of certain critical, volatile backup sets from those on-line local stores via ssh to an off-site server performing the same function. 3. Daily semi- automated (somebody has to change the disc) stores of less critical and only somewhat volatile data onto DVD kept on-site in a fireproof vault. 4. Semi-automated archiving of the rest onto tape on a weekly basis and moving these off-site (the backup job is automatically scheduled but the media has to be manually handled). We currently use an internal DDS3 tape unit for store-to-tape and are considering changing to an external...

Hi list, I'm building a backup server for 3 hosts (1 workstation, 2 server). I will use bacula to perform backups. The backup is performed on disks (2 x 3TB on mdraid mirror) and for each hosts I've created a logical volume with related size. This 3 hosts have different data size with different disk change rate. Each host must have a limited sized resource and a reserved space. If a

...problems, theft or even plain old dropping it? In general you should aim for multiple backup copies; are you willing to bet the company's future on one untried copy? You should ensure that the backup copies are held preferably off site, failing that in a separate building, or else in a secure fireproof strongbox. Start by assuming you come into work one day to find the building burnt out and collapsed. Now work out how to rebuild your system on new kit on another site and you'll find that you define your backup needs. Regards, Martin On 12/10/16 12:54, Alessandro Baggi wrote: > Hi list...

...ents about using better solutions. I'd be worried though if you use a solution that doesn't remove the backup media from the vicinity of the machine. Fine if you have a remote site, but otherwise you still need a person to physically take the tapes (or whatever) out of the machine room to fireproof storage. That's pretty manual. >> Way before LVM existed we used this technique to back up VAXes >> (and later Alphas) under VMS using "volume shadowing" (ie RAID1). >> It worked quite happily for several years with disks shared >> across the cluster. IIRC it...

On 11/13/2015 12:59 PM, J Martin Rushton wrote: > Maybe I should have been clearer: use (LVM) OR (RAID1 and break). I took your meaning. I'm saying that's a terrible backup strategy, for a list of reasons. For instance, it only works if you mirror a single disk. It doesn't work if you use RAID10 or RAID5, or RAID6, or RAIDZ, etc. Breaking RAID doesn't make the data