Veritas Backup Exec System Recovery 2010 Notification Messages

Problem

Veritas Backup Exec System Recovery 2010 Notification Messages

Solution

1. Error Messages

1.1 High Priority
1.1.1 "An error occurred while starting Backup Exec System Recovery service."
1.1.2 "Not licensed to create file and folder backups."
1.1.3 "Your trial version of Backup Exec System Recovery has expired. To continue system protection, please visit our web site."
1.1.4 "Cannot complete the restore of recovery point: <recovery point filename>."
1.1.5 "Cannot complete the restore of recovery point with multiple volumes."
1.1.6 "Invalid registry settings for GoBack setup.exe."
1.1.7 "Cannot disable GoBack. Setup.exe is not found or returned a failure status."
1.1.8 "Not licensed to copy volume."
1.1.9 "Cannot complete copying of <drive name> drive."
1.1.10 "Cannot create file backup for job: <job name>."
1.1.11 "Cannot create recovery points for job <job name>."
1.1.12 "A recovery operation failed in the Veritas Recovery Environment during the previous reboot."
1.1.13 "Cannot restore the original boot file (boot.ini) after the last recovery operation."
1.1.14 "Not licensed to use command files."
1.1.15 "Not licensed to use compression."
1.1.16 "Not licensed to use encryption."
1.1.17 "Not licensed to create incremental recovery points."
1.1.18 "Not licensed to write to CD/DVD."
1.1.19 "Not licensed to write to network locations."
1.1.20 "<backup event name> is not a supported feature"
1.1.21 "Cannot get the list of supported event monitors."
1.1.22 "Not licensed to index recovery points."
1.1.23 "Cannot complete consolidation of incremental recovery points."
1.1.24 "Cannot successfully reconcile changes since last session."
1.1.25 "There are no valid recovery point locations on this computer."
1.1.26 "Not licensed to convert recovery points to virtual disks."
1.1.27 "The conversion process could not be completed."
1.1.28 "The copy process could not be completed."
1.1.29 "Cannot reboot computer to finish the recovery operation."
1.1.30 "Cannot install license."
1.1.31 "Cannot create a new conversion job."
1.1.32 "File <conversion file name> does not exist."
1.1.33 "This operation cannot be performed while Windows is running."
1.1.34 "Express Recovery Task failed.  Unable to retrieve the time stamp of the latest recovery point."
1.1.35 "Express Recovery Task failed. No recovery points are available for this computer."
1.1.36 "Express Recovery Task failed. Specified drives do not exist on this computer."
1.1.37 "Express Recovery Task failed. One or more recovery points are either unavailable or deleted."
1.1.38 "Conversion Task failed. Convert to Virtual by Computer and Convert to Virtual by Destination Tasks are only supported by Backup Exec System Recovery version 8.5 later versions."
1.1.39 "Conversion Task failed. The specified ESX import path is supported by Backup Exec System Recovery 2010 or later versions."
1.1.40 "Invalid backup destination. A Windows computer cannot perform a backup to a Linux destination."

1.2 Medium Priority
1.2.1 "Cannot update status of <drive name> drive."
1.2.2 "Cannot update the job, <job name>, from a previous version. Please edit the job and reselect the source drives."
1.2.3 "Cannot complete scheduled consolidation of incremental recovery points for <drive name>."
1.2.4 "Cannot create offsite copy for job <job name>."
1.2.5 "There is not enough space to create the offsite copy on <offsite location>."

1.3 Low Priority
No Low Priority error messages are defined at this time.

2. Warning Messages

2.1 High Priority
2.1.1 "The following component is not installed correctly: <component name>."
2.1.2 "Distributed COM (DCOM) is currently disabled. Use dcomcnfg to enable DCOM so that remote users can connect to this computer."
2.1.3 "The conversion job <job description> references volumes that cannot be converted."

2.2 Medium Priority

2.2.1 Warning if unable to delete requested recovery point files.
When asked to delete a recovery point, but cannot delete the actual files on disk, a message will be sent. The recovery point history entries will still be deleted.
2.2.2 "Cannot enforce size and count quotas."
2.2.3 "Cannot update the system index (.sv2i) file."
2.2.4 "Cannot delete old recovery points from the destination folder."
2.2.5 "Cannot read the file backup information from the image job."
2.2.6 "Your recovery point location of <folder name> is running out of space. Please run the Cleanup Recovery Points task to free up some space."
2.2.7 "Cannot set up recovery point schedules."
2.2.8 "Cannot remove offsite copy <image file name>."
In order to make space for new image files, older image files are removed.  If a removal fails, this warning is given.
2.2.9 "Removed the following surfaced VHD volumes '<VHD volume name>' from the '<backup job name>' backup job as surfaced VHD volumes cannot be included in the same job as the hosting volumes."

2.3 Low Priority
No Low Priority warning messages are defined at this time.

3. Informational Messages

3.1 High Priority
3.1.1 "An operation was interrupted because the service was stopped."
3.1.2 "A recovery of <recovery point filename> completed successfully."
3.1.3 "Cannot complete the restore of recovery point: <recovery point filename>."
Restoration could not complete at this time. The restore operation can be completed by closing open files on the destination drive, forcing a dismount of the destination drive, or completing the restore using either the Veritas Recovery Disk or LightsOut Restore. The product will prompt the user to choose one of these options and retry the restore.
3.1.4 "A recovery of multiple volumes completed successfully"
3.1.5 "Cannot complete the restore of recovery point with multiple volumes."
Restoration could not complete at this time. The restore operation can be completed by closing open files on the destination drive, forcing a dismount of the destination drive, or completing the restore using either the Veritas Recovery Disk or LightsOut Restore. The product will prompt the user to choose one of these options and retry the restore.
3.1.6 "Cannot complete copying of <drive name> drive."
Copy could not complete at this time. The copy operation can be completed by closing open files on the destination drive, forcing a dismount of the destination drive, or completing the copy using either the Veritas Recovery Disk or LightsOut Restore. The product will prompt the user to choose one of these options and retry the copy.
3.1.7 "Copying drive <drive name> completed successfully."
3.1.8 "A file folder operation on drive <drive name> was cancelled by the user."
3.1.9 "A recovery point operation on drive <drive name> was cancelled by the user."
3.1.10 "Recovery point <filename> deleted to comply with the number of recovery points to save for each drive."
3.1.11 "Recovery point <filename> deleted to comply with the size of recovery points to save for each drive."
3.1.12 "A recovery operation completed successfully in the Veritas Recovery Environment during the previous reboot."
3.1.13 "Cannot complete consolidation of incremental recovery points."
3.1.14 "Consolidation of incremental recovery points completed successfully."
3.1.15 "A file and folder backup completed successfully. However, no files were backed up because none of the source files have changed since the last backup."
3.1.16 "The '<conversion type>' conversion process could not be completed."
3.1.17 "The '<conversion type>' conversion process completed successfully and is located at '<conversion path>'."
3.1.18 "The copy process could not be completed."
3.1.19 "The copy process completed successfully."
3.1.20 "The drive-based backup job, <job name>, has been started manually."
3.1.21 "The file and folder backup job, <job name>, has been started manually."
3.1.22 "The drive-based backup job, <job name>, has been started automatically."
3.1.23 "The file and folder backup job, <job name>, has been started automatically, according to schedule."
3.1.24 "The drive-based backup job, <job name>, has been started in response to the installation of a software program."
3.1.25 "The file and folder backup job, <job name>, has been started in response to the installation of a software program."
3.1.26 "The drive-based backup job, <job name>, has been started in response to data written to the hard drive that exceeds the limit you specified."
3.1.27 "The file and folder backup job, <job name>, started in response to data written to the hard drive that exceeds the limit you specified."
3.1.28 "The drive-based backup job, <job name>, has been started because a user has logged on to your computer."
3.1.29 "The file and folder backup job, <job name>, has been started because a user has logged on to your computer."
3.1.30 "The drive-based backup job, <job name>, has been started because a user has logged off of your computer."
3.1.31 "The file and folder backup job, <job name>, has been started because a user has logged off of your computer."
3.1.32 "The drive-based backup job, <job name>, has been started because the Maxtor OneTouch(tm) button was pressed."
3.1.33 "The file and folder backup job, <job name>, has been started because the Maxtor OneTouch(tm) button was pressed."
3.1.34 "The drive-based backup job, <job name>, has been started in response to a change in the Veritas ThreatCon level."
3.1.35 "The file and folder backup job, <job name>, has been started in response to a change in the Veritas ThreatCon level."
3.1.36 "The drive-based backup job, <job name>, has been started because an outbreak alert has been detected."
3.1.37 "The file and folder backup job, <job name>, has been started because an outbreak alert has been detected."
3.1.38 "The drive-based backup job, <job name>, has been started because an application, which you identified as a backup trigger, has been started."
3.1.39 "The file and folder backup job, <job name>, has been started because an application, which you identified as a backup trigger, has been started."
3.1.40 "The drive-based backup job, <job name>, has been started in response to an event trigger."
3.1.41 "The file and folder backup job, <job name>, has been started in response to an event trigger."
3.1.42 "A manual base recovery point of drive <drive name> was created successfully."
3.1.43 "A manual incremental recovery point of drive <drive name> was created successfully."
3.1.44 "A manual independent recovery point of drive <drive name> was created successfully."
3.1.45 "The file and folder backup job, <job name>, completed successfully."
3.1.46 "A scheduled base recovery point of drive <drive name> was created successfully."
3.1.47 "A scheduled incremental recovery point of drive <drive name> was created successfully."
3.1.48 "A scheduled independent recovery point of drive <drive name> was created successfully."
3.1.49 "The file and folder backup job, <job name>, completed successfully."
3.1.50 "A base recovery point of drive <drive name> was created successfully in response to the installation of a software program."
3.1.51 "An incremental recovery point of drive <drive name> was created successfully in response to the installation of a software program."
3.1.52 "An independent recovery point of drive <drive name> was created successfully in response to the installation of a software program."
3.1.53 "The file and folder backup job, <job name>, completed successfully in response to the installation of a software program."
3.1.54 "A base recovery point of drive <drive name> was created successfully in response to data written to the hard drive that exceeds the limit you specified."
3.1.55 "An incremental recovery point of drive <drive name> was created successfully in response to data written to the hard drive that exceeds the limit you specified."
3.1.56 "An independent recovery point of drive <drive name> was created successfully in response to data written to the hard drive that exceeds the limit you specified."
3.1.57 "The file and folder backup job, <job name>, completed successfully in response to data written to the hard drive that exceeds the limit you specified."
3.1.58 "A base recovery point of drive <drive name> was created successfully when a user logged on to your computer."
3.1.59 "An incremental recovery point of drive <drive name> was created successfully when a user logged on to your computer."
3.1.60 "An independent recovery point of drive <drive name> was created successfully when a user logged on to your computer."
3.1.61 "The file and folder backup job, <job name>, completed successfully when a user logged on to your computer."
3.1.62 "A base recovery point of drive <drive name> was created successfully when a user logged off of your computer."
3.1.63 "An incremental recovery point of drive <drive name> was created successfully when a user logged off of your computer."
3.1.64 "An independent recovery point of drive <drive name> was created successfully when a user logged off of your computer."
3.1.65 "The file and folder backup job, <job name>, completed successfully when a user logged off of your computer."
3.1.66 "A base recovery point of drive <drive name> was created successfully after the Maxtor OneTouch(tm) button was pressed."
3.1.67 "An incremental recovery point of drive <drive name> was created successfully after the Maxtor OneTouch(tm) button was pressed."
3.1.68 "An independent recovery point of drive <drive name> was created successfully after the Maxtor OneTouch(tm) button was pressed."
3.1.69 "The file and folder backup job, <job name>, completed successfully after the Maxtor OneTouch(tm) button was pressed."
3.1.70 "A base recovery point of drive <drive name> was created successfully in response to a change in the Veritas ThreatCon level."
3.1.71 "An incremental recovery point of drive <drive name> was created successfully in response to a change in the Veritas ThreatCon level."
3.1.72 "An independent recovery point of drive <drive name> was created successfully in response to a change in the Veritas ThreatCon level."
3.1.73 "The file and folder backup job, <job name>, completed successfully in response to a change in the Veritas ThreatCon level."
3.1.74 "A base recovery point of drive <drive name> was created successfully after an outbreak alert was detected."
3.1.75 "An incremental recovery point of drive <drive name> was created successfully after an outbreak alert was detected."
3.1.76 "An independent recovery point of drive <drive name> was created successfully after an outbreak alert was detected."
3.1.77 "The file and folder backup job, <job name>, completed successfully in response to an outbreak alert."
3.1.78 "A base recovery point of drive <drive name> was created successfully when an application, which you identified as a backup trigger, was started."
3.1.79 "An incremental recovery point of drive <drive name> was created successfully when an application, which you identified as a backup trigger, was started."
3.1.80 "An independent recovery point of drive <drive name> was created successfully when an application, which you identified as a backup trigger, was started."
3.1.81 "The file and folder backup job, <job name>, completed successfully when an application, which you identified as a backup trigger, was started."
3.1.82 "A triggered base recovery point of drive <drive name> was created successfully."
3.1.83 "A triggered incremental recovery point of drive <drive name> was created successfully."
3.1.84 "A triggered independent recovery point of drive <drive name> was created successfully."
3.1.85 "The file and folder backup job, <job name>, completed successfully in response to an event trigger."
3.1.86 "An unknown file system has been detected on a mounted volume."
3.1.87 "An unknown file system has been detected on the mounted volume <volume name>."
3.1.88 "The conversion job, <job name>, has been started."

3.2 Medium Priority
3.2.1 "Backup Exec System Recovery service started successfully"
3.2.2 "Backup Exec System Recovery service stopped."
3.2.3 "A cancel request was submitted during the following operation: <operation description>."
3.2.4 "The Recovery Point History was cleaned."
3.2.5 "Cannot register <computer name> with service principal name of  'VProRecovery Backup Exec System Recovery Agent 9.0.'"
3.2.6 "The job is currently disabled."
3.2.7 "An automatic recovery point was not created because an earlier recovery point from the same job was still in progress."
3.2.8 "Created offsite copy <image file name>."
3.2.9 "Removed offsite copy <image file name> because primary image was deleted."
3.2.10 “The specified volume <target volume> is a Clustered Shared Volume, therefore the <job name> job will only take full images.”

3.3 Low Priority
No Low Priority information messages are defined at this time.