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!
Device Pool, Concurrent Operation
Backup Exec 2010 R3 on Server 2003. Two Tandberg 8-slot autoloaders with one drive each, placed in a device pool. If I set my jobs to target the pool only one job runs at a time. To use both devices at the same time, I have to target the devices individually, not the pool. How do I get concurrent operation out of the device pool? Library Expansion Option is installed.Quantum i80 IBM LTO6 on BackupExec 2014 missing drive
Hello I have a Quantum i80 device with 2 IBM UKTRIUM-HH6LTO6 drives that I have updated the firmware on as Quantum has said. It is shown that the drives will work with Backupexec 2014 once I update the firmware. I have the drives attached by FC though a FC switch to the blade that is running the server. This is a brand new install. New 2012 R2 server and new tape library. I can see the Library in Backupexec with the two drives but one drive is always saying "missing device" I have tried reboots and rediscovery a bunch of times but it still just says missing device. Does anyone have any ideas?
MSL Library Windows 2012 R2 MOVE_MEDIUM Timeout
I am getting timeout errors when I try to load a tape using Backup Exec. It's been running on a Windows 2k server and BE 12 for years. Works great. I have a a new server running Windows 2012 R2 and it takes the drive and library offline. I'm running tracer from Symantec to log the commands. On the 2012 server, after 37 seconds I get a ASPI = SCSI_COMPLETED_WITH_ERROR HBA = SELECTION_TIMEOUT On the old server, after 46 seconds I get SCSISTAT_GOOD STATUS_SUCCESS I've powered down everything 5 times. I've tried HP drivers and also the stock Microsoft drivers. After 2 days of searching HP and Symantec I need some help.
Backup Exec 2014 Backup-to-Dedupe Duplicate-to-Tape
Some other questions have touched on this topic but they all seem to be just a little different than my scenario. The issue I seem to be having is the following. I have a single Windows Server 2008 R2 server with Backup Exec 2014. I am not using CASO with a MMS. I run incrementals throughout the week and then a full backup to our dedupe storage on a SAN. I then run a duplicate of the previous Full backup job (not using scheduled option for duplicate job) to duplicate to tape for off-site storage. The intention is to retain two weeks of data on-site and more off-site. However, I see instances where, if the duplicate to tape job failes, the previous Full backup is no longer on the dedupe storage. This means we have to do the entire full backup over again and then duplicate to tape. In addition, this concerns me because I wonder if all the other jobs we write to tape in this manner are also getting removed from dedupe storage after the job either completes successfully or fails. It concerns me because we want to retain some of those on-site. Is this by design? Is there a way around this?