-create {mover=<source_movername> [-policy <policy_type>]}
Designates the <source_movername> as the standby. The following
rules apply when selecting a standby Data Mover:
• The primary Data Mover cannot be a standby Data Mover.
• A standby cannot be created for a standby.
• No file systems can be mounted on the standby.
• The standby must have the same disk configuration as the
• One standby Data Mover can be created for multiple Data
-policy <policy_type>
When a fault is detected on the primary Data Mover, the
following -policy options apply:
-create rdf[=<slot_number>
Designates a remote RDF standby Data Mover as indicated by its slot
number.
SEE ALSO
Configuring Standbys on Celerra, server_setup.
EXAMPLE #1
To create a standby relationship between server_2 (primary) and
server_3 (standby), type:
$ server_standby server_2 -create mover=server_3
server_2 : server_3 is rebooting as standby
Note: Before any other actions can take place, the reboot must be complete.
EXAMPLE #2
To activate the server_3 (standby) to take over for server_2 (primary),
type:
$ server_standby server_2 -activate mover
server_2 :
server_2 : going offline
primary.
Movers. To do this, execute server_standby -create for each
primary Data Mover.
auto
Initiates immediate activation of the standby Data Mover.
retry
Attempts to recover the primary Data Mover first, then if
recovery fails, initiates activation of the standby.
manual (default)
Reboots the primary Data Mover. No action on the standby is
initiated.
]
]
The server Commands
457
server_standby
Need help?
Do you have a question about the Celerra and is the answer not in the manual?