Forum Discussion

jafferali's avatar
jafferali
Level 3
11 years ago

Getting status 10 error - Hyper V clients backed up using FT transport - Netbackup appliance 5230

Hi all,

We have added a new netbackup appliance 5230 in our environment. I tried to do a SAN client for 6 node Hyper V cluster  in which the OS is Windows 2012. When I tried backup using the normal windows level of my hyper V clusters it does via FT transport but when I tried backup one of the VM, it tries to backup via FC but failing with error status 10 (media allocation failed).

Help me to resolve this issue.

Thanks,

Jaffer

Backup and Recovery
Error messages
Managing Backup Devices
NetBackup Appliance
Not Applicable
SAN Shared Storage Option
  • SymTerry's avatar
    SymTerry
    Level 6
    11 years ago

    Hello, 

    TECH155063 might apply to this. It sounds like something is hapening at the hyper v level maybe. Could you reply with the detailed status of the failed job?

     

    EDIT:

    Also try looking for any status codes relating to Hyper V in NetBackup. Refer to the chart in HOWTO44966.

  • jafferali's avatar
    jafferali
    Level 3
    11 years ago

    Hi SymTerry,

    Please find the log below. But now the status code is different.

    3/19/2014 11:01:10 AM - Info bpbrm(pid=2346) MCTTESTWIN7-PC.domainxxx.grp is the host to backup data from     
    3/19/2014 11:01:10 AM - Info bpbrm(pid=2346) reading file list from client        
    3/19/2014 11:01:11 AM - Info bpbrm(pid=2346) starting bpbkar on client         
    3/19/2014 11:01:11 AM - Info bpbkar(pid=22436) Backup started           
    3/19/2014 11:01:11 AM - Info bpbrm(pid=2346) bptm pid: 2347          
    3/19/2014 11:01:11 AM - Info bpbkar(pid=22436) CONTINUE BACKUP received.          
    3/19/2014 11:01:11 AM - Info bptm(pid=2347) start            
    3/19/2014 11:01:12 AM - Info bptm(pid=2347) using 262144 data buffer size        
    3/19/2014 11:01:12 AM - Info bptm(pid=2347) using 16 data buffers         
    3/19/2014 11:01:12 AM - Info bptm(pid=2347) USING 262144 data buffer size for FT      
    3/19/2014 11:01:14 AM - Info bptm(pid=2347) start backup           
    3/19/2014 11:06:17 AM - Error bptm(pid=2347) media manager terminated by parent process       
    3/19/2014 11:06:24 AM - Info mwwnbu04(pid=2347) StorageServer=PureDisk:mwwnbu04; Report=PDDO Stats for (mwwnbu04): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
    3/19/2014 11:06:24 AM - Error bpbrm(pid=2346) could not send server status message       
    3/19/2014 11:06:25 AM - Info bpbkar(pid=0) done            
    3/19/2014 11:06:25 AM - Info bpbkar(pid=0) done. status: 10: allocation failed        
    3/19/2014 11:08:04 AM - Info nbjm(pid=4596) starting backup job (jobid=1614682) for client MCTTESTWIN7-PC.domainxxx.grp, policy test4, schedule test  
    3/19/2014 11:08:04 AM - estimated 31422856 Kbytes needed
    3/19/2014 11:08:04 AM - Info nbjm(pid=4596) started backup (backupid=MCTTESTWIN7-PC.domainxxx.grp_1395198484) job for client MCTTESTWIN7-PC.domainxxx.grp, policy test4, schedule test on storage unit stu_disk_mwwnbu04
    3/19/2014 11:08:05 AM - started process bpbrm (2346)
    3/19/2014 11:08:11 AM - connecting
    3/19/2014 11:08:12 AM - connected; connect time: 00:00:01
    3/19/2014 11:08:14 AM - Opening Fibre Transport Connection, Backup Id: MCTTESTWIN7-PC.domainxxx.grp_1395198484
    3/19/2014 11:08:16 AM - begin writing
    3/19/2014 11:13:26 AM - end writing; write time: 00:05:10
    allocation failed(10)

    Thanks,

    Jaffer

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    I think you may be getting things confused here...

    You Hyper-V machines you seem to have set up to use Fibre Transport (the true meaning of the term within NetBackup)

    But the clients within hyper-v will backup over the SAN but will not use Fibre Transport - so if you have set up FT ports on the appliance they will not work for SAN transport of virtual machine backups

    Fibre Transport and SAN transport backup of virtual machines are not the same thing

    Hope that makes sense!