Expired backup sets not deleted
Anybody solved that problem with Expired backup sets? I can see them expired, Allow Backup Exec to delete all expired backup sets is enabled, but BE does not delete them even when there is no disk space on storage. I saw some other posts but are few month old... Besides with no solutionSolved34KViews1like10CommentsVSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed outSolved30KViews2likes9CommentsReady; 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. Thanks28KViews1like11CommentsBackupExec Agent for Mac OS X Server not working
I cannot seem to get the BackupExec agent for OS X Server working. I have an XServe running 10.6.4 and RALUS/RAMS 2896.9 (2010r2). I have gone through the installrams script and verified everything is correct. All ports between my server and the backup server are open while troubleshooting this problem. The admin for the backup server has verified everything is correct on his end. Whenever he goes to connect to my server, it is killing the remote agent on my server. I have restarted with the logfile option and can attach if needed. The only thing that stands out to me is that some of the dylib's are not being loaded even though I have added that directory (/opt/VRTSralus/bin) to my DYLD_LIBRARY_PATH variable. Everything else looks normal, at least to me, but the agent is killed when the backup admin tries to connect to it from the BackupExec Console.26KViews0likes6Comments0xe000feb9 - The NDMP subsystem reports (Any real fixes or work arounds)
OK I have seen and read quite a few posts on this matter, with very few solutions. Here is my issue. Here is what I am having for an issue. Iam using the BackupExec 11D (7071) and backing up Windows Systems. The majority of my jobs run fine. There are a few jobs that error out because of the *** Completed status: Failed Final error: 0xe000feb9 - The NDMP subsystem reports that a request cannot be processed because it is in the wrong state to service the request. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-65209 **** I have checked out the port 10000 on the affected servers. The port on the affected system is used by Client system I have uninstalled rebooted reinstalled on the affect system with no change. Changing the port on all the servers is not a good option as the amount of systems that is affected is not large, and change it on good systems I fear may cause more harm then good. So anyone have a good solution for htis or a wokr around for the affect systems to be able to back them up? Thanks for any suggetions.24KViews0likes12CommentsImpressions of BackupExec 2012
Is it just me, or does anyone else absolutely HATE the redesign of Backup Exec? I have worked with BE since version 8, and I have become acutely familiar with the menus, where everything is, and how it works. This redesign of the UI reminds me of the differences between Microsoft Office 2003 and Office 2007, only much worse. Menus are now hidden behind other menus, and everything has a completely counter-intuitive feel. At first, I thought that the feeling would pass as I grew more familiar with the product, but in fact my dislike has grown as I have found more issues. Does anyone else feel the same way?22KViews56likes417CommentsBackup exec management services could not be started
I am facing issue in Backup exec 2014. When i started backup exec console then it first ask for credentials and then gave an error "Backup exec management services could not be started. Backup exec database is offline, turn it online then restart backup exec services" i re install the backup exec 2014 but still have the same issue. Platform consist of Windows server 2008 R2 standard and also it consist of SQL 2008 which is running by client but Backup exec database use its built in database.Solved22KViews1like14CommentsERROR: Failed to register/unregister D:\Program Files\Symantec\BACKUP~1\NT\
I am attempting to install Backup Exec 11d and i am getting the following errors:- 02-16-2007,09:16:28 : ERROR: Failed to register/unregister D:\Program Files\Symantec\BACKUP~1\NT\pvcalendar.ocx with regsvr32. 02-16-2007,09:16:28 : V-225-121: Error configuring RA main module ***To search for information about this error, click here 02-16-2007,09:16:28 : Action ended 09:16:28: InstallFinalize. Return value 3. and this one:- 02-16-2007,09:16:53 : V-225-205: ERROR: User does not have permission to alter database 'BEDB' or the database does not exist. ALTER DATABASE statement failed. sql:alter database set offline with rollback immediate ***To search for information about this error, click here I have followed the advice given for this one at http://seer.entsupport.symantec.com/docs/285131.htm But this didn't solve the problem. Can anybody help me please?19KViews0likes1Comment