Amazon S3 offline this device has not been discovered correctly
I have backup exec 15 running. When I first installed, I was able to connect to amazon S3 and backup data to a bucket that I created. This worked for a few days. Then all of a sudden the Amazon S3 storage device says "offline this device has not been discoveredcorrectly and to restart services. I restarted services, rebooted, removed/re-added, etc - and I can't figure it out. Not sure if there's a network communiaction issue between my amazon instance and S3 or what. It seems my config is correct because I was able to get it working for a few days. If I remove and re-add it seems to connect as it finds my S3 bucket, but the storage just stays offline. Not sure how to diagnoise.
NIC Teaming Slow Throughput, any ideas?
Hey guys, We currently have 2Gig set up through NIC teaming for our backup exec setup.When we have backups running, it barely reaches 35-40% of the bandwith. I am using Backup Exec 2010. Has anyone else here set up NIC teaming before? What are some things that might cause slow performance? Are there any specific settings in Backup Exec that may help? 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
BE 2010 Backup Method
Hi there, We have Backup Exec 2010. I want to backup VMDK, but not enough free space in vDisk. Backup method, before storage, and then carries the BE server's disk. I just want to back up to the BE server disk. What can I do. Thanks, Merhaba, Bizim bir Backup Exec 2010 var. Ben VMDK yedekleme istiyorum, fakat vdisk içinde yeterli boş alan yok. Yedekleme metodu, önce storage, sonra BE server diske taşımaktadır. Ben sadece BE sunucu diskine yedeklemek istiyorum. Ne yapabilirim. Teşekkürler.
Cannot backup to tape with backup exec 2012
Hello, So I've been trying for more than a week now to backup to tape with backup exec and I'm close to abandonning this program. I always get the same error message : "Physical volume library drive not found". I tried a few things on the net like reinstalling the tape drivers, updating the firmware, running as administrator. It seemed to me like people were saying that the tape driver doesn't work. So I tried installing Uranium backup in trial version and could create a backup that works with my tape right away. So what is the problem with backup exec?