Designate an Alternate CRR Recovery Server

When a CRR recovery server is unavailable, an existing SFS file pool server may be designated to act as an alternate CRR recovery server.

Note: In this situation, you temporarily have one server acting as both an SFS file pool server and a CRR recovery server, which normally is not recommended.

The alternate CRR recovery server can use the same CRR logs as the original CRR recovery server. To designate an SFS file pool server as an alternate CRR recovery server:

Log on the original CRR recovery server machine, and if in multiple user mode, enter a STOP or STOP BACKUP command. This allows the original CRR recovery server to complete any active sync points before stopping.
Process the SETUP EXEC to access minidisks needed by the original CRR recovery server machine (For more information, see SETUP EXEC):
```
setup
```
Change the CRR and LUNAME luname startup parameters to NOCRR and NOLUNAME in the original CRR recovery server's DMSPARMS file. If the optional RESYNCINTERVAL startup parameter was specified, delete it.
Remove the definition of the CRR logs from the original CRR recovery server's POOLDEF file:
```
fileserv defcrrlog delete
```
Using standard operating procedures for your installation, update the z/VM® system directory for the CRR recovery server to specify a write access password for the CRR log minidisks, if they do not already have one.
For example, if you have the IBM Directory Maintenance program, and the CRR log minidisks are at virtual device numbers 306 and 307, you would enter:
```
dirm mdisk 306 w writepass
dirm mdisk 307 w writepass
```
where:

writepass

is the write access password you are assigning to the CRR log minidisks. Save writepass for use in step 9.
Detach the CRR log minidisks from the original CRR recovery server:
```
det 306
det 307
```
Log on the existing SFS file pool server machine.
If you set up the existing SFS file pool server machine for automatic starting, as instructed in Generating a File Pool and Server, you will have to avoid executing the PROFILE EXEC when CMS is initializing. Otherwise, the PROFILE EXEC will issue a FILESERV START command.
To avoid having the PROFILE EXEC process, enter this command immediately after IPL CMS:
```
access (noprof
```
If you forget to enter the above command, stop the existing SFS file pool server by entering one of these commands:
```
stop backup
stop nobackup
```
Either one of these commands allows the existing SFS file pool server to complete any active logical units of work before stopping.
Process the SETUP EXEC to access minidisks needed by the existing SFS file pool server machine (For more information, see SETUP EXEC):
```
setup
```
Link to the CRR log minidisks that were just detached from the original CRR recovery server in step 6:
```
link to userid 306 as vdev1 w writepass
link to userid 307 as vdev2 w writepass
```
where:

userid

is the user ID of the original CRR recovery server.

306 and 307

are the virtual number of the CRR log minidisks just detached from the original CRR recovery server.

vdev1 and vdev2

are the virtual device numbers you want to assign to the CRR log minidisks for the alternate CRR recovery server (you could use 306 for vdev1 and 307 for vdev2).

writepass

is the write access password for the CRR log minidisks you saved in step 5.

Note: This link to the CRR log minidisks is only good for the present session. If z/VM goes down or if you log off, the link is gone. Consider having your system administrator add a link to the server's z/VM system directory in case the designation of the alternate CRR recovery server will last for an extended period of time. If you do this, do not forget to have the system administrator delete the links to the CRR log minidisks when this alternate CRR recovery server is no longer needed.
Define the CRR log minidisks to the existing SFS file pool server's POOLDEF file.
When entering the FILESERV DEFCRRLOG command, specify the virtual device numbers of the CRR log minidisks. If, for example, the CRR log minidisks are at virtual device numbers 306 and 307, you would enter:
```
fileserv defcrrlog 306 307
```
Add the CRR and LUNAME luname startup parameters to the existing SFS file pool server's DMSPARMS file. If the optional RESYNCINTERVAL startup parameter was specified in the original CRR recovery server's DMSPARMS file, add it here.
Note: You should specify the same luname as was specified in the original CRR recovery server's LUNAME startup parameter.
Start the existing SFS file pool server as the alternate CRR recovery server:
```
fileserv start
```

When the original CRR recovery server becomes available, change the alternate CRR recovery server back to an SFS file pool server see Remove Designation of Alternate CRR Recovery Server.