Appendix A. Error Messages

NetWorker provides user-friendly error messages that have easy-to-understand explanations. This appendix provides you with further information and solutions to assist you with your backups and recoveries.

Error Messages for Backup

NetWorker displays an error message if a backup cannot be successfully completed. Backup error messages are as follows:

Nothing marked for backup

Problem: 

Starting backup without marking any files.

Solution:  

Mark at least one file before starting the backup.

Unable to start backup

Problem:  

Error starting the backup (NetWorker could not execute the save command).

Solution: 

Contact the system administrator. There is a problem either with the NetWorker software or with your client configuration (for example, an incorrect pathname).

Your system is not a registered client.

Problem:  

The server you have chosen for your backups does not have your system configured as a NetWorker client.

Solution: 

Contact the system administrator. Your system needs to be added to the server`s list of recognized clients.

Error Messages for Recover

An error message is displayed when NetWorker is unable to recover a file. Recover error messages are as follows:

These are files marked for recovery.
Continue to ignore the marked files, or cancel to stay with this client.

Problem: 

Changing clients or changing filesystems when files are marked.

Solution: 

You have the option to continue changing clients. In this case, the marked files will not be recovered. Alternatively, you can cancel to stay with the current client and retain your marked files.

(For root user) Only 10 KBytes available (15 KBytes free) in /directory.  Filesystem will be greater than 100% full after recover is complete.  Proceed with recover command at this time? [n]
(For non-root user) No disk space available (15 KBytes free) in /directory.  The estimated recover size of 10 KBytes will not fit on this filesystem.  Proceed with recover command at this time? [n]

Problem: 

There is not enough free space in the filesystem to recover the requested files.

Solution: 

Reduce the number of kilobytes in the recovery by reducing the number of marked files. Relocate the recovery into another directory with more space. If you are recovering over existing directories, you may be able to proceed with the recovery, since files might be overwritten.

Invalid time format

Problem: 

The time specified in the Browse Time field was invalid.

Solution: 

Enter the browse time using a valid format. Valid formats are

  • hh:mm:ss (24-hour clock); for example, 15:30:00

  • hh:mm (am, pm) (PDT) mm/dd/(yy); for example, 5:30 pm PST 7/4/95

  • monthname dd (yy); for example, October 31

  • last Friday, next Friday, third Friday

  • + or - 3 seconds, minutes, hours, weeks, months, years

  • now

    Nothing in index at this time
    

Problem: 

There are no entries in the index for the browse time that was specified, or no backups were performed at that time.

Solution: 

Enter another browse time close to this one until you find the index entries you are looking for.

Unable to relocate to /directory

Problem: 

NetWorker was unable to relocate the recovered data to the specified path.

Solution: 

Enter a valid pathname in the Relocate dialog box and start the recovery again. You must have write permission for the directory you wish to use.

Error Messages for Both Backup and Recover

Some of NetWorker`s error messages are the same for both a backup or recover that is unsuccessful. The error messages used for both backups and recovers are as follows:

There are files marked for backup or recovery. Continue to ignore the marked files or cancel to stay with server.

Problem: 

You cannot change servers after you have marked files.

Solution: 

You have the option of continuing changing servers. If you change servers, the marked files are not backed up or recovered. You can cancel to stay with the current server and retain your marked files.

Bad start path

Problem:  

Specifying an invalid starting path for a search.

Solution: 

Enter a valid pathname as a starting point in the search dialog box.

No match

Problem:  

Nothing matched on this search command.

Solution: 

Enter a different pattern or a different starting path.

Bad search pattern

Problem: 

The search pattern specified is not valid.

Solution: 

You can use the IRIX shell pattern characters to specify a search pattern.

Unable to expand path

Problem:  

The path specified in the selection field does not correspond to anything in the index or filesystem.

Solution: 

Enter a valid pathname in the selection field.