Hi,
i'm backing up my HyperV environment using the HyperV Intelligence Policy.
all other hyperV client backed up fine except one which running Windows 2003 Enterprise Edition 32bit.
Is Windows 2003 Enterprise Edition 32bit not longer supported?
please advise.
TN with list of possible reasons for status 156: http://www.veritas.com/docs/000067928
You can access all Compatibility Guides here:
Master Compatibility List: http://www.veritas.com/docs/000033647
NBU 7.7 OS SCL: http://www.veritas.com/docs/000025229
Guest OS compatibility in:
Statement of Support for NetBackup in a Virtual Environment: http://www.veritas.com/docs/000006177
Look for this topic:
Supported Hyper-V guest operating systems
NetBackup for Hyper-V supports virtual machine backup and recovery on all guest operating systems supported by Hyper-V. For a list of operating systems that Hyper-V supports, consult the following: http://support.microsoft.com/kb/954958
Table 24 lists the supported Guest OS's. Win2003 still appears in this list.
Does the problem client have the correct version of the Hyper-V Intergration Services installed?
What is the status code of the failing Windows 2003 machine ?
If it is 156, it can be the VSS system inside the VM that is the problem, usually thing to look for is:
Any VSS/Volsnap or Exhaustion entries in the event logs,
State of writers with vssadmin list writers in a prompt
Size of shadow area
The blog below have helped me identify & fix a lot of VSS issues
Hello Aris56,
As you mentioned that it is working for all other hyper v client except windows 2003, what is the operating system on other hyper v servers?
Please check the below link:
https://www.veritas.com/support/en_US/article.000006177
Check page number 43 for topic "Support for Hyper-V Intelligent Policy in NetBackup 7.7 "
Also check page 39, Table 22, I do not see Windows 2003 listed there.
referring to the documentation given by Marriane, YES.
the version is 6.5.9600.16384
yes. it failed with error 156 but all the VSS writers are stable.
no errors on VSS found in event viewer
size of shadow area i think was enough for the backup.
we have 2003 enterprise edition x86(failed), 2003 standard x64 edition(success), server 2008 r2 standard(success), server 2012 r2 standard(success)
i've go through the documentation and in section "hyper-v integration services required in the Vm", no Win Server 2003 was mentioned.
the backup failed with the following error:
01/20/2016 09:09:54 - Info bpbrm (pid=143593) reading file list for client
01/20/2016 09:09:54 - Info bpbrm (pid=143593) start bpfis on client
01/20/2016 09:09:54 - Info bpbrm (pid=143593) Starting create snapshot processing
01/20/2016 09:09:55 - Info bpfis (pid=5792) Backup started
01/20/2016 09:10:47 - Critical bpbrm (pid=143593) from client BELVLL21: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
01/20/2016 09:10:47 - Critical bpbrm (pid=143593) from client BELVLL21: FTL - snapshot services: snapshot creation failed: unknown error.
01/20/2016 09:10:47 - Critical bpbrm (pid=143593) from client BELVLL21: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
01/20/2016 09:10:47 - Critical bpbrm (pid=143593) from client BELVLL21: FTL - snapshot services: snapshot creation failed: unknown error.
01/20/2016 09:10:47 - Critical bpbrm (pid=143593) from client BELVLL21: FTL - snapshot processing failed, status 156
01/20/2016 09:10:47 - Critical bpbrm (pid=143593) from client BELVLL21: FTL - snapshot creation failed, status 156
01/20/2016 09:10:48 - Warning bpbrm (pid=143593) from client BELVLL21: WRN - ALL_LOCAL_DRIVES is not frozen
01/20/2016 09:10:48 - Info bpfis (pid=5792) done. status: 156
TN with list of possible reasons for status 156: http://www.veritas.com/docs/000067928
