Fujitsu Cloud Edition V3.1.0 User Manual

Once collected, cloning images can be deployed to one or more destination servers.

Cloning images collected from the source server can only be deployed to destination servers which satisfy the following conditions:

-

Destination servers should be in either "normal", "warning", "unknown", or "stop" status.

-

Destination servers should have been placed into maintenance mode.

-

Destination servers should be of the same model as the source server.

-

I/O virtualization should be used, when destination servers are spare servers.

Cloning images cannot be deployed to managed servers where VM hosts or VM guests are running.

 

-

When the configurations of managed servers are as below, execute the following commands before deploying cloning images.

-

In a SAN data environment using a built-in disk boot, and a physical WWN or VIOM

[Windows Manager]

 

>

Installation_folder

\SVROR\Manager\bin\rcxadm server set -name 

physical server 

<RETURN>

[Linux Manager]

 

#/opt/FJSVrcvmr/bin/rcxadm server set -name 

physical server

 -attr bootagt=dos <RETURN>

-

When using the Red Hat Enterprise Linux 6 ext4 file system, and one of the following conditions is met

-

In a SAN boot environment using HBA address rename

-

When using a rack mount or tower server and the server is registered with "Disable" of "Association with server management
software (ServerView)" is selected

[Windows Manager]

 

>

Installation_folder

\SVROR\Manager\bin\rcxadm server set -name 

physical server

 -attr bootagt=winpe

<RETURN>

[Linux Manager]

 

#/opt/FJSVrcvmr/bin/rcxadm server set -name 

physical server

 -attr bootagt=winpe <RETURN>

-

In a SAN boot environment using HBA address rename, and the following model

-

PRIMERGY BX960 S1

[Windows Manager]

 

>

Installation_folder

\SVROR\Manager\bin\rcxadm server set -name 

physical server

<RETURN>

[Linux Manager]

 

#/opt/FJSVrcvmr/bin/rcxadm server set -name 

physical server

 -attr bootagt=winpe <RETURN>

If the above command has not been executed on the server from which the cloning image is being collected, the cloning image may
not be collected correctly. Delete that cloning image and then redo the cloning image collection.

- 125 -