Incremental backup configured over Amazon bucket fails
Hello, Here I'll describe my problem in case anyone canhelp me. I have a Windows 2012 R2 Server with Backup Exec 2015.Months ago I configured my backup jobs as follows: One monthly job that makes a completebackupto a shared folder which is in another Windows 2008 Server. A daily incremental job which makes the backups to an Amazon bucket. 'Till about 10 days ago everything went good. Then we've made a change in that server: part of the information we had stored locally we moved it to a virtual machine conected by iScsi (actually, it is an AWSStorage Gateway, but for Windows it works as an iScsi unit). Then, we've made the monthly job, which finished correctly but then, the daily backups start to fail with this message: It is in Spanish but the translation of the error is "A backup storage read/write error has occurred". The first suggestion says that solution could be an inventory and catalog of the storage, but I did it twice and the job still fails. Then I've made a new complete backup while I cleaned the Amazon bucket, but it didn't work. Finally I've configured again the cloud storage in the Backup Exec, and as you can imagine, it keeps on failling (if not, I wouldn't open this post). Of course, I've tried to restart the backup servicies and the server, and there aren't any new updates to install either in the O.S. or the Backup Exec. Any help would be very appreciate. Thanks in advance!!
Backup Exec 14.2 FP2 - Cloud connector to S3 Issues/info
Hi all, I have configured Backup to Amazon S3 using the cloud connector. I did a test backup of 48GB (a VM). The upload of data was free but i have been charged for transfer out. Isn't the backup just uploading data, why is there a download of 48GB (see attachment) What is backup exec doing to class it as a transfer out of S3? Also when backing up the is no way to set the storage class to Standard IA or Glacier, it seem to all go into Standard, this is crazy! Cloudberry backup can do this and its a fraction of the price. http://www.cloudberrylab.com/blog/how-to-automatically-set-amazon-standard-ia-storage-class-in-cloudberry-backup/ Any help or information would be appreciated.
AWS Gateway Cached Storage
Scenario. 2 x backup Exec 2014 servers storing backup data locally to disk. 10TB of data backed up. Aim. To duplicate backup jobs to Amazon S3 for offsite storage. This would only be accessed in a disaster scenario. Method. I've been playing with Amazon's Gateway VTL device and their Gateway Cached Volume. (I believe Gateway Stored option not available for BE) As such I have implemented both a VTL device and a cached volume device and made the storage available to backup exec via Iscsi initiator. I have performed test backup jobs of both solutions and both appear to work fine. Considerations. The cost of runnning a an Amazon Storage Gateway (either VTL or cached) is roughly £80 per month. Obviously with actual storage and reads etc on top of this. If I go down the VTL route I need to provision 2 gateways as the Iscsi initiator and the virtual tape library can only be connected to one physical BE server. My preferred method, to avoid having to use 2 gateways, is 1 Gateway cached Storage device. Within Amazon AWS I can then create 2 volumes each with a unique ID and then each BE server has it's own Iscsi volume that itcan use as disk based storage. I have tested this scenario with success. Question. How does Backup Exec manage the expiry of data sets that are stored on an Amazon S3 device? What I need to avoid is costly reads of the whole amazon volume as this is where extra additional costs are going to be incurred. Does anyone have any experience of this or have any tips to share? Thanks
Backup Exec 2014 (or 2012) AWS Storage Gateway problems
I need assistance from someone who has successfully implemented the AWS Storage Gateway-VTL in either Backup Exec 2012 or in Backup Exec 2014. On the AWS site, it shows that BE 2012 is a supported application for their Storage Gateway-VTL. On the Key feature list for BE 2014 is shows that AWS Storage Gateway is supported. I have not been able to get the VTL to work properly in either. The problem I am having is that the robotic library (an STK L700) shows up, all 10 of the tape drives show up (ULT3580-TD5), but the drives are not listed under the library. There are drives under the library, but they are all in red and have a "missing device" error. I have tried for the last 3 days to work with Symantec support to resolve this. They claim that the library is support and the drives are supported, but the drives are not support inside of the library. They provided links to the HCL for both BE 2012 and BE 2014 to prove their point. So, I asked them why their key new feature matrix for 2014 show support for AWS Storage Gateway and the setup documentation in AWS shows a screenshot of the drives under the library in BE 2012. They didn't have an answer for this. They are now telling me that instead of working with me to resolve my issue, they are instead working with the marketing group to remove support for AWS from the feature list. WTF?!? The support group is either unwilling or unable to connect me with the product team so that I can get some clarification on what components of the Storage Gateway is supported (besides the VTL, there is also a disk based gateway). So, if anyone out there has successfully connected their BE installation to the AWS Storage Gateway I would greatly appreciate it if you shared the "secret sauce". Thanks, ALM