Error messages CloudConnect Optimizer job log and workarounds for Backup Exec.

book

Article ID: 100034275

calendar_today

Updated On:

Resolution

The following table gives the CloudConnect Optimizer job log status, error messages in the job log, and the workarounds.
 
CloudConnect Optimizer job status Message in job log
Message for corrective action
Failed CloudConnect Optimizer initialization failed. Refer to the Backup Exec logs for more details. Restart all Backup Exec services. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot initialize the CloudConnect Optimizer tests. Refer to the Backup Exec logs for more details. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot get configuration details required to run the CloudConnect Optimizer tests. Refer to the Backup Exec logs for more details. Ensure that the CloudInstance.xml file is available at the Backup Exec install location. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot update configuration file with required details to run the CloudConnect Optimizer tests. Please check Backup Exec logs for more details. Ensure that the CloudInstance.lck file is available at the Backup Exec install location.
If yes:
  1. Rename the CloudInstance.xml file as CloudInstanceBackup.xml.
  2. Rename the CloudInstance.lck file as CloudInstance.xml.
  3. Verify the Backup Exec settings under Cloud Storage.
  4. If all the default settings are displayed appropriately, delete the CloudBackupInstance.xml file.
  5. Run the CloudConnect Optimizer job.
If no:
  1. Restart all Backup Exec services.
  2. Ensure that the CloudInstance.xml file is available at the Backup Exec install location.
  3. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot unlock the CloudConnect Optimizer configuration file. Refer to the Backup Exec logs for more details. Ensure that the CloudInstance.lck file is available at Backup Exec install location.
If yes:
  1. Rename the CloudInstance.xml file as CloudInstanceBackup.xml.
  2. Rename the CloudInstance.lck file as CloudInstance.xml.
  3. Verify Backup Exec settings under Cloud Storage.
  4. If all the default settings are displayed appropriately, delete the CloudBackupInstance.xml file.
  5. Run the CloudConnect Optimizer job.
If No:
  1. Restart all Backup Exec services.
  2. Ensure that CloudInstance.xml file is available at the Backup Exec install location.
  3. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed OST initialization failed. Refer to the Backup Exec logs for more details. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot create an image for the CloudConnect Optimizer tests. Refer to the Backup Exec logs for more details. Verify the credentials.  Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot generate the CloudConnect Optimizer test data. Refer to the Backup Exec logs for more details. Verify the memory requirements. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot back up the CloudConnect Optimizer test data to cloud. Refer to the Backup Exec logs for more details.
  1. Ensure that there are no network issues.
  2. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot close the image created for the CloudConnect Optimizer tests. Refer to the Backup Exec logs for more details. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed Cannot delete the image created for the CloudConnect Optimizer tests. Refer to the Backup Exec logs for more details. Refer to the following line in the Backup Exec logs to get the name of the image:
sts_delete_image failed with error=%d. Could not delete image \"%s\
Where "%s displays the image name created for the CloudConnect Optimizer job.

Delete the image from respective logical storage unit.
Failed Cannot close the OST session. Refer to the Backup Exec logs for more details. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.
Failed CloudConnect Optimizer failed. Refer to the Backup Exec logs for more details. Restart all Backup Exec services. Enable the Backup Exec Debug Monitor and then rerun the CloudConnect Optimizer job.

Note: Here is the list of UMI codes the article applies to - V-79-57344-43008, V-79-57344-43009, V-79-57344-43010, V-79-57344-43011, V-79-57344-43012, V-79-57344-43013, V-79-57344-43014, V-79-57344-43015, V-79-57344-43016, V-79-57344-43017, V-79-57344-43018, V-79-57344-43019, V-79-57344-43020, V-79-57344-43021, V-79-57344-43022, V-79-57344-43023, V-79-57344-43024

Issue/Introduction

The error messages for CloudConnect Optimizer job log in Backup Exec are listed with the workarounds.

Additional Information

UMI: V-79-57344-43008 UMI: V-79-57344-43009 UMI: V-79-57344-43010 UMI: V-79-57344-43011 UMI: V-79-57344-43012 UMI: V-79-57344-43013 UMI: V-79-57344-43014 UMI: V-79-57344-43015 UMI: V-79-57344-43016 UMI: V-79-57344-43017 UMI: V-79-57344-43018 UMI: V-79-57344-43019 UMI: V-79-57344-43020 UMI: V-79-57344-43021
Powered by Wolken Software