HP Storage Mirroring Software User Manual
Page 412
![background image](/manuals/396814/412/background.png)
Workload monitoring
Page 411 of 677
l
(112) Disk full: The disk to which data is being written on the target is
full. This issue may be resolved by deleting files on the target machine
or by adding another disk.
52501 Target module loaded successfully
The Storage Mirroring Recover target module was loaded successfully.
52502 Target module already loaded
The Storage Mirroring Recover target module was already loaded.
52503 Target module stopped
The Storage Mirroring Recover target module stopped.
53001 File was missing from target
The verification process confirms that the files on the target are identical to
the files on the source. This message would only appear if the verification
process showed that a file on the source was missing from the target.
53003 Could not read filename
Storage Mirroring Recover could not read a file on the source machine
because the file may have been renamed or deleted. For example,
temporary files show up in queue but do not show up during transmission.
(No user action required.)
54000 Kernel started
The Storage Mirroring service was started.
54001 Failover module failed to load
The Storage Mirroring Recover failover module failed to load. Look at
previous log messages to determine the reason.
54503 Failover module stopped
The Storage Mirroring Recover failover module stopped.
99001 Starting source module low memory processing
The source’s queue is full, and the auto-disconnect process will
disconnect the source and target connection. The auto-reconnect process
will automatically reestablish the connection if the auto-reconnect feature
is enabled. If the auto-reconnect feature is not enabled, you must first
verify that the connection between the source and target has been broken,
and then manually reestablish the connection in the Replication Console.
99999 Application is terminating normally
The Storage Mirroring service is shutting down normally.