Symantec高可用解决方案-v211.ppt

* 1) Improving Volume Migrations – We use traditional volume copy commands to move storage between arrays. We leverage already proven technologies in SF, but help you automate this. 2) Path management – example: port maintenance on an array. You need to check hosts (and owners of hosts) before you pull a path. Don’t want to eliminate path to active host, by pulling path down. a. The process is a mess. The storage team gives you a port number and wants you to upgrade things mapped to this port. Mapping port numbers to path names is not a simple process. You don’t want to get these things wrong. b. Nobody wants to spend 4-5 hours doing this. We automate it. 3) Tiered storage – Moving data is not the problem. Keeping the same namespace is the trick. Also, maintaining policies and propagating these policies across hosts is imperative. SFM delivers this centrally. * * * * * First, let’s make sure we’re all in agreement that multi-pathing is important. You need multi-pathing whenever you have multiple connections between a host and block storage, whether these are multiple physical connections in the case of direct attached storage, or multiple network connections in the case of SAN attached storage. Either way, you need a mutli-pathing driver to: 1.- Optimize application performance and ensure you are getting the most out of your physical infrastructure. 2.- Optimize application availability and protect them from failures of some of the connections. In this example, we have switch failure taking down one of the connections and the multipathing driver seamlessly failing over I/O traffic onto the remaining active path. 3.- Provide flexibility to both your server team and the storage team, and that provides enough visibility into the storage domain to enable your system admins to do their work accurately and efficiently. This last point is increasingly important as datacenter management becomes more complex. * * * * * * * * * Need to update with CMC graphic. - S