Sun Microsystems 3 Manual Do Utilizador
1
C H A P T E R
1
Overview
Caution –
Do not install or use the Sun StorEdge Version 3.0 Core and data services
software on servers in a Sun Cluster 3.0 environment. The Version 3.0 software is
not co-existent with the Sun Cluster 3.0 environment.
not co-existent with the Sun Cluster 3.0 environment.
The Version 3.0 software is
co-existent in the Sun Cluster 2.2 environment, where it will not interfere with
failover. The Version 3.0 core and data services software is cluster aware in the Sun
Cluster 3.0 Update 1 environment and provides high availability for the Sun
StorEdge software.
failover. The Version 3.0 core and data services software is cluster aware in the Sun
Cluster 3.0 Update 1 environment and provides high availability for the Sun
StorEdge software.
Sun SNDR Software Description
The Sun SDNR software is a remote replication facility for the Solaris™ operating
environment. It is intended for use as part of a disaster recovery and business
continuance plan to provide redundant storage of critical information across
physically separate sites. It is designed to be active during normal application access
to the data volumes, and it will continually replicate the data to the remote site.
continuance plan to provide redundant storage of critical information across
physically separate sites. It is designed to be active during normal application access
to the data volumes, and it will continually replicate the data to the remote site.
The Sun SDNR software enables you to replicate disk volumes between physically
separate primary and secondary hosts in real time. To transport data, the Sun SDNR
software uses any Sun network adapter that supports TCP/IP.
separate primary and secondary hosts in real time. To transport data, the Sun SDNR
software uses any Sun network adapter that supports TCP/IP.
The Sun SNDR software volume set consists of a primary volume residing on a local
host and a secondary volume residing on a remote host. The volume set also
includes a bitmap volume on each host to track write operations and differences
between the volumes.
host and a secondary volume residing on a remote host. The volume set also
includes a bitmap volume on each host to track write operations and differences
between the volumes.
You can update the data on the secondary volume by issuing a command to
resynchronize the volumes. You can also restore data from the secondary volume to
the primary volume by issuing a command to reverse resynchronize the volumes.
resynchronize the volumes. You can also restore data from the secondary volume to
the primary volume by issuing a command to reverse resynchronize the volumes.