Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -SPOKE TO SOON
Hi Jeff, I've just started using dnsmasq on Red Hat Linux which acts as a dns forwarder but allows me to override certain IP addresses. It's easy to configure and will get around this problem. Other than that is it out of the question to use a slightly different name for client interface that is in the backup network? (e.g. servername-b) You would then put servername-b rather than servername in the policy and the traffic would automatically route over the backup network. I've used this for all clients in my backup network from day one and it's been fine. The disadvantages that I can think of for you are - The name of the client in reports and for searches is different from the normal client name, and if it only applies to one or two servers then it will be confusing. - Backups taken before the change will be considered by the server to be of a different client so there are a few extra steps to restore from these. Best regards, Rosie. Rosie Cleary Computer Centre National University of Ireland, Maynooth Lightner, Jeff wrote [28/04/2011 20:53]: Sorry folks - NOT resolved. I thought this was resolved because the backup started but on checking I see it is using the primary LAN rather than the backup LAN. The addition of the FQDN on the client did get us past the 59 error but didn’t fix the issue I was asking about initially. The bpclntcmd is still showing the 10.x primary IP instead of the 172.x backup IP that I have in host file of the media server. We really need this backup to go across the backup LAN. *From:*veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Lightner, Jeff *Sent:* Thursday, April 28, 2011 3:11 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -RESOLVED *Dan Otto had responded and based on what he wrote I resolved the issue. The below shows the thread between us and is reposted here with his permission.* ** *From:*Lightner, Jeff [mailto:jlight...@water.com] *Sent:* Thursday, April 28, 2011 2:02 PM *To:* Daniel Otto *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? That was it. After checking bpcd log on the client we saw that it was complaining that the FQDN name wasn’t a media server. Our entry for the server was the short name for the media server. Adding the FQDN to the line that had the backup LAN IP and short name resolved the issue. It just didn’t occur to me to look at the client because I thought bpclntcmd was simply trying to resolve from the media server. I had actually tried adding FQDN of the client to the media server earlier because we have seen various issues regarding short name vs FQDN since implementing 7.1. Thanks for your help. *From:*Daniel Otto [mailto:dan_o...@symantec.com] *Sent:* Thursday, April 28, 2011 2:57 PM *To:* Lightner, Jeff *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? The 59 is thrown because whatever server hostname the client is resolving doesn’t exist in the client’s server list hence server access denied status 59 and should show up as a status 46 error in bpcd as a invalid server. If the media server couldn’t resolve the client at all or getting the wrong IP address you would be getting 58/25 or even 54’s type of errors. *From:*Lightner, Jeff [mailto:jlight...@water.com] *Sent:* Thursday, April 28, 2011 1:43 PM *To:* Daniel Otto *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? I did actually try removing dns from nsswitch.conf but it didn’t help. I haven’t looked at the client’s bpcd log – I did verify the media server is in the server list for the client. The only other one in the list is the master. *From:*Daniel Otto [mailto:dan_o...@symantec.com] *Sent:* Thursday, April 28, 2011 2:35 PM *To:* Lightner, Jeff *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? Easy fix would be to use the bpcd log on the client and whatever hostname is getting resolved simply add it to the SERVER = on the client and the 59 should go away. As to why it is not using the host file…that’s interesting. Perhaps for a quick test remove the DNS entry altogether from switch.conf to see if it then goes to the host file. Though I have only seen Solaris server do funkly things such as this. Hope this helps, Dan O *From:*veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Lightner, Jeff *Sent:* Thursday, April 28, 2011 2:22 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:*
Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -SPOKE TO SOON
We actually do that for most clients but this is a MS Exchange cluster name and we didn't need to use a separate name for this cluster in 6.5.4. To me this seems like a bug in the NetBackup tools since I can demonstrate OS level tools resolve the expected IP and it is only the NetBackup tools that are getting the wrong name. Also as I noted before this is only happening on my HP-UX media server - my master server is getting the correct IP in bpclntcmd for the client. -Original Message- From: Rosie Cleary [mailto:rosie.cle...@nuim.ie] Sent: Friday, April 29, 2011 5:06 AM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -SPOKE TO SOON Hi Jeff, I've just started using dnsmasq on Red Hat Linux which acts as a dns forwarder but allows me to override certain IP addresses. It's easy to configure and will get around this problem. Other than that is it out of the question to use a slightly different name for client interface that is in the backup network? (e.g. servername-b) You would then put servername-b rather than servername in the policy and the traffic would automatically route over the backup network. I've used this for all clients in my backup network from day one and it's been fine. The disadvantages that I can think of for you are - The name of the client in reports and for searches is different from the normal client name, and if it only applies to one or two servers then it will be confusing. - Backups taken before the change will be considered by the server to be of a different client so there are a few extra steps to restore from these. Best regards, Rosie. Rosie Cleary Computer Centre National University of Ireland, Maynooth Lightner, Jeff wrote [28/04/2011 20:53]: Sorry folks - NOT resolved. I thought this was resolved because the backup started but on checking I see it is using the primary LAN rather than the backup LAN. The addition of the FQDN on the client did get us past the 59 error but didn't fix the issue I was asking about initially. The bpclntcmd is still showing the 10.x primary IP instead of the 172.x backup IP that I have in host file of the media server. We really need this backup to go across the backup LAN. *From:*veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Lightner, Jeff *Sent:* Thursday, April 28, 2011 3:11 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -RESOLVED *Dan Otto had responded and based on what he wrote I resolved the issue. The below shows the thread between us and is reposted here with his permission.* ** *From:*Lightner, Jeff [mailto:jlight...@water.com] *Sent:* Thursday, April 28, 2011 2:02 PM *To:* Daniel Otto *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? That was it. After checking bpcd log on the client we saw that it was complaining that the FQDN name wasn't a media server. Our entry for the server was the short name for the media server. Adding the FQDN to the line that had the backup LAN IP and short name resolved the issue. It just didn't occur to me to look at the client because I thought bpclntcmd was simply trying to resolve from the media server. I had actually tried adding FQDN of the client to the media server earlier because we have seen various issues regarding short name vs FQDN since implementing 7.1. Thanks for your help. *From:*Daniel Otto [mailto:dan_o...@symantec.com] *Sent:* Thursday, April 28, 2011 2:57 PM *To:* Lightner, Jeff *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? The 59 is thrown because whatever server hostname the client is resolving doesn't exist in the client's server list hence server access denied status 59 and should show up as a status 46 error in bpcd as a invalid server. If the media server couldn't resolve the client at all or getting the wrong IP address you would be getting 58/25 or even 54's type of errors. *From:*Lightner, Jeff [mailto:jlight...@water.com] *Sent:* Thursday, April 28, 2011 1:43 PM *To:* Daniel Otto *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? I did actually try removing dns from nsswitch.conf but it didn't help. I haven't looked at the client's bpcd log - I did verify the media server is in the server list for the client. The only other one in the list is the master. *From:*Daniel Otto [mailto:dan_o...@symantec.com] *Sent:* Thursday, April 28, 2011 2:35 PM *To:* Lightner, Jeff *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? Easy fix would
Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -SPOKE TO SOON
Have you tried running bptestbpcd -client client name -verbose -debug from the media server? What are the results? Does bpgetconfig -M client name work? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: 29 April 2011 13:41 To: Rosie Cleary Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -SPOKE TO SOON We actually do that for most clients but this is a MS Exchange cluster name and we didn't need to use a separate name for this cluster in 6.5.4. To me this seems like a bug in the NetBackup tools since I can demonstrate OS level tools resolve the expected IP and it is only the NetBackup tools that are getting the wrong name. Also as I noted before this is only happening on my HP-UX media server - my master server is getting the correct IP in bpclntcmd for the client. -Original Message- From: Rosie Cleary [mailto:rosie.cle...@nuim.ie] Sent: Friday, April 29, 2011 5:06 AM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -SPOKE TO SOON Hi Jeff, I've just started using dnsmasq on Red Hat Linux which acts as a dns forwarder but allows me to override certain IP addresses. It's easy to configure and will get around this problem. Other than that is it out of the question to use a slightly different name for client interface that is in the backup network? (e.g. servername-b) You would then put servername-b rather than servername in the policy and the traffic would automatically route over the backup network. I've used this for all clients in my backup network from day one and it's been fine. The disadvantages that I can think of for you are - The name of the client in reports and for searches is different from the normal client name, and if it only applies to one or two servers then it will be confusing. - Backups taken before the change will be considered by the server to be of a different client so there are a few extra steps to restore from these. Best regards, Rosie. Rosie Cleary Computer Centre National University of Ireland, Maynooth Lightner, Jeff wrote [28/04/2011 20:53]: Sorry folks - NOT resolved. I thought this was resolved because the backup started but on checking I see it is using the primary LAN rather than the backup LAN. The addition of the FQDN on the client did get us past the 59 error but didn't fix the issue I was asking about initially. The bpclntcmd is still showing the 10.x primary IP instead of the 172.x backup IP that I have in host file of the media server. We really need this backup to go across the backup LAN. *From:*veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Lightner, Jeff *Sent:* Thursday, April 28, 2011 3:11 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] bpclntcmd and others ignoring nsswitch.conf? -RESOLVED *Dan Otto had responded and based on what he wrote I resolved the issue. The below shows the thread between us and is reposted here with his permission.* ** *From:*Lightner, Jeff [mailto:jlight...@water.com] *Sent:* Thursday, April 28, 2011 2:02 PM *To:* Daniel Otto *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? That was it. After checking bpcd log on the client we saw that it was complaining that the FQDN name wasn't a media server. Our entry for the server was the short name for the media server. Adding the FQDN to the line that had the backup LAN IP and short name resolved the issue. It just didn't occur to me to look at the client because I thought bpclntcmd was simply trying to resolve from the media server. I had actually tried adding FQDN of the client to the media server earlier because we have seen various issues regarding short name vs FQDN since implementing 7.1. Thanks for your help. *From:*Daniel Otto [mailto:dan_o...@symantec.com] *Sent:* Thursday, April 28, 2011 2:57 PM *To:* Lightner, Jeff *Subject:* RE: bpclntcmd and others ignoring nsswitch.conf? The 59 is thrown because whatever server hostname the client is resolving doesn't exist in the client's server list hence server access denied status 59 and should show up as a status 46 error in bpcd as a invalid server. If the media server couldn't resolve the client at all or getting the wrong IP address you would be getting 58/25 or even 54's type of errors. *From:*Lightner, Jeff
[Veritas-bu] NetBackup 7.1
Hello, How has everyone's 7.1 experience been? Any gotchas or things to look out for? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NetBackup 7.1 Client Software Changes
Hi, I noticed it starts up a lot of services with 7.1 # rc.d/init.d/netbackup start NetBackup Authentication daemon not started. NetBackup network daemon started. NetBackup client daemon started. NetBackup SAN Client Fibre Transport daemon started. NetBackup Bare Metal Restore Boot Server daemon started. In the past, there were little to no services (SAN Client) most recently, what is everyone's thoughts on this? Has anyone seen any issues running these services on busy hosts? As with any new software/package/change, I wonder if there have been any bugs or weird issues that someone on here may have faced? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 7.1
There appear to be differences in where fully qualified domain names need to be used. We have moved most of our environment to 7.1 but do have a few outstanding issues: Can't backup SQL 2000 on MS 2000 (not supported - we put the NBU 6.5.4 client on this server since there isn't a 7.1 version. Someone on this list says they got it working with 7.0.1 master and 6.5.3 client.). MS-Exchange 2010 GRT restores don't seem to work. We have a case open for this and have been providing info. This morning we're hearing this may be a known issue with migrating mailboxes from Exchange 2003 to 2010 and there may be an engineering binary available. No confirmation yet. Issue with bpclntcmd not resolving correct client names from HP-UX media server. (See forum for my posts on that topic.) Also we're running a RHEL6 (Linux) master and I'm seeing system lockups whenever we try to push extremely large items there. I first saw this when setting up vaulting which duplicates Data Domain to Quantum i6000 tape robot. Earlier in the week saw it again when I tried to push large Exchange (old Exchange 2003) backup to Data Domain. Both of these issues were mitigated by using the HP-UX media server for vaulting and to do the backup. (However the backup is the one affected by the bpclntcmd issue above.) -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Friday, April 29, 2011 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NetBackup 7.1 Hello, How has everyone's 7.1 experience been? Any gotchas or things to look out for? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 7.1
On Fri, 29 Apr 2011, Lightner, Jeff wrote: There appear to be differences in where fully qualified domain names need to be used. We have moved most of our environment to 7.1 but do have a few outstanding issues: Can't backup SQL 2000 on MS 2000 (not supported - we put the NBU 6.5.4 client on this server since there isn't a 7.1 version. Someone on this list says they got it working with 7.0.1 master and 6.5.3 client.). MS-Exchange 2010 GRT restores don't seem to work. We have a case open for this and have been providing info. This morning we're hearing this may be a known issue with migrating mailboxes from Exchange 2003 to 2010 and there may be an engineering binary available. No confirmation yet. Issue with bpclntcmd not resolving correct client names from HP-UX media server. (See forum for my posts on that topic.) Also we're running a RHEL6 (Linux) master and I'm seeing system lockups whenever we try to push extremely large items there. I first saw this when setting up vaulting which duplicates Data Domain to Quantum i6000 tape robot. Earlier in the week saw it again when I tried to push large Exchange (old Exchange 2003) backup to Data Domain. Both of these issues were mitigated by using the HP-UX media server for vaulting and to do the backup. (However the backup is the one affected by the bpclntcmd issue above.) The entire system locked up or just NetBackup? Does a cycle fix it? This is very scary and makes me wonder if 7.1 is ready for heavy production loads? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows?
Hello, Has anyone seen this? Windows 2008 clients: CLIENT: ALL_LOCAL_DRIVES On the client, EXCLUDE C:\ INCLUDE D:\ For the C:\ backup it will get the following error: Apr 29, 2011 10:09:22 AM - mounting TAPE01 Apr 29, 2011 10:09:24 AM - connecting Apr 29, 2011 10:09:24 AM - connected; connect time: 0:00:00 Apr 29, 2011 10:09:59 AM - mounted TAPE01; mount time: 0:00:37 Apr 29, 2011 10:09:59 AM - positioning TAPE01 to file 59 Apr 29, 2011 10:10:31 AM - positioned TAPE01; position time: 0:00:32 Apr 29, 2011 10:10:31 AM - begin writing Apr 29, 2011 10:11:31 AM - end writing; write time: 0:01:00 media manager received no data for backup image (90) With 7.0 this never happened, is this a bug? The data in D:\ does get backed up however. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows?
Why would you do that?! Are you trying to see how many errors you can cause by using non-sense combinations? Either ALL_LOCAL_DRIVES and exclude C: \ or specify D: only in the file section. You are including the D:\ drive which should be included when you said ALL_LOCAL_DRIVES. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: 29 April 2011 18:22 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows? Hello, Has anyone seen this? Windows 2008 clients: CLIENT: ALL_LOCAL_DRIVES On the client, EXCLUDE C:\ INCLUDE D:\ For the C:\ backup it will get the following error: Apr 29, 2011 10:09:22 AM - mounting TAPE01 Apr 29, 2011 10:09:24 AM - connecting Apr 29, 2011 10:09:24 AM - connected; connect time: 0:00:00 Apr 29, 2011 10:09:59 AM - mounted TAPE01; mount time: 0:00:37 Apr 29, 2011 10:09:59 AM - positioning TAPE01 to file 59 Apr 29, 2011 10:10:31 AM - positioned TAPE01; position time: 0:00:32 Apr 29, 2011 10:10:31 AM - begin writing Apr 29, 2011 10:11:31 AM - end writing; write time: 0:01:00 media manager received no data for backup image (90) With 7.0 this never happened, is this a bug? The data in D:\ does get backed up however. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 7.1
NetBackup was locked up and certain parts of the Linux OS weren't working. (e.g. I couldn't run ps -ef and get full output - it would hang). If I ran cat /proc/stat I would see process_blocked was showing 5 or higher whereas without these big things running it is typically at 0 or 1. At present I suspect this is more an issue with the server or its configuration than with NetBackup. I haven't yet had a chance to delve into it owing to the other issues and since I have a work around (other media servers) I've put it on the back burner. It works fine for most of our other UNIX/Linux/Windows backups. I saw similar issues on a RHEL5 Media server back when we were doing 6.5.4. On that server when trying to push backups to dedupe units it was experiencing similar hangs but when pushing to the tape library it wasn't. Since we got a new disk array and san switches at the same time as the library it may simply be we need to throttle things back or it could be an issue with the NFS stack. -Original Message- From: Justin Piszcz [mailto:jpis...@lucidpixels.com] Sent: Friday, April 29, 2011 12:40 PM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NetBackup 7.1 On Fri, 29 Apr 2011, Lightner, Jeff wrote: There appear to be differences in where fully qualified domain names need to be used. We have moved most of our environment to 7.1 but do have a few outstanding issues: Can't backup SQL 2000 on MS 2000 (not supported - we put the NBU 6.5.4 client on this server since there isn't a 7.1 version. Someone on this list says they got it working with 7.0.1 master and 6.5.3 client.). MS-Exchange 2010 GRT restores don't seem to work. We have a case open for this and have been providing info. This morning we're hearing this may be a known issue with migrating mailboxes from Exchange 2003 to 2010 and there may be an engineering binary available. No confirmation yet. Issue with bpclntcmd not resolving correct client names from HP-UX media server. (See forum for my posts on that topic.) Also we're running a RHEL6 (Linux) master and I'm seeing system lockups whenever we try to push extremely large items there. I first saw this when setting up vaulting which duplicates Data Domain to Quantum i6000 tape robot. Earlier in the week saw it again when I tried to push large Exchange (old Exchange 2003) backup to Data Domain. Both of these issues were mitigated by using the HP-UX media server for vaulting and to do the backup. (However the backup is the one affected by the bpclntcmd issue above.) The entire system locked up or just NetBackup? Does a cycle fix it? This is very scary and makes me wonder if 7.1 is ready for heavy production loads? Justin. Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 7.1
Hi Jeff, Thank you for your feedback, it is very useful. I will have to do more load testing from your feedback. Justin. On Fri, 29 Apr 2011, Lightner, Jeff wrote: NetBackup was locked up and certain parts of the Linux OS weren't working. (e.g. I couldn't run ps -ef and get full output - it would hang). If I ran cat /proc/stat I would see process_blocked was showing 5 or higher whereas without these big things running it is typically at 0 or 1. At present I suspect this is more an issue with the server or its configuration than with NetBackup. I haven't yet had a chance to delve into it owing to the other issues and since I have a work around (other media servers) I've put it on the back burner. It works fine for most of our other UNIX/Linux/Windows backups. I saw similar issues on a RHEL5 Media server back when we were doing 6.5.4. On that server when trying to push backups to dedupe units it was experiencing similar hangs but when pushing to the tape library it wasn't. Since we got a new disk array and san switches at the same time as the library it may simply be we need to throttle things back or it could be an issue with the NFS stack. -Original Message- From: Justin Piszcz [mailto:jpis...@lucidpixels.com] Sent: Friday, April 29, 2011 12:40 PM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NetBackup 7.1 On Fri, 29 Apr 2011, Lightner, Jeff wrote: There appear to be differences in where fully qualified domain names need to be used. We have moved most of our environment to 7.1 but do have a few outstanding issues: Can't backup SQL 2000 on MS 2000 (not supported - we put the NBU 6.5.4 client on this server since there isn't a 7.1 version. Someone on this list says they got it working with 7.0.1 master and 6.5.3 client.). MS-Exchange 2010 GRT restores don't seem to work. We have a case open for this and have been providing info. This morning we're hearing this may be a known issue with migrating mailboxes from Exchange 2003 to 2010 and there may be an engineering binary available. No confirmation yet. Issue with bpclntcmd not resolving correct client names from HP-UX media server. (See forum for my posts on that topic.) Also we're running a RHEL6 (Linux) master and I'm seeing system lockups whenever we try to push extremely large items there. I first saw this when setting up vaulting which duplicates Data Domain to Quantum i6000 tape robot. Earlier in the week saw it again when I tried to push large Exchange (old Exchange 2003) backup to Data Domain. Both of these issues were mitigated by using the HP-UX media server for vaulting and to do the backup. (However the backup is the one affected by the bpclntcmd issue above.) The entire system locked up or just NetBackup? Does a cycle fix it? This is very scary and makes me wonder if 7.1 is ready for heavy production loads? Justin. Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows?
That doesn't make any sense to me... why not just use all local drives and exclude C:\ from that... Having and exception to the exclude list of D:\ doesn't make sense... D:\ isn't part of C:\... I would just use all local drives and exclude C:\... Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Friday, April 29, 2011 10:52 AM To: Patrick Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows? Hi Patrick, The ALL_LOCAL_DRIVES is specified on the server, and then the team who handles windows can setup the includes and excludes locally on their client, that allows the user to configure the backups as they please and not require any intervention from the server-side of things other than adding the client properly. Example: Exclude Lists: All Policies All schedules C:\ Exceptions to the exclude list: All schedules D:\ Therefore, ALL_LOCAL_DRIVES backs up D:\ and System State and excludes C:\, this is how it has always worked and no errors and the data has been backed up successfully and tested via restore with no issues, the problem is with 7.0.1 and (maybe 7.0?) that it gets an error 90 for C:\ instead of just skipping it and exiting with a status 0, I think there was a tech note on this somewhere. Justin. On Fri, 29 Apr 2011, Patrick wrote: Why would you do that?! Are you trying to see how many errors you can cause by using non-sense combinations? Either ALL_LOCAL_DRIVES and exclude C: \ or specify D: only in the file section. You are including the D:\ drive which should be included when you said ALL_LOCAL_DRIVES. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: 29 April 2011 18:22 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows? Hello, Has anyone seen this? Windows 2008 clients: CLIENT: ALL_LOCAL_DRIVES On the client, EXCLUDE C:\ INCLUDE D:\ For the C:\ backup it will get the following error: Apr 29, 2011 10:09:22 AM - mounting TAPE01 Apr 29, 2011 10:09:24 AM - connecting Apr 29, 2011 10:09:24 AM - connected; connect time: 0:00:00 Apr 29, 2011 10:09:59 AM - mounted TAPE01; mount time: 0:00:37 Apr 29, 2011 10:09:59 AM - positioning TAPE01 to file 59 Apr 29, 2011 10:10:31 AM - positioned TAPE01; position time: 0:00:32 Apr 29, 2011 10:10:31 AM - begin writing Apr 29, 2011 10:11:31 AM - end writing; write time: 0:01:00 media manager received no data for backup image (90) With 7.0 this never happened, is this a bug? The data in D:\ does get backed up however. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows?
Hi, Please disregard, the actual example is: Exclude Lists: C:\ D:\ Include Lists:\ D:\Mydata Where mydata is the only path we want to backup and nothing else on D:\ (potentially TB of live DB, where, we only want the dumps, for example). Justin. On Fri, 29 Apr 2011, Chapman, Scott wrote: That doesn't make any sense to me... why not just use all local drives and exclude C:\ from that... Having and exception to the exclude list of D:\ doesn't make sense... D:\ isn't part of C:\... I would just use all local drives and exclude C:\... Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Friday, April 29, 2011 10:52 AM To: Patrick Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows? Hi Patrick, The ALL_LOCAL_DRIVES is specified on the server, and then the team who handles windows can setup the includes and excludes locally on their client, that allows the user to configure the backups as they please and not require any intervention from the server-side of things other than adding the client properly. Example: Exclude Lists: All Policies All schedules C:\ Exceptions to the exclude list: All schedules D:\ Therefore, ALL_LOCAL_DRIVES backs up D:\ and System State and excludes C:\, this is how it has always worked and no errors and the data has been backed up successfully and tested via restore with no issues, the problem is with 7.0.1 and (maybe 7.0?) that it gets an error 90 for C:\ instead of just skipping it and exiting with a status 0, I think there was a tech note on this somewhere. Justin. On Fri, 29 Apr 2011, Patrick wrote: Why would you do that?! Are you trying to see how many errors you can cause by using non-sense combinations? Either ALL_LOCAL_DRIVES and exclude C: \ or specify D: only in the file section. You are including the D:\ drive which should be included when you said ALL_LOCAL_DRIVES. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: 29 April 2011 18:22 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows? Hello, Has anyone seen this? Windows 2008 clients: CLIENT: ALL_LOCAL_DRIVES On the client, EXCLUDE C:\ INCLUDE D:\ For the C:\ backup it will get the following error: Apr 29, 2011 10:09:22 AM - mounting TAPE01 Apr 29, 2011 10:09:24 AM - connecting Apr 29, 2011 10:09:24 AM - connected; connect time: 0:00:00 Apr 29, 2011 10:09:59 AM - mounted TAPE01; mount time: 0:00:37 Apr 29, 2011 10:09:59 AM - positioning TAPE01 to file 59 Apr 29, 2011 10:10:31 AM - positioned TAPE01; position time: 0:00:32 Apr 29, 2011 10:10:31 AM - begin writing Apr 29, 2011 10:11:31 AM - end writing; write time: 0:01:00 media manager received no data for backup image (90) With 7.0 this never happened, is this a bug? The data in D:\ does get backed up however. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 7.1
How has everyone's 7.1 experience been? It runs filesystem backups well in the lab. Any gotchas or things to look out for? Things you would expect to be found in FA and to be in LBN before you discover it the hard way, including - upgrade of a solaris master with windows clients fails/takes days (look up bpplconvert in the archives; workaround available) - NDMP 3-way backups fail (workaround in Release Notes) - bandwidth directive for one client will apparently limit the entire domain's aggregate throughput to that limit (caution in Release Notes) If you've skipped 7.0[.1], be sure to read all those docs as well; important changes there are not repeated in the 7.1 docs. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows?
Hello Justin Had the same issue to just after upgrading to 7.0, a workaround that worked for was to exclude drive:\*.* Regards Michael 2011/4/29 Justin Piszcz jpis...@lucidpixels.com Hello, Has anyone seen this? Windows 2008 clients: CLIENT: ALL_LOCAL_DRIVES On the client, EXCLUDE C:\ INCLUDE D:\ For the C:\ backup it will get the following error: Apr 29, 2011 10:09:22 AM - mounting TAPE01 Apr 29, 2011 10:09:24 AM - connecting Apr 29, 2011 10:09:24 AM - connected; connect time: 0:00:00 Apr 29, 2011 10:09:59 AM - mounted TAPE01; mount time: 0:00:37 Apr 29, 2011 10:09:59 AM - positioning TAPE01 to file 59 Apr 29, 2011 10:10:31 AM - positioned TAPE01; position time: 0:00:32 Apr 29, 2011 10:10:31 AM - begin writing Apr 29, 2011 10:11:31 AM - end writing; write time: 0:01:00 media manager received no data for backup image (90) With 7.0 this never happened, is this a bug? The data in D:\ does get backed up however. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error 90 on Windows hosts with NBU 7.x client for Windows?
Hello Michael, I've tested this and I've confirmed you are correct it fixes the problem, under 7.0.1 as well! Thank you! Justin. On Fri, 29 Apr 2011, Michael Graff Andersen wrote: Hello Justin Had the same issue to just after upgrading to 7.0, a workaround that worked for was to exclude drive:\*.* Regards Michael 2011/4/29 Justin Piszcz jpis...@lucidpixels.com Hello, Has anyone seen this? Windows 2008 clients: CLIENT: ALL_LOCAL_DRIVES On the client, EXCLUDE C:\ INCLUDE D:\ For the C:\ backup it will get the following error: Apr 29, 2011 10:09:22 AM - mounting TAPE01 Apr 29, 2011 10:09:24 AM - connecting Apr 29, 2011 10:09:24 AM - connected; connect time: 0:00:00 Apr 29, 2011 10:09:59 AM - mounted TAPE01; mount time: 0:00:37 Apr 29, 2011 10:09:59 AM - positioning TAPE01 to file 59 Apr 29, 2011 10:10:31 AM - positioned TAPE01; position time: 0:00:32 Apr 29, 2011 10:10:31 AM - begin writing Apr 29, 2011 10:11:31 AM - end writing; write time: 0:01:00 media manager received no data for backup image (90) With 7.0 this never happened, is this a bug? The data in D:\ does get backed up however. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NetBackup 7.1
Do you have Windows Master Server? We ran upgrade on a standalone Windows Master Server and it went well. However, hot catalog backup failed with status code 2 on Windows Master. Had to download n install patch from Symantec's website which replaced bpbrm.exe and that solved the problem. +-- |This was sent by sandesh@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 7.1
Hi, Not sure who this was directed to, using Linux here, but good to know about that issue, thanks. Justin. On Fri, 29 Apr 2011, sandesh wrote: Do you have Windows Master Server? We ran upgrade on a standalone Windows Master Server and it went well. However, hot catalog backup failed with status code 2 on Windows Master. Had to download n install patch from Symantec's website which replaced bpbrm.exe and that solved the problem. +-- |This was sent by sandesh@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
