51CTO下载-HP-存储虚拟化技术-解决方案摘要.ppt

What about physical protection? Such as a Rack in a data center, a data center in a building or and entire building. LeftHand takes Network RAID to the next level with the Multi-site SAN. Since data is replicated across the SAN in such a way that a full copy exists on odds and evens, we can physically separate a cluster so odds are in one site and evens in the other. You define the site. It can be between racks in a data center that are on different power circuits and have different cooling units. Now, not only do you have protection at he node level, but you can an entire rack could go offline and your data would remain available. In fact, as long as you have gig connectivity, low latency, and a volume that is 2-way replicated, you can separate your cluster by what ever means available. Bottom line. You can survive any single point of failure up to, and including a site. Once again, this is included by default. * * 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