[Digital logo]
[HR]

Volume Shadowing for OpenVMS


Previous | Contents

Shadow server messages are always informational messages and include the prefix %SHADOW_SERVER-I-SSRVmessage-abbreviation. The following example includes the OPCOM banner and the shadow server message to illustrate what the messages look like when they are output to the console:

%%%%%%%%%%%   OPCOM 24-MAR-1990 15:01:30.99   %%%%%%%%%%% 
 (from node SYSTMX at 24-MAR-1990 15:01:31.36) 
Message from user SYSTEM on SYSTMX 
%SHADOW_SERVER-I-SSRVINICOMP, shadow server has completed initialization. 

The following messages are returned by the shadow server in response to shadow set operations. Several of the messages refer to a copy thread number; this is a unique identifier denoting a copy or merge operation. The messages in this section are listed in alphabetical order by message abbreviation. For simplicity, the messages shown here do not include the SHADOW_SERVER-I- prefix.

SSRVCMPFCPY, completing copy operation on device _virtual-unit: at LBN: LBN-location, ID number: copy-thread-number

Explanation: The copy operation has completed.
User Action: None.
SSRVCMPMRG, completing merge operation on device _virtual-unit: at LBN: LBN-location, ID number: copy-thread-number

Explanation: The merge operation has completed.
User Action: None.
SSRVCOMPLYFAIL, still out of compliance for per-disk license units, new shadow members may be immediately removed

Explanation: The number of shadow set members on the node has exceeded the number of VOLSHAD-DISK license units for more than 60 minutes. Attempts to bring the node into compliance by removing unlicensed members from their shadow sets have failed. If any new members are mounted, they might be removed immediately.
User Action: Ensure that the number of VOLSHAD-DISK license units on each node is equal to the number of shadow set members mounted on that node. If necessary, dismount shadow set members until the number of mounted members equals the number of VOLSHAD-DISK license units loaded on the node. If you need more VOLSHAD-DISK license PAKs, contact a Digital support representative.
SSRVINICOMP, shadow server has completed initialization

Explanation: The shadow server has been initialized at boot time.
User Action: None.
SSRVINICPY, initiating copy operation on device _virtual-unit: at LBN: LBN-location, I/O Size: number-of-blocks blocks, ID number: copy-thread-number

Explanation: A copy operation is beginning on the shadow set whose virtual unit number is listed in the message.
User Action: None.
SSRVINIMRG, initiating merge operation on device _virtual-unit: at LBN logical-block-number, I/O Size: number-of-blocks blocks, ID number: copy-thread-number

Explanation: A merge operation is beginning on the shadow set. The merge can occur after a copy operation has completed.
User Action: None.
SSRVINIMMRG, initiating minimerge operation on device _virtual-unit: at LBN LBN-location, I/O size: number-of-blocks blocks, ID number: copy-thread-number

Explanation: A shadowing minimerge is beginning on the device indicated. The message identifies the minimerge with the name of the shadow set virtual unit, and the LBN location of the minimerge, the size of the I/O request (in blocks), and the ID number of the copy thread. For example:
%SHADOW_SERVER-I-SSRVINIMMRG, initiating minimerge  operation on 
device _DSA2: at LBN 0, I/O size: 105 blocks, ID number: 33555161 

User Action: None.
SSRVINSUFPDL, insufficient per-disk license units loaded, shadow set member(s) will be removed in number minutes

Explanation: The number of shadow set members mounted exceeds the number of VOLSHAD-DISK license units loaded on the node. If this condition is not corrected before the number of minutes displayed in this message has elapsed, Volume Shadowing will remove unlicensed members from shadow sets in an attempt to make the node compliant with the number of loaded VOLSHAD-DISK license units.
User Action: Dismount shadow set members until the number of mounted members is equal to the number of VOLSHAD-DISK license units on the node.
SSRVNORMAL, successful completion of operation on device _virtual-unit: at LBN LBN-location, ID number: copy-thread-number

Explanation: The copy or merge operation has completed.
User Action: None.
SSRVRESCPY, resuming copy operation on device _virtual-unit: at LBN: logical-block-number I/O size: number-of-blocks blocks, ID number: copy-thread-number

Explanation: A copy operation is resuming. The message identifies the copy with a unique sequence number, the name of the shadow set virtual unit, the LBN location of the copy, and the size of the I/O request (in blocks). For example:
%SHADOW_SERVER-I-SSRVRESFCPY, resuming Full-Copy copy sequence number 
16777837 on device _DSA101:, at LBN 208314  I/O size: 71 blocks 

User Action: None.
SSRVSPNDCPY, suspending operation on device _virtual-unit: at LBN: logical-block-number, ID number: copy-thread-number

Explanation: A copy operation is being interrupted before it completes. (If a crash occurs during a copy operation, a minimerge assist can interrupt the copy operation to resolve inconsistencies. The shadowing software can resume the copy operation when the minimerge completes.) The following message identifies the copy operation with the name of the shadow set virtual unit, the LBN location of the copy, and a unique ID number.
%SHADOW_SERVER-I-SSRVSPNDCPY, suspending operation on 
device _DSA101:. at LBN: 208314, ID number: 16777837 

User Action: None.
SSRVSPNDMMRG, suspending minimerge operation on device _virtual-unit: at LBN: logical-block-number ID number: copy-thread-number

Explanation: A minimerge is interrupted before it completes. The message identifies the minimerge with the name of the shadow set virtual unit, the LBN location of the minimerge, and a unique ID number. For example:
%SHADOW_SERVER-I-SSRVSPNDMMRG, suspending minimerge operation 
on device _DSA101:. at LBN: 3907911, ID number: 16777837 

User Action: None.
SSRVSPNDMRG, suspending merge operation on device _virtual-unit: at LBN: LBN-location, ID number: copy-thread-number

Explanation: A merge operation has been suspended while the shadow set undergoes a copy operation.
User Action: None.
SSRVTRMSTS, reason for termination of operation on device: _virtual-unit:, abort status

Explanation: This message always accompanies the SSRVTERM message to provide further information about the copy termination.
User Action: Possible actions vary depending on the reason for the error. You might need to check and repair hardware or restart the copy operation.
SSRVTERMCPY, terminating operation on device: _virtual-unit:, ID number: copy-thread-number

Explanation: The copy thread is aborting. See the accompanying SSRVTRMSTS message for more information.
User Action: None.
SSRVTERMMRG, terminating operation on device: _virtual-unit:, ID number: copy-thread-number

Explanation: The merge thread is aborting. See the accompanying SSRVTRMSTS message for more information.
User Action: None.
SSRVTERMMMRG, terminating operation on device: _virtual-unit:, ID number: copy-thread-number

Explanation: The minimerge thread is aborting. See the accompanying SSRVTRMSTS message for more information.
User Action: None.

B.4 VOLPROC Messages

Shadowing operations can display the following status messages on the system console (OPA0) and on terminals enabled to receive disk operator messages.

Shadowing messages always include the prefix %SHADOW-I-VOLPROC and can sometimes be followed by "Volume Processing in Progress." The messages are displayed in the following format:

%SHADOW-I-VOLPROC, message-text

The following example shows a complete volume-processing status message:

%SHADOW-I-VOLPROC, DSA13: shadow set has changed state. Volume processing 
                        in progress. 

The following messages are returned by the VOLPROC in response to shadow set operations. The messages in this section are listed in alphabetical order beginning with the first word after the shadow set member name or the virtual unit name. For simplicity, the messages do not include the %SHADOW-I-VOLPROC prefix.

shadow-set-member: contains the wrong volume.

Explanation: The shadowing software discovered a volume label mismatch after failover.
User Action: Check the disk drives and unit numbers.
shadow-set-member: has aborted volume processing.

Explanation: The shadow set is dissolved. A shadow set member was not restored to operational status before the MVTIMEOUT system parameter setting expires; thus, the mount operation aborts for the shadow set.
User Action: Check error logs and the shadow set membership; the disk or controller might need repair.
shadow-set-member: has been write-locked.

Explanation: The data on the disk is protected against write I/O operations.
User Action: Remove the write lock on the volume.
shadow-set-member: has completed volume processing.

Explanation: The shadow set state change is complete.
User Action: Check the shadow set membership; the disk or controller might need repair.
shadow-set-member: is offline.

Explanation: A shadow set member is off line. The shadowing software attempts to fail over.
User Action: None.
shadow-set-member: shadow copy has been completed.

Explanation: A shadow copy operation has completed.
User Action: None.
shadow-set-member: shadow set has been reduced.

Explanation: The specified shadow set member has been removed.
User Action: If the member failed out of the set (not dismounted), look for the cause of the failure and repair it.
virtual-unit: all shadow set copy operations are completed.

Explanation: All pending shadow set copy operations have completed. The same logical block on any shadow set member contains the same data.
User Action: None.
virtual-unit: shadow copy has been started.

Explanation: Indicates the start of a shadow copy operation.
User Action: None.
virtual-unit: shadow master has changed. Dump file will be written if system crashes. Volume Processing in progress.

Explanation: The shadowing software has determined a new master disk for the system disk shadow set. You can write a dump file for this system only if the master is the same disk as the one the system booted from. This is because the boot drivers are not connected with the shadow driver, and different boot drivers from the ones that interact with the booted system disk might be needed to interact with the new master disk. For example, a system disk could be served and also locally connected, causing the served path to use different drivers from the local path.
User Action: None.
virtual-unit: shadow master has changed. Dump file will not be written if the system crashes. Volume processing in progress.

Explanation: Indicates that the disk from which you booted is no longer in the shadow set. If a system failure occurs, a dump file cannot be written to the removed disk.
User Action: Return the disk to the shadow set.
virtual-unit: shadow set has changed state. Volume processing in progress.

Explanation: The state of the shadow set is in transition. The membership of the shadow set is changing because of either the addition or removal of members from the shadow set, or failover to another device after a hardware error. Further messages give details if a change occurs.
User Action: None.


Index | Contents | [Home] | [Comments] | [Ordering info] | [Help]

[HR]

  5423P009.HTM
  OSSG Documentation
  22-NOV-1996 13:03:49.55

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal