Backup Exec 2012 Has Issues
To help someone who may be thinking about upgrading to Backup Exec 2012, be careful. Backup Exec 2012, while it does have a very nice user interface and much better view of the backup jobs, it has some major issues that are not yet resolved. We did an upgrade over a week ago and we still can not compete our backups. The issues today are: -- The upgrade got us into a look over the "deduplication" feature and needed to call support for a answer (we have placed the solution on the forum) -- The reports are not working at all. It appears it is using the old reports or is just broken. So no reports on media, or jobs, etc. -- We have run out of backup space and there is NO way to manage the "media". You can see media sets but you are unable to sort or figure out which ones you can delete. (other thanjust reading though theunordered list) NOTE: We can not run a report to view the media which was suggested as a work around. -- There is no way to change the "retention" date of a "media set". So we wanted to reduce the retention period for existing backups so the space on the backup to disk folder will be reclaimed. Well since there is no concept of a "media set" in this version, you can only change the date for future backups. -- It keeps doing "discovery" on computers we have already noted as not needed to be backed up. Discovery runs on its own and adds machines that it finds. Even if we delete the machine, the next time discovery runs we are deleting it again from the list. We need to run discovery but once we make a decision on the machine, it should stop showing up. We are committed to Backup Exec 2012 but are really in a bad way with the product right now. So if you thinking of an upgrade, it might be better to delete you old version and start from scratch. Or wait. Hopefully this will prevent another user from going through this nighmare.1.5KViews6likes10CommentsBackup an Exchange 2013 DAG without CNO/CAAP
Hi All, This is my very first post and I really do hope you can help since we have been at it already for 12 hours. Is there any way to backup an IP-less DAG? We have a new Windows server 2012 R2 Exchange 2013 cluster without CAAP/CNO and BE2014 SP2 but no joy. Any help would be appreciated. Tnx. T1.2KViews4likes4CommentsThe job failed with the following error
We have updated BackupExec from 2012 to 2014 and all job are running fine but on a few backup jobs i am receiving following error. In one job i am receiving following error.. Completed status: Failed Final error: 0xe000942a - Backup Exec did not find any resources to include in the backup. Check the backup selections for this job to make sure it includes resources that are available for backup. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-37930 and another job is failing with following error: Completed status: Failed Final error: 0x2000fe07 - FS_NO_MORE Final error category: For additional information regarding this error refer to link V-79-8192-65031 Please help me out in this...Solved5.4KViews3likes3CommentsBackup Exec Server 2012 issue problem
Hello All, I'm getting issue about Backup Exec Server 2012 version 14.0 rev. 1798 (64-bit), from my customer. The BE Server have failed to backup, then showing error code E0009B61. And then, it showing alert is reported in the Event Viewer's Application Log with Event ID 58060 : "Backup Exec Alert : Please insert media into the portal." . When I click for this solution, I get the solution in the following article regarding this : http://www.symantec.com/docs/TECH23207 The solution on the article is : Place the tape requested into the robotic library portal and respond to the alert in Backup Exec. But, I don't know where the place of the tape and how to place the tape into the robotic library portal? What must I do to solve this problem? Note : the pc machine is Windows Server 2012 DatacenterSolved908Views3likes5CommentsBackup Exec 15 SDR Backups on Media Server
I can't seem to get SDR to turn on with our BE15 media server jobs. This means I can't to a bare metal restore or conversion from point in time to VM. This basically means you can’t restore your backup exec media server in a real DR situation. Has anyone seen this before, or currently experiencing this? I am working with Veritas no support at this time.Solved3.4KViews2likes20CommentsBackup Exec 2014 duplicate to tape process taking too long
Hello everybody, I have a problem, I using BE 2014 to backup a very small folder (about 50KB) to HDD then to tape, but the process of duplicate to tape taking very long for this folder, Can anyone help me out! Many thanks473Views2likes1CommentSharepoint backup failure
Hi, The backup is failing with the following error: Job ended: Friday, September 19, 2014 at 6:37:58 AM Completed status: Failed Final error: 0xe000fe49 - An invalid parameter was specified. Final error category: Job Errors For additional information regarding this error refer to link V-79-57344-65097 V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Agent for Windows. The correct version of the Agent for Windows must be running on the target computer. How could this issue be solved? Thank you,674Views2likes2CommentsBackup Exec Policies
Hi All, I have tape library with 24 Tapes, LTO5. BE Version 2012 . Data with Full Size Daily 1.5 TB., servers: Exchange, File Server, SQL server. one of the main requirments is : offsite one Tape Daily for all Jobs in one Tape. Optional: Activate Encryption. What is the best bractice, best policies configuration? Thanks and regards,Solved595Views2likes3CommentsBE - heavy I/O on client server
Hi There is a new HP server with RAID6. Due to budget constraint, both "backup source data" and "backup target data" located on the same server. But, on different "logical partitions". It acts both as file-server and backup-storage. BE 2012 is installed on another server, with attached tape drive. During backup, data movement on LAN is: HP -> backup server -> HP. I am concerned about the read-write activities on the HP during backup. What kind I do to make it more efficient? Thanks for the advice.Solved491Views2likes3CommentsBE 2012 CASO Managed Server Missing Job Logs. Unofficial Fix Included.
Hi all, I encountered a frustrating problem in the past few days. After many colourful adjectives, alcoholic coffees, and random displays of primitive aggression, I am happy to announce that I have found a solution, and would like to share it with you. Please note that, as with anything unofficial, this is a "use at your own risk" solution. Environment and Setup: 1x Backup Exec 2012 server, fully patched SP1a, running as a Central Admin Server (Referred to as the CAS from hereon) 1x Backup Exec 2012 server, fully patched SP1a, running as a Managed Server using the Centrally Managed Backup Exec Server Mode and the Unrestricted Access To Catalogs and Backup Sets For Restore mode. (This server will be referred to as the MMS from hereon) The CAS was installed in a non-default path: D:\Backup Exec The MMS was push-installed from the CAS, to the BE default path: C:\Program Files\Symantec\Backup Exec Note: The path difference between the two servers is supported, and has always been so in previous Backup Exec versions. It even lets you change the path during the push install of a new managed server. The CAS and MMS have shared access to a single tape library using the Shared Storage Option (SSO) that comes with the Enterprise Server Option license. Load balanced backup and restore jobs work fine; the two servers happily share/queue the limited tape drive resources. Note: You can still encounter the problem discussed below, even with other storage device types, shared or non-shared. Problem encountered: Normally, after every backup or restore job - successful or failed - you could right click on a job inside the "Job History" list, click "View Job Log", and be presented with the job log for a particular job. However, I found out that some jobs wouldn't let me select the "View Job Log" option. This option was simply "greyed out". I was not allowed to read the job logs for some jobs. Upon inspection and after some tests, it was clear that only the jobs that are delegated to the MMS have this problem. (I.e., Data written to the storage device via the MMS server, or read from the storage device via the MMS server. The "storage device" here being my tape library.) The jobs that are delegated to the CAS don't have this problem; the right click option is not "greyed out" and I can view their job logs without problems. Solution / Workaround / Unofficial Fix: Log on to the MMS server locally. Inspect the "Job Log Path" attribute via: Top left BE Button > Configuration and Settings > Backup Exec Settings > Job Logs > Job Log Path (You will notice you can't change its path value.) Anyway, upon inspecting it, I noticed that it is using the path that the Central Admin Server is using! In my case, it is showing: D:\Backup Exec\Data But then, my MMS doesn't use that installatoin path, it uses: C:\Program Files\Symantec\Backup Exec Which means its job logs directory should be: C:\Program Files\Symantec\Backup Exec\Data I figured that it doesn't let me change the path here, so I fired up BEUtility.exe. (Remember I am doing this on the MMS, not on the CAS) I clicked the option "Set Job Log and Catalog Location", then I changed the "Job Log Location" to: \\<MMS hostname>\C$\Program Files\Symantec\Backup Exec\Data (Yes, you have to use the UNC path format) It.......... didn't work. An error tells me that it couldn't find the folder D:\Backup Exec\Data, which makes sense because this is the path used by the CAS, not the MMS. So I created this empty folder on the D: drive (Lucky me that my MMS server has a D: drive...), tried the "Job Log Location" change again, and it finished without errors. Effectively Backup Exec was tricked into thinking that it moved the job logs from D:\Backup Exec\Data to C:\Program Files\Symantec\Backup Exec\Data. Next, I deleted the D:\Backup Exec\Data folders on the MMS because they are no longer needed. Back on the CAS, I delegated some jobs to the MMS, jobs finished, and the "View Job Log" right click option is now working again on these new jobs. Thoughts: I'm pretty sure this is a programming mistake. A minor one though; I hope this will be patched soon. RLeon470Views2likes1Comment