Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- VOX
- Data Protection
- NetBackup
- Backup of Hyper-V cluster with 2 nodes using a CSV...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Backup of Hyper-V cluster with 2 nodes using a CSV ends with state 156
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2014 12:52 AM
Hello,
I have a MS Windows 2012 R2 Hyper-V cluster with 2 nodes using a CSV and I need to backup the guest systems (Windows, Linux, ...).
Therefor I created a policy in NetBackup 7.6.0.3
Policy Type: Hyper-V
selected some clients
Backup selction: ALL_LOCAL_DRIVES
Hype-V host: cluster_name (FQDN)
Advanced Attributes: Provider Type = Auto, Snapshot Attribute = Unspecified
When a backup job is started, some of the job ends with error 156 and the corresponding VM will stay in "saved" mode.
Now I changed the Hyper-V host to Node_1 (FQDN) and the result is the same.
Next step I tired was to change the Hyper-V host to Node_1 (short name) and all is working -WHY?
The problem here is, that if a guest system switches from Node_1 to Node_2 it will not backuped up.
My question is now, why is the backup with cluster_name (FQDN) not working?
Any help or ideas are welcome
Best regards
Wolfgang
Labels:
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2014 05:34 AM
pls post bpfis from both cluster node
also share job details.
Was it working before ?
did you tried from backing it up from 2nd node of cluster
looks like name resolution is not working as expected from 2nd node
could you pls run below from both nodes and master media
from master media to client
/netbackup/bin/bpclntcmd -ip <node 1>
/netbackup/bin/bpclntcmd -ip <node 2>
/netbackup/bin/bpclntcmd-hn <node1>
/netbackup/bin/bpclntcmd-hn <node2>
/netbackup/bin/admincmd/bptestbpcd -client fqdn of node 1 verbose -debug
/netbackup/bin/admincmd/bptestbpcd -client fqdn of node 2 verbose -debug
from hyper-v nodes to master media
/bin/bpclntcmd -pn
do the above from both nodes
also verify hosts files entries for them
verify there are no aliases created for this.
use
nbemmcmd -machinealias [-addalias -alias string -machinename string] [-deletealias -alias string] [-deleteallaliases -machinename string] [-getaliases -machinename string] -machinetype api | app_cluster |cluster | master | media | ndmp
let us know how it goes.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2014 01:55 AM
Hello,
find here the results of actions done.
===== Job Description =====
------------------------------------------------------------
Policy Name: Hyper-V_Guest_TEST
Policy Type: Hyper-V
Active: no
Effective date: 08/26/2014 10:14:45
File Restore Raw: yes
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: 1
Disaster Recovery: 0
Collect BMR info: no
Residence: (specific storage unit not required)
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 28800 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: HYPER-V Virtual_Machi VII-D1ZE
HYPER-V Virtual_Machi VII-SYSLOG
HYPER-V Virtual_Machi VII-OTRS-TEST
Include: ALL_LOCAL_DRIVES
Schedule: Full
Type: Full Backup
Frequency: every 1 day
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 1
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
------------------------------------------------------------
===== BPFIS =====
NODE 1
C:\>"c:\Program Files\Veritas\NetBackup\bin\bpfis.exe" query
INF - BACKUP START 12400
INF - FIS IDs:
INF - EXIT STATUS 0: the requested operation was successfully completed
C:\>
NODE 2
C:\>"c:\Program Files\Veritas\NetBackup\bin\bpfis.exe" query
INF - BACKUP START 4984
INF - FIS IDs:
INF - EXIT STATUS 0: the requested operation was successfully completed
C:\>
===== BPCLNTCMD on Master/Media server =====
C:\>bpclntcmd -ip 10.184.223.191
host 10.184.223.191: atvnb-hvn1.company.net at 2002:81b8:dfbf::81b8:dfbf
host 10.184.223.191: atvnb-hvn1.company.net at 10.184.223.191
aliases: atvnb-hvn1.company.net 2002:81b8:dfbf::81b8:dfbf 10.184.223.191
C:\>bpclntcmd -ip 10.184.223.192
host 10.184.223.192: atvnb-hvn2.company.net at 2002:81b8:dfc0::81b8:dfc0
host 10.184.223.192: atvnb-hvn2.company.net at 10.184.223.192
aliases: atvnb-hvn2.company.net 2002:81b8:dfc0::81b8:dfc0 10.184.223.192
C:\>bpclntcmd -hn atvnb-hvn1
host atvnb-hvn1: atvnb-hvn1.company.net at 2002:81b8:dfbf::81b8:dfbf
host atvnb-hvn1: atvnb-hvn1.company.net at 10.184.223.191
aliases: atvnb-hvn1.company.net atvnb-hvn1 2002:81b8:dfbf::81b8:dfbf 10.184.223.191
C:\>bpclntcmd -hn atvnb-hvn2
host atvnb-hvn2: atvnb-hvn2.company.net at 2002:81b8:dfc0::81b8:dfc0
host atvnb-hvn2: atvnb-hvn2.company.net at 10.184.223.192
aliases: atvnb-hvn2.company.net atvnb-hvn2 2002:81b8:dfc0::81b8:dfc0 10.184.223.192
C:\>bpclntcmd -hn atvnb-hvn1.company.net
host atvnb-hvn1.company.net: atvnb-hvn1.company.net at 2002:81b8:dfbf::81b8:dfbf
host atvnb-hvn1.company.net: atvnb-hvn1.company.net at 10.184.223.191
aliases: atvnb-hvn1.company.net 2002:81b8:dfbf::81b8:dfbf 10.184.223.191
C:\>bpclntcmd -hn atvnb-hvn2.company.net
host atvnb-hvn2.company.net: atvnb-hvn2.company.net at 2002:81b8:dfc0::81b8:dfc0
host atvnb-hvn2.company.net: atvnb-hvn2.company.net at 10.184.223.192
aliases: atvnb-hvn2.company.net 2002:81b8:dfc0::81b8:dfc0 10.184.223.192
===== BPTESTBPCD =====
C:\>bptestbpcd -client atvnb-hvn1.company.net -verbose -debug
14:58:47.556 [8176.9392] <2> bptestbpcd: VERBOSE = 0
14:58:47.649 [8176.9392] <2> vnet_pbxConnect: pbxConnectEx Succeeded
14:58:47.649 [8176.9392] <2> logconnections: BPCD CONNECT FROM 10.184.223.150.59617 TO 10.184.223.191.1556 fd = 464
14:58:47.665 [8176.9392] <2> vnet_pbxConnect: pbxConnectEx Succeeded
14:58:47.680 [8176.9392] <8> do_pbx_service: [vnet_connect.c:2152] via PBX VNETD CONNECT FROM 10.184.223.150.59618 TO 10.184.223.191.1556 fd = 484
14:58:47.680 [8176.9392] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
14:58:47.758 [8176.9392] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string59358
14:58:53.125 [8176.9392] <2> bpcr_get_version_rqst: bpcd version: 076000021 1 1
10.184.223.150:59617 -> 10.184.223.191:1556
10.184.223.150:59618 -> 10.184.223.191:1556
14:58:53.343 [8176.9392] <2> bpcr_get_peername_rqst: Server peername length = 25
14:58:53.546 [8176.9392] <2> bpcr_get_hostname_rqst: Server hostname length = 25
14:58:53.765 [8176.9392] <2> bpcr_get_clientname_rqst: Server clientname length = 25
14:58:53.983 [8176.9392] <2> bpcr_get_version_rqst: bpcd version: 07600002
14:58:54.186 [8176.9392] <2> bpcr_get_platform_rqst: Server platform length = 7
14:58:54.389 [8176.9392] <2> bpcr_get_version_rqst: bpcd version: 07600002
14:58:54.654 [8176.9392] <2> bpcr_patch_version_rqst: theRest == > <
14:58:54.654 [8176.9392] <2> bpcr_get_version_rqst: bpcd version: 07600002
14:58:54.935 [8176.9392] <2> bpcr_patch_version_rqst: theRest == > <
14:58:54.935 [8176.9392] <2> bpcr_get_version_rqst: bpcd version: 07600002
PEER_NAME = vii-backup.company.net
HOST_NAME = atvnb-hvn1.company.net
CLIENT_NAME = atvnb-hvn1.company.net
VERSION = 0x07600002
PLATFORM = win_x64
PATCH_VERSION = 7.6.0.3
SERVER_PATCH_VERSION = 7.6.0.3
MASTER_SERVER = vii-backup.company.net
EMM_SERVER = vii-backup.company.net
NB_MACHINE_TYPE = CLIENT
14:58:55.153 [8176.9392] <2> vnet_pbxConnect: pbxConnectEx Succeeded
14:58:55.169 [8176.9392] <8> do_pbx_service: [vnet_connect.c:2152] via PBX VNETD CONNECT FROM 10.184.223.150.59619 TO 10.184.223.191.1556 fd = 492
14:58:55.169 [8176.9392] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
14:58:55.231 [8176.9392] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string59360
10.184.223.150:59619 -> 10.184.223.191:1556
<2>bptestbpcd: EXIT status = 0
14:58:55.512 [8176.9392] <2> bptestbpcd: EXIT status = 0
C:\>bptestbpcd -client atvnb-hvn2.company.net -verbose -debug
14:59:03.718 [8696.9272] <2> bptestbpcd: VERBOSE = 0
14:59:03.749 [8696.9272] <2> vnet_pbxConnect: pbxConnectEx Succeeded
14:59:03.749 [8696.9272] <2> logconnections: BPCD CONNECT FROM 10.184.223.150.59639 TO 10.184.223.192.1556 fd = 464
14:59:03.749 [8696.9272] <2> vnet_pbxConnect: pbxConnectEx Succeeded
14:59:03.780 [8696.9272] <8> do_pbx_service: [vnet_connect.c:2152] via PBX VNETD CONNECT FROM 10.184.223.150.59640 TO 10.184.223.192.1556 fd = 480
14:59:03.780 [8696.9272] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
14:59:03.843 [8696.9272] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string58533
14:59:04.545 [8696.9272] <2> bpcr_get_version_rqst: bpcd version: 076000021 1 1
10.184.223.150:59639 -> 10.184.223.192:1556
10.184.223.150:59640 -> 10.184.223.192:1556
14:59:04.763 [8696.9272] <2> bpcr_get_peername_rqst: Server peername length = 25
14:59:04.966 [8696.9272] <2> bpcr_get_hostname_rqst: Server hostname length = 25
14:59:05.184 [8696.9272] <2> bpcr_get_clientname_rqst: Server clientname length = 25
14:59:05.387 [8696.9272] <2> bpcr_get_version_rqst: bpcd version: 07600002
14:59:05.590 [8696.9272] <2> bpcr_get_platform_rqst: Server platform length = 7
14:59:05.793 [8696.9272] <2> bpcr_get_version_rqst: bpcd version: 07600002
14:59:06.058 [8696.9272] <2> bpcr_patch_version_rqst: theRest == > <
14:59:06.058 [8696.9272] <2> bpcr_get_version_rqst: bpcd version: 07600002
14:59:06.323 [8696.9272] <2> bpcr_patch_version_rqst: theRest == > <
14:59:06.323 [8696.9272] <2> bpcr_get_version_rqst: bpcd version: 07600002
PEER_NAME = vii-backup.company.net
HOST_NAME = atvnb-hvn2.company.net
CLIENT_NAME = atvnb-hvn2.company.net
VERSION = 0x07600002
PLATFORM = win_x64
PATCH_VERSION = 7.6.0.3
SERVER_PATCH_VERSION = 7.6.0.3
MASTER_SERVER = vii-backup.company.net
EMM_SERVER = vii-backup.company.net
NB_MACHINE_TYPE = CLIENT
14:59:06.526 [8696.9272] <2> vnet_pbxConnect: pbxConnectEx Succeeded
14:59:06.542 [8696.9272] <8> do_pbx_service: [vnet_connect.c:2152] via PBX VNETD CONNECT FROM 129.18
4.223.150.59641 TO 10.184.223.192.1556 fd = 492
14:59:06.557 [8696.9272] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
14:59:06.604 [8696.9272] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string58535
10.184.223.150:59641 -> 10.184.223.192:1556
<2>bptestbpcd: EXIT status = 0
14:59:06.869 [8696.9272] <2> bptestbpcd: EXIT status = 0
C:\>
===== BPCLNTCMD on Hyper-V nodes =====
NODE 1
C:\>"c:\Program Files\Veritas\NetBackup\bin\bpclntcmd.exe" -pn
expecting response from server vii-backup.company.net
atvnb-hvn1.company.net atvnb-hvn1 10.184.223.191 59407
C:\>
NODE 2
C:\>"c:\Program Files\Veritas\NetBackup\bin\bpclntcmd.exe" -pn
expecting response from server vii-backup.company.net
atvnb-hvn2.company.net *NULL* 10.184.223.192 58608
C:\>
===== HOST file on Hyper-V nodes =====
NODE 1
C:\> type c:\Windows\System32\drivers\etc\hosts
EMPTY
C:\>
NODE 2
C:\>type c:\Windows\System32\drivers\etc\hosts
EMPTY
C:\>
===== NBEMMCMD on MASTER server =====
C:\>nbemmcmd -listhosts
NBEMMCMD, Version: 7.6.0.3
The following hosts were found:
server vii-backup
master vii-backup
ndmp vii-backup
virtual_machine vii-vserver.company.net
ndmp fas940-a
virtual_machine vii-vcenter.company.net
Command completed successfully.
C:\>nbemmcmd -machinealias -getalias -machinename atvnb-hvn1 -machinetype cluster
NBEMMCMD, Version: 7.6.0.3
The function returned the following failure status:
invalid host name (136)
Command did not complete successfully.
C:\>nbemmcmd -machinealias -getalias -machinename atvnb-hvn1.company.net -machinetype cluster
NBEMMCMD, Version: 7.6.0.3
The function returned the following failure status:
invalid host name (136)
Command did not complete successfully.
C:\>nbemmcmd -machinealias -getalias -machinename atvnb-hvn2 -machinetype cluster
NBEMMCMD, Version: 7.6.0.3
The function returned the following failure status:
invalid host name (136)
Command did not complete successfully.
C:\>nbemmcmd -machinealias -getalias -machinename atvnb-hvn2.company.net -machinetype cluster
NBEMMCMD, Version: 7.6.0.3
The function returned the following failure status:
invalid host name (136)
Command did not complete successfully.
C:\>nbemmcmd -machinealias -getalias -machinename atvnb-hvc1.company.net -machinetype cluster
NBEMMCMD, Version: 7.6.0.3
The function returned the following failure status:
invalid host name (136)
Command did not complete successfully.
C:\>nbemmcmd -machinealias -getalias -machinename vii-backup.company.net -machinetype master
NBEMMCMD, Version: 7.6.0.3
The following aliases were found for the alias: "vii-backup.company.net"
vii-backup
vii-backup.company.net
Command completed successfully.
C:\>
Best regards
Wolfgang
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2014 01:02 AM
Hello,
any news available?
Any further ideas are welcome.
Thank You
Wolfgang
Related Content
- Flex Scale immutability in NetBackup Appliance
- SQL intelligent policy for DB on non standard port in NetBackup
- Speed Up Cloud Universal Share Backups with Accelerator in NetBackup
- Backup Exec 22 physical server convert to virtual ? re storage in Backup Exec
- bphdb exit status = 29: failed trying to exec a command in NetBackup
