FMY messages
FMY0003S An internal processing error has occurred.
Explanation
An internal processing error has occurred.
System action
Processing ends.
User response
Retry the operation. If this error persists, contact your service representative.
FMY0004E An unknown error has been detected.
Explanation
An internal processing error has occurred that prevents the generation of a message for a return code.
System action
Processing continues.
User response
Retry the operation. If this error persists, contact your service representative.
FMY0005E Out of memory. Stop other processes and try the operation again.
Explanation
The machine has run out of memory.
System action
Processing continues.
User response
Close unnecessary processes and try the operation again.
FMY0053E License file (licensefile) could not be opened.
Explanation
An attempt to read from the license file failed.
System action
Processing ends.
User response
Install the product again. This ensures that the correct license file is installed.
FMY0054E Read failure on license file (licensefile).
Explanation
An attempt was made to read from the license file. This attempt failed.
System action
Processing ends.
User response
Reinstall the product. This will ensure that the correct license file is installed.
FMY0055E Write failure on license file (licensefile).
Explanation
An attempt to write to the license file failed.
System action
Processing ends.
User response
Make sure enough space exists on the workstation to write to the license file. If enough space exists, run the command again.
FMY0056E Data in the license file (licensefile) is not in a valid format.
Explanation
An attempt to read information from the license file failed.
System action
Processing ends.
User response
Install the product again.
FMY0057E The checksum in the license file (licensefile) does not match the license string text.
Explanation
An attempt was made to read information from the license file. The checksum was not valid so it appears that the license file is not at the correct level.
System action
Processing ends.
User response
Reinstall the product.
FMY0058E The 'Try and Buy' license has expired.
Explanation
This 'Try and Buy' license that was detected has expired.
System action
Processing ends.
User response
This product is no longer valid for use. A valid license must be obtained before running the product.
FMY0100E Incomplete command:
Explanation
This message displays the incomplete command that was entered.
System action
Processing ends.
User response
Re-enter the complete command.
FMY0101E Invalid argument:
Explanation
This message displays the command that was entered, up to and including the invalid command or option argument that was detected.
System action
Processing ends.
User response
Re-enter the command specifying a valid argument for the command or option.
FMY0102E Invalid command:
Explanation
This message displays the invalid command that was entered.
System action
Processing ends.
User response
Re-enter a valid command.
FMY0103E Invalid option for the specified command:
Explanation
This message displays the command that was entered, up to and including the option that was detected as invalid for the command.
System action
Processing ends.
User response
Re-enter the command specifying valid command options.
FMY0104E Invalid option:
Explanation
This message displays the command that was entered, up to and including the invalid option that was detected.
System action
Processing ends.
User response
Re-enter the command specifying valid command options.
FMY0105E Missing argument:
Explanation
This message displays the command that was entered, up to and including the command or option whose required argument is missing.
System action
Processing ends.
User response
Re-enter the command specifying a valid argument for the command or option.
FMY0132W Tracing could not be started. Processing will continue.
Explanation
A problem prevented tracing from beginning.
System action
Processing will continue with the command entered.
User response
Refer to the other messages that display with this message to determine the problem.
FMY0133W Could not locate installation directory. Attempting to continue...
Explanation
An attempt was made to read the registry to determine where the Data Protection application client was installed. This attempt failed.
System action
Processing will continue with the command entered.
User response
There should be other messages along with this one. Refer to the other messages to determine the problem. If the problem can not be determined, it may be necessary to reinstall the application client code. This will ensure that the registry entries are set up correctly.
FMY0134W Could not locate log directory. Processing will continue...
Explanation
An attempt was made to read the registry to determine where the Data Protection application client log is located. This attempt failed.
System action
Processing will continue with the command entered.
User response
There should be other messages along with this one. Refer to the other messages to determine the problem. If the problem can not be determined, it may be necessary to reinstall the application client code. This will ensure that the registry entries are set up correctly.
FMY0150I Operation canceled by user.
Explanation
The user has requested the application client end by entering ctrl-C.
System action
Processing ends.
User response
None
FMY0151E Errors occurred while processing the request.
Explanation
Attempting to process the request entered, an error occurred.
System action
Processing ends.
User response
Attempt to determine the source of the errors from viewing the log file. Correct the problems and try running the command again.
FMY0152I Performance stats: seconds seconds spent in apicall API calls
Explanation
The indicated number of seconds were spent making API calls for the indicated system.
System action
Processing continues.
User response
None
FMY0153I Performance stats: seconds seconds spent in function
Explanation
The indicated number of seconds were spent the named function.
System action
Processing continues.
User response
None
FMY0154E The Data Protection for Microsoft SQL Server application client cannot work with the version of the IBM Storage Protect Snapshot API you have installed. Please install version version.release.level or greater.
Explanation
The version of the IBM Storage Protect Snapshot API currently installed on the system is older than the version used to build the Data Protection for Microsoft SQL Server application client.
System action
Processing ends.
User response
Install a version of the IBM Storage Protect Snapshot API at or later than the indicated level. A copy is distributed with the Data Protection for Microsoft SQL Server application client.
FMY0155E The Data Protection for Microsoft SQL Server application client cannot work with the release of IBM Storage Protect Snapshot API you have installed. Please install release version.release.level or greater.
Explanation
The release of the IBM Storage Protect Snapshot API currently installed on the system is older than the release used to build the Data Protection for Microsoft SQL Server application client.
System action
Processing ends.
User response
Install a release of the IBM Storage Protect Snapshot API at or later than the indicated level. A copy is distributed with the Data Protection for Microsoft SQL Server application client.
FMY0156E Could not load the IBM Storage Protect Snapshot API.
Explanation
The IBM Storage Protect Snapshot API could not be loaded.
System action
Processing ends.
User response
Ensure the IBM Storage Protect Snapshot API is correctly installed. Run the Data Protection for Microsoft SQL Server application client with the /TRACEFLAGS=API /TRACEFILE=filename options and view the tracefile to determine why it could not be loaded. Another possible cause is that the TSMAPI.DLL does not exist in the system directory. Re-install the IBM Storage Protect Snapshot API, if this is the case.
FMY0160E An authentication error occurred with your stored IBM Storage Protect Snapshot password.
Explanation
You were unable to log on to the IBM Storage Protect Snapshot server due an authentication error.
System action
Processing stops.
User response
The stored IBM Storage Protect Snapshot password may have become corrupted. Contact your IBM Storage Protect Snapshot server administrator.
FMY0161E Authentication error. The password entered is not valid. You are not logged on to the IBM Storage Protect Snapshot server.
Explanation
An incorrect password was entered.
System action
Processing stops.
User response
Enter the correct IBM Storage Protect Snapshot password and try again.
FMY0162E The passwords entered do not match. Please enter them again.
Explanation
An incorrect password was entered.
System action
Processing stops.
User response
Enter the passwords again.
FMY0163E The directory path needs to be fully-qualified.
Explanation
The /intopath option was specified without a fully-qualified path.
System action
Processing stops.
User response
Enter the command again and specify a fully-qualified path in the /intopath option.
FMY0167E The fully-qualified file name is too long.
Explanation
An attempt was made to use a fully-qualified file name that was too long. This attempt failed.
System action
Processing ends.
User response
None
FMY0200E File (filename) could not be opened for reading.
Explanation
An attempt was made to open a file for reading. This attempt failed.
System action
Processing ends.
User response
None
FMY0201E File (filename) could not be opened for writing.
Explanation
An attempt was made to open a file for writing. This attempt failed.
System action
Processing ends.
User response
None
FMY0202E Read failure on file (filename).
Explanation
An attempt was made to read from a file. This attempt failed.
System action
Processing ends.
User response
None
FMY0203E Write failure on file (filename).
Explanation
An attempt was made to write to a file. This attempt failed.
System action
Processing ends.
User response
None
FMY0204E File (filename) could not be closed.
Explanation
An attempt was made to close a file. This attempt failed.
System action
Processing ends.
User response
None
FMY0205E File (filename) statistics could not be obtained.
Explanation
An attempt was made to obtain file statistics. This attempt failed.
System action
Processing ends.
User response
None
FMY0206E Directory (directory) could not be created.
Explanation
An attempt was made to create a directory. This attempt failed.
System action
Processing ends.
User response
None
FMY0207E Directory path (directorypath) is too long.
Explanation
An attempt was made to use a directory path that was too long. This attempt failed.
System action
Processing ends.
User response
None
FMY0208E There is not enough disk space for the operation attempted.
Explanation
An attempted operation required more disk space than was available. The attempt failed.
System action
Processing ends.
User response
None
FMY0209E The rename of file (filename1) to (filename2) failed.
Explanation
An attempt was made to rename a file. This attempt failed.
System action
Processing ends.
User response
None
FMY0210E The IBM Storage Protect Snapshot high level qualifier is too long.
Explanation
An attempt was made to use a IBM Storage Protect Snapshot high level qualifier that was too long. This attempt failed.
System action
Processing ends.
User response
None
FMY0211E The IBM Storage Protect Snapshot low level qualifier is too long.
Explanation
An attempt was made to use a IBM Storage Protect Snapshot low level qualifier that was too long. This attempt failed.
System action
Processing ends.
User response
None
FMY0212E The IBM Storage Protect Snapshot filespace name is too long.
Explanation
An attempt was made to use a IBM Storage Protect Snapshot filespace name that was too long. This attempt failed.
System action
Processing ends.
User response
None
FMY0213E The maximum number of objects allowed per IBM Storage Protect Snapshot transaction is too small.
Explanation
In order to maintain backup data integrity, multiple backup objects are sent to the IBM Storage Protect Snapshot server in a single transaction. The IBM Storage Protect Snapshot server has indicated that the maximum number of objects allowed per transaction is less than the minimum required by the Data Protection for Microsoft SQL Server application client.
System action
Processing ends.
User response
Increase the maximum number of objects allowed per transaction on the IBM Storage Protect Snapshot server and retry the operation.
FMY0214E The backup object's management class backup copy group does not exist.
Explanation
The IBM Storage Protect Snapshot server has indicated that the backup object's management class backup copy group does not exist.
System action
Processing ends.
User response
Contact your IBM Storage Protect Snapshot server administrator.
FMY0215E All backup objects do not have the same management class backup copy destination.
Explanation
In order to maintain backup data integrity, multiple backup objects are sent to the IBM Storage Protect Snapshot server within a single transaction. All backup objects within a single transaction are required to have the same management class backup copy destinations.
System action
Processing ends.
User response
Contact your IBM Storage Protect Snapshot server administrator.
FMY0216E Unable to obtain space information for volume (volumename).
Explanation
An attempt was made to obtain space information for a volume. This attempt failed.
System action
Processing ends.
User response
None
FMY0217E The IBM Storage Protect Snapshot filespace name is invalid.
Explanation
The filespace name or directory delimeter is invalid.
System action
Processing ends.
User response
Check that the filespace name length, characters, and directory delimeters are valid.
FMY0218E The IBM Storage Protect Snapshot high level qualifier is invalid.
Explanation
The high level qualifier name or directory delimeter is invalid.
System action
Processing ends.
User response
Check that the high level qualifier name length, characters, and directory delimeters are valid.
FMY0219E The IBM Storage Protect Snapshot low level qualifier is invalid.
Explanation
The low level qualifier name or directory delimeter is invalid.
System action
Processing ends.
User response
Check that the low level qualifier name length, characters, and directory delimiters are valid.
FMY0256E The password in your IBM Storage Protect Snapshot options file has expired. Please change your password on the IBM Storage Protect Snapshot server using the 'change password' command and then either change or remove the password value in your options file.
Explanation
Your IBM Storage Protect Snapshot password has expired. You need to change your password.
System action
Processing ends.
User response
Obtain a new password for your IBM Storage Protect Snapshot server; node using the change password command or by asking your IBM Storage Protect Snapshot administrator to change your password.
FMY0257E Your password has expired.
Explanation
Your IBM Storage Protect Snapshot password has expired. A new password needs to be obtained.
System action
Processing ends.
User response
Obtain a new password for your IBM Storage Protect Snapshot node using the change password command or by asking your IBM Storage Protect Snapshot administrator to change your password.
FMY0258E You did not enter a valid password. Processing ends.
Explanation
The password that was entered was not a valid password.
System action
Processing ends.
User response
Re-enter the command specifying a valid password.
FMY0259E The password you entered for verification does not match the password you entered for your new password. Your password will not be changed.
Explanation
The password you entered for verification of your new password does not match the new password that was entered.
System action
Processing ends.
User response
Try again to change your password being sure to enter the same password for the new password and for the verification password.
FMY0260I Password successfully changed.
Explanation
The change password command completed successfully
System action
Processing ends.
User response
None
FMY0261I There are no backups for the server named servername.
Explanation
There are no backups on the IBM Storage Protect Snapshot server for the specified server name.
System action
Processing ends.
User response
None
FMY0262E Errors occurred while processing the VSS operation. Examine the Windows Event Logs and DSMERROR.LOG for additional details.
Explanation
While attempting to process a VSS operation, an unexpected error occurred.
System action
Processing ends.
User response
Attempt to determine the source of the error by examining the IBM Storage Protect Snapshot for SQL Server log file, the client error log file (DSMERROR.LOG), the Windows Application Event Log, the Windows System Event Log, and the VSS provider log file, if applicable. Additional instructions for Windows VSS operations are located in the IBM Storage Protect Problem Determination Guide. Correct the problem and retry the operation. If this error persists, contact your service representative.
FMY0267E The verify password entered does not match the new password entered.
Explanation
The verify password does not match the new password.
System action
Processing ends.
User response
Retry the command with a matching verify password.
FMY0292E An unknown error has been detected. rc = rc
Explanation
An error occured without an error message. The return code is displayed.
System action
Processing ends.
User response
Retry the operation. If this error persists, contact your service representative.
FMY0300E Invalid restore type.
Explanation
The type of restore requested is invalid.
System action
Processing ends.
User response
Re-enter the command specifying a valid restore type.
FMY0301E Invalid backup type.
Explanation
The type of backup requested is invalid.
System action
Processing ends.
User response
Re-enter the command specifying a valid backup type.
FMY0351E Invalid trace keyword - 'keyword'
Explanation
A TRACEFLAG option in the user configuration file or on the command line is incorrect.
System action
Client program did not initialize or tracing was not enabled in the applet.
User response
Correct the value.
FMY0368E Invalid trace file name (name too long).
Explanation
A TRACEFILE option in the preferences files used a file name that is too long.
System action
Client program did not initialize.
User response
Change the file name used as the TRACEFILE so that it is equal to or less than 255 characters in length.
FMY0383E Specifying the trace file 'link' as a symbolic link is not allowed.
Explanation
Trace file 'linkname' cannot be a symbolic link.
System action
The symbolic link 'linkname' is deleted, the trace file is recreated, and processing stops.
User response
Specify the trace file location with the 'tracefile' option.
FMY0384E Symbolic link 'linkname' to 'target' was successfully deleted.
Explanation
Log 'linkname' cannot be a symbolic link.
System action
The symbolic link 'linkname' is deleted, the log is recreated, and processing stops.
User response
Check the location of the new file. To specify the location of log files, refer to the user's manual for the 'errorlogname' option, the 'schedlogname' option, and the 'DSM_LOG' environmental variable.
FMY0385E Unable to delete symbolic link 'link'.
Explanation
Log 'linkname' cannot be a symbolic link.
System action
Processing stops.
User response
Delete the symbolic link 'linkname'.
FMY0476E program-name: cannot open file file-spec: error.
Explanation
Cannot open the file. The reason is given in the message.
System action
Cannot complete the requested operation.
User response
Retry the operation. If the problem continues, check with your system administrator.
FMY0480I Temp object renamed (Filespace: '', HL: '', and LL: ').
Explanation
After a legacy backup operation, it might be a temp object remains on TSM server but for SQL Server this backup is successful already. Rename this temp object to have consistent backup.
System action
User response
No action is required.
FMY0487E Specifying the error log 'link' as a symbolic link is not allowed.
Explanation
Error log 'linkname' cannot be a symbolic link.
System action
The symbolic link 'linkname' is deleted, the error log is recreated, and processing stops.
User response
Check the location of the new error log. To specify the location of the error logs, refer to the user's manual for the 'errorlogname' option and 'DSM_LOG' environmental variable.
FMY0488E Initialization functions cannot open the error log: log-name. errno = errno-value,
Explanation
The file log-name could not be opened during initialization. The system set the error code errno-value. If the reason given is "access denied," the current user does not have permission to write to the log in the directory specified. It is also possible that no space is available at the given log location. If the reason is errno = 13, Permission denied, you have the following policy setting control enabled, User Account Control: Turn on Admin Approval Mode.
System action
Processing terminates.
User response
Set the DSM_LOG (or DSMI_LOG) environment variable to a directory into which the current user can write. You may also use the ERRORLOGNAME option to specify a file to which the current has write permission. If the reason is errno = 13, Permission denied, you should run the same operation in administrator mode.
FMY0495E Failure writing to a IBM Storage Protect Snapshot log or log-related file: file-name, errno = errno-value, reason
Explanation
A failure was encountered when writing to one of the log files or a related file named file-name. The system set the error code errno-value. reason is the system explanation of that error code. Among other things, it is possible that no space is available at the given log location.
System action
Processing terminates.
User response
Set the DSM_LOG (or DSMI_LOG) environment variable to a directory with adequate space to write the log data.
FMY0496I Converting the log-file from continuous (pruning) mode to wrapping mode. This process may take several minutes.
Explanation
The log-file was previously in continouos mode where the only size control was through the use of ERRORLOGRETENTION or SCHEDLOGRETENTION option. This is the first occasion where ERRORLOGMAX or SCHEDLOGMAX is specified for this log, so its format must be changed and old data saved.
System action
Transition processing continues.
User response
None.
FMY0497I IBM Storage Protect is converting the log-file from wrapping mode to continuous (pruning) mode. This process may take several minutes.
Explanation
The log-file was previously in wrapping mode where the size control was through the use of the ERRORLOGMAX or SCHEDLOGMAX option. This is the first occasion where ERRORLOGMAX or SCHEDLOGMAX is not specified for this log, so its format must be changed and old data saved.
System action
Transition processing continues.
User response
None.
FMY0498I count log records processed.
Explanation
This is just a progress report to let you know the process is still ongoing.
System action
Transition processing continues.
User response
None.
FMY0501E Invalid Proxy Configuration Detected: Target Node 'targetnode' is not listed as a valid node to proxy to for Node Name 'nodename'.
Explanation
The proxy node configuration on the Storage Protect Snapshot Server is not correct to support this VSS operation.
System action
The VSS operation stops.
User response
Contact the Storage Protect Snapshot Server administrator to have the correct GRANT PROXY commands issued to enable proxy authority for the nodes. If the error persists, contact your service representative.
FMY0515E Invalid DSMAGENT Node configuration found for node 'dsmagentnode'.
Explanation
The DSMAGENT Node specified is not configured properly.
System action
The VSS operation stops.
User response
Verify that the DSMAGENT Node specified is correct and that the client acceptor is running for the DSMAGENT Node. If the error persists, contact your service representative.
FMY0516I The Windows console event handler received a 'event' console event.
Explanation
A console event was received by one of the Data Protection for Microsoft SQL Server processes or programs. The following events can be recevied:
- Ctrl-C - This indicates either the user entered the ctrl-c sequence or that one of the Windows services was stopped.
System action
None.
User response
None.
FMY0517I An unexpected error was encountered. function name : function-name function : function-desc return code : TSM-rc file : file-name (line-number)
Explanation
None.
System action
Processing stops.
User response
Contact the IBM Storage Protect administrator with the information provided in this message.
FMY0518E Backups selected for restore must have the same backup location (TSM or LOCAL).
Explanation
A VSS restore operation was submitted that specified multiple backup objects. The backup objects chosen had different backup locations. This is not allowed. All backup objects submitted in the same VSS restore operation must have the same backup location, either TSM or LOCAL, but not both.
System action
The VSS restore operation stops.
User response
Retry the VSS restore operation specifying one backup object at a time.
FMY0519E The VSS operation failed with rc = returncode.
Explanation
There was a failure when Storage Protect Snapshot performed the VSS operation.
System action
The VSS operation stops.
User response
Verify that the client acceptor is installed, configured, and running properly on the machine. Retry the operation. If the error persists, contact your service representative.
FMY0520E Failed to connect to Local DSMAGENT Node 'localdsmagentnode' at address:port 'address:portnumber'. Verify that the client acceptor is installed, configured, and running properly.
Explanation
An attempt was made to connect to the client acceptor running on the local machine. A communication error occurred when this connection was attempted.
System action
The operation stops.
User response
In order to perform VSS operations, you must have a client acceptor and a IBM Storage Protect Remote Client Agent Service (DSMAGENT) installed and configured properly. In addition, the client acceptor must be running. Verify that the client acceptor is installed, configured, and running properly on the local machine. If the error persists, contact your service representative.
FMY0521E Pruning functions cannot open the prune files: log-name. errno = errno-value,
Explanation
The file "log-name" could not be opened during pruning. The system set the error code errno-value. If the reason given is "access denied," the current user does not have permission to write to the file in the directory specified. It is also possible that no space is available at the given file location or another IBM Storage Protect Snapshot process started by different user id is performing pruning at the same time.
System action
Pruning stops, processing continues.
User response
Set the DSM_LOG (or DSMI_LOG) environment variable to a directory into which the current user can write.
FMY0522E DIAG:
Explanation
The message text is provided for diagnostic purposes and is meant to provide information to IBM support in problem determination.
System action
None.
User response
None.
FMY0524S Error 'errtxt' (errno=errno) occurred trying to write to audit log 'file-name'. The audit log function is disabled.
Explanation
There was an error encountered writing to the audit log (for example, there is not enough space on the disk).
System action
Audit logging is disabled for the rest of the operation. The return code for the operation is set to 12 to indicate that the contents of the audit log are incomplete.
User response
If this is an out of space condition either free up space on the volume or try to write the audit log to a volume with more space.
FMY0555E Invalid number of snapshots:
Explanation
System action
Policy was not created.
User response
Specify a number in the range: range: 1...9999 or NOLimit
FMY0556E Invalid number of days:
Explanation
System action
The Policy was not created.
User response
Specify a number in the range: range: 0...9999 or NOLimit
FMY0571E The specified policy was not found: 'policy'
Explanation
System action
User response
Please make sure that the specified policy exists.
FMY0572E The specified policy already exists: 'policy'
Explanation
System action
Policy was not created.
User response
Enter a different name for the policy.
FMY0573E The specified policy could not be updated: 'policy'
Explanation
This is due to a problem in virtual server database.
System action
Processing stops.
User response
Make sure that IBM Storage Protect Snapshot is configured correctly.
FMY0574E The specified policy could not be deleted: 'policy'
Explanation
This is due to a problem in virtual server database.
System action
Processing stops.
User response
Make sure that IBM Storage Protect Snapshot is configured correctly.
FMY0575E The specified policy could not be created: 'policy'
Explanation
This is due to a problem in virtual server database.
System action
Processing stops.
User response
Make sure that IBM Storage Protect Snapshot is configured correctly.
FMY0576I There were no items found.
Explanation
The query completed successfully, but no results were found.
System action
None.
User response
Change the specified search criteria.
FMY0581E One or more of the volume(s) volume-list could not be locked. See more details in the VSS Requester error log file (baclient\dsmerror.log).
Explanation
The system call to lock the volume(s) failed.
System action
Processing stopped.
User response
Please verify that no other application is accessing the volume(s). During restore of an image exclusive use of the volume is required.
FMY0583E Invalid name of policy specified. Valid input characters include alphanumeric characters and underscore.
Explanation
System action
Policy was not created.
User response
Please specify a valid name.
FMY0585E Unable to connect to the client acceptor.
Explanation
Possible causes of this message include: The client acceptor is not running. The VSSALTSTAGINGDIR option setting in the TDP option file is not set to the same value as the VSSALTSTAGINGDIR option setting in the Data Protection for Microsoft SQL Server Remote Client Agent Service (DSMAGENT) option file. They must be set to the same value.
System action
The VSS operation stops.
User response
Ensure that the client acceptor is running. Ensure that the VSSALTSTAGINGDIR option setting in the TDP option file is set to the same value as the VSSALTSTAGINGDIR option setting in the Data Protection for Microsoft SQL Server Remote Client Agent Service (DSMAGENT) option file. After correcting the VSSALTSTAGINGDIR option inconsistency, retry the operation.
FMY0588E The value for the BACKUPDESTination option is not allowed. Data Protection for Microsoft SQL Server is only licensed to run data protection operations to a IBM Storage Protect Snapshot server. It is not licensed to backup or to restore locally managed snapshots.
Explanation
The value for the configuration option is not allowed. The only allowed value is TSM. Data Protection for Microsoft SQL Server is only licensed to run data protection operations to a IBM Storage Protect Snapshot server. It is not licensed to backup or to restore locally managed snapshots.
System action
Processing ends.
User response
Set the backup destination to TSM. In order to create and restore local VSS backups it is required to use and install a fully-featured valid license or to purchase an upgrade, and install IBM Storage Protect Snapshot.
FMY0589E You are not allowed to set REMOTEDSMAGentnode option. Data Protection for Microsoft SQL Server is not licensed to perform offloaded VSS backups.
Explanation
The REMOTEDSMAGentnode option is used to perform offloaded VSS backups.
System action
The operation stops.
User response
In order to perform offloaded VSS backups install a valid fully-featured license.
FMY0590E A Data Protection communication error with the IBM Storage Protect Snapshot server has occurred.
Explanation
Communications with the IBM Storage Protect Snapshot server has been lost.
System action
The operation stops.
User response
Correct the TCP/IP communications error with the IBM Storage Protect Snapshot server and retry the operation.
FMY0591I Communications with the IBM Storage Protect Snapshot server recovered.
Explanation
Communications with the IBM Storage Protect Snapshot server has been successfully recovered.
System action
None.
User response
Continue with normal operations.
FMY0592E The TCP/IP session with the IBM Storage Protect Snapshot server was canceled.
Explanation
The TCP/IP session with the IBM Storage Protect Snapshot server was cancelled.
System action
The operation stops.
User response
Correct the reason the IBM Storage Protect Snapshot server administrator cancelled the session and retry the operation.
FMY0593E Data Protection for Microsoft SQL Server is not licensed to perform offloaded VSS backups.
Explanation
Currently installed license does not allow to perform offloaded VSS backups. In order to use this feature it is necessary to install a valid fully-featured license.
System action
The operation stops.
User response
In order to perform offloaded VSS backups install a valid fully-featured license.
FMY0594E You cannot perform offloaded VSS backups in a standalone configuration.
Explanation
OFFLOAD option is not available in a standalone configuration.
System action
The operation stops.
User response
In order to perform offloaded VSS backups you have to configure IBM Storage Protect Snapshot to manage snapshot backups using a IBM Storage Protect Snapshot server. To do this, you can use the configuration wizard.
FMY0595E The options file 'optfile' does not exist. It is required for proper operation.
Explanation
The specified IBM Storage Protect API options file could not be found. It is required in order to complete the command.
System action
Processing ends.
User response
Make sure to complete IBM Storage Protect Snapshot configuration and try the operation again.
FMY0598E The application cannot run in safe mode.
Explanation
The application requires either Services or Drivers that are not available when running in safe mode.
System action
The application processing stops.
User response
Restart the system using the normal startup. When the system is started, run the application.
FMY0599E The application cannot establish a remote PowerShell connection.
Explanation
The application attempted to establish a remote PowerShell connection. The operation failed.
System action
The application processing stops.
User response
Verify you are using the correct credentials. For more information, see the Microsoft about_Remote_Troubleshooting Help topic.
FMY0601E There is a problem that causes processing to stop. To identify the source of the problem and the solution, look for details in the service level trace file.
Explanation
This problem occurs when either the local or remote PowerShell cmdlet or script reports an error. Details about the error are not available until more trace file information is analyzed.
System action
Application processing stops.
User response
To identify the problem, look for information in the service level trace files. For more information about viewing trace files, see the Troubleshooting section of the technical documentation provided with the software.
FMY0602E While attempting to communicate with the remote client, a version check reveals that the versions do not match.
Explanation
During initialization between the local client and the remote client, version checking reveals that the versions do not match. This is usually the result of an upgrade of one client module without upgrading other client modules that are part of product solution.
System action
The calling procedure returns and control is passed back the user.
User response
Check the versions of all IBM Storage Protect Client products that communicate with each other and ensure that they are all at the same version, release, and level.
FMY0603S File 'file-name' could not be found, or it cannot be read.
Explanation
- The default options file does not exist.
- The DSM_CONFIG (or DSMI_CONFIG if you are using the Data Protection for Microsoft SQL Server API) environment variable specifies an options file that does not exist.
- You specified the TSMOPTFILE or FCMOPTFILE option when starting the Data Protection for Microsoft SQL Server client, but the option file you provided does not exist.
- You specified the TSMOPTFILE or FCMOPTFILE option when starting the Data Protection for Microsoft SQL Server client, but the configuration file that you provided does not have appropriate read permissions for the user that is running the operation.
- You specified the CONFIGFILE option when starting the Data Protection for Microsoft SQL Server client, but the configuration file you provided does not exist.
- You specified the CONFIGFILE option when starting the Data Protection for Microsoft SQL Server client, but the options file that you provided does not have appropriate read permissions for the user that is running the operation.
System action
Data Protection for Microsoft SQL Server client processing stops.
User response
Make sure that the file you want to use exists, it has the read rights set for the user that is running the operation, and it is in the standard file encoding of the system. For example, on Windows the expected file encoding is ANSI. Review the configuration information in the Data Protection for Microsoft SQL Server client manual specific to your operating system. If the problem persists, ask your Data Protection for Microsoft SQL Server administrator for further assistance.
FMF0604E The Backup you are mounting is not located on a SVC volume.
Explanation
Mounting with Snap Of A Snap is only supported with SVC volumes.
System action
Processing stopped.
User response
You may mount backups located as Read Only or Read Write with Snap Of A Snap disabled.
FMF0605E The SVC Hardware Provider is not installed.
Explanation
Mounting with Snap Of A Snap is only supported by the SVC Hardware Provider.
System action
Processing stopped.
User response
Install the SVC Hardware Provider. Or you may mount backups as Read Only or Read Write with Snap Of A Snap disabled.
FMF0606E The SVC Hardware Provider is not at minimum level.
Explanation
Mounting with Snap Of A Snap is only supported by the SVC Hardware Provider version 4.12 or higher.
System action
Processing stopped.
User response
Install SVC Hardware Provider version 4.12 or higher. Or you may mount backups as Read Only or Read Write with Snap Of A Snap disabled.
FMF0607E The SVC VSS Hardware Provider has reported an error.
Explanation
The SVC VSS Hardware Provider has reported an error.
System action
Processing stopped.
User response
See the SVC VSS Hardware Provider log for more details.
FMF0608E The backup type is not a COPY backup type.
Explanation
Only COPY or COPYFULL backup types maybe mounted read write when not using the Snap Of A Snap feature
System action
Processing stopped.
User response
Enable the USESNAPOFASNAPTomount configuration option if you have a supported environment.
FMF0609E The backup has been modified and cannot be restored.
Explanation
When you mount COPY or COPYFULL type backups as read/write, the backup data is modified. A backup with modified data cannot be used for restore operations.
System action
Processing stopped.
User response
Use an alternative backup, one that has not been modified, for your restore operations.
FMY0649E The disk provider does not support the snap of a snap feature. See more details in the VSS Requester error log file (baclient\dsmerror.log).
Explanation
You can use the snap of a snap feature only on SVC and Storwize systems.
System action
Processing ends.
User response
Reset the USESNAPOFASNAPTOMOUNT option to No in the Data Protection configuration file and set MOUNTRW=Yes to mount the read/write backup.
FMY0650E The mount point provided is invalid. It must be an existing empty folder, or a drive letter in case you mount a file system backup.
Explanation
The mount point provided is invalid. It must be an existing empty folder, or a drive letter in case you mount a file system backup.
System action
Processing ends.
User response
Provide an existing empty folder, or a drive letter in case you mount a file system backup.
FMY1225E The command_stream command is not supported without an IBM Storage Protect Snapshot license.
Explanation
To issue the command, a license for IBM Storage Protect Snapshot is required. If an IBM Storage Protect Snapshot license does not exist, the command is not supported.
System action
None.
User response
Install an IBM Storage Protect Snapshot license, then issue the command again.
FMY1226E The local backup or clone cannot be deleted from current machine. It must be deleted from the machine where its snapshot was created.
Explanation
Delete operation failed because the snapshot information for the local backup or clone cannot be found in local machine.
System action
The operation stops.
User response
Delete the local backup or clone from the machine where its snapshot was created.
FMY1227E Node 'nodename' does not connect or register properly with IBM Storage Protect Snapshot Server.
Explanation
DSMAgent node cannot be connected or register properly.
System action
The VSS operation stops.
User response
Verify that the DSMAGENT Node specified is correct and that SSL is config correctly. If the error persists, contact your service representative.
FMY3000I IBM Storage Protect Snapshot for SQL Server: Starting backup type backup of database database name from server server name.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a backup is started.
System action
None
User response
None Centrally logged
FMY3001I IBM Storage Protect Snapshot for SQL Server: backup type backup of database database name from server server name completed successfully.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a database backup completes successfully.
System action
None
User response
None Centrally logged
FMY3002E IBM Storage Protect Snapshot for SQL Server: backup type backup of database database name from server server name failed, rc = return code.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a database restore fails.
System action
None
User response
None Centrally logged
FMY3003I IBM Storage Protect Snapshot for SQL Server: Starting restore type restore of backup object object name to database database name on server server name.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a restore is started.
System action
None
User response
None Centrally logged
FMY3004I IBM Storage Protect Snapshot for SQL Server: restore type restore of backup object object name to database database name on server server name completed successfully.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a database restore completes successfully.
System action
None
User response
None Centrally logged
FMY3005E IBM Storage Protect Snapshot for SQL Server: restore type restore of backup object object name to database database name on server server name failed.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a database restore fails.
System action
None
User response
None Centrally logged
FMY3006I IBM Storage Protect Snapshot for SQL Server: Starting backup for server server name.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the start of a backup.
System action
None
User response
None Centrally logged
FMY3007I IBM Storage Protect Snapshot for SQL Server: Backup of server servername is complete. Total SQL backups selected: number selected Total SQL backups attempted: number attempted Total SQL backups completed: number completed Total SQL backups excluded: number excluded Throughput rate: rate Kb/Sec Total bytes transferred: bytes Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the end of a backup request.
System action
None
User response
None Centrally logged
FMY3008I IBM Storage Protect Snapshot for SQL Server: Backup of server servername is complete. Total SQL backups selected: number selected Total SQL backups attempted: number attempted Total SQL backups completed: number completed Total SQL backups excluded: number excluded Total SQL backups inactivated: number inactivated Throughput rate: rate Kb/Sec Total bytes transferred: bytes Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the end of a backup request.
System action
None
User response
None Centrally logged
FMY3009I IBM Storage Protect Snapshot for SQL Server: backup type backup of database database name from server server name canceled by user.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating that a backup request was canceled by the user.
System action
None
User response
None Centrally logged
FMY3010I IBM Storage Protect Snapshot for SQL Server: Starting restore for server servername.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the start of a restore.
System action
None
User response
None Centrally logged
FMY3011I IBM Storage Protect Snapshot for SQL Server: Restore from server server name to server server name is complete. Total database backups inspected: number inspected Total database backups requested for restore: number requested Total database backups restored: number restored Total database skipped: number skipped Throughput rate: rate Kb/Sec Total bytes transferred: bytes Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the end of a restore.
System action
None
User response
None Centrally logged
FMY3012I IBM Storage Protect Snapshot for SQL Server: restore type restore of backup object object name to database database name from server server name canceled by user.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating that a backup request was canceled by the user.
System action
None
User response
None Centrally logged
FMY3013I IBM Storage Protect Snapshot for SQL Server: Starting Inactivate processing for backup objects from server servername
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when an inactivate process begins.
System action
None
User response
None Centrally logged
FMY3014I IBM Storage Protect Snapshot for SQL Server: Inactivate processing complete Total database backups inspected: number inspected Total database backups requested for inactivation: number requested Total database backups inactivated: number inactivated Total database skipped: number skipped Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Server activity log to indicate the end of an inactivate command.
System action
None
User response
None
FMY3015I IBM Storage Protect Snapshot for SQL Server: Inactivating backup type backup backup object.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when an inactivation of a backup object is started.
System action
None
User response
None Centrally logged
FMY3016I IBM Storage Protect Snapshot for SQL Server: Database database name from server server name is excluded from backup type backup because it has a Simple Recovery model or it is a system master database.
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log when a Simple Recovery model database or a system master database is automatically excluded from a IBM Storage Protect Snapshot for SQL Server backup.
System action
None
User response
None Centrally logged
FMY3528E Data Protection for Microsoft SQL Server is only licensed to run data protection operations to the IBM Storage Protect server. It is not licensed to backup or to restore using locally managed snapshots.
Explanation
Currently installed license allows to create and restore only VSS backups from TSM backup destination. In order to create backups and to restore local VSS backups, IBM Storage Protect Snapshot for SQL Server requires that a valid fully-featured license for IBM Storage Protect Snapshot is installed.
System action
The operation stops.
User response
In order to create and restore local VSS backups it is required to purchase and install a fully-featured valid license for IBM Storage Protect Snapshot.
FMY3532E The restore destination directory path needs to be fully-qualified.
Explanation
The /relocatedir option was specified without a fully-qualified path.
System action
Processing stops.
User response
Enter the command again and specify a fully-qualified path in the /relocatedir option.
FMY4354E SQL clone backup is not supported for the VSS System Provider snapshots.
Explanation
Data Protection for Microsoft SQL Server cannot create a SQL clone backup because it requires a VSS hardware provider that can create transportable snapshots. This is because either the production database are stored on local volumes that use the system VSS provider, or, because the vssusesystemprovider option specifies to use the Windows system provider. The Data Protection for Microsoft SQL Server error log and Windows event log can contain additional information about this error.
System action
Data Protection for Microsoft SQL Server stops the operation.
User response
Move the production database on volumes that use a VSS hardware provider, and try the operation again.
FMY5050I A new configuration file was created.
Explanation
The file specified in the /configfile parameter does not exist. A new file was created.
System action
Processing continues.
User response
None.
FMY5051I The configuration file cannot be found, using default settings.
Explanation
The file specififed in the /configfile parameter cannot be found.
System action
Processing continues.
User response
Ensure the correct file name is specified.
FMY5052E An error occurred trying to set the requested configuration option.
Explanation
An error occurred while writing to the configuration file.
System action
Processing ends.
User response
View any other messages that were displayed. After reviewing the messages and performing necessary actions, run the command again.
FMY5053E The value for the option option is not valid. See the TDPSQLC Help Set output or the User's Guide for valid Set command parameters.
Explanation
The configuration option being set is not valid.
System action
Processing ends.
User response
Run "TDPSQLC Help Set" or refer to the User's Guide for valid Set command parameters.
FMY5054I The configuration option was set successfully.
Explanation
The configuration option specified on the Set command was set successfully.
System action
Processing ends.
User response
None
FMY5056I The logfile log file could not be pruned. Processing will continue.
Explanation
An attempt to prune the log was unsuccessful.
System action
Processing continues.
User response
The log file may not exist. If the log file exists, view the log for indications of possible problems.
FMY5057I The logfile log file was pruned successfully.
Explanation
The log file mentioned pruned successfully.
System action
Processing continues.
User response
None.
FMY5058W The logfile name is greater than the maximum allowed. Processing will continue using a logfile name of logfile in the current directory.
Explanation
The logfile name entered was not fully qualified. When the fully qualified log file name was created, it was longer than the possible length of a log file.
System action
Processing continues by creating and using a log file in the current directory.
User response
Consider updating the log file name using a fully qualified path.
FMY5059W The logfile log file cannot be opened for writing. There will be no logging of events.
Explanation
The log mentioned could not be opened for appends. Therefore, no logging is performed.
System action
Processing continues without logging.
User response
Determine why the log file could not be opened. The log file may refer to a non-existent drive or partition, or the log file is marked read-only.
FMY5060E A IBM Storage Protect Snapshot API error has occurred.
Explanation
A IBM Storage Protect Snapshot API error has occurred.
System action
Processing ends.
User response
Retry the operation. If the error persists, contact your service representative.
FMY5061E A Microsoft SQL API error has occurred.
Explanation
A Microsoft SQL API error occurred.
System action
Processing ends.
User response
Retry the operation. If the error persists, contact your service representative.
FMY5063I The logfile_name log file did not need pruning.
Explanation
The log file specified did not need to be pruned.
System action
Processing continues.
User response
The log file will automatically be pruned at a later date. If the log file is currently too large, decrease the number of days the log entries are retained.
FMY5064W The logfile_name log file could not be opened for writing. The log was not pruned and there will be no logging of events.
Explanation
The log mentioned could not be opened for appends. Therefore, no logging or pruning is performed.
System action
Processing continues without logging and without pruning.
User response
Determine why the log file could not be opened. The log file may refer to a non-existent drive or partition, or the log file is marked read-only.
FMY5065E The value specified for the /SQLUSer option does not match the registry entry.
Explanation
A Backup, Restore or Query Sql command was issued with both the /SQLAUTHentication=SQLUserid and the /SQLUSer option specified. An attempt was made to obtain the sqlpassword value from the registry but the user ID in the registry does not match the user ID specified with the /sqluser option.
System action
Processing ends.
User response
Issue the command and either specify the /sqluser value which matches the registry entry or specify the desired values for both the /sqluser and /sqlpassword options on the command.
FMY5091E PASSWORDACCESS is Generate. Either the stored password is incorrect or there is no stored password. If you do not have a stored password, use the -TSMPassword=xxx option to set and store your password.
Explanation
The PASSWORDACCESS option is set to generate in the client options file. However, no password is stored. An initial password needs to be stored.
System action
Processing ends.
User response
Invoke the command again using the -TSMPassword option. Any subsequent commands should now complete without specifying a password.
FMY5097I IBM Storage Protect Snapshot for SQL Server is not configured for VSS operations.
Explanation
IBM Storage Protect Snapshot for SQL Server has not been configured to perform VSS operations.
System action
None.
User response
In order to perform VSS operations, there must be a valid license installed for IBM Storage Protect Snapshot for SQL Server, and the IBM Storage Protect Snapshot for SQL Server LOCALDSMAGENTNODE preference must be correctly set. Refer to the IBM Storage Protect Snapshot for SQL Server User's Guide for details on configuring the client for VSS operations.
FMY5098E Error obtaining VSS information from Local DSMAgent Node: 'localdsmagentnode'.
Explanation
IBM Storage Protect Snapshot for SQL Server attempted to obtain VSS information through the specified LOCALDSMAGENTNODE but failed. The error message encountered is also displayed.
System action
VSS information is not displayed.
User response
Refer to the error message displayed along with this message.
FMY5124E Invalid command. IBM Storage Protect Snapshot for SQL Server only supports VSS backup type of FULL.
Explanation
An invalid backup type was specified on the VSS backup request. IBM Storage Protect Snapshot for SQL Server supports backup types of FULL when using the VSS backup method.
System action
The backup operation is canceled.
User response
Retry the backup operation specifying a supported VSS backup type.
FMY5125E Invalid command. IBM Storage Protect Snapshot for SQL Server does not support OFFLOAD with the Legacy backup method.
Explanation
The OFFLOAD option was specified when using the Legacy backup method. IBM Storage Protect Snapshot for SQL Server does not support offload with the Legacy backup method. IBM Storage Protect Snapshot for SQL Server supports offload with the VSS backup method only.
System action
The backup operation is canceled.
User response
Retry the backup operation without specifying the offload option or by specifying the VSS backup method.
FMY5126E Invalid command. IBM Storage Protect Snapshot for SQL Server only supports Legacy backups with a backup destination of TSM.
Explanation
An invalid backup destination was specified with the Legacy backup method. IBM Storage Protect Snapshot for SQL Server only supports a backup destination of TSM when using the Legacy backup method.
System action
The backup operation is canceled.
User response
Retry the backup operation specifying a backup destination of TSM.
FMY5127E Invalid command. IBM Storage Protect Snapshot for SQL Server does not support OFFLOAD with the combination specified for backup destination and version of Windows.
Explanation
The OFFLOAD option was specified with an unsupported backup destination. IBM Storage Protect Snapshot for SQL Server only supports offload if the backup destination is TSM or BOTH.
System action
The backup operation is canceled.
User response
Retry the VSS offloaded backup operation specifying a backup destination of TSM or BOTH.
FMY5128E The VSS operation failed with rc = returncode.
Explanation
There was a failure when IBM Storage Protect Snapshot for SQL Server performed the VSS operation.
System action
The VSS operation stops.
User response
Verify that the client acceptor is installed, configured, and running properly on the machine. Retry the operation. If the error persists, contact your service representative.
FMY5129E IBM Storage Protect Snapshot for SQL Server is unable to run VSS operations. A valid license file for IBM Storage Protect Snapshot (fcmclient.lic) could not be located.
Explanation
In order to perform VSS operations, it is required that a valid license file for IBM Storage Protect Snapshot is installed in the IBM Storage Protect Snapshot installation directory.
System action
The operation stops.
User response
Verify that the prerequisites identified above are met and retry the operation. If the error persists, contact your service representative.
FMY5170E Missing, blank, or invalid Local DSMAGENT Node Name is not allowed.
Explanation
In order to run VSS operations, IBM Storage Protect Snapshot for SQL Server verifies that the Local DSMAGENT Node Name is specified and valid. This error indicates that the Local DSMAGENT Node Name is missing, blank, or invalid.
System action
The operation stops.
User response
Set the Local DSMAGENT Node Name to a valid value and retry the operation.
FMY5171E Invalid command. IBM Storage Protect Snapshot for SQL Server only supports restoring VSS backup types of FULL and COPY.
Explanation
An invalid backup type was specified on the VSS restore request. IBM Storage Protect Snapshot for SQL Server supports restoring backups of type FULL and COPY.
System action
The restore operation is canceled.
User response
Retry the restore operation specifying a supported VSS backup type.
FMY5172E Invalid command. IBM Storage Protect Snapshot for SQL Server VSS restore does not support RESTOREDATE and RESTORETIME options.
Explanation
An invalid option was specified on the VSS restore request. IBM Storage Protect Snapshot for SQL Server RESTOREDATE and RESTORETIME options are not supported for VSS restore.
System action
The restore operation is canceled.
User response
Retry the restore operation without specifying RESTOREDATE and RESTORETIME options.
FMY5186E The VSS writer didn't return any selectable backup components for the specified database(s). Ensure that the SQL Server VSS writer service has been started.
Explanation
The SQL Server VSS writer service didn't return any selectable backup components for the specified database(s).
System action
Backup fails, processing ends.
User response
Ensure that the SQL Server VSS writer service has been started and that service start type is set to automatic.
FMY5188E BOTH may not be specified for /BACKUPDESTINATION, only TSM or LOCAL are valid.
Explanation
The restore command only allows specifying backup destinations of TSM or LOCAL for identifying database(s) to restore.
System action
The restore operation is canceled.
User response
Retry the restore operation specifying TSM or LOCAL with /BACKUPDESTINATION parameters.
FMY5195I IBM Storage Protect Snapshot for SQL Server: Backup of server servername enhanced statistics. Total SQL backups deduplicated: number deduplicated Throughput rate: rate Kb/Sec Total bytes inspected: bytes inspected Total bytes transferred: bytes Total LanFree bytes transferred: lanfree bytes Total bytes before deduplication: prededup bytes Total bytes after deduplication: postdedup bytes Data compressed by: compression ratio%% Deduplication reduction: deduplication ratio%% Total data reduction ratio: reduction ratio%% Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log displaying additional statistics at the end of a backup request.
System action
None
User response
None Centrally logged
FMY5196I IBM Storage Protect Snapshot for SQL Server: Backup of server servername is complete. Total SQL backups selected: number selected Total SQL backups attempted: number attempted Total SQL backups completed: number completed Total SQL backups excluded: number excluded Total SQL backups deduplicated: number deduplicated Throughput rate: rate Kb/Sec Total bytes inspected: bytes inspected Total bytes transferred: bytes Total LanFree bytes transferred: lanfree bytes Total bytes before deduplication: prededup bytes Total bytes after deduplication: postdedup bytes Data compressed by: compression ratio%% Deduplication reduction: deduplication ratio%% Total data reduction ratio: reduction ratio%% Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the end of a backup request.
System action
None
User response
None Centrally logged
FMY5197I IBM Storage Protect Snapshot for SQL Server: Restore from server server name to server server name is complete. Total database backups inspected: number inspected Total database backups requested for restore: number requested Total database backups restored: number restored Total database skipped: number skipped Throughput rate: rate Kb/Sec Total bytes transferred: bytes Total LanFree bytes transferred: lanfree bytes Elapsed processing time: time Secs
Explanation
This is an informational message written to the IBM Storage Protect Snapshot Server activity log indicating the end of a restore.
System action
None
User response
None Centrally logged
FMY5198W WARNING: The LOG backup of the 'database' database failed, however, the log may have been truncated. You should perform a FULL backup of the database.
Explanation
The LOG backup of the database failed, however, the log may have been truncated. You should perform a FULL backup of the database.
System action
Processing continues.
User response
You should perform a FULL backup of the database.
FMY5204E None of the specified databases exist, or are available for backup.
Explanation
A request was made to backup databases which do not exist, or are not available.
System action
Processing ends.
User response
Ensure that all of the databases exist and are available, and restart the backup.
FMY5205E The command is not valid. IBM Storage Protect Snapshot for SQL Server supports restoring the VMVSS FULL backup type.
Explanation
When the VMVSS restore request is entered, an invalid backup type is specified. The FULL backup type is supported with IBM Storage Protect Snapshot for SQL Server restore backups.
System action
The restore operation is canceled.
User response
Start the restore operation after you specify a supported VMVSS backup type.
FMY5400E The Virtual Device Interface is not registered with the Common Object Model.
Explanation
The virtual device interface could not be created because it is not registered with the common object model. The SQL server may not be installed properly.
System action
Processing ends.
User response
Verify that the SQL server is installed properly and retry the operation. Contact your service representative if the error persists.
FMY5401E The Virtual Device Interface could not be created.
Explanation
The Virtual Device Interface could not be created. The SQL Server Virtual Device Interface (VDI) log or Windows event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5402E The Virtual Device Set could not be created.
Explanation
The Virtual Device Set could not be created. The SQL Server Virtual Device Interface (VDI) log or Windows event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5403E The configuration of the Virtual Device Set could not be obtained.
Explanation
The configuration of the Virtual Device Set could not be obtained. The SQL Server Virtual Device Interface (VDI) log, SQL Server activity log, SQL Server error log, or Windows application event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not help resolve the problem retry the operation. If the error persists, contact your service representative.
FMY5404E The Virtual Device Set could not open a virtual device.
Explanation
The Virtual Device Set could not open a virtual device. The SQL Server Virtual Device Interface (VDI) log, SQL Server activity log, SQL Server error log, or Windows application event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5405E An unknown virtual device error has been detected.
Explanation
A virtual device returned and unknown return code.\n" The SQL Server Virtual Device Interface (VDI) log, SQL Server activity log, SQL Server error log, or Windows application event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5406E The SQL Server closed a virtual device prematurely.
Explanation
The SQL Server aborted the operation on the selected database. The SQL Server Virtual Device Interface (VDI) log, SQL server activity log, SQL Server error log, or Windows application event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5407E The SQL Server aborted the operation.
Explanation
The SQL Server aborted the operation on the selected database. The SQL Server Virtual Device Interface (VDI) log, SQL Server activity log, SQL Server error log, or Windows application event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5421E Received the following from the MS COM component: SQL message
Explanation
A SQL error has occurred.
System action
Processing for this operation ends.
User response
If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5422E Received the following from the MS SQL server: SQL message
Explanation
A SQL error has occurred.
System action
Processing for this operation ends.
User response
If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5423E The following string is too long: string
Explanation
A SQL error has occurred.
System action
Processing for this operation ends.
User response
If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5424E Could not connect to SQL server; SQL server returned: SQL message
Explanation
A SQL error has occurred.
System action
Processing for this operation ends.
User response
If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5425E The SQL server is not running: SQL message
Explanation
A SQL error has occurred.
System action
Processing for this operation ends.
User response
Start the SQL server and retry the operation.
FMY5426E The SQL log on does not have the Sysadmin role: SQL message
Explanation
An attempt was made to logon to the SQL server but the specified logon name does not have the Sysadmin role.
System action
Processing for this operation ends.
User response
Try the operation again and specify either a log on name with the Sysadmin role or change the specified log on name to have the Sysadmin role.
FMY5428E The SQL server is not on the local machine: SQL message
Explanation
An attempt was made to use the application client specifying a SQL server that was not on the local machine.
System action
Processing for this operation ends.
User response
Retry the operation on the machine where the SQL server resides.
FMY5429E Could not obtain an event from SQL server: SQL message
Explanation
A SQL error has occurred.
System action
Processing for this operation ends.
User response
If the SQL server messages do not resolve the problem, retry the operation. Contact your service representative if the error persists.
FMY5430E The SQL Server Name is blank or NULL.
Explanation
In the query to obtain the SQL Server Name, the system returned a blank name. A valid SQL Server Name is necessary to continue the operation.
System action
Processing for the current operation ends.
User response
Check the SQL Server Name by using the "select @@servername" command from the SQL Query Analyzer. If that returns NULL, use the "sp_addserver" stored procedure to set the SQL Server Name to the correct value. After setting the SQL Server Name, retry the operation. Contact your service representative if the error persists.
FMY5431E Multiple dbnames are not allowed.
Explanation
An invalid RESTORE command was issued. It is not valid to specify multiple database names in the <dbname> parameter list when using the /STANDBY, /RELOCATE, or /INTO options.
System action
Processing ends.
User response
Enter the command again with a valid value in the positional parameter or option.
FMY5432E Equal numbers of the /RELOCATE and /TO options must be specified.
Explanation
Unequal numbers of the /RELOCATE and /TO options were specified on a RESTORE command.
System action
Processing ends.
User response
Re-enter the command specifying the same number of /RELOCATE and /TO options.
FMY5433E Wildcards are not allowed as part of the following parameters/options:
Explanation
This message displays the positional parameters and/or options that were specified incorrectly.
System action
Processing ends.
User response
Re-enter the command specifying the correct parameters and/or options.
FMY5434E The following options cannot be specified together:
Explanation
This message displays the conflicting command options that were entered.
System action
Processing ends.
User response
Re-enter the command specifying valid command options.
FMY5435E This command requires one of the following options:
Explanation
This message displays the options that were missing from the command entered.
System action
Processing ends.
User response
Re-enter the command specifying one of the command options required by the command.
FMY5436E A failure occurred on stripe number (stripe number), rc = return code
Explanation
A failure occurred on the numbered stripe.
System action
Processing ends.
User response
There should be other messages along with this one. Refer to the other messages to determine the problem.
FMY5450E The specified number of stripes (number of stripes) is invalid. Processing will continue with the maximum number of stripes (maximum number of stripes).
Explanation
An invalid number of stripes was specified.
System action
Processing continues utilizing the allowed maximum number of stripes.
User response
None
FMY5452E Unable to delete temporary object: (filespace name) (high level qualifier) (low level qualifier)
Explanation
When a backup fails, the IBM Storage Protect agent attempts to delete all temporary backup data objects from the Storage Protect Snapshot server. This message indicates that the specified temporary backup data object could not be deleted from the Storage Protect Snapshot server. This error is usually caused by the loss of all Storage Protect Snapshot server sessions.
System action
Processing continues.
User response
None. A backup of the database should detect the temporary backup data object and delete it from the Storage Protect Snapshot server.
FMY5453E The number of Storage Protect Snapshot sessions (number of sessions) is invalid for the specified number of stripes (number of stripes). Processing will continue with the number of Storage Protect Snapshot sessions (number of sessions) as the number of stripes.
Explanation
An invalid number of Storage Protect Snapshot sessions was detected for the specified number of stripes. This message is caused by the circumvention of an internal error.
System action
Processing continues utilizing the number of Storage Protect Snapshot sessions as the number of stripes.
User response
Try the operation again. Contact your service representative if this error persists.
FMY5454E The maximum number of objects allowed per Storage Protect Snapshot transaction (number) is invalid for the specified number of stripes (number of stripes). Processing will continue with number stripes.
Explanation
The maximum number of objects allowed per Storage Protect Snapshot transaction is invalid for the specified number of stripes for at least one of the Storage Protect Snapshot sessions. All Storage Protect Snapshot sessions must allow at least one more object per Storage Protect Snapshot transaction than the number of stripes
System action
Processing continues utilizing the new number of stripes.
User response
Reduce the number of stripes. You can also update the Storage Protect Snapshot server to increase the maximum number of logical files that a client can send to the server in a single transaction (TxnGrpMax).
FMY5455E The backup is corrupt and can not be restored.
Explanation
The backup being restored is corrupt because the data object or objects found do not correspond to the metadata.
System action
Processing ends.
User response
Try the operation again. Contact your service representative if the error persists.
FMY5456W The backup is corrupt and is not fully restorable. Processing will continue.
Explanation
The backup being restored is corrupt because the data object or objects found do not correspond to the metadata. Depending on the restore command and the backup type, a partial restore may be possible.
System action
Processing continues.
User response
Try the operation again. Contact your service representative if the error persists.
FMY5457E An unknown SQL API error has occurred.
Explanation
A SQL API error has occurred but the associated error message could not be found. The SQL Server activity log, SQL Server error log, or Windows application event log may contain more information.
System action
Processing ends.
User response
If the SQL Server messages do not resolve the problem, try the operation again. Contact your service representative if the error persists.
FMY5458W The Storage Protect Snapshot Server 'backup delete' setting for node (server node name) is set to NO. It should be set to YES for proper operation. Processing continues.
Explanation
The Storage Protect Snapshot Server setting that allows Storage Protect Snapshot clients to delete their own backups is set to NO for the specified node name. The backup delete value must be set to YES in order for cleanup operations to complete successfully. A NO value means that unusable residual data might be stored on the Storage Protect Snapshot Server.
System action
Processing continues.
User response
Make sure the 'backup delete' setting for the specified node name is set to YES on the Storage Protect Snapshot Server. Your Storage Protect Snapshot Server administrator can change this setting for your node. The setting can only be changed on the Storage Protect Snapshot Server.
FMY5459W Database object name excluded from backup.
Explanation
The specified database was excluded from backup by the /EXCLUDEDB setting.
System action
Database isn't backed up.
User response
None.
FMY5460W Database object object name doesn't exist or isn't valid.
Explanation
The specified backup object doesn't exist or isn't valid.
System action
Processing for this backup object ends.
User response
Make sure the specified backup object exists.
FMY5500E The MultiByteToWideChar() function failed.
Explanation
This is an internal error that indicates corrupted storage.
System action
Processing for this database ends.
User response
Try the operation again. Contact your service representative if this error persists.
FMY5501E The Common Object Model (COM) library failed to initialize.
Explanation
The unsuccessful call was CoInitializeEx(NULL,COINIT_MULTITHREADED). OLE32.dll or another COM DLL may be missing, down-level, or corrupted.
System action
Processing for this database ends.
User response
Verify your Windows installation is complete and try the operation again. Contact your service representative if this error persists.
FMY5550I There are no backups matching the filespec directorypathfilename and the server name servername.
Explanation
There are no database backups on the IBM Storage Protect Snapshot server for the specified server name.
System action
Processing ends.
User response
None
FMY5551I There are no backups matching the criteria specified for server name servername.
Explanation
There are no database backups on the IBM Storage Protect Snapshot server matching the query criteria for the specified server name.
System action
Processing ends.
User response
Specify a broader range of search criteria when issuing this query.
FMY5552I No matches were found for the criteria specified.
Explanation
The SQL Server was searched for databases that matched the specified criteria.
System action
Processing ends.
User response
Check the specified search criteria (database name, group name, logical filename). Enter the command again.
FMY5616W Database cannot be backed up because its name contains '\', '?', '*', or ':' character(s).
Explanation
Databases whose names contain directory or volume separator cannot be backed up or restored.
System action
Database was excluded from backup.
User response
Rename the database and restart backup.
FMY5617I Database was excluded from backup because database name contains '\', '?', ':' or '*' character(s).
Explanation
Databases whose names contain directory or volume separator cannot be backed up or restored.
System action
Database was excluded from backup.
User response
Rename the database and restart backup.
FMY5629E No Backups have been selected for restore.
Explanation
The Restore button was pressed but nothing was selected in the tree or list view.
System action
Processing stops.
User response
Make a selection in the tree or list view and press the Restore button again.
FMY5630E Backups from multiple Server instances have been selected for restore.
Explanation
The Restore button was pressed and the user has selected backups from multiple server instances.
System action
Processing stops.
User response
Make a selection in the tree for backups belonging to the same server instance only
FMY5631E Restoring full Legacy backups and full VSS backups in the same restore operation is not supported. Retry the restores in separate operations.
Explanation
At least one VSS backup object and one Legacy backup object were selected for a restore in the same operation. This is not supported.
System action
The restore operation is canceled.
User response
Retry the restores specifying the Legacy backups and VSS backups in separate operations.
FMY5715E Error writing option_name preference to the configuration file.
Explanation
Could not write the specified preference to the configuration file.
System action
Preferences processing ends.
User response
Make sure you have a valid configuration file, then try to update the preference again.
FMY5716W An error was encountered with IBM Storage Protect Snapshot API initialization, rc = returncode. Examine the dsierror.log for more information or determine if the Storage Protect Snapshot API is installed properly.
Explanation
Errors were encountered during an attempt to run setup for the IBM Storage Protect Snapshot API.
System action
Processing continues.
User response
Examine the dsierror.log file to determine the problem. If this file does not exist, the Storage Protect Snapshot API may not be installed properly. If the Storage Protect Snapshot API is not installed properly, install the Storage Protect Snapshot API and run the command again.
FMY5717E Unable to log on to the SQL server.
Explanation
An error occurred while trying to log on to the SQL server.
System action
If running the client from the command line, the client ends. If running the client from the GUI, a prompt is displayed to enter the SQL user ID and password, or to choose Windows authentication.
User response
Make sure the SQL server is running.
FMY5718I When the view is refreshed all selections will be lost and an attempt will be made to expand the new tree to the currently highlighted item. Do you want to continue?
Explanation
The refresh toolbar button or pulldown menu item has been selected.
System action
Processing continues.
User response
Select Yes to refresh the view or select No to leave the current view unchanged.
FMY5719I There are currently no backups on the Storage Protect Snapshot server.
Explanation
The SQL server name expansion button was pressed on the Inactivate page.
System action
Processing stops.
User response
Either nothing was backed up to a Storage Protect Snapshot server or all active backups were inactivated.
FMY5720I No databases have been selected for backup.
Explanation
The Backup button was pressed on the GUI but no databases were selected from the tree or list.
System action
Processing stops.
User response
Select a database and press the Backup button again.
FMY5721I No backups have been selected for restore.
Explanation
The restore button was pressed on the GUI but no backup objects were selected from the tree or list.
System action
Processing stops.
User response
Select a backup object and press the Restore button again.
FMY5722I No backups have been selected for inactivate.
Explanation
The Inactivate button was pressed on the GUI but no backup objects were selected from the tree or list.
System action
Processing stops.
User response
Select a backup object and press the Inactivate button again.
FMY5723E A named mark must be specified.
Explanation
The "Stop At Mark" or "Stop Before Mark" option was chosen but the named mark was not specified.
System action
Processing stops.
User response
Enter a named mark or choose the "Stop At" option.
FMY5770E Cannot read the SQL Server version from Windows registry.
Explanation
An attempt was made to read the SQL Server version for the provided server instance from the Windows registry. This attempt failed because the server name is not found in the registry.
System action
Processing for this operation ends.
User response
Provide an existing valid SQL Server instance.
FMY5784E A log must be selected to use point in time.
Explanation
A log must be selected before setting point in time parameters.
System action
Processing stops.
User response
Select at least one log for restore before specifying a point in time.
FMY5804I Unable to get information. If data is backed up to tape check the "Wait for Tape Mounts for File Information" checkbox.
Explanation
Processing stops.
System action
None
User response
Try checking the box specified in the message.
FMY5915E An attempt to query detailed managed capacity failed.
Explanation
System action
User response
FMY5958W The selected database <> is offline -- skipping.
Explanation
A request was made to backup a database which is offline.
System action
Processing continues, but offline databases are skipped.
User response
Ensure that the selected databases are online and retry the backup.
FMY5959E Unable to run data protection operations to a IBM Storage Protect Snapshot virtual server. A valid IBM Storage Protect Snapshot license file could not be located.
Explanation
In order to perform data protection operations to a IBM Storage Protect Snapshot virtual server, a valid license for IBM Storage Protect Snapshot must be installed in the IBM Storage Protect Snapshot installation directory. This license file is named fcmclient.lic.
System action
The operation stops.
User response
Verify that the prerequisites identified above are met and retry the operation. If the error persists, contact your service representative.
FMY5960E This product is not licensed to run data protection operations to the IBM Storage Protect Server. A valid license file for Data Protection for Microsoft SQL Server could not be located. With the current licenses only data protection operations to the IBM Storage Protect Snapshot virtual server can be run.
Explanation
In order to perform data protection operations to the IBM Storage Protect server, a valid license for Data Protection for Microsoft SQL Server (called sqlclient.lic) must be installed. The license file for Data Protection for Microsoft SQL Server should be installed in the installation directory of Data Protection for Microsoft SQL Server.
System action
The operation stops.
User response
Verify that the prerequisites identified above are met and retry the operation. If the error persists, contact your service representative.
FMY5961E The parameters /BACKUPMETHOD or /BACKUPDESTINATION or both are invalid when performing data protection operations using a IBM Storage Protect Snapshot virtual server.
Explanation
Data protection commands default to /BACKUPMETHOD=VSS and /BACKUPDESTINATION=LOCAL when performed against a IBM Storage Protect Snapshot virtual server. The IBM Storage Protect Snapshot supports no other values for these parameters. As a result it is no longer necessary to specify these parameters. For compatibility with other products values for /BACKUPMETHOD and /BACKUPDESTINATION can be specified as long as they are set to their only valid values. This means that /BACKUPMETHOD can only be set to VSS and /BACKUPDESTINATION can only be set to LOCAL.
System action
The operation stops.
User response
Retry the command removing the /BACKUPDESTINATION and /BACKUPMETHOD parameters.
FMY5965E Database state does not allow log backup with TRUNCATE=YES.
Explanation
Database status is not Normal. Log has to be backed up with truncation turned off.
System action
The backup operation failed.
User response
Back up log with TRUNCATE=NO.
FMY5966E Logical name was not found in the database.
Explanation
The logical name specified during relocation was not found in the database.
System action
Processing for this operation ends.
User response
Specify the correct logical name and retry the operation.
FMY5969E Database state does not allow backup log tail.
Explanation
Database status is not Normal. By now we only support backup the tail of the log when database is not offline or damaged.
System action
The backup operation failed.
User response
Back up the tail of the log when database status is normal.
FMY6060I No matched backup is found according to the Query conditions.
Explanation
Information: No matched backup is found in IBM Storage Protect Server according to the Query conditions.
System action
Processing continues.
User response
FMY6065E Mount backup command failed. The mount point and / or backup specified is invalid. Please refer to dsmerror.log for further details.
Explanation
The mount backup command failed. The backup specified may already be mounted and or the drive to map to may already be in used. Check if the provided directory to contain the mount point directories for all snapshots is an empty NTFS directory without hidden or system files and / or directories.
System action
Processing stops.
User response
Check to make sure that the backup specified is not already mounted and that the drive to map to is available. Repeat the command using an empty NTFS directory as the snapshots mount points directory.
FMY6066E Unmount backup command failed. Please refer to dsmerror.log for further details.
Explanation
The unmount backup command failed. The backup specified may not be mounted.
System action
Processing stops.
User response
Check to make sure that the backup specified is mounted.
FMY6067E In the component list that is specified, the following object is not valid: 'object'.
Explanation
The command that is entered includes a component list. The list of components contains one or more invalid objects. For example, when entering a BACKUP or RESTORE command, if the component list includes a volume or mount point that is not valid or is not eligible for back up, this message is displayed. In addition, the GUID volume name cannot be specified. For RESTORE, MOUNT BACKUP, or DELETE BACKUP commands, this message is displayed if the component list contains a backup specification that is not found in the backup inventory.
System action
The operation stops.
User response
Verify the correct syntax is used when entering the command. If the message is displayed again, verify the volume and mount point names are correctly identified. A misspelling can trigger this message.
FMY6101I Backup of database 'database name' is bypassed because it is a secondary replica in an AlwaysOn Availability Group that is using Microsoft SQL Server Standard Edition.
Explanation
Backup processing bypasses the database on a secondary replica in an AlwaysOn Availability Group that is using Microsoft SQL Server Standard Edition.
System action
Backup processing continues but the database on a secondary replica in AAG that is using Microsoft SQL Server Standard Edition is skipped.
User response
Install SQL Server Enterprise Edition and retry the backup.
FMY6103I AlwaysOnPriority is skipping the backup of availability database name because it is not on the preferred replica.
Explanation
When the AlwaysOnPriority option is specified SQL Server is queried to see if the current availability replica is the preferred replica. The backup of the availability database will only be performed on the preferred replica. The backup is skipped on all replicas that are not the primary replica.
System action
Processing for this backup object ends.
User response
No response is needed.
FMY6104I Backup Type backup for database database name is not supported from none-readable secondary replica.
Explanation
Database on none-readable secondary replica only supports full backup and copyonly backup.
System action
Run the same backup from primary replica or readable secondary replica.
User response
Run the same backup from primary replica or readable secondary replica.
FMY6105I Differential backup database database name from secondary replica is not supported. Exclude it for backup.
Explanation
Differential backup databases from secondary replica is not supported.
System action
Run the same backup from primary replica.
User response
Run the same backup from primary replica.
FMY6110W Backup of database 'database name' is bypassed because it is offline. Database attributes are database attributes.
Explanation
Backup processing bypasses the offline database.
System action
Backup processing continues but the offline database is skipped.
User response
Ensure that the selected database is online or normal database and retry the backup.
FMY6111I Backup of database 'database name' is bypassed because it is a database snapshot. Database attributes are database attributes.
Explanation
Backup processing bypasses the database snapshot.
System action
Backup processing continues but the database snapshot is skipped.
User response
Ensure that the selected database is online or normal database and retry the backup.
FMY6112W Backup of database 'database name' is bypassed because it is in restoring status. Database attributes are database attributes.
Explanation
Backup processing bypasses the database with restoring status database.
System action
Backup processing continues but the database with restoring status database is skipped.
User response
Ensure that the selected database is online or normal database and retry the backup.
FMY6113I Backup of database 'database name' is bypassed because it is a mirrored database. Database attributes are database attributes.
Explanation
Backup processing bypasses the mirrored database.
System action
Backup processing continues but the mirrored database is skipped.
User response
Ensure that the selected database is online or normal database and retry the backup.
FMY6114W Backup bypassed some databases because of their status.
Explanation
Backup processing bypasses the offline, snapshot, mirrored, or with restoring state database.
System action
Backup processing continues but some databases are skipped.
User response
Ensure that the skipped databases are online, and retry the backup.
FMY6115I Backup of database 'database name' is bypassed because it is offline. Database attributes are database attributes.
Explanation
Backup processing bypasses the offline database.
System action
Backup processing continues but the offline database is skipped.
User response
Ensure that the selected database is online or normal database and retry the backup.
FMY6116I Backup of database 'database name' is bypassed because it is in restoring status. Database attributes are database attributes.
Explanation
Backup processing bypasses the database with restoring status database.
System action
Backup processing continues but the database with restoring status database is skipped.
User response
Ensure that the selected database is online or normal database and retry the backup.
FMY6117I Actions were taken to fix the error messages FMY5436E and FMV0328E.
Explanation
This is an informational message to let you know that the merge error was fixed.
System action
None
User response
None
FMY6200W The data center node is not correctly configured. To correct the problem, re-run the configuration wizard and set the datacenter node field with the node that was used to perform the VM backups.
Explanation
Warning: Because the data center node is not configured to match the query and restore conditions, this warning is reported.
System action
Processing continues, but the data center node configuration problem persists until you update the configuration.
User response
Run the IBM Storage Protect configuration wizard. If the status of the Configuring Recovery Agent rule does not indicate Passed, there is a configuration problem.
FMY6201W The license for the Recovery Agent, part of the IBM Storage Protect for Virtual Environments, is either not valid or not found.
Explanation
Warning: Without a valid license for the Recovery Agent, you cannot use parts of Data Protection for Microsoft SQL Server to recover Microsoft SQL databases from a VM backup.
System action
The software continues to run, but you cannot use Data Protection for Microsoft SQL Server to recover Microsoft SQL databases from a VM backup.
User response
Verify that the correct license file is in the correct directory. If you use the installation wizard, the license file should be saved to the correct directory.
FMY6202W Storage Protect Snapshot Recovery Agent is either at an earlier level or not found. The VM backup data query or restore is not issued.
Explanation
Warning: To issue the VM backup data query or restore, update the software. Please upgrade it to support this feature.
System action
The command is ignored and processing continues.
User response
FMY6203I The tail-log backup of the database from the secondary replica is not supported. databases name is excluded from the backup process.
Explanation
Tail-log backups of databases from the secondary replica are not supported.
System action
The database backup operation is canceled.
User response
Run the backup from the primary replica.
FMY6204I The tail-log backup of the database name database from the primary server removes the databases from the AAG. Do you want to continue? Enter 'Y' for Continue or 'N' to cancel.
Explanation
The tail-log backup of databases from the primary server removes databases from the AAG.
System action
If the database is not removed from the AAG, the SQL Server reports an error when completing the backup.
User response
To continue with the tail-log backup and remove database from the AAG, enter Y. To cancel, enter N.
FMY6205E The tdpsqlc command that was entered exceeds the maximum length limit. The length limit of each option is 1790 characters.
Explanation
The length of tdpsqlc command is too long. It is invalid. When the length limit is exceeded, the command is ignored. There is no truncation.
System action
tdpsqlc command will fail with error. An error message is displayed. The command is not processed.
User response
Check the length of tdpsqlc options, especially check the length of multiple databases name. If possible, enter abbreviated parameters and options. If multiple database names are entered, the length of the database names can cause this error.
FMY6206W Database '' was excluded from backup because the database name contains special string ''.
Explanation
There are certain characters and strings that conflict with IBM Storage Protect Snapshot for SQL Server backup operations. A database name that contained one of the special characters or strings was encountered during a backup operation. Therefore, it was excluded from the backup.
System action
The database was excluded from backup.
User response
Rename the database and retry the backup.
FMY6209W Database database name is being backed up on non-readable secondary replica. A restore operation with the database files relocation is not possible for this backup.
Explanation
The information about database files cannot be retrieved on non-readable secondary replica, and is not available for the restore process. A restore operation with the database files relocation cannot be run for these backups.
System action
Processing continues.
User response
To restore database files with a new location, the backup must be taken on the primary or readable secondary replica.
FMY6210W The backup for database database name does not contain information about database files. A restore operation is not possible for this backup.
Explanation
The information about database files cannot be retrieved from the backup.
System action
Processing continues.
User response
Check if the backup was taken on a non-readable secondary replica. If the restore operation with relocation fails, try restoring from a backup that was taken on a readable replica.
FMY6211E The file cannot be restored. The directory paths specified as the target locations do not exist or are invalid.
Explanation
The file cannot be restored to a target location that is non-existent or invalid. The target directory paths specified for the /relocatedir parameter must exist on the server and be valid.
System action
Processing stops.
User response
Verify that the target directory paths specified for the /relocatedir parameter exist on the server and are specified correctly.
FMY6212I Invalid objects (Filespace: '', HL: '', and LL: ') have been deactivated or not been found on the IBM Storage Protect Snapshot server.
Explanation
During the full backup operation, the system found invalid objects on the IBM Storage Protect Snapshot server as a result of a previous unsuccessful backup operation. When the full backup is complete, Data Protection for Microsoft SQL Server operations deactivate the invalid objects automatically.
System action
Data Protection for Microsoft SQL Server operations deactivate the invalid objects on the IBM Storage Protect Snapshot server automatically.
User response
No action is required.
FMY6213E The version of the installed SQL Server instance is not supported.
Explanation
The version of the installed SQL Server is not supported.
System action
Processing for this operation ends.
User response
Upgrade SQL Server to a supported level. If you proceed without upgrading, then the SQL Server is not supported.
FMY6214W The preference or preferences preference list that can be specified in the preference file preference file name are not valid for the current operation. Default values will be used instead.
Explanation
Some of the preference values specified in the configuration file are not valid for the current operation. Unless you specify valid corresponding options using the command line, default values will be used instead. Consult the Configuring or Reference information chapters of the Data Protection for Microsoft SQL Server Installation and User's Guide for valid preference values.
System action
Processing continues.
User response
Check the configuration file and correct the preference values per those outlined in the Configuring or Reference information chapters of the Data Protection for Microsoft SQL Server Installation and User's Guide.
FMY6215E A RELOCATEDir option must be specified when restoring to an alternate SQL instance.
Explanation
A RELOCATEDir option must be specified. Restore to original location is not supported when restoring to an alternate SQL instance.
System action
Processing ends.
User response
Specify a RELOCATEDir value, then try the operation again.