Re: [Veritas-bu] NetBackup Not Using Backup NIC
Hello John The REQUIRED_INTERFACE option in bp.conf/registry might be what you are after A route through eth2 for contacting your backup server might be an option Regards Michael 2011/3/18 Crowey netbackup-fo...@backupcentral.com Gidday, I'm trying to troubleshoot some really bad performance issues when writing to disc for NetBackup differentials, and as part of that process I noticed that NetBackup is not using the backup NIC I have configured on our main server. Our main server has two NICs configured, eth0 on 172.20.10.23 and eth2 on 172.20.10.24. In DNS I have eth0's address resolving to server, and eth2's address resolving to server-backup. I have NetBackup configured to connect to the address server-backup. And in the Admin Console | Host Properties | Clients I can connect to the server - ostensibly via the configured DNS address of server-backup. I can ping both addresses on the Master/Media NetBackup server as well as the server itself. However if I do a ifconfig eth0/2 on the server in question I get this ... eth0 Link encap:Ethernet HWaddr 00:14:4F:0D:82:92 inet addr:172.20.10.23 Bcast:172.20.10.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe0d:8292/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:126134922 errors:0 dropped:0 overruns:0 frame:0 TX packets:249411328 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:46698652928 (43.4 GiB) TX bytes:289231929457 (269.3 GiB) Base address:0x8800 Memory:85b8-85ba eth2 Link encap:Ethernet HWaddr 00:14:4F:0D:7E:FA inet addr:172.20.10.24 Bcast:172.20.10.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe0d:7efa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:197097 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:92088745 (87.8 MiB) TX bytes:782 (782.0 b) Base address:0xc800 Memory:b3d8-b3da Clearly eth2 (server-backup) is receiving OK, but nothing is going back out. Any ideas what I can do to resolve this? - I'm sure its probably something stupid, but I'd be grateful for any advice on this matter. (I'm running RHEL AS 4.6 x86_64 by the way) Cheers John +-- |This was sent by jcr...@marketforce.com.au 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
Re: [Veritas-bu] NetBackup Not Using Backup NIC
Both NICs are on the same IP segment. addr:172.20.10.23 Mask:255.255.255.0 addr:172.20.10.24 Mask:255.255.255.0 As far as the OS is concerned they are on the same dedicated segments with equal weight (Metric:1) in the routing table and probably binding to eth0 first. Run bpclntcmd -self to see which interface(s) NBU thinks it is using. My guess is both will show up. REQUIRED_INTERFACE only works for outbound TCP SYN requests sent from the server. If you are backing up using both interfaces then REQUIRED_INTERFACE is not an option. If only using the eth2 then try this- REQUIRED_INTERFACE = server-backup. Otherwise to try using static host routes to force the OS to pick eth2 over eth0 depending on which IP segment the clients are on if you want your backups to use that interface. Dan O -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Crowey Sent: Thursday, March 17, 2011 9:08 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] NetBackup Not Using Backup NIC Gidday, I'm trying to troubleshoot some really bad performance issues when writing to disc for NetBackup differentials, and as part of that process I noticed that NetBackup is not using the backup NIC I have configured on our main server. Our main server has two NICs configured, eth0 on 172.20.10.23 and eth2 on 172.20.10.24. In DNS I have eth0's address resolving to server, and eth2's address resolving to server-backup. I have NetBackup configured to connect to the address server-backup. And in the Admin Console | Host Properties | Clients I can connect to the server - ostensibly via the configured DNS address of server-backup. I can ping both addresses on the Master/Media NetBackup server as well as the server itself. However if I do a ifconfig eth0/2 on the server in question I get this ... eth0 Link encap:Ethernet HWaddr 00:14:4F:0D:82:92 inet addr:172.20.10.23 Bcast:172.20.10.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe0d:8292/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:126134922 errors:0 dropped:0 overruns:0 frame:0 TX packets:249411328 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:46698652928 (43.4 GiB) TX bytes:289231929457 (269.3 GiB) Base address:0x8800 Memory:85b8-85ba eth2 Link encap:Ethernet HWaddr 00:14:4F:0D:7E:FA inet addr:172.20.10.24 Bcast:172.20.10.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe0d:7efa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:197097 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:92088745 (87.8 MiB) TX bytes:782 (782.0 b) Base address:0xc800 Memory:b3d8-b3da Clearly eth2 (server-backup) is receiving OK, but nothing is going back out. Any ideas what I can do to resolve this? - I'm sure its probably something stupid, but I'd be grateful for any advice on this matter. (I'm running RHEL AS 4.6 x86_64 by the way) Cheers John +-- |This was sent by jcr...@marketforce.com.au 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
Re: [Veritas-bu] NetBackup 7.1GA
Yeah, I was in the same boat, had just upgraded to 7.0.1 and then realized 7.1 was available. Delving into the 7.0.1 docs related to VMware backups using the vStorage API, if you're planning on using a VM guest as a backup host using the hotadd feature for access to the vmdk's, I'm pretty certain 7.0.1 isn't compatible with the vSphere 4.1 vStorage API, but 7.1 is. I ended up deciding to go 7.1 as our VMware support group had just upgraded to vSphere 4.1. The 7.1 upgrade was very smooth and I haven't run into any new problems so far. -John On 03/16/2011 06:20 AM, WEAVER, Simon (external) wrote: I just upgraded to 7.0.1 - Wonder if its worth upgrading again. -Original Message- From: Bill Coleman [mailto:bill_cole...@symantec.com] Sent: Tuesday, March 15, 2011 9:48 PM To: veritas-bu@mailman.eng.auburn.edu Cc: Marianne Van Den Berg; jpis...@lucidpixels.com; WEAVER, Simon (external) Subject: RE: [Veritas-bu] NetBackup 7.1GA Netbackup 7.1 has gone generally available after over 315 customers installed the software for a total of 4000 days of usage. 40% of those customers installed it into a production environment. How customers can access the software: Symantec will be sending an official Software Version Upgrade notification during the week of March 21st, which will include your license keys and media access information. However, should you require immediate access to your licenses and media, we invite you to visit the Licensing Portal. Please follow these instructions for registering your product on the Symantec Licensing Portal: 1.Go to https://licensing.symantec.com 2.Returning customers Login. New users must Create an Account first. 3.After logging in, select the 'I don't have an Upgrade Notification ID' button. 4.Choose your customer number from the drop down menu and click on the select button 5.Click on the appropriate notification ID 6.Click on the 'upgrade' button 7.If you have not upgraded previous versions of Symantec NetBackup, you will be required to do so sequentially in order to obtain your Symantec NetBackup 7.1 information 8.Select the licenses you would like to upgrade and click the 'Upgrade' button. 9.Verify contact information for the licenses you are upgrading and click the 'Complete Registration' button. 10. The license key(s) will be provided on the next screen. 11. You may then click the 'Get Software' button to obtain your product. Please Note: In some instances you may be required to repeat the upgrade process in order to retrieve the current version of the NBU product. Should you require any further assistance, please contact our Customer Care team. http://go.symantec.com/customercare -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, March 15, 2011 9:43 AM To: Marianne Van Den Berg; jpis...@lucidpixels.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NetBackup 7.1GA Thakns :) -Original Message- From: Marianne Van Den Berg [mailto:mvdb...@stortech.co.za] Sent: Tuesday, March 15, 2011 2:40 PM To: WEAVER, Simon (external); 'jpis...@lucidpixels.com'; 'veritas-bu@mailman.eng.auburn.edu' Subject: Re: [Veritas-bu] NetBackup 7.1GA You can no longer download from the ftp site - you have to use FileConnect. I believe that the GA announcement was a bit premature though, and that the downloads will only be available later this week. Will follow up with URL's as soon as I'm online again. M. Sent from my BlackBerry Bold - Original Message - From: veritas-bu-boun...@mailman.eng.auburn.edu veritas-bu-boun...@mailman.eng.auburn.edu To: Justin Piszcz jpis...@lucidpixels.com; veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Sent: Tue Mar 15 16:27:32 2011 Subject: Re: [Veritas-bu] NetBackup 7.1GA Thoughts I have are I just upgrade to 7.0.1:-(( -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin Piszcz Sent: Tuesday, March 15, 2011 12:38 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NetBackup 7.1GA Hi, Apparently its out now: http://www.symantec.com/connect/forums/netbackup-71-now-available But, I don't see it on the FTP site? ftp://ftp.nbu.support.veritas.com/pub/support/products/NetBackup_Enterpr ise_Server/ Thoughts? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] media expiration as of Start Time.
Dear All, Please advise.. Our some of the big size backup's taking 18 hours to complete and these backups spans to 4-5 Tapes. The issue is all the Backup (4-5) Tapes have different expiration time. Assume my backup start at 01:00 am and it takes 18 hours to complete. I have the backup retention policy to 3 weeks. Once the tapes are back after 3 weeks I can see the data expiration is as of 18:00 hours... etc... where my backup will start at 01:00 am and it will fail with error 96. Please advise how I can expire the backup images before the next Backup Start Time.. With Warm Regards =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Harpreet Singh Chana Phone : (O) 6895 - 4326 Fax : (O) 6895 - 4991 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** Please do not print this email unless it is absolutely necessary. Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media expiration as of Start Time.
You can use the bpexpdate command to expire images (you want to expire images rather than tapes - this frees up space on the tapes and if these are the only images will expire the tape). However, your question implies you are rather tight on tapes in the first place and rather than manually expiring tapes early you might want to invest in some new ones so you can have things expire automatically. You also don't mention how often you're running this backup. Hopefully you don't do it just once ever 3 weeks. That is to say hopefully you do not expire the last backup before you run the current one. If your system crashes in the middle of the current backup you wouldn't have any if you're overwriting the same tapes the way you imply. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Harpreet SINGH Sent: Friday, March 18, 2011 12:14 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media expiration as of Start Time. Dear All, Please advise.. Our some of the big size backup's taking 18 hours to complete and these backups spans to 4-5 Tapes. The issue is all the Backup (4-5) Tapes have different expiration time. Assume my backup start at 01:00 am and it takes 18 hours to complete. I have the backup retention policy to 3 weeks. Once the tapes are back after 3 weeks I can see the data expiration is as of 18:00 hours... etc... where my backup will start at 01:00 am and it will fail with error 96. Please advise how I can expire the backup images before the next Backup Start Time.. With Warm Regards =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Harpreet Singh Chana Phone : (O) 6895 - 4326 Fax : (O) 6895 - 4991 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** Please do not print this email unless it is absolutely necessary. Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. ___ 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] media expiration as of Start Time.
If the intent is to re-use the same set of tapes, you'd could either set the retention period to something less than 3 weeks (e.g. 19 days) or manually expire the images on the tapes prior starting the next backup. The later could be done using a combination of the 'bpexpdate' and 'vmquery' utilities. Something like, bpexpdate -m $media_id -d 0 -force vmquery -deassignbyid $media_id 2 0 This could probably be scripted with a bpstart_notify.policy_name script if you knew which tapes you would be using. -John On 03/18/2011 12:14 PM, Harpreet SINGH wrote: Dear All, Please advise.. Our some of the big size backup's taking 18 hours to complete and these backups spans to 4-5 Tapes. The issue is all the Backup (4-5) Tapes have different expiration time. Assume my backup start at 01:00 am and it takes 18 hours to complete. I have the backup retention policy to 3 weeks. Once the tapes are back after 3 weeks I can see the data expiration is as of 18:00 hours... etc... where my backup will start at 01:00 am and it will fail with error 96. Please advise how I can expire the backup images before the next Backup Start Time.. With Warm Regards =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Harpreet Singh Chana Phone : (O) 6895 - 4326 Fax : (O) 6895 - 4991 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** Please do not print this email unless it is absolutely necessary. Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. ___ 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] media expiration as of Start Time.
Actually ignore the vmquery ... portion below. Forgot this is has been depricated in current releases and is handled by the bpexpdate utility. -John On 03/18/2011 01:29 PM, John Meyers wrote: If the intent is to re-use the same set of tapes, you'd could either set the retention period to something less than 3 weeks (e.g. 19 days) or manually expire the images on the tapes prior starting the next backup. The later could be done using a combination of the 'bpexpdate' and 'vmquery' utilities. Something like, bpexpdate -m $media_id -d 0 -force vmquery -deassignbyid $media_id 2 0 This could probably be scripted with a bpstart_notify.policy_name script if you knew which tapes you would be using. -John On 03/18/2011 12:14 PM, Harpreet SINGH wrote: Dear All, Please advise.. Our some of the big size backup's taking 18 hours to complete and these backups spans to 4-5 Tapes. The issue is all the Backup (4-5) Tapes have different expiration time. Assume my backup start at 01:00 am and it takes 18 hours to complete. I have the backup retention policy to 3 weeks. Once the tapes are back after 3 weeks I can see the data expiration is as of 18:00 hours... etc... where my backup will start at 01:00 am and it will fail with error 96. Please advise how I can expire the backup images before the next Backup Start Time.. With Warm Regards =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Harpreet Singh Chana Phone : (O) 6895 - 4326 Fax : (O) 6895 - 4991 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** Please do not print this email unless it is absolutely necessary. Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. ___ 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 -- John Meyers Lead Systems Programmer Wright State University Dayton, Ohio. Voice: 937-775-3580 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Server OS and NBU upgrades
Does anyone have any experience (good or bad) with upgrading from Windows Server 2003 to 2008 and NBU 6.5 to 7.0? Currently my backup server is running the older versions of both. I have the software to upgrade both of them. Is there a preferred sequence: upgrade NBU then the OS or upgrade the OS first and then NBU? When upgrading NBU, will it preserve the settings and policies already created? James McDonald System Administrator SAIC - IISBU 410-312-2232 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Brain storm for the Week End (for a shall script)
Dear All,
I am on Netbackup 7.0 and OS = Redhat 5.4
Need your help to have a look on this attached script and advise.
This script will send us a consolidated backup status Report after 18
hours.
Also I am able to send the Backup Status by Backup Policy Selection. i.e.
Team A will not know the backup status of Team B
In this script the email sent option is as
-- If backup has any exceptions (i.e. Backup Status Code more than 0 )
then send email to XYZ + ABC + AB
-- If backup completed successfully then send email to ABC + AB
-- send the Netbackup Logs to AB
(See attached file: mail_bp_reports.txt)
I am heaving a issue with this script where I am not able to select the
Exact Backup Policy Name
ie.
BOSS-BKUP
ERP-Backup
I have noticed if I create a new backup policy with 'BOSS-BKUP-1' or
'ERP-Backup-2' it is also appearing in the backup status. Where I don't
want this.
Please help to have a look and advise how I can select the EXACT Policy
Name i.e. 'BOSS-BKUP' or 'ERP-BKUP' as per my Policy List.
gen_outfile_for_backup_policy()
{
backupPolicyList= \
BOSS-BKUP \
ERP-Backup \
Windows_Bkup\
Windows_Bkup_All\
Windows_Bkup_M-N\
FS-S-BKUP \
FS-S-BKUP-1 \
FS-N-BKUP \
ESX_VCB_BKUP\
Resignee_Usrs1 \
Resignee_Usrs2
With Warm Regards
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Harpreet Singh Chana
Phone : (O) 6895 - 4326
Fax : (O) 6895 - 4991
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
** Please do not print this email unless it is absolutely necessary.
Notice
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying or distribution of the message, or
any action taken by you in reliance on it, is prohibited and may be
unlawful. If you have received this message in error, please delete it
and contact the sender immediately. Thank you.
mail_bp_reports.txt
Description: Binary data
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Check_coverage :-Script not working.
Hello Mates, Below is the url : ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Check_coverage :-Script not working.
Hello Mates, Below is the url that states ,how to generate Hardware,OS and NB client version in a text file. http://www.symantec.com/business/support/index?page=contentid=TECH128723 I have tried but every time hardware output is always empty. Also ,while running this ,i am getting ./check_coverage: test: argument expected Generating Hosts Report Completed report The Hardware/OS Report can be found in /tmp/hardware_rpt.03-18@17:09 The Hosts Report can be found in /tmp/hosts_rpt.03-18@17:09 Please suggect if I am doing something else i see that there is a bug in the check_coverage script. Do we have any other option to generate the clients os ,harware and NB verion ? Thanks ,| pranav___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
