NetBackup Technical Information Updates: Deduplication FAQs
Speeding up deduplication Check here for new and updated technical articles (and videos) on NetBackup and NetBackup Appliances that have been vetted by a cross-functional content council of NBU product and technical support engineers. The first article (link above) takes a deeper dive into the NetBackup deduplication process. Read this article if you have ever wondered why: MSDP is always busy, even with no jobs running TLog processing takes days to complete DiskVolume is down You are getting Status Code 83, 84, or 2074 If you have feedback or questions on any of the articles, or if you have key topics or areas that you would like to see addressed, please comment and let us know. Our aim is to provide you with the most up-to-date technical information on the NetBackup issues that concern you most.
PUT MORE IN THE GUI!!!!!
I get more frustrated everyday! When I call Symantec support and ask for a simple solution....I am always told to "run this cmd". Netbackup is suppossed to be the industry leader in backup software....so I am told. My company has spent over $500K on the netbackup software.....I can just imagine how much other compaines have spent. Here is 1 small example..... We are planning on moving our datacenter around and need to move alot of servers from this rack to that rack. Some of the servers include the netbackup servers(master & medias). Due to synthetic backups and MSDP(kudos for that)...all backups are done but the duplications to tape are still running. I have 10 duplications pending to run and they will not finish by the time we need to bring down the servers. WHY can I not just right click and hold or suspend these duplications? I am sure it would not take to much to program that into the the gui. NO I have to run some cmd that takes me 30 minutes to gather all of the information I need. Then another 30 minutes to write the cmd to release the duplications. I am sure I could come up with atleast 5 examples of where GUI improvements would make everyone's life's better. I understand that in 7.6 there are suppossed to be ALOT of improvements in SLP's and what can be done. I have been asking for these "improvements" for 3yrs now. Like I said...my company has spent ALOT of money to purchase....and for support for this product. You would think it would not take too much to program in these improvements. Maybe if more of us let Symantec know how we feel....they might do something!
NetBackup 7.1 is now available!
(Crossposted from the "Netting Out NetBackup" blog) I'm very pleased to announce the General Availability (GA) of NetBackup 7.1! As you may have already read during the First Availability (FA), the key new features of NetBackup 7.1 include: Disaster Recovery AIR: Auto Image Replication Virtualization Linux single file restore for VMware Smart Policies for VMware Manageability / Ease of Use Customer Experience License / Inv / Deployment reporting Capacity model OpsCenter VBR parity Audit Trails (Phase 2) SLP Reporting LiveUpdate- Client Major Version Upgrade Deduplication HPUX MSDP support Oracle dedupe improvements IPv6 Support Supportability Job flow logging improvements Status Code 5 Cleanup Proliferation Red Hat 6 AIX 7 FT Media Server – 8Gb HBA BMR Windows support of SFW5 Snapshot Client updates Your power links for NetBackup 7.1 information are: The NetBackup Enterprise Server overview page: http://www.symantec.com/business/support/index?page=landing&key=15143 NetBackup 7.1 Download Information: http://symantec.com/docs/TECH153200 NetBackup 7.1 Documentation: http://symantec.com/docs/TECH154178 NetBackup 7.1 Late Breaking News (LBN): http://symantec.com/docs/TECH153422 NetBackup 7.x Compatibility Lists: http://symantec.com/docs/TECH59978 EDIT: Yes, you can upgrade to 7.1 from ANY 6.x! To assist with your upgrade, we recommend a stop at the Symantec Operations Readiness Tools page: https://sort.symantec.com/checklist/installVeritas InfoScale 7.0: Storage management feature support matrix for Veritas InfoScale products on Oracle
In the Veritas InfoScale 7.0 release, the Storage Foundation High Availability (SFHA) product portfolio has been replaced with a more simplified, robust, and comprehensive Veritas InfoScale portfolio that includes the following four products: Veritas InfoScale Foundation Veritas InfoScale Storage Veritas InfoScale Availability Veritas InfoScale Enterprise The core features of SFHA, storage management and availability, are consolidated in the Veritas InfoScale portfolio. This simplifies product licensing, installation, and performance. With this release, the storage management feature support map for Veritas InfoScale products on Oracle has been rearranged to suit the new Veritas InfoScale product model. The following table provides a mapping of the features for each product: For information on the use cases of the storage management features, see the Veritas InfoScale™ 7.0 Storage and Availability Management for Oracle Databases document. For more information on Veritas InfoScale products, see the following sections in the Veritas InfoScale What's new in this release document: About the Veritas InfoScale product suite About Veritas InfoScale Foundation About Veritas InfoScale Storage About Veritas InfoScale Availability About Veritas InfoScale Enterprise Veritas InfoScale documentation can be found on the SORT website.
OpsCenter 7.6 Upgrade Purge Setting Changes - Important for Analytics Users - Please Read!
In OpsCenter 7.6, purge settings will change from 420 to 220 days. For fresh 7.6 installations, there should be no cause for concern. However, upgrades from previous versions of OpsCenter, could cause a large amount of historical job information to be purged from OpsCenter. Symantec NetBackup OpsCenter 7.6 Administrator's Guide PDF http://www.symantec.com/docs/DOC5042 pg. 254 Note: Before OpsCenter 7.6,the default data purge period for the backup jobs data was 420 days. In case of OpsCenter 7.6 upgrade, the default data purge period that is displayed for backup jobs data depends on what you had in the previous OpsCenter version. If you retained the default data purge period in the previous OpsCenter version (that is 420 days), in OpsCenter 7.6, it is set to 220 days. If you changed the default data purge period in the previous OpsCenter version, the same period is displayed in OpsCenter 7.6. For example: If you changed the default period in OpsCenter 7.5 from 420 to 500 days, in OpsCenter 7.6, it is set to 500 days In short, if you have never changed your default purge settings from 420 days (default) in OpsCenter 7.0, 7.1, or 7.5, and upgrade to 7.6, your default will become 220 days. When OpsCenter triggers its purge cycle, 200 days of historical information will be lost. Please Note: This is only for users that have never modified the default purge setting of 420 days, in previous releases.
