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 PieracciniSolved3.5KViews0likes7CommentsS3 Cloud Storage error
Trying to get a Cloud storage Device setup on BU 15 (version 14.2 rev 1180). Everything works and but at the step when entering server name and logon account I get the message "There are no storage locations found on the server.". If I change the user info or amazon:amazon.com I get a different message so sure the settings are correct. Bucket can be found using S3 browser, and bucket name is all in lower case (no spaces or special characters). Any pointers as to how I can get this to work ?644Views0likes1CommentAmazon S3 Bucket - share or connect with second BEX server?
We have two Backup Exec 2015 FP4 servers, one CASO, one MMS at different sites via site-to-site links. We are testing the Amazon S3 connector on the CASO - so far so good. It’s basically a giant disk-based storage device. I heard it’s the Hotel California of storage (HA!) free to write to, minimal storage cost, expensive to get data out. So I’m thinking about DR and all that jazz, what if this server (or building) decides to melt down? How do we access the Amazon S3 bucket from the other server? When I try to attach the existing bucket to the second server it won’t let me as this name already exists. I was hoping it would be like a shared Dedupe storage, but no dice. Just curious if anyone has this working – the same bucket with two servers – so that we can restore from either. I suppose I can delete the AWS storage from the CASO and then connect to it on the MMS but I would hope that we can set this up before disaster strikes, not after. I plan on testing this but though I would ask this community.885Views0likes0Comments