HP Hitachi Dynamic Link Manager Software Licenses - Manual (Page 161)

Note
In Solaris 8 or Solaris 9, find and make a note of the boot device
names to specify in the OBP for all owner paths in case an error
occurs on the path specified for the boot device.
12
.
Boot the system from the post-migration environment.
¢
Perform steps 13 to 17 only if SDS or SVM is being used and you are
migrating a replica of the SDS or SVM state database to the post-
migration environment. In this case, keep the pre-migration
environment recognized by Solaris.
¢
Skip to step 18 if SDS or SVM is being used but you are not migrating
a replica of the SDS or SVM state database to the post-migration
environment.
¢
Skip to step 18 if SDS or SVM is not being used.
13
.
Check the state database settings.
An example is shown below.
14
.
Add the post-migration boot disk to the SDS or SVM state database.
An example is shown below.
# metadb -a /dev/dsk/c8t50060E80004361D1d1s7
# metadb -a /dev/dsk/c8t50060E80004361D1d2s7
# metadb -a /dev/dsk/c8t50060E80004361D1d3s7
15
.
Make sure that the post-migration boot disk has been added to the SDS
or SVM state database.
An example is shown below.
16
.
Delete the SDS or SVM state database replica that exists in the pre-
migration boot disk.
The following shows an example of executing the command:
# metadb -d /dev/dsk/c0t0d0s7 /dev/dsk/c0t0d1s7 /dev/dsk/c0t0d2s7
17
.
Make sure that the SDS or SVM state database replica that exists in the
pre-migration boot disk has been deleted.
The following shows an example of executing the command:
Creating an HDLM Environment
3-95
Hitachi Dynamic Link Manager (for Solaris) User Guide