FBP messages

FBP0001E The Recovery Agent is already running.

Explanation

This issue is encountered when multiple users are logged on to the system and attempting to run the Recovery Agent. Only one active Recovery Agent instance is supported.

System action

The Recovery Agent was not started.

User response

To resolve this issue, close the current Recovery Agent instance or start the Recovery Agent on a different system.

FBP0002E The Tivoli Storage Manager server connection cannot be removed.

Explanation

There are currently active instant restore sessions or mounted volumes that require the connection to the Tivoli Storage Manager server. As a result, the existing connection cannot be removed.

System action

The remove connection operation is canceled.

User response

To resolve this issue, wait until the instant restore sessions complete. Or, forcibly end the instant restore sessions or mounted volumes and then disconnect the Tivoli Storage Manager server.

FBP0003E 'Authentication node' and 'Target node' cannot specify the same node.

Explanation

Three node authentication methods are available to access snapshots on the Tivoli Storage Manager server: 'Asnodename' authenticates with a proxy node, 'Fromnode' authenticates with a node that contains limited access, and 'Direct' authenticates directly. When 'Fromnode' or 'Asnodename' are selected, a target node must be specified. The target node is the Tivoli Storage Manager node where the virtual machine backups are located.

System action

The system waits for a user response.

User response

Specify the correct 'Authentication node' and 'Target node'. See information about the node authentication methods in the product documentation.

FBP0004E Recovery Agent failed to mount.

Explanation

The mount operation on the Windows Recovery Agent proxy host failed.

System action

The operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs for information about why the mount operation failed.

FBP0005E RAID mirror status was not obtained.

Explanation

During the instant restore session, the Recovery Agent failed to obtain the status of the mdadm mirror device.

System action

An attempt to recover the instant restore session is being made.

User response

Check the instant restore status in the Recovery Agent GUI and the Recovery Agent engine logs for solutions to this problem.

FBP0006E Incorrect parameters were specified during the Recovery Agent mount operation.

Explanation

The mount operation on the Windows Recovery Agent proxy host failed because incorrect parameters were specified.

System action

The operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs for information about why the mount operation failed.

FBP0007E The selected snapshot is already mounted.

Explanation

The Windows Recovery Agent proxy host identified the selected snapshot as already mounted to the requested target.

System action

None.

User response

The instant restore session or mounted snapshot is available for use.

FBP0010E Failed to dismount.

Explanation

The dismount operation on the Windows Recovery Agent proxy host failed.

System action

The operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs for information about why the dismount operation failed.

FBP0011E The node data was not retrieved.

Explanation

The Windows Recovery Agent proxy host failed to retrieve the node data when querying the Tivoli Storage Manager server.

System action

The operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs for information about why the querying operation failed.

FBP0012E Tivoli Storage Manager server snapshots were not found.

Explanation

The Windows Recovery Agent proxy host failed to expose the snapshots on the specified Tivoli Storage Manger server.

System action

The operation is canceled.

User response

Verify that the correct Tivoli Storage Manager server and node that own the snapshots are specified.

FBP0013E The snapshot was not found. Click 'Refresh'.

Explanation

The selected snapshot was not found on the Tivoli Storage Manager server.

System action

The operation is canceled.

User response

Click Refresh in the Recovery Agent GUI to load the current snapshots on the Tivoli Storage Manager server.

FBP0016E Invalid parameters were specified.

Explanation

The mount operation on the Windows Recovery Agent proxy host failed.

System action

The operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs for information about why the mount operation failed.

FBP0017E The mdadm version is not supported.

Explanation

The installed version of the mdadm utility on the Linux machine is not supported.

System action

The operation is canceled.

User response

Upgrade the mdadm utility on your Recovery Agent Linux machine to a supported version. For current software requirements, see technote 1505139.

FBP0018E The mdadm utility was not found.

Explanation

The mdadm utility is not installed on the Linux machine.

System action

The operation is canceled.

User response

Install the mdadm utility on your Recovery Agent Linux machine. For current software requirements, see technote 1505139.

FBP0019E The iscsiadm version is not supported.

Explanation

The installed version of the iscsiadm utility (for Recovery Agent on RedHat Linux machines) or open-iscsi (for Recovery Agent on SUSE Linux machines) is not supported.

System action

The operation is canceled.

FBP0020E The iscsiadm utility was not found.

Explanation

The iscsiadm utility is not installed on the Linux machine.

System action

The operation is canceled.

User response

Install the iscsiadm utility on your Recovery Agent Linux machine. For current software requirements, see technote 1505139.

FBP0021E The lsscsi version is not supported.

Explanation

The installed version of the lsscsi utility is not supported.

System action

The operation is canceled.

User response

Upgrade the lsscsi utility on your Recovery Agent Linux machine to a supported version. For current software requirements, see technote 1505139.

FBP0022E The lsscsi utility was not found.

Explanation

The lsscsi utility is not installed on the Linux machine.

System action

The operation is canceled.

User response

Install the lsscsi utility on your Recovery Agent Linux machine. For current software requirements, see technote 1505139.

FBP0023E The Secure Shell (SSH) version is not supported.

Explanation

The installed version of the SSH client is not supported.

System action

The operation is canceled.

User response

Upgrade the SSH client on your Recovery Agent Linux machine to a supported version. For current software requirements, see technote 1505139.

FBP0024E The Secure Shell (SSH) was not found.

Explanation

The SSH client is not installed on the Linux machine.

System action

The operation is canceled.

User response

Install the SSH client on your Recovery Agent Linux machine. For current software requirements, see technote 1505139.

FBP0025E Not all instant restore sessions were stopped.

Explanation

The Recovery Agent was unable to stop all instant restore sessions.

System action

Some of the instant restore sessions are still visible in the Recovery Agent 'Instant Restore' panel.

User response

Try stopping the instant restore sessions one after the other. If the problem persists, check the Linux Recovery Agent engine log file. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf. Also check the Windows Recovery Agent proxy host logs for any errors related to this issue.

FBP0026E Failed to read instant restore session.

Explanation

The Recovery Agent was unable to read the instant restore status file.

System action

Information about the instant restore is not available.

User response

Try restarting the instant restore session. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0027E Mount session already exists.

Explanation

The selected snapshot is already mounted to the requested target.

System action

None.

User response

The instant restore session or mounted snapshot is available for use.

FBP0028E Failed to create the mount sessions directory.

Explanation

The Recovery Agent was unable to create the directory for the mount operation.

System action

The operation is canceled.

User response

Try the mount operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0029E Failed to encrypt node credentials.

Explanation

The Recovery Agent was unable to encrypt the node credentials.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0030E Failed to decrypt node credentials.

Explanation

The Recovery Agent was unable to decrypt the node credentials.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0031E Failed to remove mount session.

Explanation

The Recovery agent was unable to delete the mount status file.

System action

The mounted snapshot remain in the Recovery Agent 'Mounted Volumes' panel.

User response

Try unmounting the mounted snapshot again. If the problem persists, check the Linux Recovery Agent engine log file. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf for more information. Also check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0032E Instant restore session already exists.

Explanation

A similar instant restore session already exists or a similar instant restore status file exists.

System action

The new instant restore session is canceled.

User response

Check the Linux Recovery Agent engine log file for more information. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0033E Failed to create the instant restore sessions directory.

Explanation

The Recovery Agent was unable to create the directory for the instant restore operation.

System action

The instant restore operation is canceled.

User response

Try the instant restore operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0034E Failed to remove the instant restore session.

Explanation

The Recovery Agent was unable to delete the instant restore status file.

System action

The instant restore session remains in the Recovery Agent 'Instant Restore' panel.

User response

Try stopping the instant restore session again. If the problem persists, check the Linux Recovery Agent engine log file. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf for more information. Also check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0035E Failed to read from the configuration file that is used for mount and instant restore operations.

Explanation

The Recovery Agent was unable to read the configuration file.

System action

Information about the mount or instant restore is not available.

User response

Try the operation again. If the problem persists check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0036E Failed to write to the configuration file that is used for mount and instant restore operations.

Explanation

The Recovery Agent was unable to write to the configuration file.

System action

Information about the mount or instant restore is not available.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0037E Failed to read from the configuration file section that is used for mount and instant restore operations.

Explanation

The Recovery Agent was unable to read the configuration file.

System action

Information about the mount or instant restore is not available.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0038E Failed to write to the configuration file section that is used for mount and instant restore operations.

Explanation

The Recovery Agent was unable to write to the configuration file.

System action

Information about the mount or instant restore is not available.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0039E Failed to unmount. Device is busy.

Explanation

The Recovery Agent was not able to unmount the file system of the selected mounted snapshot because the file system is in use.

System action

The unmount operation is canceled.

User response

Close any application that might be accessing this volume. Then, try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0040E Not all mount sessions were unmounted.

Explanation

The Recovery Agent did not unmount all mounted snapshots.

System action

Some of the mounted snapshots sessions are still visible in the Recovery Agent 'Mounted Volumes' panel.

User response

Try to unmount the mounted snapshots one after the other. If the problem persists check the Linux Recovery Agent engine log file. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0041E Failed to retrieve data from the Recovery Agent CLI.

Explanation

The Recovery Agent was unable to read the Recovery Agent CLI (TDPVMWareShell) output file.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0042E Failed to parse data from the Recovery Agent CLI.

Explanation

The Recovery Agent was unable to parse the data from the Recovery Agent CLI (TDPVMWareShell) output file.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux Recovery Agent engine log file. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0043E Failed to create query for the Recovery Agent CLI.

Explanation

The Recovery Agent was unable to create the Recovery Agent CLI (TDPVMWareShell) output file.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0044E Failed to retrieve mount data from the Recovery Agent CLI.

Explanation

The Recovery Agent was unable to create the Recovery Agent CLI (TDPVMWareShell) output file.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0045E Failed to create mount query for the Recovery Agent CLI.

Explanation

None.

FBP0046E Failed to connect to the Recovery Agent CLI.

Explanation

The Linux Recovery Agent was unable to retrieve the Recovery Agent CLI (TDPVMWareShell) installation path from the registry on the Windows machine.

System action

The operation is canceled.

User response

Check the connectivity to the Windows machine, verify that the SSH is configured correctly, and that the user defined on Cygwin has administrative privileges. For more information, see the product documentation.

FBP0047E Failed to create the mount directory.

Explanation

The Recovery Agent was unable to locate or create the directory for the mount operation.

System action

The mount operation is canceled.

User response

Try the mount operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0048E Failed to mount the file system of the snapshot.

Explanation

The Recovery Agent succeeded connecting to the mounted snapshot iSCSI device. However, the Recovery Agent was unable to mount the file system of the snapshot.

System action

The mount operation failed. The Recovery Agent automatically attempts to mount the file system every 5 minutes.

User response

Since the mounted snapshot is available as an iSCSI device, attempt to mount the file system of the device. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0049E Failed to set the SSH server address.

Explanation

The Recovery Agent was unable to set the SSH server address. The specified server address might be incorrect.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux Recovery Agent engine log file for more information. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0050E Failed to set SSH user name.

Explanation

The Recovery Agent cannot access the Windows Recovery Agent CLI (TDPVMWareShell) using the defined 'SSH login' user.

System action

The operation is canceled.

User response

Using Secure Shell verify that you can connect to the Windows Recovery Agent CLI machine using the user defined under 'Settings'>'SSH login'.

FBP0051E Failed to run SSH command.

Explanation

None.

FBP0052E Failed to send query to the TDPVMware Shell.

Explanation

None.

FBP0053E Failed to send query to the Recovery Agent CLI.

Explanation

While using SSH, the Recovery Agent failed to send an input command file to the Windows Recovery Agent CLI (TDPVMWare Shell). This issue might be caused by an SSH user without read and write privileges on the Windows Recovery Agent CLI machine.

System action

The operation is canceled.

User response

Verify that the SSH user defined under 'Settings'>'SSH login' has read and write privileges on the Windows Recovery Agent CLI machine. Also check the Linux Recovery Agent engine log file for more information. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0056E Failed to locate the block device specified for the mount point.

Explanation

The Recovery Agent failed to locate the block device for the mount point that was specified for the instant restore operation.

System action

The instant restore operation is canceled.

User response

Verify that the mount point specified for the instant restore operation is correct.

FBP0057E Failed to locate the mount point for the specified block device.

Explanation

The Recovery Agent failed to locate the mount point for the specified instant restore block device.

System action

The instant restore operation is canceled.

User response

Verify that the specified block device for the instant restore operation is correct and mounted.

FBP0058E The specified mount point is not mounted on the block device.

Explanation

The specified mount point is not mounted on the specified block device.

System action

The instant restore operation is canceled.

User response

Verify that the specified mount point and block device are correct, and that the mount point is mounted on that block device.

FBP0059E Restore is not allowed to '/' or '/boot'.

Explanation

The Recovery Agent does not support instant restore operations to target devices that are '/' or '/boot' volumes.

System action

The instant restore operation is canceled.

User response

Specify a different target device for the instant restore operation.

FBP0060E Restore is not allowed to RAID devices.

Explanation

The Recovery Agent does not support instant restore operations to RAID devices.

System action

The instant restore operation is canceled.

User response

Specify a different target device for the instant restore operation.

FBP0061E The restore operation failed to start.

Explanation

The Recovery Agent failed to start the instant restore operation.

System action

The instant restore operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux Recovery Agent engine log file for more information. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0062E Failed to get the iSCSI initiator name.

Explanation

No iSCSI initiator was specified.

System action

The operation is canceled.

User response

Verify that the iSCSI initiator name is specified correctly.

FBP0063E iSCSI target is not logged in.

Explanation

None.

FBP0064E Failed to resolve the IP address to a hostname.

Explanation

The Recovery Agent failed to associate a hostname with the specified IP address.

System action

The operation is canceled.

User response

Verify that the IP or hostname are correct. Then, try the operation again. If the problem persists, check the Linux Recovery Agent engine log file for more information. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0065E The iSCSI service was not found.

Explanation

The iSCSI daemon is not installed on the Recovery Agent Linux machine.

System action

The operation is canceled.

User response

Install the required iSCSI daemon on the Recovery Agent Linux machine. See information about related iSCSI tasks in the product documentation.

FBP0066E Failed to start the iSCSI daemon.

Explanation

The Recovery Agent was unable to start the iSCSI daemon.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0067E Failed to discover iSCSI targets.

Explanation

The Recovery Agent was unable to discover the iSCSI targets.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0068E Failed to log in to the iSCSI target.

Explanation

The Recovery Agent was unable to log in to the iSCSI target.

System action

The operation is canceled.

User response

Check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0069E Failed to log out of the iSCSI target.

Explanation

The Recovery Agent was unable to log out of the iSCSI target.

System action

The operation is canceled.

User response

Check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0070E Failed to delete the iSCSI target.

Explanation

The Recovery Agent was unable to delete the iSCSI target.

System action

The operation is canceled.

User response

Check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0071E Failed to identify the block device for the iSCSI target.

Explanation

The Recovery Agent successfully logged in to the iSCSI target; however, the iSCSI block device was not found.

System action

The operation is canceled.

User response

Check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0072E Failed to create the RAID mirror device.

Explanation

The Recovery Agent was unable to create the RAID mirror device using the mdadm utility.

System action

The instant restore operation is canceled.

User response

Check the Linux system log (usually located at /var/log/messages) for any errors related to this issue.

FBP0073E Failed to stop the RAID mirror device.

Explanation

The Recovery Agent uses the mdadm utility to stop the RAID mirror device. However, the Recovery Agent was unable to stop the RAID mirror device.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent engine log file on the Linux machine for more details about why the device did not stop. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf. Also check the Linux system log (usually located at /var/log/messages).

FBP0074E Failed to add the target block device to the RAID mirror.

Explanation

The Recovery Agent uses the mdadm utility to add the target block device to the RAID mirror. However, the Recovery Agent was unable to add the target block device to the RAID mirror.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent engine log file on the Linux machine for more details about why the device was unable to add the target block device to the RAID mirror. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf. Also check the Linux system log (usually located at /var/log/messages).

FBP0075E Failed to mark the target block device in RAID mirror as faulty.

Explanation

The Recovery Agent uses the mdadm utility to mark the target block device in the RAID mirror. However, the Recovery Agent was unable to mark the target block device as faulty.

System action

The instant restore session is paused.

User response

Check the Recovery Agent engine log file on the Linux machine for more details about why the device was not marked. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf. Also check the Linux system log (usually located at /var/log/messages).

FBP0076E Failed to remove the target block device from the RAID mirror.

Explanation

The Recovery Agent uses the mdadm utility to remove the target block device from the RAID mirror. However, the Recovery Agent was unable to remove the target block device.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent engine log file on the Linux machine for more details about why the device was not removed. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf. Also check the Linux system log (usually located at /var/log/messages).

FBP0079E Unknown key.

Explanation

None.

FBP0080E The operation timed-out.

Explanation

The Recovery Agent engine scripts did not reply to the Recovery Agent GUI in a timely manner.

System action

The operation is canceled.

User response

Try the operation again. If the problem persists, check the Recovery Agent engine log file on the Linux machine. This file is usually located at /opt/tivoli/tsm/TDPVMWare/mount/engine/var/TSM4VE_IR_LOG_0040.sf.

FBP0081E Internal error.

Explanation

None.

FBP0083E The snapshot does not contain a partition with a supported file system.

Explanation

The Recovery Agent successfully parsed the partition structure of the disk. However, the partitions do not use any of these supported file systems: FAT, NTFS, EXT2, EXT3, EXT4, or ReiserFS. As a result, volume-level operations, such as 'Instant Restore' and 'Mount as Virtual Volume', are not supported for this snapshot.

System action

The operation is canceled.

User response

To restore data from the selected snapshot, use the Windows Recovery Agent proxy host to mount and expose the snapshot. See information about mounting as iSCSI targets in the product documentation.

FBP0084E Failed to retrieve partitions.

Explanation

The Windows Recovery Agent proxy host was unable to retrieve the partition list from the disk snapshot.

System action

The operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs about why the partition list was not retrieved.

FBP0085E Recovery Agent can connect only to a Tivoli Storage Manager server node.

Explanation

None.

FBP0086E Failed to remove the Tivoli Storage Manager server connection.

Explanation

The Windows Recovery Agent proxy host reported that there are active instant restore sessions or mounted volumes that require the connection to the Tivoli Storage Manager server. As a result, the existing connection cannot be removed.

System action

The remove connection operation is canceled.

User response

Check the Windows Recovery Agent proxy host logs about the active instant restore sessions or mounted volumes.

FBP0088E Mount operation failed because the Write cache is either full or configured incorrectly.

Explanation

Mount and instant restore sessions (that run on the Linux machine) access the Virtual Volume write cache on the Windows Recovery Agent proxy host . This proxy host reported that the write cache is unavailable.

System action

The operation is canceled.

User response

Check the log files on the Windows Recovery Agent proxy host for information about why the write cache is unavailable. Verify that the Virtual Volume write cache is configured correctly in the Windows Recovery Agent GUI. See information about setting the Virtual Volume write cache options in the product documentation.

FBP0089E The Recovery Agent GUI storage type option is 'Tape', and the requested media is busy.

Explanation

When the Recovery Agent GUI storage type option specifies 'Tape', only a single snapshot can be mounted.

System action

The operation is canceled.

User response

Dismount the currently mounted snapshot before you attempt to mount another snapshot.

FBP0090E Operation timed-out. Manual intervention might be required.

Explanation

The Linux Recovery Agent GUI operation timed-out during a mount or instant restore operation.

System action

The operation is canceled.

User response

Follow the "Responding to a timeout during a file restore or an instant restore (Linux)" procedure documented in the Data Protection for VMware Installation and User's Guide.

FBP0091E The selected disk is not an MBR disk.

Explanation

The Recovery Agent cannot parse the partition structure of the disk, because the disk is not a Basic, MBR-based disk. Volume-level operations, such as 'Instant Restore' and 'Mount as Virtual Volume', are not supported for this snapshot.

System action

Mount and instant restore operations are disabled.

User response

To restore data from the selected snapshot, use the Windows Recovery Agent proxy host to mount and expose the snapshot using 'Mount as iSCSI target' method.

FBP0092E Operation failed. Recovery Agent is initializing.

Explanation

Mount and instant restore operations cannot proceed when the Windows Recovery Agent proxy host is initializing.

System action

The mount or instant restore operation is canceled.

User response

Wait until the Windows Recovery Agent proxy host completes initializing. Then, try the operation again.

FBP0093E The mount point is already in use by another mount session.

Explanation

The mount operation failed because the target mount point is currently in use.

System action

The mount operation is canceled.

User response

Specify a target mount point that is not in use.

FBP0094E The mount point is already in use by another instant restore session.

Explanation

The instant restore operation failed because the target mount point is currently in use.

System action

The instant restore operation is canceled.

User response

Specify a target mount point that is not in use.

FBP1001I The folder:folder pathdoes not exist. Do you want to create the folder?

Explanation

The selected folder does not exist. You can create the folder by proceeding with the instructions displayed on the screen.

System action

The system waits for a user response.

User response

Specify Yes to create the folder and continue with the operation. Specify No to not create the folder and end the current operation.

FBP1003I Specify a folder for the cache files

Explanation

A folder that is used to store the virtual disk and virtual volume cache files was not specified. The cache is used to store write operations to the virtual disk and virtual volume during the mount operation.

System action

The system waits for a user response.

User response

Specify a folder to store the virtual disk and virtual volume cache files.

FBP1005I mount path already has a mounted virtual volume. Do you want to dismount the volume before you continue?

Explanation

The selected path already has a mounted virtual volume. This existing mounted virtual volume must be dismounted to continue with the current mount operation.

System action

The system waits for a user response.

User response

Specify Yes to dismount the existing mounted virtual volume and continue with the current mount operation. Specify No to end the current mount operation.

FBP1009I Recovery Agent cannot be closed while mounted volumes exist. Do you want to dismount all volumes?

Explanation

Existing mounted virtual volumes and virtual disks must be dismounted before closing the Recovery Agent application.

System action

The system waits for a user response.

User response

Specify Yes to dismount all the existing mounted virtual volumes and virtual disks and close the Recovery Agent application. Specify No to not dismount all the existing mounted virtual volumes and virtual disks and return to the Recovery Agent application.

FBP1008I Recovery Agent cannot be started because it is being used by another user

Explanation

The Recovery Agent application is already running on this machine. For example, this situation occurs when the application is started by another user on another session.

System action

The operation is canceled.

User response

Log in to the machine as the user that started the Recovery Agent application.

FBP1011I The Virtual Volume Driver was registered successfully

Explanation

Successful Recovery Agent Virtual Volume Driver registration is required to use the mount function.

System action

Operation completed successfully.

User response

The Recovery Agent application is ready for operations.

FBP1013I Connection to Tivoli Storage Manager server resumed.

Explanation

Communication between the Recovery Agent application and the Tivoli Storage Manager server is established.

System action

Operation completed successfully.

User response

The Recovery Agent application is ready for operations.

FBP1014I You must restart the Recovery Agent application for changes to the Data Access options to take effect.

Explanation

Recent changes to the Data Access options cannot be implemented until the Recovery Agent application is restarted.

System action

The Recovery Agent application operates with the existing Data Access options setting until it is restarted.

User response

Restart the Recovery Agent application so that changes to the Data Access options are implemented.

FBP1100I Received CONTINUE from service manager

Explanation

The Recovery Agent service received a SERVICE_CONTROL_CONTINUE command.

System action

The Recovery Agent service resumes activities.&msgnl;The latest Recovery Agent driver events are written to the Recovery Agent log file.

User response

The Recovery Agent application is ready for operations.

FBP1101I Received PAUSE from service manager

Explanation

The Recovery Agent service received a SERVICE_CONTROL_PAUSE command.

System action

This command has no effect on the Recovery Agent service.

User response

The Recovery Agent application is ready for operations.

FBP1102I Received a STOP command from the service manager

Explanation

The Recovery Agent service received a SERVICE_CONTROL_STOP command. This message is issued when the service is stopped from the service manager. Opening the Recovery Agent GUI from the Start menu sends a stop command to the service.

System action

The Recovery Agent service stops.

User response

The Recovery Agent application is ready for operations.

FBP1103I Service stopped, reporting to service manager

Explanation

The Recovery Agent service stops. The service can be restarted from the service manager.

System action

The Recovery Agent application stops.

User response

No user action required.

FBP1104I --- Recovery Agent version string started ---

Explanation

The Recovery Agent application started. The version string is printed in the message.

System action

Operation completed successfully.

User response

The Recovery Agent application is ready for operations.

FBP1300I License is OK.

Explanation

The license file is valid.

System action

Operation completed successfully.

User response

The Recovery Agent application is ready for operations.

FBP1301W Not for resale license.

Explanation

The license file is valid.

System action

Operation completed successfully.

User response

The Recovery Agent application is ready for operations.

FBP1302E Error accessing license file.

Explanation

The license file could not be accessed. This situation occurs when the license file cannot be located, it cannot be opened because of permission restrictions, or the file is corrupted.

System action

The Recovery Agent application stops.

User response

Obtain a new license for the Recovery Agent application.

FBP1303E Corrupted license file.

Explanation

The license registration string is not valid.

System action

The Recovery Agent application stops.

User response

Obtain a new license for the Recovery Agent application.

FBP1304E Trial period has expired.

Explanation

The license registration string is not valid.

System action

The Recovery Agent application stops.

User response

Obtain a new license for the Recovery Agent application.

FBP1305I Try and buy license. days left.

Explanation

The license file is valid.

System action

Operation completed successfully.

User response

The Recovery Agent application is ready for operations.

FBP5003W target volume : The repository is not loaded.Load the repository and resume the session.

Explanation

The instant restore session is unable to resume since the Recovery Agent failed to reestablish connection to the Tivoli Storage Manager server where the backup snapshots are located.The restored volume is inaccessible while the session is paused.

System action

The instant restore session is paused.

User response

Click "Select IBM Storage Protect server" in the Recovery Agent GUI to connect to the Tivoli Storage Manager server and resume the instant restore session.

FBP5005W Windows indicates the destination volume target volume might be a network-mapped drive. If volume target volume again is confirmed as a network-mapped drive, the operation fails. Continue anyway?

Explanation

The Recovery Agent does not support instant restore sessions to a network-mapped drive.

System action

The instant restore session is canceled.

User response

Specify a destination volume that is not on a network-mapped drive.

FBP5007W Read block from the source has failedThe problem might have been caused by a network failure.See log file for more details.If the problem was caused by a network failure,correct the problem and resume the session.

Explanation

The instant restore session is unable to retrieve data from the Tivoli Storage Manager server. As a result, the instant restore session is paused.The problem might be caused by a network failure. The restored volume is inaccessble while the session is paused.

System action

The instant restore session is paused.

User response

Check the Recovery Agent logs for information regarding the cause of the problem. After resolving the issue, resume the session.

FBP5008W There are open handles to the volume being restored (volume name).Close any application (such as Windows Explorer or a command prompt) that might be accessing this volume and try again.If you select Ignore, applications using these handles might become unstable once the restore process begins.

Explanation

The target volume for the restore is in use.Restoring a volume to a viewable storage volume involves overwriting data on that existing storage volume. After the restore begins, the current volume contents are permanently erased.

System action

The system waits for a user response.

User response

Close any application (such as Windows Explorer or a command prompt) that might be accessing this volume and try the operation again.If you select Ignore, applications that currently use these open handles might become unstable when the restore operation begins.

FBP5010W System is low on memory.Write operations to virtual volumes might be lost.

Explanation

Changes that are done on mounted volumes are written to memory. As a result, the Recovery Agent can use a large amount of RAM when it operates in read/write mode.

System action

Write operations to virtual volumes might be lost.

User response

Dismount some of the mounted volumes (when possible) or mount the volumes as read-only.The value of the 'Read Ahead cache size' option affects the memory usage. See information about setting this option in the product documentation.

FBP5011W Recovery Agent still has number of mounted volumes volumes mounted. Stopping the Recovery Agent might cause the system to become unstable. Are you sure you want to stop the Recovery Agent?

Explanation

Stopping the Recovery Agent without first dismounting the virtual volumes might cause both the system and active applications to become unstable.

System action

The system waits for a user response.

User response

Specify No to prevent the Recovery Agent from stopping, then dismount any mounted volumes.Specify Yes to stop the Recovery Agent, even though both the system and active applications might become unstable.

FBP5012W The Recovery Agent still has number of active sessions active instant restore session. These sessions will be paused and the restored volumes will appear unformatted, until the Recovery Agent service restarts.Are you sure you want to stop the Recovery Agent?

Explanation

Stopping the Recovery Agent without waiting for the restore to complete makes the restored volumes display as if they are unformatted. The restore process resumes when the Recovery Agent service restarts.

System action

The system waits for a user response.

User response

Specify No to prevent the Recovery Agent from stopping and to continue the instant restore session.Specify Yes to stop the Recovery Agent, even though the volumes that are still being processed display as if they are unformatted.Do not attempt to format these volumes as such an attempt causes data loss.

FBP5013W Abort selected sessions?All data is lost and volumes require reformatting.

Explanation

Aborting the instant restore sessions causes the loss of all data that was written to the restored volumes.The restored volumes display as unformatted and require reformatting.

System action

The system waits for a user response.

User response

Specify Yes to abort the instant restore sessions. All data that was written to the restored volumes during these sessions is lost.Specify No to continue the instant restore sessions.

FBP5015W All data on target drive volume name will be lost. Note 1: Successful instant restore processing requires sufficient network connectivity and bandwidth to the repository. Note 2: Use of instant restore is recommended only for applications that primarily issue READ I/O's.Do you want to continue?

Explanation

Instant restore processing overwrites data on the target storage volume.A sufficient data transfer rate from the Tivoli Storage Manager server is required for a successful instant restore operation.

System action

The system waits for a user response.

User response

Click YES to confirm that you understand the effects and to start the instant restore operation.

FBP5017W There are open files on the volume mounted on:mounted volume name.A forced dismount invalidates all of the open files.Are you sure you want to continue?

Explanation

The virtual volume that is being dismounted is in use by another application. For example, the volume might be open in Windows Explorer. For virtual iSCSI devices, the iSCSI initiator is still logged on to the device.Forcing this volume to dismount might cause the files or applications that are accessing the volume to become unstable.

System action

The system waits for a user response.

User response

Identify and close any files or applications that are accessing the volume. Or, specify 'Continue' to ignore the warning message and continue dismounting the volume.For iSCSI devices, make sure that the iSCSI initiator is logged off the device.

FBP5018W The volume selected for restore is located on a clustered disk.See the product documentation for guidelines when restoring clustered volumes.Failure to follow these guidelines might result in data loss, if a hardware or Windows error occurs.Do you want to continue?

Explanation

Instant restore of a volume in a clustered environment is supported.Other volumes in the cluster are not affected. You can work with the cluster and with the restored volume in parallel.During the instant restore operation, the disk that is being restored cannot fail over if the node fails.

System action

The system waits for a user response.

User response

Specify YES to confirm that you understand the guidelines and to start the instant restore operation.

FBP5020W The Virtual Volume Driver is not yet registered. Recovery Agent can register the driver now. During registration, a Microsoft Windows Logo warning may be displayed. Accept this warning to allow the registration to complete.Do you want to register the Virtual Volume Driver now?

Explanation

User should register the Virtual Volume Driver in order to work with the Recovery Agent.This message is displayed following the first attempt to mount after a silence install, since the driver registration is not performed in silent install.

System action

The system waits for a user response.

User response

Specifying Yes will start the registration process. After registration the Recovery Agent application is ready for operations.

FBP5021W The mounted volume 'mounted volume name' is in use.Dismounting the volume might cause the application that is using it to become unstable.Do you want to continue?

Explanation

The virtual volume that is being dismounted is in use by another application. For example, the volume might be open in Windows Explorer. For virtual iSCSI devices, the iSCSI initiator is still logged on to the device.

System action

The system waits for a user response.

User response

Identify and close any applications that are accessing the volume. Or, specify 'Continue' to ignore the warning message and continue dismounting the volume.For iSCSI devices, make sure that the iSCSI initiator is logged off the device.

FBP5023W There are active instant restore sessions.These sessions will be paused and the restored volumes will appear unformatted, until the application finishes loading and resumes the sessions.Do you want to continue?

Explanation

Opening the Recovery Agent UI from the 'Start>All Programs' menu stops the service.The active instant restore sessions are paused until the application finishes loading and resumes the sessions.

System action

The system waits for a user response.

User response

Specify Yes to stop the service and load the Recovery Agent UI. This action pauses and then resumes the instant restore sessions.Specify No to not load the Recovery Agent UI. This action leaves the instant restore sessions to run in the background in service mode.

FBP5025W There are 'num active sessions' sessions using the write cache. Updates to the cache settings are processed when there are no active sessions that use the cache. Do you want to continue?

Explanation

Updates to the write cache settings were detected. These updates are applied when there are no active sessions that use the cache.

System action

The Recovery Agent application operates with the existing write cache settings.

User response

Update the write cache settings when there are no active sessions that use the cache.

FBP5026W The size of the write cache is num write cache percentage% full.

Explanation

Mount and instant restore sessions that run on a Linux machine use the Recovery Agent Virtual Volume write cache for write operations. The Cache size is approaching its maximum limit.Linux mount and instant restore sessions might fail when the cache size reaches its limit.

System action

None.

User response

Do not start a new Recovery Agent mount or instant restore session on the Linux machine until the Virtual Volume write 'Cache size' value decreases.See information about setting this option in the product documentation.

FBP5028W The file system of the selected partition (partition format) might not be supported by the current operating system.The appropriate File System driver must be installed for Windows to read the volume.Do you want to continue?

Explanation

The partition file system must be supported and recognized by the Windows operating system where the volume is mounted. This condition is required to view the file structure of the mounted partition..It is recommended to mount volumes with native Linux file systems on a Linux machine.

System action

The system waits for a user response.

User response

Make sure the appropriate file system driver is installed on the Windows operating system where the volume is mounted.

FBP5029W The connection to Tivoli Storage Manager server was lost.

Explanation

The connection between the Recovery Agent application and the Tivoli Storage Manager server was lost.

System action

Mounted volumes might become inaccessible. The instant restore sessions are paused.

User response

Check the Recovery Agent logs for information regarding the connection failure. After resolving the issue, resume any paused instant restore sessions.

FBP5030W No snapshots are available for the selected virtual machine. Or, the Authentication node is not authorized to restore this virtual machine.

Explanation

No snapshots were located for the selected virtual machine.Either no snapshot completed successfully, or if the 'From node' access method was used, the Authenticate node does not have permission to restore the selected virtual machine.

System action

The operation is canceled.

User response

If the 'From node' access method is used, make sure sufficient permissions are set for the Authetication node.See the product documentation for details and an example of how to set permissions by using the IBM Storage Protect Data Mover 'set access' command.

FBP5031W Some snapshots are currently mounted. If you continue, these snapshots will be dismounted. If a mounted volume is currently being used by an application, the application might become unstable.Do you want to continue?

Explanation

Opening the Recovery Agent UI from the 'Start>All Programs' menu stops the service. The active mounted volumes are dismounted.

System action

The system waits for a user response.

User response

Close any application (such as Windows Explorer or a command prompt) that might be accessing the mounted volumes. Then, open the Recovery Agent UI. If you continue without closing the applications that are accessing the mounted volumes, these applications might become unstable.

FBP5032W The selected snapshot will not be protected from expiration during this operation. See the product documentation for information about expiration.

Explanation

When the 'From node' authentication method is used, the Authentication node is granted Read-only access to the target node with the 'set access' command. The target node owns the snapshot. As a result, the snapshot cannot be marked as being in use on the server. Therefore, the snapshot might expire while the restore operation is in progress.

System action

The system waits for a user response.

User response

If you proceed, disable the expiration process for the snapshot during the operation. Or, make sure that no snapshots are created for the restored machine during the restore operation. Otherwise, cancel the restore operation.

FBP5033W No snapshots exist in the selected node.

Explanation

Either no snapshot was completed, or the selected Tivoli Storage Manager node is not the node that owns the snapshots.

System action

No snapshot is shown.

User response

If Tivoli Storage Manager for Virtual Environments snapshots were completed, select the Tivoli Storage Manager node that owns the snapshots.

FBP5034W The snapshots are not protected from expiration during the mount operation. An expiration can produce unexpected results and negatively impact the mount point.

Explanation

The mounted snapshots will not be marked as being in use on the server. Therefore, the snapshots might expire while the restore operation is in progress.

System action

The system waits for a user response.

User response

If you proceed, make sure that no snapshots are created for the restored machines during the restore operations. Otherwise, enable the expiration protection.

FBP5035W The selected snapshot is not protected from expiration during this mount operation. An expiration can produce unexpected results and negatively impact the mount point.

Explanation

The mounted snapshot will not be marked as being in use on the server. Therefore, the snapshot might expire while the restore operation is in progress.

System action

The system waits for a user response.

User response

If you proceed, make sure that no snapshots are created for the restored machine during the restore operation. Otherwise, enable the expiration protection on the 'settings' panel and perform the operation again.

FBP7003E The folder:folder name is invalid.

Explanation

The specified path is not a valid folder path.

System action

The system waits for a user response.

User response

Specify a valid folder path.

FBP7004E The folder:folder name could not be created.

Explanation

The system failed to create the requested folder.

System action

The operation is canceled.

User response

Check the Recovery Agent logs for information about why the folder was not created.

FBP7005E folder name is not empty. Only empty folders can be used as a mount point.

Explanation

The system can mount a volume snapshot only to an empty folder.

System action

The operation is canceled.

User response

Specify an empty folder path.

FBP7006E snapshot size (snapshot size) is larger than target size (partition name)

Explanation

The volume size of the destination location must be equal to, or greater than, the size of the original volume on the snapshot to be restored.

System action

The instant restore operation is canceled.

User response

Specify a target volume with a size equal to, or greater than, the source volume on the snapshot to be restored.

FBP7007E A valid iSCSI target name must be specified. Valid iSCSI names consist of the following items: lower-case English characters, digits, '.', ':' and '-'.

Explanation

When a snapshot is exposed as an iSCSI target, a valid iSCSI target name must be entered.

System action

The system waits for a user response.

User response

Specify a valid iSCSI target name.

FBP7008E A valid iSCSI initiator name must be specified. Valid iSCSI names consist of the following items: lower-case English characters, digits, '.', ':' and '-'.

Explanation

The specified iSCSI initiator is not a valid initiator name. When a snapshot is exposed as an iSCSI target, a valid initiator name must be specified by the user.

System action

The system waits for a user response.

User response

Specify a valid iSCSI initiator name.

FBP7009E A valid folder name must be specified.

Explanation

The path to the folder is invalid or was not specified. The path to the mount point for the volume snapshot must include an empty folder.

System action

The system waits for a user response.

User response

Specify a valid path to an empty folder.

FBP7012E Already connected to a Tivoli Storage Manager server. To connect to a different server, or to a different node within the server, select the current server from the list and click 'Remove'.

Explanation

Recovery Agent can connect only to a single Tivoli Storage Manager server and node.

System action

The operation is canceled.

User response

Remove the existing connection by selecting the server from the list and click 'Remove'. You cannot remove a connection to a server that has active mounted volumes or instant restore sessions.

FBP7013E Instant restore is not supported in Tape Mode.

Explanation

Instant restore of snapshot data that is stored on tape is not supported.

System action

The operation is canceled.

User response

Either migrate the snapshot data to a disk storage pool, or use a different restore method.

FBP7014E Cannot mount more than one snapshot in Tape Mode.

Explanation

Only a single snapshot can be mounted when the snapshot data is stored on a tape.

System action

The operation is canceled.

User response

Dismount the currently mounted snapshot before you attempt to mount another snapshot.

FBP7015E No local volume is available as a destination for instant restore.

Explanation

Instant restore is done to a local volume that has a volume letter and is not the system volume.

System action

The operation is canceled.

User response

Make sure you have a local volume that has a volume letter and that is not the system volume as a destination for the instant restore.

FBP7016E The Recovery Agent 'Read Ahead size' option requires a value of 0 through 8192.

Explanation

The Recovery Agent 'Read Ahead size' value specifies the number of extra data blocks retrieved from the storage device after a read request is sent to a single block.

System action

The system waits for a user response.

User response

Specify a valid 'Read Ahead size' value of 0 through 8192. See information about setting this option in the product documentation.

FBP7017E The Recovery Agent 'Read Ahead cache size' option requires a value of 1000 through 75000. The value must also be at least 1 block larger than the value of the 'Read Ahead size' option.

Explanation

Recovery Agent 'Read Ahead cache size' value specifies the size of the cache where the 'Read Ahead' extra data blocks are stored.

System action

The system waits for a user response.

User response

Specify a valid 'Read Ahead cache size' value of 1000 through 75000 and at least 1 block larger than the value of the 'Read Ahead size' option. See information about setting this option in the product documentation.

FBP7018E The Recovery Agent cannot read the snapshot data from the Tivoli Storage Manager server. Make sure that the storage type setting matches the actual storage device. For example, if the data resides on tape, make sure that the storage type is set to 'Tape'. If this does not solve the problem, check the Tivoli Storage Manager server activity log for additional errors.

Explanation

The required data does not exist on the server or the data is inaccessible. Inaccessible data is typically caused by a 'Storage type' configuration that does not match the actual storage where the data is stored. Recovery Agent cannot read data stored on Tape or VTL if storage type is set to 'Disk'.

System action

The operation is canceled.

User response

Click 'Settings' in the Recovery Agent GUI and select the correct storage device from which to mount the snapshot. You can select 'Disk/File', 'Tape', or 'VTL'. When the storage type is changed, you must restart the Recovery Agent for the changes to take effect. Also, check the Recovery Agent logs and the Tivoli Storage Manager server activity log for any additional errors.

FBP7019E The selected disk is not a basic disk with an MBR partition style.

Explanation

Recovery Agent could not parse the partition structure of the disk, because the disk is not a Basic, MBR-based disk. Volume-level operations, such as 'Instant Restore' and 'Mount as Virtual Volume', are not supported for this snapshot.

System action

Volume-level operations are disabled.

User response

Use other methods, such as 'Mount as iSCSI target', to restore data from the selected snapshot.

FBP7020E The partitions in the selected disk are not formatted with a supported file system.

Explanation

Recovery Agent successfully parsed the partition structure of the disk. However, none of the partitions use these supported file systems: FAT, NTFS, EXT2, EXT3, EXT4, or ReiserFS. As a result, volume-level operations, such as 'Instant Restore' and 'Mount as Virtual Volume', are not supported for this snapshot.

System action

Volume-level operations are disabled.

User response

Use other methods, such as 'Mount as iSCSI target', to restore data from the selected snapshot.

FBP7021E Select the node access method.

Explanation

Three node authentication methods are available to access snapshots on the Tivoli Storage Manager server: 'Asnodename' authenticates with a proxy node, 'Fromnode' authenticates with a node that contains limited access, and 'Direct' authenticates directly.

System action

The system waits for a user response.

User response

Specify the node authentication method to access the snapshots on the Tivoli Storage Manager Server. See information about these three methods in the product documentation.

FBP7022E You must specify a Tivoli Storage Manager server name or IP.

Explanation

Recovery Agent requires this information to access the virtual machines backup snapshots on the Tivoli Storage Manager Server.

System action

The system waits for a user response.

User response

Specify the host name or IP address of the Tivoli Storage Manager Server where the backup snapshots are located.

FBP7023E You must specify a valid Tivoli Storage Manager Server port.

Explanation

Recovery Agent requires this information to access the virtual machines backup snapshots on the Tivoli Storage Manager Server.

System action

The system waits for a user response.

User response

Specify the port number that is used by the Tivoli Storage Manager Server where the backup snapshots are located.

FBP7024E You must specify an authentication node.

Explanation

No authentication node was specified. Specify the Tivoli Storage Manager node that owns the snapshots.

System action

The system waits for a user response.

User response

Specify the Tivoli Storage Manager node that owns the snapshots. See information about the node authentication methods in the product documentation.

FBP7025E You must specify a target node.

Explanation

Recovery Agent provides three node authentication methods. When 'Fromnode' or 'Asnodename' are selected, a target node must be specified. The target node is the Tivoli Storage Manager node where the virtual machine backups are located.

System action

The system waits for a user response.

User response

Specify the target node where the virtual machine backups are located. See information about the node authentication methods in the product documentation.

FBP7026E You must specify a node password.

Explanation

No password was specified for the authentication node.

System action

The system waits for a user response.

User response

Enter the password of the Tivoli Storage Manager node that owns the virtual machine snapshots.

FBP7027E The Recovery Agent 'Driver timeout' option requires a value of 60 through 300.

Explanation

The Recovery Agent 'Driver timeout' option specifies the amount of time (in seconds) to process data requests from the file system driver. When processing does not complete within the specified time, the request is canceled and an error is returned to the file system driver.

System action

The system waits for a user response.

User response

Specify a valid 'Driver timeout' value of 60 through 300. See information about setting this option in the product documentation.

FBP7028E The Recovery Agent 'Write cache size' option requires a value of 1 through upper limit

Explanation

During Linux instant restore and mount operations, the Recovery Agent on the Windows backup proxy host saves data changes in the write cache folder. The maximum cache size is 90% of the available space for the selected folder.

System action

The system waits for a user response.

User response

Specify a valid Virtual Volume write 'Cache size' value. See information about setting this option in the product documentation.

FBP7029E The Recovery Agent CLI mount command is missing one or more required parameters.

Explanation

The Recovery Agent CLI mount command cannot complete without all required parameters.

System action

The operation is canceled.

User response

Issue the 'RecoveryAgentShell.exe -h mount' (Windows) or 'RecoveryAgentShell -h mount dump' (Linux) command to view the required parameters. Then, issue the mount command again with all required parameters.

FBP7030E Repository 'repository name' was not found

Explanation

The Tivoli Storage Manager Server connection specified in the Recovery Agent '-rep' tag was not found.

System action

The operation is canceled.

User response

Correct the Recovery Agent CLI command '-rep' tag to identify the Tivoli Storage Manager Server where the backup snapshots are located.

FBP7031E A valid iSCSI target name must be specified. Valid iSCSI names consist of the following items: lower-case English characters, digits, '.', ':' and '-'.

Explanation

When a snapshot is exposed as an iSCSI target, a valid iSCSI target name must be entered.

System action

The operation is canceled.

User response

Specify a valid iSCSI target name.

FBP7032E Mount target 'mount target' is not valid.

Explanation

The specified mount path is not a valid folder path.

System action

The operation is canceled.

User response

Specify a valid folder path.

FBP7033E Reparse point 'reparse point' was not found and cannot be created

Explanation

The specified mount target path was not found and cannot be created.

System action

The operation is canceled.

User response

Specify a valid folder path.

FBP7035E Failed to load partition 'partition'

Explanation

The Recovery Agent was unable to retrieve the partition list from the disk snapshot.

System action

The operation is canceled.

User response

Check the Recovery Agent logs for information about why the partition list was not retrieved.

FBP7036E Incorrect partition number 'partition number'

Explanation

The specified partition was not found on the disk snapshot.

System action

The operation is canceled.

User response

Specify a valid partition number.

FBP7037E 'Cache size' must be at least 1GB.

Explanation

Mount and instant restore sessions that run on a Linux machine use the Recovery Agent Cache for write operations.

System action

The system waits for a user response.

User response

Specify a valid size for the 'Write Cache' size field. 'Cache size' must be at least 1GB.

FBP7038E The value of the Recovery Agent write 'Cache size' option must not exceed max size in GBGB

Explanation

During Linux instant restore and mount operations, the Recovery Agent on the Windows backup proxy host saves data changes in the write cache folder. The maximum cache size is 90% of the available space for the selected folder.

System action

Linux mount and instant restore sessions might fail when the cache size reaches its limit.

User response

Do not start a new Recovery Agent mount or instant restore session on the Linux machine until the Virtual Volume write 'Cache size' value decreases. See information about setting this option in the product documentation.

FBP8001E resume failed

Explanation

The instant restore session is unable to resume. As a result, the instant restore session pauses. The restored volume is inaccessible while the session is paused.

System action

The instant restore session pauses.

User response

Check the Recovery Agent logs for information about why the resume failed. After the issue is resolved, resume the session.

FBP8002E failed to mount because of too many mount points

Explanation

The Recovery Agent supports a maximum of 128 simultaneously mounted snapshots. That maximum was exceeded.

System action

The mounting operation is canceled.

User response

Dismount at least one of the currently mounted snapshots before an attempt to mount another snapshot.

FBP8003E failed to dismount mounted volume name

Explanation

The Recovery Agent failed to dismount the mounted snapshot. This issue might be caused by a disconnection from the Tivoli Storage Manager server that owns the snapshots.

System action

The dismount operation is canceled.

User response

Check the Recovery Agent logs for information about why the dismount operation failed.

FBP8004E failed to load repository name

Explanation

The Recovery Agent failed to expose the snapshots of the specified Tivoli Storage Manager server.

System action

The operation is canceled.

User response

Verify that the correct Tivoli Storage Manager server and node that own the snapshots are specified.

FBP8007E Virtual Volume Driver not enabled

Explanation

Mount operations require a working Recovery Agent Virtual Volume Driver.

System action

The mount operations are canceled.

User response

Check the Recovery Agent logs for information about why the Virtual Volume Driver is not enabled.

FBP8008E snapshot not found.

Explanation

The selected snapshot was not found on the Tivoli Storage Manager server.

System action

The operation is canceled.

User response

Click Refresh in the Recovery Agent GUI to load the current snapshots on the Tivoli Storage Manager server.

FBP8009E already mounted

Explanation

The selected snapshot was already mounted to the requested target.

System action

None.

User response

The mounted snapshot is available for use.

FBP8012E target is a network-mapped drive

Explanation

Mounting snapshots to a network-mapped drive is not supported.

System action

The mount operation is canceled.

User response

Specify a target drive that is not on a network-mapped drive.

FBP8015E volume letter is in use. Select another

Explanation

The selected drive letter for the mount operation is in use.

System action

The mount operation is canceled.

User response

Select a target drive letter that is not in use.

FBP8016E failed to mount

Explanation

The Recovery Agent failed to complete the mount operation.

System action

The mount operation is canceled.

User response

Check the Recovery Agent logs for information about why the mount operation failed to complete.

FBP8019E failed to stop

Explanation

The current request to abort the selected instant restore session failed because the Recovery Agent could not locate the selected session.

System action

None.

User response

The abort request for the instant restore session was already done.

FBP8020E failed to finalize the session

Explanation

The product encountered an internal error when it attempted to finalize the instant restore session.

System action

The operation is canceled.

User response

Check the Recovery Agent logs for information about why the session did not finalize.

FBP8023E target partition is too small

Explanation

The volume size of the destination location must be equal to, or greater than, the size of the original volume on the snapshot to be restored.

System action

The instant restore operation is canceled.

User response

Specify a target volume with a size equal to, or greater than, the source volume on the snapshot to be restored.

FBP8024E load repository repository name failed: error message

Explanation

The Recovery Agent failed to expose the snapshots of the specified Tivoli Storage Manger server.

System action

The operation is canceled.

User response

Verify that the correct Tivoli Storage Manager server and Node that own the snapshots are specified.

FBP8025E repository inaccessible. Dismounting volume

Explanation

The Recovery Agent is unable to retrieve data from the Tivoli Storage Manager server. As a result, the currently mounted snapshots are dismounted.

System action

Mounted snapshots are dismounted.

User response

Check the Recovery Agent logs for information about why the repository is inaccessible.

FBP8026E 'path to repository' inaccessible or not a repository

Explanation

The Recovery Agent failed to expose the snapshots of the specified Tivoli Storage Manger server.

System action

The operation is canceled.

User response

Verify that the correct Tivoli Storage Manager server and Node that own the snapshots are specified.

FBP8027E failed to open repository

Explanation

The Recovery Agent failed to expose the snapshots of the specified Tivoli Storage Manger server.

System action

The operation is canceled.

User response

Verify that the correct Tivoli Storage Manager server and Node that own the snapshots are specified.

FBP8029E session stopped by user

Explanation

The user requested to abort the instant restore session. Aborting the instant restore sessions causes all data that was written to the restored volume to be lost.

System action

The instant restore session ends.

User response

The restored volume is shown as unformatted and requires reformatting.

FBP8031E Exclusive access to the mounted snapshot was not obtained on the Tivoli Storage Manager server.

Explanation

An exclusive access to the snapshot data on the Tivoli Storage Manager server could not be obtained. As a result, the version being restored could expire, leading to inability to complete the restore. Failure to obtain exclusive access is often the result of the snapshot data residing on a target replication server.

System action

The mount operation is canceled.

User response

If expiration protection is enabled, check the status of the target Tivoli Storage Manager server. If the target server is the replication server in failover mode, or if you verified no snapshots are running on the primary server, disable expiration protection. Then, try the operation again. If expiration protection was disabled when this error occurred, visit the IBM Support Portal for additional information at http://www.ibm.com/support/entry/portal/.

FBP8032E failed to unmount volume

Explanation

The target volume for the restore operation is in use. As a result, the instant restore operation did not start. Restoring a volume to a viewable storage volume involves overwriting data on that existing storage volume. After the restore session begins, the data on the existing volume is permanently erased.

System action

The instant restore session is canceled.

User response

Close any application (such as Windows Explorer or a command prompt) that might be accessing this volume. Then, try the operation again.

FBP8033E failed to restore blocks

Explanation

The instant restore operation is either unable to retrieve data from the Tivoli Storage Manager server or unable to write data to the target volume.

System action

The instant restore session ends.

User response

Check the Recovery Agent logs for information about why the blocks failed to restore. The restored volumes display as unformatted and require reformatting.

FBP8034E failed to mount volume

Explanation

The Recovery Agent failed to mount the target volume and start the instant restore operation.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent logs for information regarding why the target volume could not be mounted.

FBP8036E Failed to finalize

Explanation

The Recovery Agent failed to finalize the instant restore session.

System action

The instant restore session is canceled.

User response

Check the Recovery Agent logs for information about the cause of the problem. The restored volumes might display as unformatted and require reformatting.

FBP8037E initialization failed. See logs for the reason

Explanation

The Recovery Agent failed to initialize the instant restore operation.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent logs for information about the cause of the problem.

FBP8041E cannot restore to a dynamic disk

Explanation

Instant restore to a dynamic volume is not supported.

System action

The instant restore operation is canceled.

User response

Select a basic volume as the instant restore target. Then, try the operation again.

FBP8042E cannot restore to clustered disk

Explanation

Instant restore of a volume in a clustered environment is supported. However, the user canceled the restore to a volume in a clustered environment.

System action

The instant restore operation is canceled.

User response

Select a different volume as the instant restore target. Then, try the operation again.

FBP8043E failed to create bitmap

Explanation

The Recovery Agent failed to create the required internal data structure for the instant restore operation.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent logs for information about why the data structure was not created.

FBP8044E failed to scramble first block

Explanation

The Recovery Agent failed to overwrite the first sector of the disk.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent logs for information about why the overwrite to disk failed.

FBP8045E failed to notify driver

Explanation

The Recovery Agent failed to notify the kernel driver regarding the start of the instant restore session.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent logs for information about why the driver was not notified.

FBP8046E failed to unscramble first block

Explanation

The Recovery Agent failed to overwrite the first sector of the disk.

System action

The instant restore session ends.

User response

Check the Recovery Agent logs for information about why the overwrite to disk failed. The restored volumes might display as unformatted and require reformatting.

FBP8047E cannot restore to a FAT volume. Format target volume as NTFS

Explanation

Instant restore to a volume formatted as an FAT32 file system is not supported.

System action

The instant restore operation is canceled.

User response

Format the volume as an NTFS file system. Then, try the operation again.

FBP8048E session not responding

Explanation

The instant restore session did not respond to the abort request within 5 minutes. As a result, the instant restore session was forcibly stopped.

System action

The instant restore session ends.

User response

Check the Recovery Agent logs for information about why the Recovery Agent did not respond to the abort request. The restored volumes might display as unformatted and require reformatting.

FBP8050E failed to create first block file

Explanation

The Recovery Agent failed to create a memory-mapped file for the instant restore session.

System action

The instant restore operation is canceled.

User response

Check the Recovery Agent logs for information regarding why the memory-mapped file was not created.

FBP8051E cannot restore to disk with signature '0'

Explanation

Instant restore in not supported for disks without an MBR disk signature.

System action

The instant restore operation is canceled.

User response

Select an instant restore target volume on an MBR disk that contains a disk signature.

FBP8052E Recovery Agent is currently initializing.

Explanation

Mount and instant restore operations cannot proceed when the Recovery Agent is initializing.

System action

The mount or instant restore operation is canceled.

User response

Wait until the Recovery Agent completes initializing. Then, try the operation again.

FBP8053E failed to read data from server

Explanation

The Recovery Agent failed to expose the snapshots of the specified Tivoli Storage Manger server.

System action

The operation is canceled.

User response

Verify that the correct Tivoli Storage Manager server and Node that own the snapshots are specified. Check the Recovery Agent logs for more information.

FBP9000E failed connecting to a kernel driver

Explanation

Instant restore operations require a working Recovery Agent kernel driver.

System action

The instant restore operations are canceled.

User response

Check the Recovery Agent logs for information about why the Recovery Agent failed to connect to the driver.

FBP9001E Incompatible Virtual Volume Driver (FBVV) Version , expecting expected major version.expected minor version , installed installed major version.installed minor version

Explanation

The kernel driver version does not match the Recovery Agent version. A valid driver is required for the Recovery Agent to work properly.

System action

The Recovery Agent application closes.

User response

The Recovery Agent was not installed correctly. Follow the Recovery Agent installation instructions in the product documentation.

FBP9002E Cannot initialize Windows Sockets.

Explanation

The Recovery Agent failed to initialize the Windows Sockets DLL file.

System action

The Recovery Agent application closes.

User response

Check the Windows events logs for errors related to this issue. Also check the Recovery Agent logs for information about why the Windows Sockets DLL file failed to initialize.

FBP9003E Cannot obtain the application data directory path

Explanation

The Recovery Agent was unable to retrieve the application data directory path from the operating system.

System action

The Recovery Agent application closes.

User response

Check the Windows events log for errors related to this issue. Also check the Recovery Agent logs for information about why the Recovery Agent was unable to obtain the application data directory path.

FBP9004E Cannot create directory directory name

Explanation

The Recovery Agent failed to create the application data directory.

System action

The Recovery Agent application closes.

User response

Check the Windows events logs for any errors. Check the Recovery Agent logs for information about why the Recovery Agent failed to create the application data directory.

FBP9005E failed to initialize module name module

Explanation

The Recovery Agent failed to initialize.

System action

The Recovery Agent application closes.

User response

Check the Recovery Agent logs for information about why the Recovery Agent failed to initialize.

FBP9006E another instance of Recovery Agent is already running

Explanation

Only one active Recovery Agent instance is supported. This issue is encountered when multiple users are logged on to the system and attempting to run the Recovery Agent.

System action

The Recovery Agent is not started.

User response

Either close the current Recovery Agent instance or run the Recovery Agent on a different system.

FBP9007E unable to install the Recovery Agent

Explanation

The Recovery Agent failed to install. A valid installation is required for the Recovery Agent to function properly.

System action

The Recovery Agent is not started.

User response

Follow the Recovery Agent installation instructions in the product documentation.

FBP9008E Cannot get folder name for AFS.dll

FBP9009E Registration of Virtual Volume Driver failed .Check the file file name\\installFBVV.log for more information Do you want to retry registering the Virtual Volume Driver?

Explanation

The Virtual Volume Driver must be registered correctly in order for the Recovery Agent to function correctly.

System action

The system waits for a user response.

User response

>Check the Recovery Agent logs for information about why the Recovery Agent failed to register the driver. Click 'Retry' to make another attempt to register the driver or click 'Cancel' to end the operation.

FBP9010E Write Cache is full.

Explanation

Mount and instant restore sessions that run on a Linux machine use the Recovery Agent Virtual Volume write cache for write operations. Linux mount and instant restore sessions might fail when the cache size reaches its limit.

System action

Write operations to the Linux instant restore and virtual volumes might be lost.

User response

Unmount some of the mounted volumes on the Linux machine to make available space in the write cache. Instant restore volumes on the Linux machine might display as unformatted. When the cache is full, all data that is written to the Linux instant restore volumes is lost.