05-22-2017 11:17 AM
Solved! Go to Solution.
05-22-2017 01:03 PM
Hi Vickie,
For me, its does not make sense...If you can make backup by NBD transport mode and cannot make using SAN, there is a problem with the Luns that were presented to VM backup host.
When this happen the backup job failed with an error message similar to this one:
Ex:
From Detailed Status:
10/21/2013 11:18:28 - Info bptm (pid=14932) using 1048576 data buffer size
10/21/2013 11:18:28 - Info bptm (pid=14932) setting receive network buffer to 1048576 bytes
10/21/2013 11:18:28 - Info bptm (pid=14932) using 512 data buffers
10/21/2013 11:18:29 - Info bptm (pid=14932) start backup
10/21/2013 11:18:32 - begin writing
10/21/2013 11:18:34 - Error bpbrm (pid=14922) from client winclient.local: ERR - Error opening the snapshot disks using given transport mode: Status 23
10/21/2013 11:18:37 - Error bptm (pid=14932) media manager terminated by parent process
10/21/2013 11:18:42 - Info backup2 (pid=14932) StorageServer=PureDisk:backup2; Report=PDDO Stats for (backup2): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
10/21/2013 11:18:42 - Info bpbkar (pid=0) done. status: 6: the backup failed to back up the requested files
10/21/2013 11:18:42 - end writing; write time: 0:00:10
the backup failed to back up the requested files (6)
Make sure LUNs are accessible to the VMware Backup Host and check the Troubleshotting below:
Troubleshooting for some common transport mode related failures
Backups/Restores failing with status 6 or status 13 or status 11 with following indication in Activity monitor might indicate that there is some issue with transport modes:-
Regards,
Thiago
05-22-2017 11:50 AM
Hi Vickie,
All datastore were mapped for the vm backup host? What is the error that you are facing?
About Transport modes, take a look this TN.
https://www.veritas.com/support/en_US/article.000094725
Regards,
Thiago
05-22-2017 12:40 PM
05-22-2017 01:03 PM
Hi Vickie,
For me, its does not make sense...If you can make backup by NBD transport mode and cannot make using SAN, there is a problem with the Luns that were presented to VM backup host.
When this happen the backup job failed with an error message similar to this one:
Ex:
From Detailed Status:
10/21/2013 11:18:28 - Info bptm (pid=14932) using 1048576 data buffer size
10/21/2013 11:18:28 - Info bptm (pid=14932) setting receive network buffer to 1048576 bytes
10/21/2013 11:18:28 - Info bptm (pid=14932) using 512 data buffers
10/21/2013 11:18:29 - Info bptm (pid=14932) start backup
10/21/2013 11:18:32 - begin writing
10/21/2013 11:18:34 - Error bpbrm (pid=14922) from client winclient.local: ERR - Error opening the snapshot disks using given transport mode: Status 23
10/21/2013 11:18:37 - Error bptm (pid=14932) media manager terminated by parent process
10/21/2013 11:18:42 - Info backup2 (pid=14932) StorageServer=PureDisk:backup2; Report=PDDO Stats for (backup2): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
10/21/2013 11:18:42 - Info bpbkar (pid=0) done. status: 6: the backup failed to back up the requested files
10/21/2013 11:18:42 - end writing; write time: 0:00:10
the backup failed to back up the requested files (6)
Make sure LUNs are accessible to the VMware Backup Host and check the Troubleshotting below:
Troubleshooting for some common transport mode related failures
Backups/Restores failing with status 6 or status 13 or status 11 with following indication in Activity monitor might indicate that there is some issue with transport modes:-
Regards,
Thiago
05-22-2017 01:31 PM - edited 05-22-2017 01:34 PM
Hi Thiago,
I also could not understand why the backup working in NBD and getting failed in SAN.
However the Datastore is accessible by Backup Host (NetBackup Appliance 5230), as the backup of other vm there on the same Datastore is getting successfully completed.
06-07-2017 12:55 PM
Hi @Vickie,
Any update? Your backups are still failing? From netbackup appliance, by CLISH - Manage --> FibreChannel --> Show, and see if
All HBA ports are available and the status
All datastore are show;
Regards,
Thiago Ribeiro
06-07-2017 01:00 PM
06-07-2017 05:47 PM
Ive found that even if you run a scan on the appliance once LUNs are presented, and it appears to be presented, the only way it will work is to reboot the appliance and it will then work.
If you are running NBU 773 or higher and the VM has a duplicate BIOS UUID as another or multiple VMs, it will fail no matter what. This is a huge known issue to Veritas that has not been corrected since 773 came out. Don't get me started on this mess!!
06-08-2017 05:47 AM
Hi @HunkerDownOneMo,
That true what you said...I faced the same problem with NBU version 8.0 ( Appliance 5240 3.0)...The Luns were presented and even after scan on the appliance they dont appear and I need to reboot the appliance.
Regards,
Thiago Ribeiro
06-12-2017 03:02 AM
Thanks All for your assistance and support.
Vertias suggested to Upgrade the appliace to 2.7.3 version, that's too for collecting the vxms logs at vm end and then they will gonna identify route cause. As of now they did not find anything.
So for time being we are taking backup over LAN mode.
09-30-2020 08:34 AM
If the LUNs are presented to the host, then the solution is:
Clean the / tmp folder.
10-01-2020 12:22 AM