1. Introduction to Netbackup

Overview:NetBackup provides high-performance backups and restores for a variety of platforms, including Microsoft Windows, UNIX, and NetWare systems. Administrators can set up schedules for automatic, unattended backups for clients anywhere in the network. These backups can be full or incremental and are managed entirely by the NetBackup master server. Users can start backups and restores from the computer where they are working. A user can also archive files. An archive operation backs up a file and then deletes it from the local disk if the backup is successful. Once started, user operations are managed by the NetBackup server. NetBackup’s Media Manager software manages the media and storage devices. Robots require no intervention on the part of the administrator, operator, or the user. Standalone drives (those not in a robot) that contain appropriate media also require no intervention.

NetBackup includes both the server and client software:

◆ Server software is on the computer that manages the storage devices.

◆ Client software is on the computer whose data you want to back up. A server also has client software and can be backed up like other clients.

NetBackup servers and clients can be any one of a number of platform types as described in the data sheets and release notes for the product.

NetBackup supports both master and media servers. The master server manages the backups, archives, and restores. Media servers provide additional storage by allowing NetBackup to use the storage devices that they control. Media servers can also increase performance by distributing the network load.

During a backup or archive, the client sends backup data across the network to a NetBackup server that has the type of storage specified for the client. The storage requirement is specified during NetBackup configuration (for example, 4 mm tape). During a restore, users can browse and then select the files and directories that they want to recover. NetBackup finds the selected files and directories and restores them to the disk on the client.

NetBackup Administration Interfaces

The NetBackup Administration Console provides a graphical-user interface through which the administrator can manage NetBackup. The console is available in two forms:

◆ A Windows-based interface to run on a Windows system.

◆ A Java-based interface able to run on a Windows system.

This interface is called the NetBackup-Java Windows Display Console and is not automatically installed on the system. Installation is available on the main NetBackup for Windows installation screen.

It is also possible to display the console on a Java-capable UNIX platform and display it back to a Windows system by using third-party X terminal emulation software.

Running the Windows-Based NetBackup Administration Console The NetBackup Administration Console is installed with the NetBackup server software. It can also be installed without server software as the Remote Administration Console.

To start the NetBackup Administration Console

1.Log on to the Windows workstation as a member of the user group authorized for NetBackup administration.

2.Go to Programs > VERITAS NetBackup > NetBackup Administration Console. The NetBackup Administration Console appears.

The NetBackup Administration Console is the starting point for administering NetBackup. The left pane in the console contains a node for each major area of NetBackup administration. Clicking a node displays information related to that node in the Details pane on the right. The menus contain commands relevant to the selected node.

User Backups, Archives, and Restores

To perform backups and archives for this system, and restores for this system and other clients, open the client interface by clicking on the Backup, Archive, and Restore button in the toolbar. Users can back up, archive, and restore files, directories, and raw partitions that reside on their own client computer. A user can restore files at any time but can back up and archive only during the time periods that the administrator defines with the schedules. Users can also view the progress and final status of the operations they perform.

Activity Monitor

Use the Activity Monitor to monitor and control NetBackup jobs, services, processes, and drives.

NetBackup Management

This manual describes the applications and utilities listed under NetBackup Management in the NetBackup Administration Console tree. The Media Manager System Administrator’s Guide describes applications and utilities under Media and Device Management. The following sections describe items found under NetBackup Management.

Policies

Use Policies to create and specify the backup policies, which define the rules for backing up a specific group of one or more clients. For example, the backup policy specifies when automatic backups will occur for the clients and when users can perform their own backups. The administrator can define any number of backup policies, each of which can apply to one or more clients. A NetBackup client must be covered by at least one backup policy and can be covered by more than one. The properties of a backup policy include the following:

◆ General attributes that define the:

◆ Priority of backups for this policy relative to backups for other policies.

◆ Storage unit to use for backups of clients covered by this policy.

◆ Volume pool to use for backups performed according to this policy. A volume pool is a set of volumes that the administrator can assign to specific backup policies or schedules. For example, it is possible to have one volume pool for weekly backups and another for quarterly backups.

◆ List of client computers covered by the policy.

◆ List of files to include in automatic backups of the clients. The backup selection list does not affect user backups because the user selects the files.

◆ Schedules that control when backups and archives can occur for the clients. As mentioned above, each backup policy has its own set of schedules. These schedules control when automatic backups start and also when users can start a backup or archive. Each schedule is unique with attributes that include:

◆ Type of schedule. Specify schedules for automatic full or incremental backups or user backups or archives. There are also schedule types that apply only when separately-priced options are installed (for example, a backup schedule for Microsoft Exchange or Oracle databases).

◆ Backup window. For automatic full or incremental backup schedules, this is the time period when NetBackup can start automatic backups of clients covered by this policy. For user schedules, this is the time period when users can start a backup or archive of their own client.

◆ Frequency. How often automatic and calendar-based backups should occur and which dates should be excluded from the schedule (dates when backups should not occur).

◆ Retention. How long NetBackup keeps the data that is backed up by this schedule.

◆ Storage unit. The storage unit for the data that is backed up by this schedule. This setting, if used, overrides the storage unit specified at the backup policy level.

Volume pool:

The volume pool to use when saving data backed up by this schedule. This setting, if used, overrides the volume pool specified at the backup policy level. The administrator can also manually start a backup schedule for an automatic full or incremental backup. Manual backups are useful if, for example, a client system is down and misses its scheduled backup.

Storage Units:Use Storage Units to display storage unit information and provide commands for managing NetBackup storage units. A storage unit is a group of one or more storage devices of a specific type and density that attach to a NetBackup server. The media can be removable (such as tape) or a directory on a hard disk. Removable media can be in a robot or a standalone drive. The devices in a removable-media storage unit (such as a tape drive) must attach to a NetBackup master or media server and be under control of Media Manager. The administrator first sets up Media Manager to use the drives, robots, and media and then defines the storage units. During a backup, NetBackup sends data to the storage unit specified by the backup policy. Media Manager then picks an available device within the storage unit. When the storage unit is a directory on a hard disk, the administrator specifies the directory during configuration and NetBackup sends the data to that directory during backups. Media Manager is not involved. Storage units simplify administration because once they are defined, the NetBackup configuration points to a storage unit rather than to the individual devices it contains. For example, if a storage unit contains two drives and one is busy, NetBackup can use the other drive without administrator intervention.

Catalog:

Use Catalog to create and configure a special type of backup NetBackup requires for its own internal databases—a catalog backup. These databases, called catalogs, are on the NetBackup server's disk and have setup information as well as critical information on client backups. The catalog backups are set up and tracked separately from other backups to ensure recovery in case of a server crash. Catalog is also used to search for a backup image in order to verify the contents of media with what is recorded in the NetBackup catalog, to duplicate a backup image, to promote a backup image from a copy to the primary backup copy, to expire backup images, or to import expired backup images or images from another NetBackup server.

Host Properties:

Use Host Properties to customize NetBackup configuration options. In most instances, no setting changes are necessary. However, Host Properties settings allow the administrator to customize NetBackup to meet specific site preferences and requirements for master servers, media servers, and clients.

Media and Device Management:

The software that manages the removable media and storage devices for NetBackup is called Media Manager. This software is part of NetBackup and is installed on every NetBackup server. The administrator can configure and manage media through Media and Device Management in the NetBackup Administration Console.

2. Managing Backup Policies

Backup policies define the rules that NetBackup follows when backing up clients. A backup policy can apply to one or more clients. Every client must be covered by at least one backup policy. The best approach to configuring backup policies is to divide clients into groups according to their backup and archiving requirements, then create a policy for each group.

I

ntroduction to Backup Policies Backup policies are configured on four tabs, as described in the following sections.

General Attributes on the Attributes Tab

The general attributes on the Change Policy Attributes tab determine the basic characteristics of all the backups that NetBackup performs according to a policy. These include:

◆ Whether the policy is active and what date and time the policy will go into effect (so NetBackup can use it for backups).

◆ The type of backup policy, which primarily defines the type of clients the policy is set up to include.

◆ The priority that NetBackup gives to the backups for this policy relative to other policies.

◆ The storage unit that NetBackup uses by default when backing up clients covered by this policy. This setting can be overridden for individual schedules by specifying a storage unit for the schedule.

Schedules on the Schedules Tab

The schedules determine when the backups occur. Each schedule also includes criteria, such as how long to retain the backups. There are two basic categories of schedules, automatic and user, and there are different types of schedules within these categories:

◆ Automatic schedules back up the backup selection list on all clients in the policy according to the timetables set up in the schedules. For example, you can set one schedule for daily incremental backups and another for weekly full backups. A cumulative incremental backup includes all files that have changed since the last full backup. A full backup includes all files in the backup selection list regardless of whether they have changed.

Note: NetBackup recommends that you do not combine differential incremental backups and cumulative incremental backups within the same Windows policy when the incremental backups are based on archive bit (default).

Client List on the Clients Tab

The client list names the computers that will be backed up according to a policy. A client must be covered by at least one backup policy and can be covered by more than one. Having a client in more than one backup policy is useful, for example, to back up different sets of files on the client according to different rules.

Backup Selections on the Selections Tab

The backup selections list names the files, directories, directives, scripts (used for database policies), and templates (used for Oracle and DB2 policies), that NetBackup includes in automatic backups of clients covered by a policy. NetBackup uses the same selection list for all clients backed up according to a policy. All the files and directories do not need to exist on all the clients, as NetBackup backs up the files in directories NetBackup finds.

Example Policies

The following figures show the clients, backup selection list, and schedules for two example backup policies. Example 1 specifies that files in C:\ and D:\Docs be backed up for the clients mars, jupiter, and neptune. This policy has daily, and weekly automatic schedules and a user backup schedule. All backups go to 8 mm tape.

Example 2 has different scheduling requirements. For example, this policy has monthly fulls that go to DLT tape.

Policy Planning Guidelines for Backups Policies allow you to meet the needs of a wide variety of clients in a single NetBackup configuration. However, taking full advantage of policies for use in backups requires careful planning before starting your configuration. The following procedure provides planning guidelines. The planning worksheets in this manual may also be helpful.

1.Divide clients into groups according to the types of work they perform.

Clients used for similar tasks usually have a high level of commonality in their backup requirements. For example, most clients in an engineering department create the same types of files at similar levels of importance.

In some instances, you can create a single policy for each group of clients. In other cases, you will have to further subdivide the clients and cover them in separate policies, based on their backup requirements as explained later in this procedure.

The table below is the initial grouping for our example. We assume these clients are in the same work group and the initial plan is to cover them all in the same backup policy.

1. Gather information about each client. Include information relevant to the backups such as the names, size, and number of files.

In our example client list, mercury is a file server and has a large amount of data. To avoid excessively long backup times, we include mercury in a separate policy called S1 and the workstations in a policy called WS1. Later, we may find that we need more than one policy for mercury, but we will evaluate other factors first. For now, the backup policies are as follows

 

1. Gather information about each client. Include information relevant to the backups such as the names, size, and number of files.

In our example client list, mercury is a file server and has a large amount of data. To avoid excessively long backup times, we include mercury in a separate policy called S1 and the workstations in a policy called WS1. Later, we may find that we need more than one policy for mercury, but we will evaluate other factors first. For now, the backup policies are as follows:

3. Create backup policies to accommodate special storage requirements.

The storage unit and volume pool settings apply to all files that are backed up by the policy. If files have special storage unit and volume pool requirements, create separate policies for them, even if other factors, such as schedules, are the same.

In the example below, we create a separate policy (S2) for D:\h002\DevExp and D:\h002\DesDoc on mercury because those files go on DLT tape. Other files on mercury go on 8 mm tape. If it is necessary to keep backups for some files on separate media, create a policy that specifies a unique volume pool for those backups. Then, add the media for that volume pool.

 

5. Create separate policies for clients that require different general attribute settings than other clients. Some attribute settings to consider are:

◆ Policy Type: There are several types of backup policies and you must use the correct one for the client. For example, include Windows NT and Windows 2000 clients in an MS-Windows NT policy. ◆ Follow NFS: Select this attribute if a UNIX client has NFS mounted files and you are going to back them up from that client. It is also a good idea to use a separate policy for these clients so problems with NFS do not affect the other clients. ◆ Backup Network Drives: Select this attribute to back up files that the client stores on network drives (applies only to MS-Windows-NT policies). ◆ Compression: Set this attribute if you want a client to compress its backups before sending them to the server. Note that the time to compress can increase backup time and make it unsuitable to use for all clients. ◆ Policy Priority: Use this attribute to control the order in which NetBackup starts its backups. The client in the higher priority policy is backed up first.

There are also other general attributes that are explained later in this chapter. In our example, no extra policies are required because of general attribute settings.

6. Create separate policies as necessary to maximize the benefits of multiplexing.

Using multiplexing for slower clients that produce small backups is a strategy for maximizing drive utilization. However, higher-performance clients that produce long backups are likely to fully utilize drives and not benefit from multiplexing.

7. Evaluate total backup times for each schedule and further subdivide your policies to reduce backup times to an acceptable level.

In our example, backing up D:\User, D:\h001, and E:\h002\Projects on mercury takes too much time so we create a new policy for E:\h002\Projects. This new policy (S5) has the same requirements as S1 but we can now back up E:\h002\Projects separately thus reducing backup time. The next table shows the final set of backup policies.

In addition to reducing the backup time for each policy, backing up the files with separate policies can reduce the total backup time for the server mercury. NetBackup processes files within a backup selection list serially and in the order they appear in the backup selection list. However, separate policies are processed in parallel if enough drives are available and the maximum jobs attributes are set to allow it.

Multiplexing and Allow Multiple Data Streams also allow processing backup policies in parallel.

What Type of Policy: Policy Attributes Tab The general policy attributes on the Attributes tab determine the basic characteristics of all the backups that NetBackup performs according to this backup policy.

▼To set the general policy attributes

1.In the NetBackup Administration Console, expand NetBackup Management > Policies.

2. Double-click the policy name in the left pane. The Change Policy dialog appears, containing four policy attribute tabs: Attributes, Schedules, Clients, Backup Selections.

3. Select a tab and make any changes.

4. Click OK to save the changes, then click Close to close the Change Policy or New Policy dialog.

The following sections describe the policy configuration attributes in the Attributes tab. Policy attribute are configurable depending on the type of policy and the options installed. For example, Encryption is available only when the NetBackup Encryption option is installed.

Policy Type:

The Policy Type selection determines the type of clients that can be part of the policy and, in some cases, the types of backups that can be performed on the clients. Select the type of policy from the drop-down list. If you change the policy type for an existing policy that contains schedules that are invalid for the new policy type, NetBackup prompts you, then either deletes the invalid schedules or, if possible, changes the schedules to an equivalent type.

Policy Storage Unit:

The Policy Storage Unit policy attribute specifies the default storage unit for backups of this policy. NetBackup uses the default storage unit for all schedules that do not specify another storage unit. A schedule-level storage unit (when specified) overrides the policy default.

Select the policy storage unit from the drop-down list. You can also indicate Any Available. If you select Any Available, NetBackup tries locally-attached storage units first, and if none are found, the storage units are tried in alphabetical order. NetBackup uses the first storage unit that meets the following requirements:

◆ The storage unit must not be designated as On Demand Only

◆ The storage unit must have available drives

◆ The storage unit must have media available in the required volume pool The only exception is in the case of a client that is also a media server with locally connected storage units. The locally available storage units take precedence over the sequence based on alphabetical order.

Policy Storage Unit Example

Assume that all schedules but one can use a Tape Stacker 8MM. The schedule that is the exception requires a Tape Library DLT. Here, you specify Tape Stacker 8MM at the policy level and specify the following on the schedules:

◆ For schedules that can use the Tape Stacker 8MM, clear Override Policy Storage Unit. When these schedules run, NetBackup uses a Tape Stacker 8MM.

◆ For the schedule that requires DLT, select Override Policy Storage Unit and select Tape Library DLT. When this schedule runs, NetBackup overrides the policy default and uses the DLT library.

Policy Volume Pool The Policy Volume Pool policy attribute specifies the default volume pool for backups of this policy. Select the desired volume pool name from the drop-down list. The list displays all previously-configured volume pools. Whenever a new volume is required for either a robotic or standalone drive, it is allocated to NetBackup from the requested volume pool.
A volume pool is a set of media used only by the users and hosts designated when configuring the pool. Volume pools are created and media assigned when configuring media in Media Manager type storage devices. It is not available for disk type storage devices. A volume pool named NetBackup is always created by default and, unless otherwise specified in the policy, all backups go to media in the NetBackup pool. Other pools can be created for NetBackup to use. For example, create Auto and User volume pools, then specify that automatic backups use media from the Auto pool and user backups go to media in the User pool. A schedule-level volume pool, when specified, overrides the policy default set here.
If there is no volume pool specified in the Attributes tab of either the policy or the schedule, NetBackup uses the NetBackup pool. The volume pool concept is relevant only for storage units managed by Media Manager, and does not apply to disk storage units.

Volume Pool Example

Assume that you want all schedules but one to use the backups pool. The exception in this case is a user-archive schedule that requires the archive pool. Here, set Policy Volume Pool to backups. When you set up the schedules for the policy, set Override Policy Volume Pool as follows:

◆ For schedules that use the backups volume pool, clear Override Policy Volume Pool.

◆ For the schedule that requires the archive volume pool, select Override Policy Volume Pool and specify archive for the pool name.

Notes on Volume Pools

◆ This setting is optional for Media Manager type storage units and is not available for Disk type storage units.

◆ It is possible to configure a scratch pool from which NetBackup can automatically transfer volumes when another volume pool does not have media available.

Checkpoint Restart for Backup Jobs

The Checkpoint Restart Every check box indicates whether NetBackup will take checkpoints during backup jobs based on this policy at the frequency indicated. Taking checkpoints during a backup is beneficial if a backup based on this policy fails. Without Checkpoint Restart enabled, a failed backup based on this policy is restarted from the beginning of the job. By taking checkpoints periodically during the backup, NetBackup can retry a failed backup from the last checkpoint rather than restarting the entire job. The number of times that NetBackup will automatically reattempt a failed backup is configured by the Schedule Backup Attempts property located in the master server Global Attributes host properties. Policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support checkpoints for backup jobs.

Limit Jobs Per Policy

If the Limit Jobs Per Policy check box is clear (default), the maximum number of backup jobs that NetBackup will perform concurrently for this policy can be up to 999. To specify a lower limit, select the check box and specify a value from 1 to 999. You can leave this attribute at the limit or default, except when there are enough devices that the possible number of concurrent backups will affect performance.

Notes on Limit Jobs Per Policy The number of concurrent backup jobs that NetBackup can perform depends on:

◆ Number of storage devices available and multiplexing limits. To process more than one backup job at a time, your configuration must include more than one storage unit, or a storage unit with enough drives to perform more than one backup at a time, or storage units configured to multiplex. With removable media devices such as tape drives, this depends on the total number of drives in the storage units. With magnetic disk, the storage device is defined as a file path and the available disk space determines how many paths are possible. ◆ Server speed: Too many concurrent backups interfere with the performance of the server. The best number depends on the hardware, operating system, and applications that are running. ◆ Network loading: The available bandwidth of the network determines how many backups can occur concurrently. If you encounter loading problems, consider backing up over multiple networks or using compression.

A special case exists when backing up a client that is on the same machine as the server. Here, network loading is not a factor because you do not use the network. Client and server loading, however, is still a factor.

◆ Multiplexing. If you use multiplexing, set Limit Jobs Per Policy high enough to support the specified level of multiplexing.

Active. Go Into Effect At

To activate the policy, select the Active policy attribute check box. The policy must be active for NetBackup to run automatic-backup schedules or allow user backups or archives. The Go Into Effect field specifies when this policy may begin scheduling backups. If today is Monday and you enter Wednesday at 12:00 AM, the policy will not run until after that time. This is useful for configuring a series of policies in advance of when you want them to become active.

Backup Network Drives

The Backup Network Drives policy attribute specifies that NetBackup should back up or archive files that are on network drives and are named in the backup selection list (or indicated by the user in the case of a user backup). With Backup Network Drives selected, NetBackup also backs up CD-ROM drives on Windows systems. Clear the check box to prevent the backing up or archiving of network drives or the backing up of CD-ROM drives. The network (shared) drives must be available to the service account that the NetBackup Client service logs into at startup. By default, the startup account is set to System. You must change this account on each Windows client where you are backing up network drives.

Note: Since it is not possible to back up mapped drive letters, mapped drive letters do not appear when browing for backups.

Cross Mount Point Examples

The next two examples illustrate the concepts mentioned above. In these examples, assume the client disks are partitioned as shown below