How important is it to verify the replication of (already verified) disk-based backup sets to cloud?
My company is a little bit behind on the adoption of cloud technology; there hasn't been a compelling need to change anything. Anyway, I was hoping to at least modify my disk-to-disk-to-tape backup scheme to a disk-to-disk-to-cloud one. Having to change tapes is a pain, especially now since I have to make a special trip into the office to do it. There's no way to "budget" anything until I have some sense of how much this would all cost. Amazon has cost calculators, but they ask for metrics I have no way of getting at. So as a test, I created an AWS S3 bucket and did some test Duplicate jobs from existing backup sets to the bucket. The first ~15.5 GB backup set cost $1.59 to duplicate to 1Z-IA. So a full 3 TB backup would scale up to approximately $320 every week. Plus, with a 4-week retention period, 12 TB of data storage would be another $120/mo. That would be a nonstarter with management. Then I dug into the Amazon Cost Explorer and found that most of this ($1.38) was Data Transfer out. The cost appeared because the duplicate job did a Verify, and to do that, the Backup Exec server had to read all that data back in from AWS. I verify the duplicate to tape because there's no cost to that. If I skip the Verify, the weekly cost for AWS backups would drop a lot. A subsequent 70 GB Duplicate, without the verify, cost about 25 cents. What would I lose if I skipped the verify? The backups to local disk would still be verified as part of the job that creates them. There's some error correction built into Ethernet, would that remove the need? Getting rid of tapes, I could restructure the backups to do incremental forever, so I wouldn't need to keep 4 full backups in local storage or in the cloud. But I'd like to first estimate costs using the closest structure to existing practice.817Views0likes2CommentsBackupExec + 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.5KViews0likes7CommentsAWS Tape Gateway Wiping Tapes
We are currently playing with Backup Exec & the AWS Tape Gateway to backup to VTL in S3/Glacier. We have an issue where backups are failing and also where once a week (sometimes every other week) when one backup job begins, it first wipes all tapes. Has anyone seen this before?441Views0likes0CommentsBackup 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? Thanks2.3KViews0likes3CommentsBackup Exec 15 to AWS Tapes
Hey all, I've setup backup exec to backup our 2 weekly jobs to AWS tapes. It's been working fine the last few weeks. Each backup going to individual tapes. This past weekend, both jobs went to the same tape. I would like to set it so that it uses individual tapes so if i need to recover in the future, I dont have to pull down the entire weeks data and save on download costs. Can you please explain how i can set it up? Thanks1.2KViews0likes3CommentsBackup Exec: EC2 and On-Premises CAS/MBES configuration
We are working with a client who wants to move all his on-premises infrastructure to AWS cloud. There is a limitation with his WAS bandwidth which is 1gb. Their total data size is 30TB. Since the data size is big and the WAN bandwidth is limited they are going with a transportable disk which will take the initial full back to the cloud and then there will be just incremental backups that will be sent to cloud. My query is has anyone done a configuration where there is a CAS and an MBES on EC2 virtual machines and then there is another MBES which is on premises. Can we have some pointers on how we can achieve this setup. How will the communication between the CAS Backup Exec server on the EC2 and the on-premises MBES server happen? What are VPN configurations that need to be done to get this configurations working. I believe that if the communications between all the servers is working, then this setup should work and the customer can achieve what he is looking for. Any pointers regarding this will help a lot. Thanks in advance!1.1KViews0likes2Comments