HP Integrity NonStop H-Series - Manual (Page 306)

Managing DSM/SCM
DSM/SCM User’s Guide — 529846-014
17 - 13
Moving the ZDSMSCM Subvolume to Another
Volume
Moving the ZDSMSCM Subvolume to Another Volume
You should normally use the first ZDSMSCM subvolume installed on the system,
regardless of how many subvolumes are created by subsequent additions of targets.
However, you can run DSM/SCM from a volume other than the one on which INITENV
was run. You can create ZDSMSCM subvolumes on other volumes, but the subvolume
name cannot change.
Creating a New ZDSMSCM Subvolume
To change ZDSMSCM subvolumes:
1. Copy the existing ZDSMSCM subvolume to a new volume:
> FUP DUP $oldvol.ZDSMSCM.*, $newvol.*.*,saveall
2. Edit the PATHCOOL file to point to the $newvol.PATHSCM and the
\system.$newvol.ZDSMSCM.PATHMAIN.
3. Replace all occurrences of $oldvol.ZDSMSCM with $newvol.ZDSMSCM in the
PATHTARG or PATHHOST file.
4. Run PATHCOLD from $newvol.ZDSMSCM to create $newvol.PATHSCM.*.
5. Run STARTSCM from $newvol.ZDSMSCM.
6. Update Winsock with the new volume name:
a. Edit the $vol.ZTCPIP.PORTCONF file to point to $newvol.ZDSMSCM.
b. Cycle the TCP/IP LISTNER process. For more information, see the TCP/IP
documentation.
7. Run Verify Database. (See Verifying the Target System Database (ZPHITI) on
page 17-18.)
8. Create an independent snapshot. (See Creating an Independent Snapshot of the
Target System on page 17-19.)
9. Receive the snapshot into the host database. (See Task 9: Transfer and Receive
the Snapshot Into the Host Database on page 9-27.)
To purge $oldvol.ZDSMSCM.* after you have confirmed that DSM/SCM is running
properly, use the new ZDSMSCM subvolume. After purging an old ZDSMSCM
subvolume, repeat Steps 7 through 9.