[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] does DUMP backup only the 'used' HD fraction, OR, the 'entire' HD, blank space and all ?
- Subject: [ale] does DUMP backup only the 'used' HD fraction, OR, the 'entire' HD, blank space and all ?
- From: transam at VerySecureLinux.com (Bob Toxen)
- Date: Fri, 9 Mar 2012 15:43:10 -0500
- In-reply-to: <[email protected]>
- References: <[email protected]> <CAEo=5Px1AnnpRUK1JKpDLru9CGm8=wYd97VPykhtV60fBvsZag@mail.gmail.com> <[email protected]> <[email protected]>
ACLs were not being used.
Either restor was broken or the person at Rackspace was in the pile of
tools needing sharpening, IMO.
Bob
On Fri, Mar 09, 2012 at 02:42:30PM -0500, Vernard Martin wrote:
> On 3/9/2012 2:13 PM, Bob Toxen wrote:
> >Beware!
> >
> >Some versions of dump/restore fail to preserve directory permissions,
> >instead creating all directories mode 777 on restore!
> >
> >I saw this about 5 years ago when Rackspace restored my client's backup
> >following hard disk failure. It was UGLY to recover from.
> >
> >I'd suggest either rsync or tar.
> >
> >Be sure to ALSO record inode to file names. This is critical in case of
> >file system damage so that when fsck reports inode ### as damaged you
> >know which file/dir to restore.
> >
> >I suggest something similar to the following just before one does
> >backups so that /root/inode_list can be recovered from backup if
> >necessary.
> >
> > find / -ls> /root/inode_list
> >
> Also check and verify that ACLs are not being used. IF they are,
> then you need to save/restore those as well. Rsync is nice and will
> do this for you but judicious use of getfacl/setfacl is sometime
> most efficacious.
>
> V