Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

V-79-57344-38308 on my Full File Server backup by VMware agent

Created: 23 Aug 2012 | 11 comments

All my Full File Server backup by VMware agent failed with the following error

 

V-79-57344-38308 - The Virtual Machine resource is not responding. Backup set canceled.
 
Even backup is finished and I can use it for restore. Teh error apperias because it's taking long time to remove shapshot from VMserver.
Can I extend this time, to avoid teh error?

Comments 11 CommentsJump to latest comment

lampar's picture

 

1. Remove the provisioned disk from Vshpere client. OR

2. Allocate the Disk in the Guest VM under Disk Management.

3. Delete the Snapshot (If present) under Snapshot Manager.

                had 4, deleted all

4. Browse to Datastore and check for any old Snapshot files under Guest VM folder.

                 no snapshots in Datastore Browser

5. If Snapshot files present, Take new Snapshot through Snapshot Manager.

                 Should I Take new one?

                  I did it anyway

6. Open the Snapshot Manager and check whether old snapshot listed.

                  only one in a list

7. Delete all the snapshots including the old one.

                  deleted it

8. If old Snapshot not present, then delete the snapshot files from Datastore.

                  no spanshots

9. Re-Try the backup job and it should work.

                  sparted job and will inform as soon it's over

 

lampar's picture

 

after full backup I got the same error!

 

V-79-57344-38308 - The Virtual Machine resource is not responding. Backup set canceled.
 
On Snaphot Manager i have Consolidate Helper - 0 (Helper snapshot for online consolidate)
On Datastore Browser one .vmsn snapshot file
 
So, simes this solution is not my case
King_Julien's picture

Got this same issue on random servers. I don't know what else to do...

 

A second of your life, ruined for life.

VJware's picture

Would you please confirm if there is an application error (event id 1000) on either the Backup Exec media server or the remote servers ?

King_Julien's picture

Hi VJware, 

I just checked the event viewer of my media server and I found an event id 1000 but is not the same as http://www.symantec.com/business/support/index?page=content&id=TECH153800, still, just in case, I checked the option "Enable TCP dynamic port range" and let's see what happens during this weekend, got to backup 5 Tb only in fileservers, that's sad because I can't run those backup during productive hours to do some tests, I have to wait till next monday to see the status.

By the way, I also checked on my vsphere server, but I didn't found any event 1000.

The issue occurs both on Windows and Linux VM's, and it' s random, as I mentioned before I don't know what else to do about this, it seems that the backup fails at the end. My most recent failed backup is from yesterday. It started to run at 6:30 PM and fails after 8 hours, after backing up 832 Gb. 

 

 

Media Label: IMG000742
GRT backup set folder: \\XX.X.XX.XXX\XXXXX\IMG000742
Transport mode 'hotadd' was used for the disk 'xxxxxxxxxxx.vmdk'
Transport mode 'hotadd' was used for the disk 'xxxxxxxxxxx.vmdk'
Backup Exec has discovered and protected 'C:' on virtual machine 'xxxxxxxxxxxxxxxxxxx'.
Backup Exec has discovered and protected 'E:' on virtual machine 'xxxxxxxxxxxxxxxxxxx'.
V-79-57344-38724 - Directory 'E\TEMP' does not support Granular Recovery Technology (GRT).  Granular restores cannot be performed for items in this directory.
V-79-57344-38275 - The Virtual Machine resource is not responding. Backup set canceled.
 
Backup completed on 25/01/2013 at 03:06:22 a.m..
 
Backup Set Summary 
Backed up 1593144 files in 223027 directories.
Backed up 1 virtual machines
Backed up 2 virtual machine disks
Processed 884936467998 bytes in  8 hours,  33 minutes, and  48 seconds.
Throughput rate: 1643 MB/min
 
 
I was just told by the sys admin that the E drive is a dynamic disk so I must disable GRT for this job, the main error is V-79-57344-38275 - The Virtual Machine resource is not responding. Backup set canceled, that file server has 1 Tb in total and just 832 gb were backed up. 
 
thanks in advance.
 
 

A second of your life, ruined for life.

VJware's picture

Would you pls post a complete description of the event 1000

King_Julien's picture

Hi VJware, 

Here's an extract from another job.

Backup started on 21/01/2013 at 06:52:56 p.m..

 

 
Backup Set Detail Information 
Transport mode 'hotadd' was used for the disk 'XXXXXXXXXXXXXX-000003.vmdk'
Transport mode 'hotadd' was used for the disk 'XXXXXXXXXXXXXXX(1)-000003.vmdk'
V-79-57344-38275 - The Virtual Machine resource is not responding. Backup set canceled.
 
Backup completed on 21/01/2013 at 06:54:59 p.m..
 
On the event viewer of that VM, there's nothing such as event id 1000; Instead I found this event generated two minutes ago of when the backup was "completed" 
 
Log Name:      Application
Source:        VSS
Date:          21/01/2013 06:56:12 p.m.
Event ID:      8224
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Description:
The VSS service is shutting down due to idle timeout. 

 

I did a vssadmin list writers command on that server and all of them are stable with no errors. 

On the media server, I got the following event id from that time/date, I don't know if it's related to it.

 

 

Log Name:      System
Source:        VDS Basic Provider
Date:          21/01/2013 06:56:07 p.m.
Event ID:      1
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXXXXXx
Description:
Unexpected failure. Error code: D@01010004
 

Still, this is a random behavior, I don't know when it's going to work or when it's going to fail.

 

Regards, 

 

 

A second of your life, ruined for life.

VJware's picture

The event 1000 would be on the media server... could be possible beremote.exe is either stopping/crashing during VMware backups... if so there is a workaround...however need to confirm if there is such an event logged or not.

King_Julien's picture

 

Hi, 
 
I just get in the office, I checked the application event viewer and I found this event id 1000 from yesterday. 
 
Log Name:      Application
Source:        Application Error
Date:          29/01/2013 10:00:33 p.m.
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MYMEDIASERVER
Description:
Faulting application name: vds.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc520
Faulting module name: vdsutil.dll, version: 6.1.7600.16385, time stamp: 0x4a5be07e
Exception code: 0xc0000005
Fault offset: 0x0000000000013904
Faulting process id: 0x17fc
Faulting application start time: 0x01cdfde5e1b8a6cd
Faulting application path: C:\Windows\System32\vds.exe
Faulting module path: C:\Windows\System32\vdsutil.dll
 
14 minutes later, I found this related to beremote:
 
Log Name:      Application
Source:        BEDBG
Date:          29/01/2013 10:14:32 p.m.
Event ID:      257
Task Category: (1)
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      MYMEDIASERVER
Description:
A memory dump has been captured C:\Program Files\Symantec\Backup Exec\BEDBG\beremote.exe_2700_2.dmp
 

In fact, I take a look into that directory and I have some dmp files. 

 

Is that the event ID 1000 you were asking about?

 

 

Regards,

A second of your life, ruined for life.

King_Julien's picture

Just in case... Another event 1000, but this was generated while I was retaining some backup sets

 

 

Log Name:      Application
Source:        Application Error
Date:          15/02/2013 11:14:31 a.m.
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Myserver
Description:
Faulting application name: BackupExec.exe, version: 14.0.1798.105, time stamp: 0x4fa3e005
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0
Exception code: 0xe0434352
Fault offset: 0x000000000000aa7d
Faulting process id: 0x87c
Faulting application start time: 0x01ce0aee95ec9503
Faulting application path: C:\Program Files\Symantec\Backup Exec\BackupExec.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 0371e639-777a-11e2-a2c4-005056c00008
 
__________________________________________
 
Log Name:      Application
Source:        .NET Runtime
Date:          15/02/2013 11:14:31 a.m.
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Myserver
Description:
Application: BackupExec.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
   at System.Windows.Window.set_Owner(System.Windows.Window)
   at BackupExec.App.DisplayApplicationError(System.Exception)
   at BackupExec.App.App_DispatcherUnhandledException(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
   at System.Windows.Threading.Dispatcher.CatchException(System.Exception)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run()
   at BackupExec.App.Main()
 

Are any of them related to your event id 1000 ????

A second of your life, ruined for life.