Yesterday I was talking with a Symantec user about the decisions you have to make when picking how to recover from a failure. Like most companies they had a whole slew of options from clustering and high-availability, to replication, snapshots and tape. Most people we talk with have some idea of the amount of time they can tolerate to get back up from a failure and the amount of data they are willing to lose but these two things (time and data lost) are more related than most people think and this user especially understood that...particularly when it comes to applications. It really is one of the biggest problems applications have when you try to back them up. They have to be stopped or paused since some data may be in memory or logs that haven't been fully written to disk. So most backup apps have a "hot backup" mode or quiesce (I can never spell that word) that lets you flush the application out so it can be backed up in a known...