NetBackup 7.6.1 / 2.6.1 - MSDP Conversion
After going through the 'pain' of MSDP conversion when moving appliances from 2.5.x to 2.6.0.x, whereby I saw conversion taking anywhere from 4hrs to 27hrs, I was surprised to see the conversion is required AGAIN when moving from NBU 7.6.0.3 to 7.6.1. I have only performed this upgrade in my test lab which has very little data in the MSDP pool, and is WIndows based NOT an appliance - but I am assuming this will also be the case when moving the appliances from 2.6.0.x to 2.6.1. Has anyone moved an appliance to 2.6.1 yet, and if so is the MSDP conversion a similar duration to that when moving from 2.5.x to 2.6.0.x ? As I mentioned my MSDP pool is tiny in the lab and conversion only took a minute or so. Thanks, AJ1.8KViews4likes11Comments
NBU 5220 Performance
We recently deployed a 5220 appliance into our environment as it was to be the savior in our battle against a backup window we were no longer able to meet. When we finally got it online and into our NBU environment the initial performance was great. The area we were to most benefit was with VMware backups. The data stores mounted directly to the appliance would allow direct access to the snapshots for a fast and efficient backup. Before this, we were performing client side backups so the impact on the hosts every night was significant as we tried backing up 600+ vms. The plan was to be able to move all Dev and test off-host backups to the middle of the day as the performance impact was minimal and the end result was an increased window to complete things. As we started with noon-time backups deduplication rates were high and so were the speeds. However, this performance gain was short lived, as we began increasing the load we suddenly saw performance drop to a point of concern. Backups were no longer speedy, 3500KB per second to 10,000KB. There are some that might pop to 24,000KB, but in a sample size of 15 as I write this, only one is showing 24,000. Now, I do have a few ideas. 1. We have a 72TB appliance, therefore, 2 disk trays, during the backups, the one disk tray is going crazy, all the lights are flashing and you can really see that it is working. However, the second tray is doing nothing. While you might see a blink here or there, it is almost nothing compared to the other disk tray. Is this to be expected? When we looked at the disk configuration, it shows concat, is this normal? 2. Too much data at once and we are simply burying the appliance. In reality, what sort of performance should I be able to expect from the appliance? 3. Relating to number 2, since we only have the one appliance right now while we wait to get the remote appliance in place, we are duping off to tape. This is running at the same time as a backup, so this means at the same time the appliance is writing a lot of data, it is also reading it back to tape. 4. We are overloading the data store so that read speed is bad from source to destination. We have fewer hosts,therefore, if we limit the jobs per host we limit the number of machines backing up at once (obviously). This means that backups take way long, so we removed the limit per host and just set a limit per data store. As we are new to it all, I am not sure what impact where, but again, I am trying to list any and all ideas from the start. 5. The appliance does not support multi-pathing, therefore, we only have a single path to the disk. Beyond that I am not sure, but this is something that doesnt help with the showcasing of the appliances to management at the moment. However, given the initial performance I am confident we can get back there.Solved3.2KViews4likes50Comments
duplications from wrong media server
I have two 5200 appliances (2.0.1) one is in our primary data center and one is at our DR site connected by a 43mb pipe. My primary appliance has two LTO tape libraries directly attachedvia fiber that are used for doing monthly backups. I am using SLP's for the back up and duplications. Every weekend we do a full backup (1.3tb)that is backed up to my primary appliance and then duplicated to my DR appliance.During this backup i notice that my media server that is being used is primary > primary (for backup) and DR > DR (for duplications). This is perfectly fine. Now heres the trouble. When i mix a duplication to tape in this process the system trys to load balance the duplication between my media servers. Meaning: One duplication job will show the primary as the media server for the tape backup and one job will show the DR appliance. This would all be ok if the DR appliance was on my local LAN but it is not and therefore any duplication using it as the media server to tape can take over 24 hours to complete. In the SLP for my monthlys I have removed the DR appliance as a duplication so i dont know why it keeps responding. Example: i had a 245gb exchange DB duplication thatwas usingmy DR appliance as the media server and it had been running for 48hours and was only 60% complete. I noticed the job and cancled it. When it retried it picked up my primary appliance as themedia server and in25min it was complete(over fiber channel). I opened a ticket with support 2 months ago but we have yet to figure out the deal. This hasnt been that big of an issue until another group wanted to replicate some VTL's to the DR and realized that the bandwith is 100% consumed all the time by netbackup. i have been tinkering with this for months and cannot figure out what i have configured wrong so i want to consult the almight Community for answers. LOL! To me it sounds like the media servers are setup so that they can load balance but i cant find were to disable that.Solved1.9KViews4likes6Comments
SNMP configuration for 5020-DeDupe appliance & 5220-MSDP
Is there any way to add a query to MIB list to recive an alert in trap reciever(SNMP server) fromDeDupe appliance & 5220-MSDP, whenever entire pool goes down(Situation when backup fails with status 2074). How can I change the priority for MIB lists ???? Regards, BharathSolved655Views3likes1CommentAfter upgrading appliance to 2.6.0.2 , backups fail intermittantly with error 24 and 14
Hi All, We recently upgraded on of our appliance from 2.5.3 to 2.6.0.2. It was a direct upgrade to 2.6.0.2 version. Since the upgrade backups are failing with error 24 and 14 mainly socket errors and we can see winsock error 10060 in bpbkar. The interesting thing is if we move the backups to the appliance which is not yet upgraded to 2.6.0.2 and is still at 2.5.3 level, the backup goes on fine. We have opened a case with Symantec and are still struggling for more than a week. Anyone of you had similar issues after upgrade. Kindly share and advise.Solved4.7KViews2likes36Commentsopscenter port
Hii, Netbackup : 7.6.0.2 OS : Linux Opscenter :OpsCenter_7.6.0.1 Link : https://*.*.*.*:443/opscenter/ Can anybody please tell me the port required for accessingopscenter through web browser. Becausing when I am accessing opscenter through URL I am getting below error. "An unknown exception occured"Solved2.8KViews2likes3Comments
NIC Bonding
Hello, Having a little trouble getting 802.3ad nic teaming working on two 5230 appliances. I've configured teaming before on Windows 2008 servers and it seems to work fine. The network team configures LACP on the switch side, and on the server side, I create the team in 802.3ad mode. On the appliance however, I create the bond, and on cli as well as through the web interface of the appliance, it looks to be created and functional, but on the switch side it doesn't look to be active. The bond has been created with eth1,2 and 3 ports (1 Gb/s). The web interface shows them all as up, and the network configuration shows the correct IP on bond0(eth1,eth2,eth3) with bond mode at 802.3ad. On the switch side, for some reason, the bond automatically splits into 2 separate bonds, 1 bond with eth1 and the other with eth2 and eth3. Both bonds show with LACP configured. We have two identical appliances, and we have tried configuring bonding on both appliances and the exact same thing happens. Has anyone come across this, or have any suggestions of what else to check? Thanks!Solved4.3KViews2likes8Comments
NetBackup Appliances: Best Practices, Known Issues, Installation, Configuration, and Troubleshooting tips, Documentation and Downloads
Don't Miss This!!! This article gives you a single point of access for help with NetBackup Appliance known issues, best practices, and troubleshooting tips for common Appliance problems such installation and configuration. The Symantec Technical Support team has found these KB articles to be especially helpful to NetBackup Appliance customers. Links to NetBackup downloads and documentation are also included. Let us know if you have any comments or questions! https://www-secure.symantec.com/connect/articles/netbackup-appliances-best-practices-known-issues-installation-configuration-and-troubleshoo420Views2likes0CommentsHOW TO - configure a SAN based Tape Drive and Libr on a 5220 Appliance
Hello Techies, Could someone please provide a step by step guide on how to configure a SAN based Tape Drive and Libr on a 5220 Appliance configured as a Media Server to a traditional Master Server. NBU v7.5 5220 -v2.5 I understand that zoning of tape drive and libr is required but how to go about selecting the HBA port and locating a WWPN from the appliance to zone and the following steps. thank you to those who reply. -ESMSolved3.9KViews2likes3Commentsunallocated disk space
Hi experts I have 2 NBU appliance 5220 , version 2.5.1 I could see 12.4GB unallocated disk on expansion unit storage. is this fairly normal??? if not how can I allocate 12.4GB to Expansion Unit Storage (unit_2) . please tell me complete process. NBUapp.Storage> show ---------------------------------------------------------------------- Device | Total | Unallocated | Status ---------------------------------------------------------------------- Appliance Operating System (sda) | 930.38 GB | - | In Use Base Unit Storage (unit_1) | 4.5429 TB | 0 GB | In Use Expansion Unit Storage (unit_2) | 35.470 TB | 12.450 GB | In Use Base Unit Storage (unit_1) ------------------------------- Catalog : 1 GB Deduplication: 4.5419 TB Expansion Unit Storage (unit_2) ------------------------------- Deduplication: 35.458 TB ---------------------------------------------------------------- Partition | Total | Available | Used | %Used ---------------------------------------------------------------- AdvancedDisk | 0 GB | 0 GB | 0 GB | 0% Deduplication | 40 TB | 1.8994 TB | 38.100 TB | 96 Unallocated | 12.450 GB | - | - | - Appliance Model is NetBackup Appliance 5220. Appliance Version is 2.5.1.Solved1.6KViews1like5Comments
NetBackup 7.6.1 / 2.6.1 - MSDP Conversion
After going through the 'pain' of MSDP conversion when moving appliances from 2.5.x to 2.6.0.x, whereby I saw conversion taking anywhere from 4hrs to 27hrs, I was surprised to see the conversion is required AGAIN when moving from NBU 7.6.0.3 to 7.6.1. I have only performed this upgrade in my test lab which has very little data in the MSDP pool, and is WIndows based NOT an appliance - but I am assuming this will also be the case when moving the appliances from 2.6.0.x to 2.6.1. Has anyone moved an appliance to 2.6.1 yet, and if so is the MSDP conversion a similar duration to that when moving from 2.5.x to 2.6.0.x ? As I mentioned my MSDP pool is tiny in the lab and conversion only took a minute or so. Thanks, AJNetBackup Appliances: Best Practices, Known Issues, Installation, Configuration, and Troubleshooting tips, Documentation and Downloads
Don't Miss This!!! This article gives you a single point of access for help with NetBackup Appliance known issues, best practices, and troubleshooting tips for common Appliance problems such installation and configuration. The Symantec Technical Support team has found these KB articles to be especially helpful to NetBackup Appliance customers. Links to NetBackup downloads and documentation are also included. Let us know if you have any comments or questions! https://www-secure.symantec.com/connect/articles/netbackup-appliances-best-practices-known-issues-installation-configuration-and-troubleshoo
