Check that the client names are the FQDNs of the virtual guests to be
backed up.  Also make sure you've got all the prerequisite hotfixes
from Chapter 2 of the NetBackup for Hyper-V guide installed, we had a
lot of strange errors before that, but even on a fully up to date box
we still have a few VMs that always result in a 156 status.

On Fri, Nov 6, 2009 at 7:42 AM, Jim Caldwell
<caldwellj AT nccommunitycolleges DOT edu> wrote:
> Trying to create a Hyper-V backup and get "HyperV -- client: SOUItest
> -- Snapshot could not be created with Hyper-V method  (Status 223)"
> We have looked at /etc/hosts to ensure that both sides have the same names
> and i/ps.
> We reply yes to bypass but when we run the policy we get Status 156.
> 11/06/2009 08:39:52 - end Flash Backup Windows: Read File List; elapsed time
> 0:00:00
> 11/06/2009 08:39:52 - begin Flash Backup Windows: Create Snapshot
> 11/06/2009 08:39:53 - started process bpbrm (pid=3429)
> 11/06/2009 08:40:02 - Critical bpbrm (pid=3429) from client SOUItest: FTL -
> snapshot creation failed, status 156
> 11/06/2009 08:40:02 - end Flash Backup Windows: Create Snapshot; elapsed
> time 0:00:10
> 11/06/2009 08:40:03 - end writing
> Operation Status: 156
>
>
> James M. Caldwell
> NCCCS Unix Support
> Operation & Systems Analyst
> caldwellj AT nccommunitycolleges DOT edu
> 919-807-7234 (Office)
> ___________________________________________________
> E-mail correspondence to and from this address may be subject
> to the North Carolina Public Records Law and shall be disclosed
> to third parties when required by the statutes. (NCGS.Ch.132)
> ___________________________________________________
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu