Symantec NetBackup Blueprints - VOXvox.veritas.com/legacyfs/online/veritasdata/NetBackup 7.6... ·...

Symantec NetBackup Blueprints

Symantec NetBackup Blueprints Blueprint for NetBackup Catalog

Symantec Backup and Recovery Technical Services

1


FEEDBACK

Please hide this slide before presenting. For Internal Use only.

To provide Feedback and Rate this document, please use the FEEDBACK LINK.

Note: You must be in Slide Show mode to make the link clickable.

This link will redirect you to Adobe Forms.

Thank you

Symantec NetBackup Blueprints FEEDBACK

2

https://adobeformscentral.com/?f=EYuqDaSjg*DNbSstHXN9hQ




Notice

This NetBackup Blueprint presentation includes example diagrams that contain objects that represent applications and platforms from other companies such as Microsoft and VMware. These diagrams may or may not match or resemble actual implementations found in end user environments. Any likeness or similarity to actual end user environments is completely by coincidence.

The goal of the diagrams included in this blueprint presentation is not to recommend specific ways in which to implement applications and platforms from other companies such as Microsoft and VMware; the purpose of these diagrams is to illustrate NetBackup best practices only.

For guidelines and best practices on installing and configuring applications and platforms from other companies, please refer to best practice documentation and other resources provided by those companies.

Symantec NetBackup Blueprints Preface/disclaimer

3


Symantec NetBackup Blueprints How to use ?

4

These Blueprints are designed to show customer challenges and how NetBackup solves those.

• Each Blueprint consists of:

– Pain Points: Explain the current challenges a customer faces.

– Whiteboards & Example Diagrams: Describe the implementation of NetBackup solution.

– Best Practices: Present NetBackup best practices to avoid common pitfalls

• Use these Blueprints to present the NetBackup best practice implementation example

Introduction

Symantec NetBackup Blueprints 5


NetBackup Catalog What is it?

• In the broadest sense, the NetBackup Catalog refers to all NetBackup configuration and metadata.

• It resides on master server.

• It is the internal database containing information about:

– NetBackup configuration and settings

– the backups that have been performed

– the files backed up and the media they were stored on

6

NetBackup Catalog It manages..


Catalog

Image Metadata

Backup policies

Client Database

Backup Content

Error Logs

Licensing Data


NetBackup Catalog Components

8

NetBackup Configuration

Files

NetBackup Database (NBDB)

Image Database

File Metadata

Image Header

Class

Client

Config

Failure _history

Images

Jobs media

Ss

Snapshot

Vault

DARS_DATA

DARS_INDEX

DBM_DATA

EMM_DATA

EMM_INDEX

JOBD_DATA

NBAZDB

NBDB

SEARCH_DATA

SEARCH_INDEX

VXDBMS.conf Windows: Windows:install_path\NetBackup\db

Unix:/usr/openv/netbackup/db Windows: install_path\NetBackupDB

Unix:/usr/openv/db


NetBackup Catalog Components: Configuration files

9

• The NetBackup configuration files include policies, schedules, job logs, and other files used by NetBackup.

• These are sometimes referred to as flat files because they are not stored in a relational database, and are stored in simple files on the file system of the NetBackup master server.

• The directories for the configuration files are located at

/usr/openv/netbackup/db (UNIX) or install_path\NetBackup\db (Windows).


NetBackup Catalog:

Components: The NBDB

• The NetBackup relational database (NBDB) is created during the installation of the Master server.

• It is a relational database that uses Sybase SQL Anywhere

• It stores data for several NetBackup services, including media and device data, backup image headers, authentication and authorization.

• Because the first service to use the relational database was the Enterprise Media Manager in earlier releases of NetBackup, the database is sometimes referred to as the EMM database.

10


NetBackup Catalog:

Components: The image database

• A critical NetBackup component is the image database, which stores backup image metadata.

• These files contain information about backups that have been performed.

• Although its name implies that it is a database, the image database is actually stored partially in flat files located on the master server disk, and partially in the NBDB.

11


NetBackup Catalog:

Components: The image headers

• Image Headers contain information about the backup itself – client, STU’s, hosts, policy, etc.

• Every image has a single Image Header.

• Prior to the 7.5 release, image headers were stored as flat files. These have now been migrated to the NetBackup Database (NBDB)

12


NetBackup Catalog:

Components: The dot f files

• Dot F Files (or Files File) contain information about the files and attributes that were backed up in an image.

• These are stored as flat files in binary format. They can be viewed in ASCII format using the cat_convert utility.

• Dot f files comprise a large portion of the image catalog.

13


NetBackup Catalog The Hot catalog backup

• Hot Catalog Backups allow you to backup the entire NetBackup Catalog for disaster recovery purposes.

• It is called ‘hot’ because it allows you to backup the catalog

while jobs are running. This was introduced in NetBackup 6.0 Prior to that, catalog backups could only be taken when NBU was not running.

• It backs up the entire database, image and configuration files.

14

Catalog Backup



NetBackup Catalog Catalog backup process

1. A child job copies the NBDB database files to /usr/openv/db/stagingUNIX) or install_path\NetBackupDB\staging (Windows).

2. A second child job starts, which backs up the files from the staging directory or folder to the storage unit specified in the catalog backup policy. This job backs up the files in a single stream.

3. A third child job starts, which backs up the NetBackup configuration files which includes part of the images database, policies, configuration, and other catalogs on the master server.

16


NetBackup Catalog Walkthrough:configuiring catalog backup

17

Click ‘NetBackup Management’ and select ‘Configure the Catalog Backup’

This Wizard helps you configure the catalog backup.



18

select a policy from the list of existing catalog backup policies. Or create a new policy and click next.

Enter a unique policy name. Notice that NBU-Catalog is automatically selected as the policy type.



19

Select the backup type(s). And click next. User Backup does not apply for NBU-Catalog policies.



20

Select the rotation schedule. By default, a frequency-based schedule is selected.

After each backup session refers to a period when no regular backup policy is running.



21

Configure the location for DR file.



22

It is recommended to email the DR file.



23

DR tab is added in the policy.

Critical policies are the policies that should be recovered before backups from other policies are recovered.


NetBackup Catalog Walkthrough: Monitoring the Catalog backup

24

• 1006 :Parent backup job • 1007:First child job which performs staging of NBDB • 1008:Second child job which backs up the NBDB • 1009:Third child job which backs up Configuration files • Parent job is not marked as successfully completed until all the

child jobs are completed successfully.


NetBackup Catalog Configuring catalog backup in clustered master

25

To configure an online, hot catalog backup in a cluster, 1. Follow the instructions for creating online catalog backups as

described earlier. 2. Create a policy to back up the following directory on each

node in the cluster. • Win:install_path\netbackup\var

• Unix/linux:/usr/openv/var

Note: An online catalog backup does not back up information on the inactive nodes.

Catalog Recovery



NetBackup Catalog Recovery options

27

Several options to recover the catalog exist as follows:

Recovery Option Description

Recover the entire catalog

Symantec recommends that you recover the entire catalog. Doing so helps ensure consistency among the various parts of the catalog. This method is most useful for recovering a catalog to the same environment from which it was backed up.

Recover the catalog image files and configuration files

This type of restore also restores the NetBackup relational database (NBDB) to the staging directory so that it is available for further processing if required.

Recover the relational database files

Recover the relational database if it is corrupt or lost but the catalog image files exist and are valid..


NetBackup Catalog Recovering the entire catalog

28

Select Recover the catalog option which starts the Catalog Recovery wizard



29

Specify the path to DR file and click Next. If DR file is missing, see the technote http://www.symantec.com/docs/HOWTO72613

Once the DR file is located correctly, click Next to continue.

http://www.symantec.com/docs/HOWTO72613



30

Recover entire catalog option is selected here. The job priority is set to highest. You cannot cancel the restore job in the middle.



31

Recovery is completed successfully. You need to restart the NetBackup services.


NetBackup Catalog Recovering the entire catalog –using bprecover

32

The bprecover -wizard command is an alternative to using the NetBackup Administration Console wizard

Full path for the DR file is provided here.


NetBackup Catalog Recovering partial catalog

33

Select Recover the Catalog option which starts the Catalog Recovery Wizard

For partial catalog recovery, select the second option as shown.


NetBackup Catalog Recovering partial catalog

34

Recovery is completed successfully. You need to restart the NetBackup services.


NetBackup Catalog Recovering partial catalog using bprecover

35

Partial catalog recovery can be initiated by answering to this question and additionally answering whether or not to include policy data.


NetBackup Catalog Recovering NBDB

You can recover the NetBackup relational databases independently of an entire catalog backup.

• If the NBDB database is available and the SQL Anywhere server is running, the only steps that need to be followed includes those that replace the existing database with the copy from the catalog backup:

– Make the media available

– Run the bprecover -r -nbdb command

• Refer to following technotes which discuss some more scenarios involved during the recovery of NBDB

– Recover from a backup http://www.symantec.com/docs/HOWTO72618

– Recover from the staging directory http://www.symantec.com/docs/HOWTO91618

– Recovering the NetBackup catalog when NetBackup Access Control is configured http://www.symantec.com/docs/HOWTO91287

36









NetBackup Catalog More Recovery Scenarios

• How to recover the NetBackup catalog from a non-primary copy of the catalog backup http://www.symantec.com/docs/TECH125784

• NetBackup catalog recovery without importing tapes http://www.symantec.com/docs/TECH28722

• About NetBackup catalog recovery from disk devices http://www.symantec.com/docs/HOWTO91737

• How to recover NetBackup Catalog from an MSDP pool http://www.symantec.com/docs/TECH173220

• Performing partial catalog restore http://www.symantec.com/docs/HOWTO90020

37

http://www.symantec.com/docs/TECH125784













NetBackup Catalog Archiving

38

• Customers may need to maintain their backups for many years for reasons such as government regulations and auditing purposes.

• Archiving catalog images allows you to save space on the master server and manage older backup images which you won’t need to recover from anytime soon.

• Catalog archiving allows you to backup dot-f files of older images and remove them from the master server.

• The headers for the images remain in the database. So the images are still visible in the catalog. Whenever you want to restore from those images, they will need to be un-archived first.

• Archiving older images mean catalog backups have to backup much lesser data.



39

• Catalog archiving requires you to configure a policy called as catarc for performing the archival. You can only have one archiving policy. Refer to http://www.symantec.com/docs/TECH36433

• Images can be archived with these CLIs:

bpcatlist | bpcatarc | bpcatrm

• Images can be un-archived using:

bpcatlist | bpcatres






40

Use bpcatlist to determine what image files will be archived.

This indicates that catalog archiving has not been previously run

These are the image files which can be archived.



41

This command will

archive all the images created before May 25 2014 for all clients.



42

This command will

restore all the catalog archive files prior to May 25 2014 for all clients.

• To restore the catalog archive, you must first use the

bpcatlist command to list the files that need to be restored.

• Once bpcatlist displays the proper files to restore, then the bpcatres can be run to restore the actual files.


NetBackup Catalog Verifying consistency –NBCC

43

• NetBackup consistency check utility (NBCC) is a command line utility used to analyze the integrity of portions of the NetBackup configuration, catalog and database information.

• It queries the EMM database to obtain the primary host name, associated host names, and server attributes for host name normalization.

• It does through examination of the NetBackup configuration, identifies cluster, application cluster and servers.

• It gathers the database and catalog information


NetBackup Catalog Verifying consistency –NBCC

44

• It analyzes the consistency of the gathered configuration and database and catalog information.

• It creates a packaged bundle for Symantec technical support to review.

• It resides in the following location: Unix:/usr/openv/netbackup/bin/support/NBCC

Windows:install_path\NetBackup\bin\support\NBCC.exe

• By default, it displays its progress numerically to standard output. The name of the output file is nbcc-info.txt

• See the troubleshooting guide for more details.


NetBackup Catalog Consistency check repair utility –NBCCR

45

• The NetBackup consistency check repair (NBCCR) utility is a command line tool that processes database-catalog repair actions.

• Symantec technical support analyzes the data that is collected by the NBCC utility and site-specific configuration information.

• This analysis may result in the generation of a suggested repair actions (SRA) file.

• Before NBCCR is run, Symantec technical support interacts with the customer to determine which repairs are needed.

• Undesirable repair actions are deleted or commented out of the SRA file.


NetBackup Catalog Consistency check repair utility –nbccr

46

• Each line of the SRA file contains one repair action that is paired with an associated parameter.

• NBCCR resides in the following location: • Unix:/usr/openv/netbackup/bin/support/NBCCR

• Windows:install_path\NetBackup\bin\support\NBCCR.exe

• NBCCR accepts one input file, creates two output files, and uses one temporary file.


NetBackup Catalog Image import

47

• NetBackup can import the backups that have expired, the backups from another NetBackup server

• Import happens in two phases:

– Phase I

o Import process creates a list of expired images from which to select to import in Phase II. It regenerates image headers and imports them into the database. No import actually happens in Phase I. If an image has only undergone Phase I import, it is removed during the next cleanup.

– Phase II

o The dot-f files are regenerated and moved into the catalog.


NetBackup Catalog Compression

48

• Compressing the image catalog accomplishes the following objectives:

– Reduces greatly the disk space that is consumed.

– Reduces the media that is required to back up the catalog.

• Before NetBackup 7.6, NetBackup used the compress command on the server (UNIX) to perform compression after each backup session.

• NetBackup 7.6 uses a built-in compression method to compress the image catalog.

• The operation occurs while NetBackup expires backups and before it runs the session_notify script and the backup of the NetBackup catalogs.

• The time to perform compression depends on the server speed and the number and size of the files being compressed. Files are compressed serially, and temporary working space is required in the same partition.

• Compression method is based on zlib- faster and better ratios


NetBackup Catalog Compression

49

Use this property to specify how old the backup information must be before it is compressed.

To uncompress the NetBackup Catalog, refer following article: http://www.symantec.com/docs/HOWTO86598




NetBackup Catalog Migration

50

• It is possible to move the NetBackup catalog from one master to another master server running on the same "primary" platform (i.e. from a Windows server to another Windows server or from a UNIX or Linux server to another UNIX or Linux server) using a simple catalog backup and recovery operation as described in TECH77447 and TECH77448.

• Please note, a migration of this sort must be a part of a conscious, planned, and permanent transition, and should not be part of a disaster recovery process or any part of a disaster recovery plan.

• Please contact a NetBackup Sales Representative for assistance in engaging a certified Symantec consultant or Consulting Partner.



Best Practices


• /usr/openv/netbackup/MAX_FILES_PER_ADD – affects all backups, default is 5,000 (Can be used to tune problems with backing up file systems with many files and also file adds into catalog exceeding bpbrm timeout)

• /usr/openv/netbackup/FBU_MAX_FILES_PER_ADD – affects FlashBackup, default is 95,000

• /usr/openv/netbackup/CAT_BU_MAX_FILES_PER_ADD – affects catalog backups, default is maximum allowed 100,000

• Refer to following technote for further details http://www.symantec.com/docs/HOWTO56209

52

NetBackup Catalog Best Practices: Catalog tuning

NetBackup 7.6 Best Practices




NetBackup Catalog Best Practices: top support technotes

53

• Strategies that ensure successful NetBackup catalog backups on Windows http://www.symantec.com/docs/HOWTO34437

• Recommendation for sizing the catalog http://www.symantec.com/docs/HOWTO56093

• How to calculate the size of your NetBackup image database http://www.symantec.com/docs/HOWTO56068

• How to calculate the size of the NetBackup relational database http://www.symantec.com/docs/HOWTO56055

• Best practice for NetBackup catalog layout http://www.symantec.com/docs/TECH144969

• Key performance considerations for NetBackup 7.6 master servers http://www.symantec.com/docs/TECH216680

















NetBackup Catalog Best Practices: top support technotes

54

• About catalog policy schedules http://www.symantec.com/docs/HOWTO86595

• Concurrently running catalog backups with other backups http://www.symantec.com/docs/HOWTO86594

• Veritas NetBackup (tm) Catalog Replication: Conditional Support Statement http://www.symantec.com/docs/TECH50942

• How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains. http://www.symantec.com/docs/TECH31385













Thank You!

Symantec Backup and Recovery Technical Services


Symantec NetBackup Blueprints - VOXvox.veritas.com/legacyfs/online/veritasdata/NetBackup 7.6... ·...

Documents

Transcript of Symantec NetBackup Blueprints - VOXvox.veritas.com/legacyfs/online/veritasdata/NetBackup 7.6... ·...