S3

3 Topics

BackupExec + S3 [A backup storage read/write error has occurred]
Hi, We have BackupExec 20.4 with StoreOnce on premise and use Amazon S3 with Storage Gateway for Virtual Tape Library (VTL). My jobs create backup onsite on StoreOnce and then they are pushed to the cloud via AWS S3 with a duplicate job. I only get this error from time to time and have already checked with my ISP, VPN Network team and opened a ticket with AWS. I ask if anyone can help me out with these failures that occur: Job ended: venerdì 19 giugno 2020 at 02:27:11 Completed status: Failed Final error: 0xe00084c7 - 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 Duplicate- VMVCB::\\XXXXX\VCGuestVm\(DC)XXXX(DC)\vm\XXXX An unknown error occurred on device "HPE StoreOnce:3".V-79-57344-33991 - 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.V-79-57344-65072 - The connection to target system has been lost. Backup set canceled. I can't try cloudconnect optimizer because it's a iScSi connection. Any help would be great. Thank you, Federico Pieraccini
Solved
supportocg
5 years ago Place Backup Exec
3.5KViews
0likes
7Comments
Backup Exec 16 - AWS S3 or Tape Gateway
Icurrently have the aws tape gateway setup to do weekly backups for our servers. Its working well minus the auto ejecting after the job is over (will see if this issue still happens with backupexec 16, just upgraded yesteraday). I noticed backupexec 16 has the ability to add AWS S3 as a storage. Can someone please explain the advantages/disadvantages of s3 versus tape gateway? Thanks
kahoots1
7 years ago Place Backup Exec
2.3KViews
0likes
3Comments
BE 15 fp 5 backup to the private S3
I'm currently trying to test configuration with backup to our private S3 which is compatible with Amazaon S3 but unfortunately I am unable to complete it. here is the list of my actions: 1) configure cloud instance using BE MCLI according to BE MCLI *.chm help. It finishes with success. 2) Configure Cloud Storage using BE GUI. All configuration wizard steps completes with success, wizard even successfully retrieves the list of S3 buckets from the S3 service, and completes the configuration with no error. 3) At the end of configuration BE offers to restart it's services to finalize the cloud storage. 4) After the restart device is still shown as offline. There is an alert at the time of services start: Unable to connect to to the OpenStorage device. Ensure that the network is properly configured between the device and the Backup Exec server. For more information, see V-275-1017 on the Symantec Knowledge Base. However, I was unable to find any useful reference in KB to solve this particular issue. The main question is to understand what is missing from either configuration steps or S3 itself. Does anyone know how this can be debugged?
mmironov
8 years ago Place Backup Exec
4.2KViews
0likes
15Comments