HP StorageWorks P4000 G2 SAN 解决方案.pptVIP

Presentation Title Copyright ? 2005 LeftHand Networks corporate presentation. All rights reserved. * * Remote Copies are based on snapshots. A Remote Copy is essentially a snapshot that is copied to a remote cluster. Because they’re based on snapshots, they also take advantage of thin provisioning and do not require reserve space. If you have a primary site with volumes and snapshots and a second DR site, you can copy the volume and snaps to the remote site via your WAN link Remote copies can be scheduled based on your DR needs. The initial data copy copies the entire volume – Each additional remote copy sends only the changed data to the remote site. Remote Copies can be run over most any WAN link, and can take advantage of WAN encryption (VPN) and/or compression (Riverbed) Bandwidth can be managed through the CMC by editing the management group properties. Like snapshots, no space needs to be reserved ahead of time on the remote cluster You can mount these remote copies as fully readable and writable volumes, so that if the primary site goes down, you simply attach the remote copy to a host and continue A wizard guides you through both the failover and failback scenarios * * Presentation Title Copyright ? 2005 LeftHand Networks corporate presentation. All rights reserved. * This slides describes what University of Maryland has implemented Campus SAN across 6 city blocks Point out that it is a single volume with replicated blocks written to multiple sets of modules in the cluster – this is key vs. separate SAN at each site with two sets of volumes that need to be managed as primary secondary and have VM pointed to right volumes at second site after VMware HA brings them up at the other site. Full automated failover, failback of BOTH application servers and associated storage Key is no system admin time or on-site presence required to get applications back on line at other site after site failure. VM’s reconnect to volume automatically – it is same volume as