Backup Exec 2010 R3
Hi All, We have a Quantum Superloader 3 and were running Backup Exec 2010 R2. Compression was working fine and with the LTO 5 tapes it was all fitting on a single tape. We then upgraded to R3 and we get no compression. I can force compression to be enabled on the Superloader 3 but as soon as I run a print job from R3 it sets it to disabled again. What is going on? I may have to go back to R2 if there is no hotfix. With no compression our backups are running into 3 tapes!
Final error: 0xe00084ec - A backup storage read/write error has occurred.
Good morning, I recently gotten this error everytime my schedule job run on Symantec Backup Exec 2010 Final error: 0xe00084ec - 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. Final error category: Backup Media Errors Tried to reinstall backup exec and repluging all cable but still fail. Any solution or idea?
Backup Exec 2010R2 agents upgrade
Hi All, I've just successfully install BE 2010 R2, i wonder if i should upgrade the agents in all o my systems (Exchange, SHarePoint, SQL Server or Domain Controllers) for it to work properly ? from the what's new the R2 only affecting SharePoint server 2010, while mine is 2007 do i still have to upgrade it ?Periodic tape backup throughput issues
I’m having a perplexing throughput issue with my tape backups. Every two weeks (on a Tuesday for the past two months) my tape backup throughput decreases dramatically – from 1,360 MB/min to 130 MB/min. The speed decrease happens regardless of the source of the backup – over the LAN or running a duplicate job where the backup-to-disk folder is stored on the backup server hard drive. This situation does not impact the speeds of disk-to-disk backups. The only way to resolve the issue is to reboot the backup server. Below is my configuration. Dell PowerEdge 2850 Dell PowerVault 124T LTO-3 Adaptec 39160 SCSI adapter Windows Server 2003 Std x64 SP2 fully patched Backup Exec 2010 fully patched Troubleshooting steps I’ve taken contacted Symantec who had me run various diags contacted Dell who had me upgrade the firmware for the tape/autoloader checked to make sure there are no scheduled tasks running during this time checked Task Manager for processing consuming CPU or generating lots of I/O – none found compared running processes to server after reboot – no differences rebooted server for several consecutive days to see if it would extend the interval – it did not verified all the drivers were at the latest levels – tape, autoloader, SCSI adapter checked Windows Application and System logs for errors – none found checked tape autoloader logs for errors – none found checked tapes for errors – none found Anyone have any ideas what could be causing those or what other steps I could take to troubleshoot the problem?VMWare backup failing
Hello all, I've got an issue when trying to backup vSphere 4 VMs using Backup 2010R2. It's an intermittent issue, so I'm not exactly sure of the cause. I have between 15-20 VMs to be backed up. Everytime I run a backup job I will get one or two VM backups failing with the error below>>>>>>>>>>>>>>>> Job Completion Status Job ended: Saturday, August 21, 2010 at 5:27:51 AM Completed status: Failed Final error: 0xe00095a7 - The operation failed because the virtual center or ESX server reported that the virtual machine's configuration is invalid. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-38311 It's frustrating, because I will then run a seperate job after the failed job and the VMs complete without any errors. The link that Symantec provide does not contain any information. The credentials for the job are good, the media device is a local disk - not sure if any further information is required! Any thoughts? Cheers Magyar
BE2010 locking profiles
We have a single Server 2003 box running Terminal services. The backups are scheduled each night and complete the following morning. We recently upgraded BE from v11d to v2010. Since then we are having problems with profiles locking after the backup completes. If I restart the server then problem goes away. If I do not run the backup then then the problem doesn't appear. It doesn't seem to make a different if AFO is enabled for the backup or not. I have also tried things like eliminating the system state for the selection -> problem still exists. The server was running SEP which can apparently cause problems but SEP has now been removed. Any ideas?Specify "sunday after first saturday of month" (for example ! Read more in description)
Dear all, In BackupExec, if you want to do big monthly backups on first Saturday (for example) and you want not to do some backups on Sunday (the next day) you can't ! Let me give you an example : If you say, do task A on first Saturday each month do task B on first Sunday each month then you have a big risk that task B is done one week before task A : it happens each time Sunday is the 1st of the month ! Is that right or is there a way to to it some other way ? Thanks a lot !