Deduplication folder stays offline
Forum, We upgraded Backup Exec from 2010-R3 to 2012-SP1. We have the dedupe option for both versions. The upgrade was done two weeks ago and we have been running dedupe jobs successfully. Now the deduplication folder will not come online. We have about 10TB of backups extending back 6 months. Under “Storage” this message is displayed next to the dedupe folder: This device has not been discovered correctly. Cycle the services on _CoSRV-BEX to retry device discovery. This alert is also logged: Backup Exec was unable to initialize and communicate with the device [SYMANTECOstLdr MACF] (The handle is invalid.). Click the link below for more information on how to diagnose the problem. http://www.symantec.com/business/support/index?page=answers&startover=y&question_box=V-275-1017 note the above link is for 2010, not 2012. Actions taken: Using the BE Services mgr, the services were recycled (many times) – no improvement. The server was rebooted – no improvement. Using the BE Services mgr, the services (including the dedupe services) were recycled – no improvement. The server and drive array were powered off and powered back on. All is normal. We did recycle the services with and without the dedupe services after this power up - no improvement. FYI We have a Dell PowerEdge R710 and an MD1200 array for the local D: drive, which has the dedup folder and nothing else. The server runs Win Server 2008R2 and has 64GB RAM. There are no hardware errors. The physical array is normal and drive D can be browsed. Live Update shows we are up-to-date. Some google searches suggest solutions for 2010, not 2012 . . . that the solution is to remove the target servers from the devices window, and disable client side dedupe. How can that be done in 2012? I have opened a support ticket with Symantec, but I cannot get them to call me back. Symantec advises that they will have the Deduplication support team call me back. I was promised a call back 3 ½ hours ago, but that hasn’t happened. I have called back twice with the ticket number and been shunted over to the voice mail of engineer that owns the ticket. Is there any hope for this? Should I look for a replacement to Backup Exec? ... Frustrated and hoping we don't have to restore anything.Solved4.2KViews25likes2CommentsE0008821 - Job was recovered as a result of Backup Exec RPC service starting
Hello, I have Symantec BackUp exec 2010 in a windows sbs 2008 standard, with a strategy Grandfather . I'm new here (the guy who was in charged before left, and also de server is in German and I don't speak German). The last monthly copy didn't work because of E0008821 - Job was recovered as a result of Backup Exec RPC service starting (with initial hour 31/March/2012 23:00:04 and finalize at 31/March/2012 23:00:02), and also the last 6 weekly copies didn't work for the same reason. I don't know what to do, what do you think about this? You have Domino/Notes? If yes do the registry changes HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\DOMINO\ Enable Change Journal = 0 Enable Notes Database Filtering = 01.1KViews8likes2CommentsTECH184002 - Further solution coming for backup exception "Failed to load the configuration xml file..."?
KB Article TECH184002 was updated today with a solution, one which is underwhelming at best. In many cases, including ours, adding a physical disk to the server just to make a backup error go away is simply not an option. The bottom line is that if the "Convert to Virtual" option is not enabled for a backup, it shouldn't matter whether any of your disks support that feature. Hopefully this is only meant as a workaround and a proper fix is forthcoming. Thanks...398Views8likes2CommentsVerify Fails on Incremental Backup to Disk - BE 2010 R3
Backup Exec 2010 R3 I do incremental backups to disk on about30-40 servers. Recently all of the servers being backed up were failing to verify, despite the actual backup looking like it ran fine. The catalogs seemed to represent everything accordingly and I could restore data. I tried rebooting the server hosting Backup Exec, and also restarted the storage device (Snap Server), but this did not help. The error on the verify: The query for media sequence number -32768 of this media family was unsuccessful. Ensure that all media in the family have been inventoried and cataloged. I showed this to a colleague andhe recognized that -32768 was the minimum value for a short integer. This led him to believe that we had somehow maxed out the number of media sequencespossible. What we found out was that the media set being used had the Append Period set to "Infinite - Allow Append". Our B2D device media is 1GB each, our incremental backups are around 200-300GB per day. I would assume that the media sequence number would get changed per backup job. So for example, my nightly incremental being 300GB, the highest media sequence number would be in the low 300's (1 media sequence number for each gigabyte, since the device media is 1GB each). I would also think that a full media event would reset the media sequence number in which case it would seem impossible to max out. What it seems like is that with the Append Period set to Infinite, the media sequence number never gets reset, but just continues to increment by 1 until it reaches the maximum value for a short integer. I resolved the issue by changing my Append Period to 1 hour. I don't know if this allowed the media sequence number to start over or what, but it did seem to resolve the issue for me. In hindsight, I don't know why I would ever want the append period set to indefinite on a B2D scenario where the incrementals are only retained for 2 weeks anyway. I also don't understand how I would be able to restore anything if the media is improperly sequenced. Hope this helps someone...or maybe someone else can offer further explanation. Aaron1.1KViews6likes7CommentsBackup of Esx host failing
Hi, I have a 2008 server running backup exec 14.1 Rev 1786 with the Agent for VMware and Hyper-V installed. I am trying to create a backup job to backup all the vms on a Esxi 5.5.0 host. I have added to root credentails for the esx host and backup execis able to browse the host and see all the vms and vmdks but the job fails with the following error "The logon account that was provided does not have valid credentials.Ensure that the user name and password are correct, and then try again." The credentials test is sucessfulon the host but not on the vms. The host isnt part of a domain Do I need to have credentials for each VM? Thanks530Views5likes2CommentsSymantec Backup exec 12.5 Help
Symantec Backup exec 12.5 on windows 2008 with a robotic tape library fujitsu eternus 120 i have isntall the software and licenses , follow the steps created the jobs but they allways fail, is like the program and the tape unit don comunicate and i'm useing the recomended drivers just how it sys in the isntalatio, in a inventory just stais there without end947Views5likes5CommentsHow to increase the time out for Backup Exec 2012 UI
If you get the time out error as: The request channel timed out while waiting for a reply after 00:09:59.9980000. Increase the timeout valuepassed to thecall to Request or Increase the sendTimeout value on the Binding. The time alloted to this operation may havebeen aportion of a longer timeout. This means, the UI of Backup Exec 2012 has waited for 10 minutes for the underlaying services to reply back. If you want BE UI to wait for longer time (let us say 20 minutes), Stop the UI. Open the file BackupExec.exe.config (located at Program Files/Symantec/Backup Exec) Replance all the occurrences of 00:10:00 with 00:20:00 Start the UI. My Senario: In my case, a report was taking more than 10 minutes to generate (pretty sad, but dont worry, developers are working continuously for better performance). So I increased the sendTimeout of 'NetTcpBinding_Job' to 20 minutes, And boooom !!, the report got executed successfully in 14 minutes.Solved1.2KViews5likes1CommentBE2012 keeps crashing for no reason, huge BEX*.XML Files (45GB)
Hi, i have some jobs running for ever and the complete backup chain is not working anymore. Most of the time, the backup exec engine is not responging anymore, even a restart of the service doesn´t work. I always need to kill the engine. In this situation i always found huge BEX*.XML Files in the symantec backup exec subfolder. the last one had 45GB, 9GB, 5GB ... in size. With these files in place it´s not possible to restart the services. After i move these files to a tmp folder, everything looks fine. I had 2 cases open, but symantec wasn´t able to find the problem at all. Anyone with more information for this obvius bug?Solved444Views5likes2CommentsQuestion : Regards backup exec 10d
Issue is Server was carashed re-built a new server with same hardware and trying to restore the backup from old server to a new server Getting error : Invalid physical volume library media identifier. Customer want to know if this is related to hardware issue or software issue ? I found a KB link : "Invalid Physical Volume Library Media Identifier" (a0008105 HEX or e00008105 HEX) is reported when a restore job fails. Please let me know If the above KB link will be helpfull ?990Views5likes8CommentsServer Agent out of date
I started seeing LiveUpdate Information About the agent for windows on at least one server does not have the most recent updates? To Install the most recent updates, on the Backup and restore tab, right click the remote computer that is out of date, and then select Update. 1.There is no indication on what server agent is out of date 2.After right clicking on each server on some I can see Update is grayed out and on some its clickable 3.Does this mean they are out of date and need to be updated? 4.What happen if I update the server will I have to reboot? 5.The server is Windows 2003 with exchange 2003 running on a cluster serves with 2 nodes 6.It seem each node might need the upgrade and the cluster seems to need 7.I am assuming after I update the active node the cluster will be up-to-date 8.Should I manually run LiveUpdate on the backup Exec server monthly and after an update I should update the clients?1.2KViews5likes18Comments