02-17-2016 05:49 AM
Hello
I need help with my Symantec Netbackup version 7.6.0.1 running on a Windows 8.1 Pro 64-bits.
I've a backup server with is link to an HP Autoloader through an HBA card.
I've two backup politics which are Weekly and Monthly. Weekly are done every Saturdays while Monthly is done on the last Sunday of the month.
Since few weeks now I cannot perform any backups of my VMware Virtuals Machines (Weekly/Monthly).
First I got the error message such like : "2009, EMM Status: All compatible drive paths are down, but media is available" for the Weekly
Note: I thought that the issue could provide from the tape's order into the library, so I veryfied the tape's order and I've to move one from the media to the path 1.
Then, the next sunday (Monthly backup) I got the error message such like : "4239 - unable to find the virtual machine"
You can see the error message below.
I've tried to find out the logfile on the "event logs" in C:\WINDOWS\system32\config ofmy Management Workstation, but even if I have found files, I can't open them.
Can someone help please ?
Many thanks,
Dany
02-17-2016 06:09 AM
The two errors are unrelated and need troubleshooting separately.
Status 2009 (all drives are down) means that you have a hardware problem - tape library, tape drives or bad media.
Status 4239 (unable to find the virtual machine) has to do with a problem with VMware backup configuration.
Let us go back to your opening line:
Symantec Netbackup version 7.6.0.1 running on a Windows 8.1 Pro 64-bits.
NetBackup 7.6.x master server is NOT supported on Windows 8.
See the NBU OS SCL: http://www.veritas.com/docs/000040842 (click on Attachments)
Microsoft Windows 8 is only supported as NetBackup Client. Not Master or Media server.
So, before we continue - Find/provide a server with supported OS (Windows 2008 or 2012), connect devices as per hardware installation guide from the vendor, install NetBackup as Master server, then config devices and Storage Units, add media, followed by creating normal file-level test backups (e.g. some files/folders on the master).
Only when this is working fine do we proceed to configuration of VM backups.....
02-17-2016 06:15 AM
I see you have previously experienced 'Drive Down' issues on a Linux server:
HP ULTRIUM5-SCSI DRIVE IN "DOWN-TLD" STATUS ON NETBACKUP
In the above post you stopped responding to attempts to help you?
02-17-2016 08:07 AM
Hello Marianne
Many thanks for your reply.
My mystake: I've a Netbackup Administration Console on a Windows 8.1 Pro Workstation and the Netbackup program version 7.6.0.1 is running on a RedHat 6.4X64 OS.
Regarding the "HP ULTRIUM5-SCSI DRIVE IN "DOWN-TLD" STATUS ON NETBACKUP" request, I think that I still needs to investigate (that's why I didn't replied you yet) but later because I have to face to others issues at the moment.
Could you please help me to find out the "event logs" and to troubleshoot the status 2009 and 4239 issues ?
Many thanks,
Dany
02-17-2016 08:55 AM
02-17-2016 01:05 PM
02-18-2016 02:24 AM
Marianne
Thank you very much for your reply.
So, for the 2009 error code, I will process asap.
Before processing, could you please confirm me that
1. In order to add VERBOSE entry to vm.conf on master/media server, I have to access the /usr/openv/volmgr file and only add VERBOSE as a single line ?
2. For restarting the NBU, I have to run these commands:
Stop:
/usr/openv/netbackup/bin/goodies/netbackup stop
Start:
/usr/openv/netbackup/bin/goodies/netbackup start
Later, I will open/start a separate discussion for 4239 error code.
Dany
02-18-2016 03:27 AM
02-18-2016 05:39 AM
Marianne
I've accordingly added the term "VERBOSE" in the vm.conf.
Before:
MM_SERVER_NAME = RD-BMO-BCK01
~
~
~
~
After:
MM_SERVER_NAME = RD-BMO-BCK01
VERBOSE
~
~
~
Then I've restarted the NBU with the 2 commands.
Result: in the "Device Monitor" section the HP.ULTRIUM5-SCSI.001 drive is down and I cannot put it UP (even if I do a right-click on and select UP).
I'd a look in /var/log/messages which is below (this is a short extract, if you want I can provide you the full file).
Feb 18 12:33:02 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:35:05 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:35:05 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:35:05 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:35:05 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:35:05 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:35:05 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:35:05 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:37:07 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:37:07 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:37:07 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:37:07 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:37:07 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:37:07 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:37:07 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:39:09 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:39:09 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:39:09 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:39:09 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:39:09 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:39:09 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:39:09 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:41:11 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:41:11 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:41:11 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:41:11 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:41:11 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:41:11 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:41:11 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:43:13 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:43:13 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:43:13 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:43:13 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:43:13 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:43:13 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:43:13 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:45:15 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:45:15 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:45:15 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:45:15 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:45:15 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:45:15 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:45:15 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: new high speed USB device number 4 using ehci_hcd
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: New USB device found, idVendor=18a5, idProduct=0302
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: Product: STORE N GO
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: Manufacturer: Verbatim
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: SerialNumber: 1402000000000002
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usb 2-1.5: configuration #1 chosen from 1 choice
Feb 18 12:45:30 RD-BMO-BCK01 kernel: Initializing USB Mass Storage driver...
Feb 18 12:45:30 RD-BMO-BCK01 kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Feb 18 12:45:30 RD-BMO-BCK01 kernel: usbcore: registered new interface driver usb-storage
Feb 18 12:45:30 RD-BMO-BCK01 kernel: USB Mass Storage support registered.
Feb 18 12:45:31 RD-BMO-BCK01 kernel: scsi 4:0:0:0: Direct-Access Verbatim STORE N GO 1.01 PQ: 0 ANSI: 2
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: [sdb] Write Protect is off
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sdb: sdb1
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 18 12:45:31 RD-BMO-BCK01 kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
Feb 18 12:45:31 RD-BMO-BCK01 kernel: uhci_hcd 0000:01:00.4: Controller not stopped yet!
Feb 18 12:46:43 RD-BMO-BCK01 SQLAnywhere(nb_rd-bmo-bck01): Starting checkpoint of "NBAZDB" (NBAZDB.db) at Thu Feb 18 2016 12:46
Feb 18 12:46:43 RD-BMO-BCK01 SQLAnywhere(nb_rd-bmo-bck01): Starting checkpoint of "NBDB" (NBDB.db) at Thu Feb 18 2016 12:46
Feb 18 12:46:43 RD-BMO-BCK01 SQLAnywhere(nb_rd-bmo-bck01): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Thu Feb 18 2016 12:46
Feb 18 12:46:43 RD-BMO-BCK01 SQLAnywhere(nb_rd-bmo-bck01): Finished checkpoint of "NBDB" (NBDB.db) at Thu Feb 18 2016 12:46
Feb 18 12:47:17 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00P
Feb 18 12:47:17 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:47:17 RD-BMO-BCK01 tldcd[49160]: tldcd.c.3039, process_request(), received command=9, from peername=RD-BMO-BCK01, version 50
Feb 18 12:47:17 RD-BMO-BCK01 tldcd[49160]: TLD(0) opening robotic path MISSING_PATH:MXA338Z00
Feb 18 12:47:17 RD-BMO-BCK01 tldcd[49160]: TLD(0) [49160] robotic path MISSING_PATH:MXA338Z00P does not exist
Feb 18 12:47:17 RD-BMO-BCK01 tldd[49131]: DecodeQuery() Actual status: Unable to open robotic path
Feb 18 12:47:17 RD-BMO-BCK01 tldd[49131]: TLD(0) unavailable: initialization failed: Unable to open robotic path
02-18-2016 05:57 AM
My Mistake: in the "Device Monitor" section the HP.ULTRIUM5-SCSI.001 drive is TLD and it is written NO in the "Ready" column.
I guess it is UP otherwise DOWN-TLD should be written in the "Control" column as below:
02-18-2016 06:08 AM
robotic path MISSING_PATH:MXA338Z00P does not exist DecodeQuery() Actual status: Unable to open robotic path TLD(0) unavailable: initialization failed: Unable to open robotic path
In your post of 3 Nov 2015: HP ULTRIUM5-SCSI DRIVE IN "DOWN-TLD" STATUS ON NETBACKUP
it became clear that changes were made to physical connections.
Changes like that result in device paths changing.
You were adviced to delete all devices in NetBackup and to rescan and re-add.
Have you done this yet?
NOTHING is going to work while there are MISSING_PATH errors.
PLEASE delete ALL devices - robot and tape drives and restart NBU.
Confirm with 'scan' and 'cat /proc/scsi/scsi' that devices are seen correctly at OS-level.
If correct, use the Device Config Wizard to rescan and add devices in NetBackup.
02-18-2016 08:25 AM
Thank you Marianne.
Please let me investigate 2/3 days.
Dany
02-18-2016 09:12 AM
02-19-2016 05:19 AM
Marianne
I think that it was working after the operation that I've done after the 3rd of November.
In fact, people who has done the configuration are not working anymore and I've to fix the issue asap, and then, I'll be able to correct the MISSING_PATH error message (by re-doing correctly the cabling).
According to me, I've the "MISSING_PATH" error message because the SCSI.000 cable wis not plugged anymore. And also the SCSI.000 cable is in relation with "TLD0" that I do not use all.
I'm only focused on "TLD01" which is used by the SCSI.001 cable and which is plugged to a port "TenGigabitEthernet" of my Switch.
Because I've only one SCSI cable plugged (mounted on the /dev/nst0 "Drive") and because the issue seems to raised since some people changed the DNS configuration, I would think that the issue could come from the VMware side.
Because the error message that I get is "unable to find Virtual machine", I had a look on this website and find-out a post where you recommanded to provide credentials for NetBackup to access the vCenter server in order to backup the VM which are turned-off.
Link: https://www.veritas.com/community/forums/vmware-error-4239
On my side, VMs that I want to backuped are not turned-off but I guess the issue could come from VMware.
Will it be something to check into the Vcenter or the DNS ?
Please check the "ATTACH FILES" section, I've put a draw of the rack's connection + picture of cables.
Many thanks for your help.
Kind regards,
Dany
02-19-2016 08:21 AM
02-29-2016 06:01 AM
Marianne
Please give me more time to fix this issue.
For sure, I will comeback in few weeks and provide you a proper answer.
Dany
02-29-2016 06:31 AM
Marianne
Could you please tell me which forum do I have to choose in order to post a question related to Netbackup and VMware ?
I'd like to know how to perfrom a restore from VMware (once these VM has been restored on Netbackup).
In advance,thank you for your help.
Kind regards,
Dany
02-29-2016 06:46 AM
Post in the same forum: Backup and Recovery -> NetBackup.
We just need different issues to be in different discussions as troubleshooting and resolution are not related.
Device issues are not related to VMware issues.