Final error: 0xe00084ec - A backup storage read/write error has occurred.
If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.
If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.
If the storage is cloud based, check for network connection problems. Run the CloudConnect Optimizer to obtain a value for write connections that is suitable for your environment and use this value to run the failed backup job. Review cloud provider specific documentation to help determine the source of the problem. If the problem still persists, contact the cloud provider for further assistance.
Final error category: Backup Media Errors
V-79-57344-34028
For cloud backup, as the bold message portion indicates, these errors with a cloud storage device are typically caused by an interruption or limitation with the network connection to the cloud storage. During operation, Backup Exec can use multiple connections to cloud storage to help with performance. These read and write connection settings can be viewed and manually modified in Backup Exec Settings under Cloud Storage. The default settings were established based on average internet connection speeds.
You can configure and run the CloudConnect Optimizer job to get a suggested Write Connections value for backups.
The Backup Exec CloudConnect Optimizer displays a job log with the suggested Write Connections value for the specific cloud server type. This value is updated to the Backup Exec settings if you select the Use the suggested number of Write Connections for the upcoming jobs check box in the Backup Exec CloudConnect Optimizer.
.
To configure the CloudConnect Optimizer job
|
Job name |
Displays a name for the CloudConnect Optimizer job. You can edit the name of the job. |
|
Cloud server type |
Displays the type of cloud server. |
|
Use the suggested number of Write Connections for the upcoming jobs |
Select the check box to update the suggested value in the Backup Exec settings. |
|
Run now |
Runs the job immediately. |
|
Run on |
Schedules the job to run on a specific date and time. |
The CloudConnect Optimizer job runs based on whether you have scheduled for it to run immediately or scheduled for a later date.
In case of CAS-MMS scenario, from the Central Admin Server (CAS), you can create a CloudConnect Optimizer job only for the devices that are local to the CAS server or the one shared with the CAS server. For devices that are local to the Managed Backup Exec Server (MBES), a CloudConnect Optimizer job can only be created from that particular MBES. If a cloud storage device is shared between CAS and MBES, and you want job to run on MBES, you must to create job from MBES only. The CloudConnect Optimizer job runs on the media server where the job is created.
The CloudConnect Optimizer job is displayed on the Job Monitor and Storage tab. If the CloudConnect Optimizer job is scheduled for a later date, the job status displays the Scheduled status. After the job completes successfully, the Job Monitor > Job Histories section and Storage > Job History section displays the job details and the job status.
After the CloudConnect Optimizer job completes, the job log displays the suggested Write Connections value. If you have selected the check box to update the suggested value in the Backup Exec settings, this value is updated and used for the upcoming jobs. A confirmation message is displayed that the value is successfully updated in the Backup Exec settings.
IMPORTANT NOTE: The settings suggested by the CloudConnect Optimizer are based on a single backup job running. If multiple backup jobs are running simultaneously, the connections number recommended should be divided among all jobs running at any one time. For example, if the CloudConnect Optimizer recommends a write connection number of 24 and 4 backup jobs are typically running at one time to this cloud storage location then the connections for each backup should be the total divided by 4 backups or 6 write connections. This setting can be made manually through Configuration and Settings | Backup Exec Settings | Cloud Storage. This value is a suggested starting point - if performance seems slow the number of write connections can be increased but monitor backups for errors if the connection number is set too high or if more jobs are run simultaneously.