On Tue, Nov 29, 2005 at 11:29:19AM -0700, Michael Loftis wrote: > LVM provides a block level device. However you don't want to back up there > anyway, you'll just end up with corrupt garbage. You need to back up at > the filesystem level unless you're using your LVM LVs for Oracle or > something similar in which case the backup software needs to support that > by putting Oracle or the related application into the correct hot backup > mode before attempting to directly read the LVM data, as well as backing up > the transaction/redo logs. Surely by using snapshots, a block level backup could be "OK". You'd need to (ideally) tell the file-system layer to put the machine into a fit state to be snapshotted (quick & dirty, obviously issues with it, you could remount it readonly, snapshot, and then mount read-write again). It's also going to backup dead space, which is going to waste backup media (e.g. tape) at best, and leak information at worst. If you have a journalling filesystem, then taking a snapshot of the active device would probably be acceptable... Not ideal, but depending on the relative importance of getting a perfect backup/restore and reducing the load on the system while the backup is being done, it might be acceptable to most people. Obviously if your backup solution can tie into the filesystem's own backup utilities then you're going to get a better result, but for some people that's not the important thing (and not an option in backup utilities for others). I know that dump/restore on solaris is unsafe to use on live partitions, I can't see any reference within the dump man pages to see if the same applies to linux, and have never used it in anger on an active filesystem - old habits die hard, so I do my best to keep it inactive when using it. Graham _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
