VSS 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 outSolved30KViews2likes9Comments
BackupExec 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.26KViews0likes6Comments
V-79-57344-41488 this backup cannot be used for conversion
Hi I am getting this error on Backup Exec 15 only on the System State Job: V-79-57344-41488 - Due to one or more errors in \\SERVERNAME.misc.local\System?State, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore. V-79-57344-33928 - Access Denied. Cannot backup directory \ and its subdirectories. Only System State is selected on the selection list There is a Full and Incremental AOFOis switched on Does anyone have any ideas?18KViews0likes16Comments
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Running Backup Exec 12.0 Small Business Server Suite Rev. 1364 og getting random failing file data-backupjobs with error code E000FED1: Backup- E: DataV-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Event Logs, Writer ID: {EEE8C692-67ED-4250-8D86-390603070D00}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Windows Internet Name Service, Writer ID: {F08C1483-8407-4A26-8C26-6C267A629741}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10). When runningVSSADMIN LIST WRITERS - command from prompt I'm given the following output: C:\Documents and Settings\xxx>VSSADMIN LIST WRITERS vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {e1eae7cb-e621-4ab2-ba63-e5a534cc5e7a} State: [1] Stable Last error: No error Writer name: 'FRS Writer' Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} Writer Instance Id: {51359454-ca5e-44f2-bbde-6fd81712dcc1} State: [1] Stable Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {dc2f12b7-d951-41ba-8724-bc474e7a5f7e} State: [1] Stable Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {5cb6d93a-bb72-4a0d-b90b-e6174402c580} State: [1] Stable Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {a0bbbb7a-8d3d-47ae-93b2-7f7e008365d0} State: [10] Failed Last error: Retryable error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {3be2277a-66e1-43f1-a484-446320b9681f} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {23e6136d-6943-4108-90cb-a40089bad1b9} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {8ae68311-ead2-4af4-8009-874337783ecc} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {bc0eb6b5-835b-4a97-a8d0-7ba5f6db426e} State: [1] Stable Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {8a3a101e-0dfd-46a2-9334-8ac0d57bf929} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {af7bf8db-a57e-47a8-a0b5-3a754d46f58a} State: [1] Stable Last error: No error The following warnings and errors is shown in Windows Event Viewer: Event Type: Error Event Source: ESENT Event Category: ShadowCopy Event ID: 2004 Date: 09-10-2012 Time: 01:09:09 User: N/A Computer: SERVER01 Description: wins (3316) Shadow copy 13 time-out (70000 ms). Event Type: Warning Event Source: VSS Event Category: None Event ID: 12290 Date: 09-10-2012 Time: 01:09:29 User: N/A Computer: SERVER01 Description: Volume Shadow Copy Service warning: ESENT ERROR {f08c1483-8407-4a26-8c26-6c267a629741} WINS Jet Writer: -2402. hr = 0x00000000. Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Date: 09-10-2012 Time: 06:20:30 User: N/A Computer: SERVER01 Description: Backup Exec Alert: Job Failed (Server: "SERVER01") (Job: "MANDAG-DATA") MANDAG-DATA -- The job failed with the following error: A failure occurred querying the Writer status. The data selected for the backup-job is pure files and System State. The server is a Windows Small Business Server 2003 SP2.Solved18KViews1like12Comments
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 ;) .Solved17KViews0likes10CommentsA failure occurred querying the Writer status.
Dear all, Since some weeks I have been experiencing this horrible error. I have consulted the Symantec Support pages, but I can find no 'permanent' solution for the environment I am using. Rebooting the server every day is not an option, this is the fileserver that people access remotely almost nearly 24/7. It also doesn't seem to work, the first one or two backups after a reboot work but then it just goes back into the error listen in this threads topic. There is also a suggestion about freeing more space on C:\, I think there is enough (see below). My backup server is Windows Server 2008 R2 Standard. It's fully up to date up with the most recent Windows Updates. This is a physical server. The server I am having trouble with is Windows Server 2012 Standard. It's fully up to date up with the most recent Windows Updates. This is also a physical server. It has a C:\ drive with 125GB free of 150GB It has a D:\ drive with 1.6TB free of 1.6TB It has an E:\ drive with 2.2TB free of 5.5TB I have attached a screenshot showing the amount of times this server won't backup properly because of the above error. The worst thing about it is because I am backup up such an immense amoutn of data it takes about 25-30 hours to do a full backup. But it doesn't go into error until it's completely done! How can it POSSIBLY give a Writer error status at the very end of the backup process!! How is that even possible? The writer error is about failing to make a snapshot, why does it not INSTANTLY see that theres a problem and goes into error, why do I have to wait for 30 hours in anticipation to see if the backup software does why I purchased it. I have 53 servers to backup which takes me over four days, if my fileserver goes into error my entire backup schedule for that week goes out the window. This is becoming increasingly annoying.I don't want to have to come in on weekends because the backup software andomly decides it doesn't want to work. I'd like to add that my Exchange server also experiences this problem, except not that often. It's just as annoying though as you can understand that if my fileserver gets used 24/7 the Exchange server can't exactly get a daily reboot either. It's even more of a pita to reboot. All my other servers never have any problems, physical or virtual. Hyper-V or V-Sphere. It just works. Please advise. ThanksSolved17KViews1like7Comments
Disk is Full - How to Delete Old Backup Jobs
Hi All, We have 12TB of Disk space using BE2010, disk is now 92%. I set the option the option to delete overwritable backups few weeks ago. Disk space looks like paus there and not expanding any further. Could some one please advise - what is the best way to erase old backups, I have attached one picture from one of the backups but I don't understand what to erase, advise would be highly appreciated. Thanks NysohSolved17KViews1like4CommentsBackup Exec 2014 - Stuck on 'Discovering Resources'
Small Business Server 2011 - fully patched and freshly rebooted Backup Exec 2014 Small Business Edition - fresh install Set up a Friday full job and a Monday-Thursday differential jobs to a set of USB drives that are rotated. The Friday full job sits on 'Discovering Resources' for HOURS. I started the job almost 7 hours ago and it has not backed up a single byte. There is no one on the server, no open files, nothing going on. Resource monitor is very quiet. Thoughts as to what is going on?Solved17KViews1like7Commentsall devices stuck at "discovering devices
I have an issue with my media servers where all devices get stuck at "discovering devices" and service restart or reboot of the server. We are running BE2010R3 on windows server 2008r2 platform. I know back in the day there was a regedit for diodrivers as a temp fix, but need to get this resolved permanently ASAP.Solved16KViews1like5CommentsProblem with VSS ASR Writer
Hi all, I'm using Backup Exec 2012 fully patched on Windows 2008 R2 standard SP1 Very often I have a situation that many backup jobs failed for various reasons. The weird thing is that the very same jobs run perfectly for many days (with the same selections for the same remote servers) until I get to the point with massive failures. After that, (because I know now what is the cause most of the times) I have to check the VSS writers status where I'm always getting the ASR writer in failed state or waiting for completion. This is a really frustrating situation because I can't be rely to the continuity of backup operations. Finally, what is the reason that the ASR writer in getting into unstable status so often? Is there any other workaround to bring it back to a stable status without a server restart? Is it a Symantec or a Microsoft issue and is there any released to public patch that I can use? Please help guys! Honestly, it is not a solution to have to restart a server (Media, Exchange, etc) because every now an then a writer fails. Many thx in advanceSolved15KViews2likes17Comments
BackupExec 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.V-79-57344-41488 this backup cannot be used for conversion
Hi I am getting this error on Backup Exec 15 only on the System State Job: V-79-57344-41488 - Due to one or more errors in \\SERVERNAME.misc.local\System?State, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore. V-79-57344-33928 - Access Denied. Cannot backup directory \ and its subdirectories. Only System State is selected on the selection list There is a Full and Incremental AOFOis switched on Does anyone have any ideas?