Backup Jobs are getting failed with V-79-57344-41488 - Due to one or more errors in \\server\E:, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore.
Hello All, We are using Backup Exec 2014 SP2 In a Windows 2012 R2 server as a media server and taking backups of the Clients through Remote agent. Few are windows 2008 server and one of them is Windows 2012 R2 server. The issue started with the Win2012 R2 remote agent while backing up the backup is getting failed for the drives with the above mentioned error.The files are normal flat files. Media Server : Windows 2012 R2 64 bit Remote Agent : Windows 2012 R2 64 bit I have tried to take backup of those problematic folder through WIndows server backup however it got successful in that case. The account which we are using for taking backup is domain user however its been added to remote agents local admin too.But no luck. Would appreciate if any wrokariound or solution can be provided except asking for upgrade it to BE 15 ;) .Solved17KViews0likes10CommentsReady; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks28KViews1like11CommentsBE 2012 - After migration, storage pools but no storage devices
Migrated our BE 2012 server using the steps in the article below. We moved from a Win2K8 R2 Enterprise OS to Win2K8 R2Standard OS for licensing reasons. Everything seemed to migrate successfully except for the storage devices which are simply network drives/shares. In the BE console on the new BE server, the storage pools, that were on the old BE server, are there and the properties of the storage pools show the related storage devices. The problem is that the storage devices do not show up as individual devices on the storage tab of the BE console, so I cannot edit the properties or even use them with the migrated backup jobs. I tried renaming the old BE server and taking it offline, then renaming the new BE server to the old BE server name, but I could not log into BE using the old or new name after that. I put the new name back into place so now I'm back at square one again. I thought about just configuring new storage devices with new names but I'm concerned about how that will affect my ability to restore existing backed up data that is on these drives. Ideally, I would like to get some help on how I can get this migrated BE server to recognize the storage devices again. https://support.symantec.com/en_US/article.TECH129826.html Thank You, RA914Views0likes3CommentsBacking up Active Directory: V-79-57344-33928 - (AD LDS) database was not found.
Hello, We have this error from time to time, but it usually fixes itself without any end user intervention. However I am getting this error three nights in a row now on one of our domain controllers. This started happening on Wed morning, and continued through Friday morning. In all three instances the error message in the log is: Job ended: Thursday, October 29, 2009 at 1:18:54 AM Completed status: Failed Final error: 0xe0008488 - Access is denied. Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-33928 Errors Click an error below to locate it in the job log Backup- \\dc1.domain.com\System?State V-79-57344-33928 - Unable to complete the operation for the selected resource using the specified options. The Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) database was not found. So I checked the selections and under the server in question, I can see System State > Active Directory > C:_WINDOWS_NTDS, and this is all checked off. I did a test Resource Credentials for everything in this backup and it all returnedsuccessfulso I'm at a loss. Under Settings > Microsoft Active Directory for this job properties we have all three boxes checked (GRC, Consistency Check, Continue if Consistency check fails.) Backup method is greyed out, but says Full - Back up entire Active Directory. We are using Symantec Backup Exec 12.5 for Windows Servers Media Server Version 12.5 Rev 2213 Administration Console 12.5 Rev 2213 Desktop and Laptop Option: Version 3.1 Rev. 3.41.32a Installed updates: Service Pack 2 Hotfixes: 324947 317436 325647 319242 324012 326004 323894 324011 Thanks for the help, we really do appreciate it!3.2KViews0likes11CommentsError V-79-100000-11223 VSS Snapshot Error
I am using Backup Exec 2014 - Server Version is 14.1 Rev. 1786 (64 Bit) I created a backup job on a new server with the standard Full/Incremental backup set. I did *not* select the Snapshot Option - that tab is completely blank. When I run the job, I get: -Snapshot Technology: Initialization failure on: "\\IGSBACEBGS017.gs.doi.net\Shadow?Copy?Components". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected cannot snap this volume. Some reasons for this could be: - The snapshot provider that you selected does not support the volume that you are trying to snap. Try selecting the default snapshot provider, and then run the job again. -A disk with a size greater than 63 terabytes or a 4K sector disk may exist on your computer. These types of disks can cause VSS to stop unexpectedly when it creates snapshot This server is 72 Terrabytes (native) but with formatting and RAID it shows as a 60 TB drive. The sector size is the standard 512. How can I back up my share? Doesn't Symantec Backup Exec work on large drives? Why does it try to force the snapshot option even though it is not selected? Thanks in advance for your help!!!Solved3.8KViews0likes5CommentsAdamm Mover Error After Upgrading to SP4 on Backup Exec 2012
Since upgrading to sp4 on Backup Exec 2012 I am seeing this error on a couple servers pretty frequently. Before sp4 I was not seeing this error. [6484] 05/13/14 15:45:01 Adamm Mover Error: DeviceIo: ndmpSendRequest->connection error to 192.168.3.70:10000, 100542.4KViews0likes8CommentsUnable to delete managed backup exec server from caso
Hi, I'm unable to delete managed backup exec server from caso server. I think I started to do this in wrong way because I first uninstalled the backup exec server from managed server. Now in caso server I try to delete managed server but I get error. How I can delete managed server from caso in situation where managed backup exec server is allready uninstalled? Br.MattiSolved1.7KViews0likes5CommentsEnterprise Vault Databases unavailable for selection after Agent Backup
Hello forum, we have a case where the BE Agent for Enterprise Vault (BE 2012) was tested for evaluation purposes in the past but it was decided to switch back to normal script based backups (where the SQL Database would be backed up normally through the BE SQL Agent). The issue is that even after uninstalling the RAWS from the EV Server and removing the "Directory on ..."-Entry from the serverlist the EV databases are still grayed out when creating a new backup job. All other Databases on the same SQL Server are available for selection so the issue is only with the EV databases - presumably because BE still things they are backed up via the EV agent. The EV Agent itself cannot be removed from the installed options on the BE server (like in erlier version) as it is now included in the "Agent for Applications and Databases"-Option. We even removed the entries from the NRDSAgent-Table - the checkboxes for these databases remain grayed out though. Any ideas on how make them selectable again?Solved1.2KViews2likes2Comments"the query for ResourceContainer failed" BE2012 - Clean Install
Hi All, just want to share the problem i have with BE 2012. It is a clean fresh installation on clean newly installed Win2008 R2 SP1 (all pre-checks passed fine). After remote push of 2 agents and creation oddedupe folder, the console reports error in lower left corner of the screen saying : "The query for ResourceContainer failed". The result is that nothing is visible inside GUI anyomore (groups, agents, jobs...). Debugging shows : MANAGEME: [03.27.12 15:00:28] [0000] ERROR: Reason: DataAccess DataAccessBEServer QueryResourceContainer: caught an exception:Invalid column name 'finaljobstatus'.. MANAGEME: [03.27.12 15:00:28] [0000] ERROR: Stack: at BackupExec.Management.Components.DataAccess.DataAccessBEServer.QueryResourceContainer(ItemCriteria& queryInfo) I have tried reinstall, removal of installation, deletition of profile, registry keys, deletition of all associated folders and tried a clean install, also i have trye dusing another SQL server as opposed to using SQL express, but always the same error appears (will have to rebuild the server form scratch it seems). Any ideas? Ayone seen this before? Thanks. All the best, KresimirSolved5.8KViews1like13Comments