Alan Altmark wrote: > If you *do* know how the application is implemented and fully understand > the relationships of all the files, then you can build customized backup > strategies. You can just put all relevant files on a single dasd (for flashcopy) or LVM volume (for dm-snapshot). Seems easy enough to me.
> But rather than focus on that "edge" condition, we are all, I think, in > violent agreement that you cannot take a volume-by-volume physical backup > from outside a running Linux system and expect to have a usable backup. That is a wrong assumption, I clearly disagree with it. If planned proper, and I agree that there are lots of things one can do wrong when planning the setup, physical backup of mounted and actively used volumes _is_ reliable. > Shared dasd on System z has all the same issues that shared LUNs have on > distributed systems. The backup *strategies* are identical, even if the > mechanisms used to create the backups are not. Dm-snapshot also works with shared LUNs, and Flashcopy would also do the job if the storage server in the distributed world is a shark that supports it. cheers, Carsten ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
