Symantec NetBackup 7

Still waiting for Symantec NetBackup 7 release announcement. It has not been released yet,  but actually since Dec 2009, Symantec has been offered what they call as Symantec NetBackup 7.0 First Availability (FA) program.

What’s New In Symantec NetBackup 7

Just a little bit overview of new features in the latest NetBackup 7.0 release:

Integrated Deduplication
Includes native deduplication within the NetBackup client and allows customers to increase the speed of backups in remote offices, the data center, and virtual environments.
  • Built-in client-side deduplication improves physical & virtual backups speeds by up to 10x
  • Software-based deduplication reduces costs by up to 70% versus appliance approaches
  • Integrated client and target-side deduplication provides more coverage with fewer tools
  • Manage and improve the performance of 3rd party deduplication appliances using OpenStorage
Simple & Comprehensive Data Protection for Virtual Environments
Simplifies virtual server data protection by standardizing backup of Hyper-V and VMware.
  • New VMware data protection improves speed by 50% and reduces storage by up to 40%
  • Only NetBackup offers instant file recovery from any type of VMware or Hyper-V backup
  • Complete deduplication across all virtual and physical systems regardless of backup method
  • No backup or recovery compromises for customers who backup directly to tape
Faster Disaster Recovery with Global Data Protection
Ensure rapid and easy recovery of critical applications and backup data at other sites with integrated replication features.
  • Recover terabytes of application data in seconds from anywhere at any point-in-time
  • Efficiently manage and move up to 80% less data between different sites with optimized replication
  • Unified analytics and reporting reduces recovery risk across locations and backup products
Improved Management Console and Usability
Provides centralized console for integrated reporting, monitoring, alerting and management for multiple backup and archive domains.
  • Better predict backup and archiving storage consumption
  • Analyze risk and quantify exposure and assess the recoverability of clients and applications
  • Easily track backup success rates by backup application across the entire organization
Expanded Support for Windows Server and Applications
  • NetBackup 7 fully supports Windows 2008 R2, Vista/XP/Windows 7, and Storage Server 2008
  • NetBackup 7 offers full backup and recovery support for Exchange 2010 DAG environments and Exchange 2003

For more detail, you can attend the Webcast: What’s New in Symantec NetBackup 7 on Tuesday, February 2 2010 @ 9:00 AM PT Presented By: Peter Elliman, Senior Product Marketing Manager, NetBackup.

Attend this webcast and learn how NetBackup 7 can enable your company to:

  • Reduce backup storage growth and network utilization by up to 80-90%
  • Streamline global backup and recovery management across both physical and virtual environments
  • Simplify and speed recovery of critical information from anywhere

REGISTER Webcast here.

Related docs:

NetBackup 7.0 Upgrade Portal (Updated Jan 19th, 2010):
The NetBackup 7.0 Upgrade Portal contains important information regarding upgrading to NetBackup 7.0 from a previous 6.x version.

UPDATE:

Netbackup 7 released already. Read the manual guide:

Installation:

NetBackup 7.0 Upgrade Portal    http://entsupport.symantec.com/docs/332137
NetBackup Release Notes    http://entsupport.symantec.com/docs/340098
Additional Operational Notes    http://entsupport.symantec.com/docs/337179
Installation Guide for Windows  http://entsupport.symantec.com/docs/340100
Installation Guide for UNIX and Linux  http://entsupport.symantec.com/docs/340101
LiveUpdate Guide  http://entsupport.symantec.com/docs/340102

Administrator Guides:

Administrator’s Guide for UNIX,Linux, I  http://entsupport.symantec.com/docs/340103
Administrator’s Guide for UNIX,Linux, II  http://entsupport.symantec.com/docs/340104
Administrator’s Guide for Windows, I  http://entsupport.symantec.com/docs/340105
Administrator’s Guide for Windows, II  http://entsupport.symantec.com/docs/340106
OpsCenter Administrator’s Guide  http://entsupport.symantec.com/docs/340107
OpsCenter help set  http://entsupport.symantec.com/docs/340108
NDMP Administrator’s Guide  http://entsupport.symantec.com/docs/340109
Snapshot Client Administrator’s Guide  http://entsupport.symantec.com/docs/340110
NetBackup for Hyper-V Guide  http://entsupport.symantec.com/docs/340111
NetBackup for VMware Guide  http://entsupport.symantec.com/docs/340112

For complete manual guides, go to here:

http://seer.entsupport.symantec.com/docs/341274.htm

Top 10 Recommended Veritas NetBackup TechNotes

Document ID: 284146

http://support.veritas.com/docs/284146

Top 10 Recommended Veritas NetBackup ™ TechNotes


Details:

TechNote ID Description
183702 NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS – how they work and how to configure them
276739 STATUS CODE: 156 “snapshot error encountered” occurs when utilizing VSP or VSS for open file backups.
290185 Welcome to the Veritas NetBackup ™ 6.5 Upgrade Portal!
254809 DOCUMENTATION: How to configure email notifications for Windows clients using BLAT and nbmail.cmd in Veritas NetBackup ™
274063 Robtest commands that can be used to test the SCSI functionality of a robot
280202 GENERAL ERROR: When attempting to expire a media in Veritas NetBackup ™ 6.0 with the bpexpdate command, the message “requested media id was not found in the EMM database” is received.
278533 STATUS CODE: 800, NetBackup 6.0 jobs are failing with Status 800 (resource request failed).
244652 DOCUMENTATION: How to configure buffers for NetBackup in a Windows NT/2000 environment to improve performance
264924 DOCUMENTATION: How to restore an Exchange 2000/2003 database to the same or alternate client
245184 DOCUMENTATION: How to configure NetBackup for Mailbox backups of an Exchange 2000/2003 server

Note: Links to each of the documents listed in the following chart (by TechNote ID) can be found below, in the Related Documents section.

Related Documents:

183702: NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS – how they work and how to configure them
http://support.veritas.com/docs/183702

244652: DOCUMENTATION: How to configure buffers for NetBackup in a Windows NT/2000 environment to improve performance
http://support.veritas.com/docs/244652

245184: DOCUMENTATION: How to configure NetBackup for Mailbox backups of an Exchange 2000/2003 server
http://support.veritas.com/docs/245184

254809: DOCUMENTATION: How to configure email notifications for Windows clients using BLAT and nbmail.cmd in Veritas NetBackup ™
http://support.veritas.com/docs/254809

264924: DOCUMENTATION: How to restore an Exchange 2000/2003 database to the same or alternate client
http://support.veritas.com/docs/264924

274063: Robtest commands that can be used to test the SCSI functionality of a robot
http://support.veritas.com/docs/274063

276739: STATUS CODE: 156 “snapshot error encountered” occurs when utilizing VSP or VSS for open file backups.
http://support.veritas.com/docs/276739

278533: STATUS CODE: 800, NetBackup 6.0 jobs are failing with Status 800 (resource request failed).
http://support.veritas.com/docs/278533

280202: GENERAL ERROR: When attempting to expire a media in Veritas NetBackup ™ 6.0 with the bpexpdate command, the message “requested media id was not found in the EMM database” is received.
http://support.veritas.com/docs/280202

290185: Welcome to the Veritas NetBackup ™ 6.5 Upgrade Portal!
http://support.veritas.com/docs/290185

Veritas Netbackup Status Code and Troubleshooting Guide

If you got failed or error with Netbackup, sometimes it’s not easy to troubleshoot. The common error that always faced with my customer is ‘status code 196 : client backup was not attempted because backup window closed‘, or the worst is the got ‘status code 96 : unable to allocate new media for backup, storage unit has none available‘.

I think if you familiar with Netbackup, and somebody told you about these error code, probably with confident smile you will say, “Owh, its easy man; for status code 196, check the backup schedule then re-arrange the backup window time between all server, client and mediaserver and then for status code 96, just simply put new cartridges on its volume pool, then run backup again, I bet 100% the error code will gone. right?.

But do you remember the whole Netbackup status code and how to troubleshoot? If you don’t then here are the Technote contains a table for NetBackup’s Status Codes, with links to potential resolutions for each:

http://seer.entsupport.symantec.com/docs/301522.htm

or, you can also directly go to this page:

http://www.symantec.com/business/support/overview.jsp?pid=15143

then just put the keyword, exp: “status code 196”.

Example:

Download also the “Veritas NetBackup Troubleshooting Guide for UNIX, Linux, and Windows

Veritas Netbackup Command Line Guide

This is just my own notes on Veritas Netbackup Command Line Guide, feel free to copy-paste;-):
————————————————————————————-
/usr/openv/netbackup/bin/jnbSA >>run NBU GUI
/usr/openv/netbackup/bin/bpadm >>NBU Menu Interface
/usr/openv/volmgr/bin/vmquery -deassignbyid QOSFEB 1 0 >>deassign media
/usr/openv/netbackup/bin/admincmd/bpexpdate -m QOSFEB -d 0 -force >>Expired
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -L >
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -add -max_jobs 99 >>set max jobs to 99
/usr/openv/netbackup/bin/bplist -C aziz -t 4 -R / >>chek list file that backed up already
/usr/openv/netbackup/bin/bpbackup -i -p test -s full -S sunserver1 >>Run jobs
/usr/openv/volmgr/bin/ltid -nsu >>robot will’t unload tape
/usr/openv/volmgr/bin/stopltid >>stop ltid
/usr/openv/netbackup/bin/admincmd/bperror -statuscode 96 >>explanation error
/usr/openv/netbackup/bin/admincmd/bpbackupdb >>backup catalog
/usr/openv/netbackup/bin/bpclntcmd -pn >>query master server communication
/usr/openv/netbackup/bin/bpclntcmd -sv >>query master server version
/usr/openv/netbackup/bin/admincmd/get_license_key >>add/remove license key

#/usr/openv/netbackup/bin/admincmd/:
bpmedia -movedb -ev -oldserver -newserver
bpmedia -movedb -ev PR0161 -oldserver drsskdb1 -newserver masterbackup >>move database to newserver

bpimage -newserver masterbackup -oldserver drsskdb1 -id BI0336 >>

/usr/openv/volmgr/bin/vmoprcmd -crawlreleasebyname

/usr/openv/netbackup/bin/bpdbm -consistency >>Catalog Backup Integrity check

Restore Catalog:
—————–
/usr/openv/netbackup/bin/admincmd/bprecover –help
/usr/openv/netbackup/bin/admincmd/bprecover -r all -dpath f: >>restore dari catalog di disk
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d dlt >>tape model dlt
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d 8mm >>tape model 8mm
/usr/openv/netbackup/bin/admincmd/bprecover -r all -tpath /dev/rmt/0cbn >>
bprecover -l -tpath /dev/rmt/hc2d4
————

{Verify the Netbackup communication daemons are listening for request:
netstat -a |grep bpcd
netstat -a |grep vnetd

{UNFREEZE TAPE MEDIA MARKED AS FROOZEN:
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT738L4
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT626L4

c:\Program Files\Veritas\Netbackup\bin> bpmedia -unfreeze -m -h
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -U -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -L -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bpmedialist -summary
c:\Program Files\Veritas\Netbackup\bin\goodies\available_media

{Remove information about existing media ID from NBU Catalog then delete the existing media ID:
/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m

{initiate import media ID JKT152:
./bpimport -create_db_info -id JKT152

——————————————————————————————–
TUNING AND TWEAKING:

/usr/openv/netbackup
cat /usr/openv/netbackup/NET_BUFFER_SZ
65536

For example, a Network Buffer Size of 64KB could be configured and checked like this:
# echo “65536” > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536

/usr/openv/netbackup/db/config:
NUMBER_DATA_BUFFERS
SIZE_DATA_BUFFERS
NUMBER_DATA_BUFFERS_RESTORE

NUMBER_DATA_BUFFERS:
8 for non-multiplexed backups
4 for multiplexed backups
8 for non-multiplexed restore, verify, import and duplicate

SIZE_DATA_BUFFERS:
32768 for non-multiplexed backups
65536 (64512 on Solaris) for multiplexed backups

NUMBER_DATA_BUFFERS_RESTORE:
12 (only effects restores of multiplexed backups)

—-
tpautoconf -report_disc , this command will list what device that had been missing or found.
tpautoconf -replace_drive drive_name –path drive_path, this command will update the existing device

{STOP NEXT SHCEDULE BACKUP REQUEST:
bprdreg -terminate >>WILL STOP BPRD services

{SHARED SYMANTEC PROCESS:
check with bpps -x command:

/opt/VRTSpbx/bin/vxpbx_exchange start
/opt/VRTSpbx/bin/vxpbx_exchange stop

Veritas NetBackup 6.5 and 6.5.x Manuals and links

6.5.x Release Updates
The 6.5.x Release Updates provide documentation updates for the additional features provided in each release. The links to the documentation updates for each version is as follows:
-6.5.4 Release Update:
-6.5.3 Release Update:

Step Upgrading to Veritas Netbackup 6

Step by Rakesh Khandelwal:

First check release notes to make sure H/W and O/S you are about to use is supported or not. Release Notes for UNIX and Windows (http://support.veritas.com/docs/279259 )
Symantec’s Upgrade Guide, Version “B” ( http://support.veritas.com/docs/285590 )

Assuming you have already checked databse consistency and resolved any known or preexisting consistency issues or catalog inconsistencies

Step 1 : Prepare, Upgrade and Patcvh the Master Server

  1. Backup the catalogs
  2. In a c clustered environment, take NetBackup offline.
  3. Deactivate all policies.
  4. On Solaris Only, uninstall the old version of NetBackup.
  5. Upgrade the software:
  6. Stop all services.
  7. run the installation.
  8. Apply the latest maintenance packs.
    NOTE : For Windows clustered environments, perform NetBackup upgrade installations from the system console, not from a Remote Terminal Services sessions.

Step 2: Populate the EMM database

  1. Ensure that the daemons or services and processes are running.
  2. Run nbpushdata -add on the ipgraded systems in the following order:
    a) The host that was the 5.x Global Device Database host
    b) All upgraded master servers
    c) All upgraded 5.x Volume Database hosts
  3. Restart the services/daemons.
  4. Run nbpushdata -modify_5x_hosts on all 6.0 master servers.


Step 3: Upgrade the NetBackup Remote Administration Console System and any addition components

1.Stop all services/daemons

2.Run the installation.

3.Apply the latest maintenace packs.

4.Restart the services/daemons.

5.Upgrade and add-on components.

6.Install the latest maintenance packs for the add-on components.


Step 4: Prepare, upgrade and Patch the Media servers

  1. On Solaris only, uinstall the old version of NetBackup.
  2. Upgrade the software:
    a) Stop all services/daemons.
    b) Run the instalation.
  3. Apply the latest maintenance packs.
  4. Restart the services/daemons.
  5. Populate the EMM database:
    nbpushdata -add

Step 5: Upgrade the clients

  1. Perform local or remote client upgrades.
  2. Install the latest maintenance packs.

Step 6: Complete and Test the upgrade

  1. Activate the policies
  2. Run test backup jobs.
  3. Backup the catalogs.

Additional Information from Dennis Strom:

here all the info I have on upgrading. I even included a link to this post since I really liked Rakesh’s post.

Other link:

Upgrading to Veritas NetBackup 6.0 on Supported Windows Platforms

VERITAS NetBackup 6.0 Release Notes, for UNIX, Windows, and Linux

Upgrading to Veritas NetBackup 6.0

VERITAS NetBackup 6.0

How to restore LTO1 or 2 on LTO 3 Drive

For many reason, I re-post again about this issue; How to restore LTO1 or 2 on LTO 3 Drive…

The procedure is as follows:

  1. Inject the tape into the ACS library, then perform a robot inventory of the ACS library.

  2. After the volume database is updated, the RobotType of the media will change to “ACS” and the tapes should be recognized as “hcart”.

  3. Run “vmchange -new_mt <new density> -m <media ID>” to change the density. <new density> should be “hcart3” for the LTO Gen-3 drive and <media ID> refers to the media barcode. An eg would be “vmchange -new_mt hcart3 -m dx0333”

  4. Run “vmquery -m <mediaID>” to check that the density have been updated to “hcart3” from “hcart”.

  5. Run “bpmedia -changeden -new <density> -ev <mediaID>”

  6. eg “bpmedia -changeden -new hcart3 -ev dx0333” Note: This command will take some time to complete. Please be patient and let it complete on it’s own. If terminated halfway, strange things may occur later.

  7. Run “bpmedialist -m <mediaID>” to check that the density have been updated.

  8. Run the normal restoration procedure to restore the data from the LTO Gen1 tapes using the ACS library.

  9. Once, we have completed the restoration, the tape should be ejected from the ACS library to prevent it from being used for future backups. If necessary, will need to execute the commands in Step 3 and 5 to change the density back to “hcart”.