of server log and system log messages, refer to the Celerra Network Server Error
Messages Guide.
5 Notice
6 Info
7 Debug
Table 18 Server Log Message Severity Levels (Continued) Severity
Level Meaning
Table 19 Server Log Messages
Server Log Messages Definition Corrective Action Other Considerations
/.etc/BackupDates corrupted, it has been renamed in
BackupDates.bad and rebuilt
The /.etc/BackupDates file, which saves backup dates, is corrupted.
No corrective action is necessary.
The backup level has been reset. You will need to restart the backup. There is no impact to a previous restore, if applicable. <MOVER_LISTEN> before tape open
The NDMP client sends a MOVER_LISTEN request before a TAPE_OPEN request.
Verify that your backup software is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Note: The backup or restore will fail if the client does not correct the error.
<MOVER_LISTEN> with read only tape
A Data Mover listen request requires a tape write, but the tape is in read-only mode.
Verify that your backup software is qualified with Celerra.
The NDMP client needs to send the message in read/write mode.
Refer to EMC NAS Interoperability Matrix on page 12.
3-way DAR unable to fsr
1234, residualCount 998 Occurs during a three-way direct access restore (DAR). The forward skip record failed with the remaining records and the restore fails.
Verify that your hardware, drivers, and backup software are qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Answer occurred with pdi==NULL
This point should not be reached with pdi==NULL. The Data Mover terminates the NDMP job, and the backup
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Backup type not supported: ufsdump
Celerra does not support the backup type specified in the NDMP backup software. Celerra supports the tar and dump backup types.
This message occurs when using NDMP version 2.
Verify that the NDMP client is using either the tar or dump backup type.
Refer to your backup software vendor’s documentation and to
Setting Environment Variables on page 34.
Note: The backup will fail without a valid backup type specified.
BlockBuf count in PAX Pool: <number>
Displays the number of buffers initialized in the pool. This message reflects the PAX ReadBuff parameter.
<number> = number of buffers
To change the parameter values, edit the param file.
Refer to Configuring Data Movers on page 21.
Cannot reply connect An error occurred when sending a reply to
CONNECT_OPEN. The Data Mover terminates the NDMP backup job.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
cannot send
NDMP_CONFIG_GET_TAPE_IN FO reply
An error occurred when sending a reply to this message. The Data Mover terminates the NDMP backup job.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
cannot send
NDMP_CONNECT_OPEN reply
A reply to this request cannot be sent. The Data Mover terminates the NDMP job.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Table 19 Server Log Messages (Continued)
Can't convert filename using the specified NDMP.dialect, or invalid utf8 filename: 0x999
inode_%3456 is using for filename
These two messages appear together and indicate one of the following:
• Internationalization on a Data Mover is turned on and the specified dialect cannot be used to convert the filename from UTF-8 to the client’s dialect.
• The original filename is not a valid UTF-8 name. For example, if a Celerra client (which may be a different client from the NDMP client) creates a file using a character outside its own code page, Celerra saves the filename using an invalid UTF-8 name. In the inode_%3456 error message, inode_<number> is used in place of the file name.
Verify that the NDMP
dialect parameter specifies the correct dialect.
Refer to Configuring Data Movers for International Character Sets on page 25.
Can't have DIRECT=y/Y, and RECURSIVE=y/Y
Celerra does not support a recursive restore for a directory using DAR. The Celerra rejects this type of restore.
In your backup software, change the recursive restore setting to n.
Verify that your backup software is qualified with Celerra.
For more information about DAR, refer to the NDMP Backup Concepts on page 6
section. For information on environment variables, refer to Setting Environment Variables on page 34 and to your backup software vendor’s documentation.
Can't open file_name for write in 3214 File <file_name> create error in 3294
These two messages indicate that the Celerra encountered a problem opening a file during a restore. The file
<file_name> is skipped, and the restore continues.
Verify that your backup software is qualified with Celerra. The problem may be due to a failed backup.
Refer to EMC NAS Interoperability Matrix on page 12.
create /.etc/ BackupDates file failed, error: <error message>
Creation of the file
BackupDates failed. This file saves backup dates.
The backup is terminated. <error message> = type of error, for example, I/O error
You need to restart the backup.
Data interface is already deleted
At the time of a DATA_STOP request, the Data interface is already deleted.
The backup should complete successfully.
No action is needed. Table 19 Server Log Messages (Continued)
Empty archive The FILESYSTEM or PREFIX NDMP environment variable is not set in the NDMP client software.
On the NDMP client, set a value for the FILESYSTEM or PREFIX environment variable.
Refer to Setting
Environment Variables on page 34 and to your backup software vendor’s
documentation.
Error in NDMP restore arguments, argument <argument>
An error in the restore argument occurred. <argument> = argument name, for example, TYPE
Verify in the server log that you specified the correct backup root and path, for example, verify the spelling and the pathname.
ERROR MOVER try to Abort in state <state>
The state is illegal for aborting the MOVER interface; legal states are LISTEN, ACTIVE, or PAUSED.
<state> = mover interface state, for example,
NDMP_MOVER_STATE_IDLE
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER try to change record size in state <state>
The state is illegal for setting record size; only the IDLE state is legal.
<state> = mover interface state, for example,
NDMP_MOVER_STATE_ACTIVE
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER try to Continue in state <state>
The state is illegal for a MOVER_CONTINUE command; only the PAUSED state is legal. <state> = mover interface state, for example,
NDMP_MOVER_STATE_ACTIVE
Verify that your backup software is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER try to disconnect in state not connected
In a three-way configuration, the mover interface tried to disconnect while in a disconnected state.
Verify that your backup software vendor is qualified with Celerra and supports three-way backups.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER try to Listen in state <state>
The NDMP client tried to stop the data interface in an invalid state.
<state> = mover interface state, for example,
NDMP_MOVER_STATE_ACTIVE
Verify that your backup software is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER try to Set window in state <state>
The state is illegal for setting window size; only LISTEN or PAUSED states are legal.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Table 19 Server Log Messages (Continued)
ERROR MOVER try to Stop in state <state>
The state is illegal for stopping the MOVER interface; only the HALTED state is legal. <state> = mover interface state, for example,
NDMP_MOVER_STATE_IDLE
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER try to Stop in state <state>
Reason:<reason>
The NDMP client sent a message not compliant with the NDMP Version 4 specification.
<state> = mover interface state, for example,
NDMP_MOVER_STATE_IDLE <reason> = reason for pause, for example,
NDMP_MOVER_PAUSE_EOF
Confirm that your NDMP client software is qualified with Celerra.
If your software is qualified, then this message is
informational only and you do not need to take any action.
Refer to EMC NAS Interoperability Matrix on page 12.
ERROR MOVER type LOCAL try to Read
This should be a three-way read, but the mover interface type is not three-way compliant (it is not TCP).
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Error on checking restore name list
An error occurred in the restore name list, which contains the file and directory names to restore.
Verify that the file and directory names you want to restore are listed correctly.
Refer to your backup software vendor’s documentation.
Error on environment variable: <variable>
The NDMP client sent an invalid environment variable. <variable> = variable associated with the error, for example, LEVEL
Verify that the environment variable listed in the log message is supported by Celerra.
Refer to Setting
Environment Variables on page 34 and to your backup software vendor’s
documentation.
extractFtreeList: bad path /xyz
The backup path provided does not exist.
Ensure that the correct path was specified and that the files specified for backup exist.
Note: This path is an absolute path and is case-sensitive.
Refer to your NMDP client documentation for more information.
level exceeded maximum allowed (11)
An incorrect increment level for backup was specified in the NDMP client software.
Verify that the backup level specified by the NDMP client is between 0 and 10.
Refer to Setting
Environment Variables on page 34 and to your backup software vendor’s
documentation. Table 19 Server Log Messages (Continued)
Mover connection error (connectDone)
A connection to a three-way Data Mover accepting a TCP stream failed.
The NDMP client sent an invalid command.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Mover continue before changing tape!!!
A MOVER_CONTINUE request was sent by the NDMP client before the tape was changed. The backup fails.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
Mover not created The NDMP client sent an invalid command.
The mover interface was not created when the NDMP client requested
CONFIG_GET_CONNECTION_ TYPE.
Verify that your backup software vendor is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
name /foo/
skoilksfoiefslk... length 1102 too long
A pathname and filename is greater than 1024 bytes, which exceeds Celerra’s limit.
Ensure that the file and pathnames in the backup directory are less than 1024 bytes.
Refer to your NDMP client documentation.
ndmp already started The NDMP client attempted to start an NDMP listen thread while one was already running; starting another is
unnecessary.
Verify that your backup software is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
NDMP Tape parameter not set.
NDMP_TAPE_OPEN_REQUEST denied.
The NDMP ntape parameter is not set in the param file. The ntape parameter specifies the number of tape drives attached to a Data Mover.
Set the NDMP ntape parameter in the param file, and then reboot the Data Mover.
Note: You must set this parameter for both Data Movers involved in a three- way backup.
Refer to Configuring Data Movers for NDMP Backups on page 22.
NDMP.bufsz > 1168K in param file, bufsz was reset to 128K.
The Data Mover’s buffer size parameter (bufsz) is too large.
The bufsz value is
automatically reset to 128 KB, the default value.
To change the bufsz parameter value, edit the param file, and then reboot the Data Mover.
Refer to Configuring Data Movers for NDMP Backups on page 22.
Table 19 Server Log Messages (Continued)
NDMP_MOVER_STATE_ACTIV E
For NDMP V4, the state is illegal for setting the window size; only the LISTEN and PAUSED states are legal.
Verify that your backup software is qualified with Celerra and supports NDMP Version 4.
Refer to EMC NAS Interoperability Matrix on page 12. For more information on NDMP- version compatibility refer to
Overriding the NDMP Version on page 27.
network error
(ndmp_mover.cxx: 2210)
Cannot send a message due to a network error.
Verify that the network is in a good state.
next_head fail (filename: line#)
The file cannot be restored because a notification to the NDMP client to read the file header failed for a direct access restore (DAR).
Verify that your backup software is qualified with Celerra and that it supports DAR.
Refer to your backup software vendor’s
documentation and to EMC NAS Interoperability Matrix on page 12.
No password for NDMP user:ndmp
Retry:3 to get NDMP user:ndmp - Passwd
The NDMP password is not set on the Celerra Network Server.
Use the server_user command to set the NDMP password or to verify that the password is set properly.
Note: You must use the same password for the Celerra Data Mover and the NDMP client software. Also, the username must be ndmp.
Refer to Assigning Data Movers a Username and Password on page 32.
open /.etc/BackupDates file failed, error: <error message>
An open request failed on the backup dates file, which stores the backup run level.
<error message> = type of error, for example, I/O error
No action is needed. This message could reflect a problem with the root file system. param PAX.<paramName> 1024 out of range (4, 512) param PAX.<paramName> is set to 64
These two errors indicate that the value for the PAX
parameter <paramName> is outside the parameter’s allowed range.
Configure an acceptable value for the PAX parameter.
Refer to Configuring Data Movers for NDMP Backups on page 22 and to Viewing and Modifying Parameters on page 43 for parameter descriptions and value ranges.
Pattern Not Matched: / fs/file3 (not restored)
This pattern (file or directory) is not found in the archive.
Verify the integrity of the backup media and the backup path you entered.
Table 19 Server Log Messages (Continued)
pax not started At the time of the
DATA_CONNECT request, PAX was not started.
The Data Mover netd configuration file needs to include PAX. The netd file resides in /nas/server/ slot_<x>/netd. Where:
<x> = slot number of the Data Mover, for example, slot_2
Verify that your backup software is qualified with Celerra.
Verify that the netd file includes PAX.
Refer to EMC NAS Interoperability Matrix on page 12 for qualification information.
PAX.nFTSThreads is reset to 64
This message indicates that a value has been specified for the PAX.nFTSThreads parameter that is too large. The value is reset and the backup continues normally.
No particular action is necessary. The backup still succeeds; it simply uses fewer threads to perform the backup.
Refer to Configuring Data Movers on page 21 for instructions on setting parameters.
pax_cmd_thread expected ARCHIVE/ EXTRACT act, but received <action>
An internal error between NDMP and PAX occurred. The Data Mover and NDMP client establish a connection, an ARCHIVE or EXTRACT message is expected, but not others.
<action> = action received, for example, LIST
Verify that your backup software is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
pax_NotifyDataRead failed (filename: line#)
Notification to the NDMP client to read the first file header for a three-way direct access restore (DAR) failed.
Verify that your backup software is qualified with Celerra and that it supports three-way DAR.
Refer to your backup software vendor’s
documentation and to EMC NAS Interoperability Matrix on page 12.
Read fault on /fs/test with error: <error message>
The file you are trying to back up cannot be read on Celerra. The attempt to read the file data failed.
<error message> = type of error, for example, I/O error
Verify that the file or file system exists on Celerra, is in a good state, and is not being used by other applications.
Refer to EMC NAS Interoperability Matrix on page 12.
RecBuf in NDMP Pool (count:64),
NDMPMAXBUFSIZ is 128
Displays the number of buffers initiated in the pool and the maximum buffer size.
This setting reflects the bufsz parameter.
To change the buffer size, edit the bufsz parameter in the param file, and then reboot the Data Mover.
Refer to Configuring Data Movers for NDMP Backups on page 22.
Table 19 Server Log Messages (Continued)
Request (0x702) not supported (No mover)
The request is not supported because the mover interface is not yet created.
Verify that your backup software is qualified with Celerra.
Refer to EMC NAS Interoperability Matrix on page 12.
rw_thr() TCP connection closed with mover
PAX failed to receive a message from the TCP connection.
Verify that the network is in a good state.
Tape number > 8 in param file
The ntape parameter exceeds the maximum value, which is 8.
The value specifies the number of tape drives attached to a Data Mover. Celerra supports no more than eight tape drives per Data Mover.
Change the NDMP ntape parameter value to 8 or less and reboot the Data Mover.
Refer to Configuring Data Movers for NDMP Backups on page 22.
TAPE_OPEN c1t2l0 fails with stat: <state>
A TAPE_OPEN request failed with <state>.
Many factors can trigger this message.
<state> = state of the device, for example, Device Busy
Verify that no contention for the backup device exists among backup clients or Data Movers.
This may cause the backup to fail.
thrdId 0 directory/ link error
During a restore, the Celerra encountered a problem with the directory and/or link.
Verify that your backup software is qualified with Celerra. You will need to restart the restore. The problem may be due to a failed backup.
Refer to EMC NAS Interoperability Matrix on page 12.
thrdId 0 error on restore file to root filesystem
Permission denied to restore <file or dir>