Solstice Backup 5.1 Administration Guide

Chapter 2 Getting Started

This chapter expands on the configuration tasks and Quick Tour described in the Solstice Backup Installation and Release Notes. It describes the initial administration tasks required to get Backup running with a default configuration and lists the default configurations for major Backup components.

This chapter consists of the following sections:

Initial Administration Tasks

After you install Backup according to the instructions in the Solstice Backup Installation and Release Notes, you must do several tasks before you can use Backup to back up data.

Basic Configuration for the Backup Server

To configure your Backup server, you can either use the GUI (nwadmin) or character-based interface (nsradmin) of the Backup administration program, or you can enter commands at the command line. Refer to the online help or Backup man pages for instructions explaining how to use each interface. Before you can run Backup, some configuration is required that is strictly unique to your environment:

Enter an enabler code that unlocks the features of the software that you purchased for you to use for 45 days. (Evaluation enabler codes unlock the features of the software for you to use for 45 days. Before the 45 days expire, you must purchase and enter a permanent enabler code to continue to use each evaluated feature). See "Enabler Code Entry " for more information.
Register the software. Enter the authorization code that SunSoft returns to you to permanently enable your products. See "How to Register and Authorize Your Software " for more information.
Configure your devices and label backup media. See "Device Configuration " and "Volume Labels " for more information.
Set up the client portion of the Backup server and other Backup clients. See "Preconfigured Resources" for more information.

Only users who have administrative privileges can create or apply configurations. Because only root@server-name has Backup administrative privileges by default, you must become root on the Backup server before you start any Backup administration programs or tasks. You can add other users to the list of authorized Backup administrators later.

The Backup server manages the clients on a network through a resource allocation protocol (RAP). The server maintains the configurations that you enter as Failed Cross Reference Format. Each resource contains a set of Failed Cross Reference Format to which values are assigned (for example, the Name attribute found in several Backup resources contains a value that defines the name of the resource).

You can configure and manage your Backup software in the following ways:

Backup administration program (nwadmin) - You can register, configure, and monitor the Backup servers, clients, storage nodes, and devices in your network using the Backup administration program. The Backup administration program is a GUI for X Windows environments. To start the Backup administration program, type nwadmin at the shell prompt.
Backup character-based interface (nsradmin) - You can use the Backup character-based interface on any display, including those that do not support graphics. You can perform many of the same configuration and management tasks as in the GUI. To start the character-based version of the Backup administration program, type nsradmin -c at the shell prompt. For more information about using the character-based interface, refer to the nsradmin man page.
Backup command line interface - You can perform any of the configuration and administration tasks available through the Backup administration program, as well as the tasks available in the client-side backup, recover, archive, and retrieve programs, through Backup commands that you enter at the shell prompt. See Appendix B, Command Line Reference Utilities and the referenced online man pages for instructions on how to use the Backup command line interface.

Enabler Code Entry

After you install Backup, you can use either the Backup administration program or the nsrcap command to enter the enabler codes you purchased for your Backup software products. The enabler code is printed on the Enabler Certificate you received with your software. Enter the base enabler code for the Backup server before you enter the enabler codes for additional features that you purchased, such as the Autochanger Software Module.

After you enter the enabler code for the software, you can configure and perform Backup backups for up to 45 days before you must enter an authorization code to continue to use Backup.

You can purchase additional enablers for added features, such as the Archive Application and Backup HSM as well as support for additional clients or autochangers that you add to your network after you install Backup.

How to Enable Your Software Using the Command Line

See "nsrcap " for information on how to enable your software with the nsrcap command.

How to Enable Your Software Using the GUI

To enable your software with the GUI version of the Backup administration program:

Become root on the Backup server machine.

Issue the nwadmin command to start the GUI version of the Backup administration program.

Open the Registration window.

Click Create.

Enter the enabler code.

Click Apply.

How to Register and Authorize Your Software

After you enable your Backup products, you must register and authorize the products within 45 days to continue to perform backups. To register your software, follow these steps:

Become root on the system where you installed the Backup server software.

Enter the nwadmin command or the nsradmin -c command at the shell prompt to start the Backup administration program.

Enter your company and product information in the Server window (nwadmin) or select and edit the NSR License resource (nsradmin).

You must enter all required company and product information in the Server resource, or you cannot register your products properly.

Change the Server window to a tabular view and print the contents of the Server resource.

Email the registration information to license@Sun.com.

Alternately, you can fax the Product Registration Form to the Sun Licensing Center at 1-801-431-3657.

When you receive the authorization code from the Licensing Center, become root on the Backup server and start the administration program.

Open the Registration window, enter the authorization code in the Auth Code field, and apply the changes.

Repeat the entry process for each Backup product you purchased.

After you enter the authorization code, your Backup software is authorized for permanent use.

Note -
If you have questions about the authorization code process, call the Sun Licensing Center at 1-800-872-4786. Callers from Canada may call at 1-800-722-4786. (The Web address is http://www.sun.com/licensing.) Authorization codes for this product will only be issued from the U.S. Sun Licensing Center.

How to Remove an Enabler Code

If you need to remove an enabler code later, whether or not it is permanently authorized, follow these steps:

Become root on the system where you installed the Backup server software.

Enter the nwadmin command at the shell prompt to start the Backup administration program, or enter the nsradmin -c command to start the character-based interface in visual mode.

Open the Registration window (nwadmin) or edit the NSR_license (nsradmin) resource.

Highlight the enabler code you want to remove and select the Delete option.

Caution -
You cannot remove a base enabler. You can update a base enabler using the nsrcap -v -c command.

Device Configuration

Before the Backup server can use your storage devices, you must first configure each storage device separately. A device is standalone, a file, or located in an autochanger or silo tape library (STL). The type of device (standalone, file, autochanger, or silo) determines how you configure the device.

When you install the Backup software, Backup configures the SCSI devices for the device choices you make. If you decide you need to add, delete, or modify your Backup storage devices after you install Backup, edit the Devices or Jukeboxes resources. You can use either the nwadmin (GUI) or the nsradmin (character-based) version of the Backup administration program.

Caution -

For devices in STLs, you cannot use nwadmin or nsradmin to add, delete, or modify the configuration. See Chapter 10, Silo Support Module for more information about configuring devices in a silo.

For instructions on how to use the nwadmin program or the nsradmin program to configure your backup devices, refer to the online help provided in each program.

Devices Resource

Use the Devices resource to configure standalone devices. Enter the name of the device and the media type. Any devices you add in the Devices resource are displayed in the Backup administrator program in the Devices display. For details on device configuration, see "Device Configuration ".

Jukeboxes Resource

You perform most of the necessary autochanger configuration with the jb_config command described in the Solstice Backup Installation and Release Notes. After the jb_config command is completed, the configured options are displayed in the Jukeboxes resource of the administration program. The Jukeboxes resource displays the name of the autochanger, the model, control port pathnames, device pathnames, barcode label choices, and available slots that you originally created when you installed Backup.

The only changes you can make to your autochanger in the Jukeboxes resource are to the available slots, devices, and barcode label attributes. If you need to make additional changes, you must first delete the autochanger from the list, and then run the jb_config command again. For further details on these attributes, see "Autochanger Device Configuration ".

If your storage devices reside in a silo, see Chapter 10, Silo Support Module for information on the use of a silo with Backup.

Volume Labels

Before Backup can use a volume, you must first label it with a valid Backup label. Backup uses an internal volume label to identify the media it uses for backups, archives, and migration. Backup provides several preconfigured label templates for you to use to label your volumes. See "Label Template Resource " for the preconfigured label template settings.

To label a volume, you must first mount it on a device. You can select the Mount speedbar button displayed in the main window of the nwadmin program GUI, or you can issue the nsrmm -m command at the shell prompt.

Preconfigured Resources

The software ships with several resources already configured so you can use Backup right away, without need for further configuration. As you become familiar with the software, you can customize the Backup resources to suit your storage management needs.

Clients Resource

The first client of the Backup server is the server itself; the Client resource for the server is automatically created for you when you install the software. The configurations that ship with Backup are already in place for the client setup for the server. Table 2-1 lists the preconfigured settings for the Client resource.

Table 2-1 Preconfigured Attribute Settings for Client Resource


Attribute	Preconfigured Setting
Archive Services	Disabled (client cannot perform archives)
Schedule	Default
Browse Policy	Month (client file index entries remain browsable for one month after backup)
Retention Policy	Year (retains media database entries for the client's save sets for one year)
Directive	Null (does not use special directives for the client's backup)
Group	Default
Save Set	All (backs up all filesystems for the client)
Remote Access, Remote User, Password	Null (only users on the client machine can browse the client's file index and recover data)
Backup Command	Null (uses the standard client `save program)`
Aliases	Null (the client does not have other qualified names used for contact)
Archive Users	Null (there are no authorized login IDs required for Archive services)

You can change any of the preconfigured client settings to suit your needs. If you want to apply customized settings for the Group, Schedule, Browse Policy, Retention Policy, or Directive attributes, you must first create customized resources for these attributes before you can apply them to a new or existing Backup client. Because these resources rely on other settings, create customized resources in the following order:

Groups
Pools
Schedules
Policies
Directives

For information on how to customize resources for Backup clients, see Chapter 5, Backup Client Operations.

After you create the customized resources, all the preconfigured and custom configurations created in the Groups, Schedules, Policies, and Directives resources are displayed as choices in the Clients resource for you to apply to your new or existing clients.

Groups Resource

In the Groups resource, you determine which machines back up together and at what time. Use groups to back up selected machines at different times to control the amount of traffic on your network. You can also use the Groups resource to automatically Failed Cross Reference Format backup data.

All Backup clients are initially assigned to the preconfigured Default group. When you first install Backup, the Default group's Autostart attribute is disabled. When you are ready to test your Backup software, you can select Start Now to override the assigned Start Time of 3:33. To begin regularly scheduled backups, select the Enabled choice for Autostart.

Table 2-2 lists preconfigured attribute settings for the Groups resource.

Table 2-2 Preconfigured Attribute Settings for Groups Resource


Attribute	Preconfigured Setting
Name	Default
Autostart	Disabled
Autorestart	Disabled
Client Retries	1
Stop Now	False
Start Time	3:33
Interval (how frequently the group runs, using the 24 hour clock)	24:00
Clones	No
Clone Pool	Default Clone
Migration Clone Pool	Migration Clone
Inactivity Timeout (number of minutes of inactivity before concluding the client is hung)	30
Printer	assigned default printer for server

For further details on how to use backup groups, see "Monitoring and Managing Group Backups ".

Pools Resource

The Pools resource determines where backup data is directed. Backup ships with several preconfigured pools to choose from. The Default group is preconfigured to be backed up to media labeled for the Default pool. Table 2-3 lists preconfigured settings for the pools resource attributes.

Table 2-3 Preconfigured Attribute Settings for Pools Resource


Attribute	Preconfigured Setting
Name	Default
Enabled	Yes
Pool Type	Backup
Label Template	Default
Store Index Entries	Yes
Auto Media Verify	No
Recycle to Other Pools	No

Schedules Resource

Backup uses the Schedules resource to determine the level of data to back up for each client on a given calendar day. When you create a new Backup client, the Schedules attribute is automatically assigned the default schedule. You can assign a different preconfigured schedule or customize one of your own.

Backup ships with five preconfigured schedules, described in Table 2-4. You can use these schedules without further configuration if they fit your backup requirements. Otherwise, you can create new schedules to accommodate your specific needs.

You can modify, but not delete, the preconfigured Default schedule. The attributes for all of the other preconfigured schedules can be deleted or modified, but you cannot modify the names of the preconfigured schedules. Table 2-4 lists preconfigured Backup backup schedules.

Table 2-4 Preconfigured Backup Schedules


Schedule Name	Backup Backup Operation
Default	Completes a full backup every Sunday and incremental backups on all other days.
Full Every Friday	Completes a full backup every Friday and incremental backups on all other days.
Full on 1st Friday of Month	Completes a full backup on the first Friday of the month and incremental backups on all other days. Backup ships with the Failed Cross Reference Format options already preset for this schedule. The overrides for this schedule carry over year to year.
Full on 1st of Month	Completes a full backup on the first calendar day of the month and incremental backups on all other days.
Quarterly	Completes a full backup on the first day of the quarter and performs a level 5 backup on the first day of the other months in the quarter. Every seven days, a level 7 backup occurs; incremental backups occur on all other days. When you customize a quarterly schedule, use the Month period to set the level backups, then use an override to set each quarterly full backup on the calendar.

Policies Resource

You use the Policies resource to create a life cycle to use for both the Failed Cross Reference Format and Failed Cross Reference Format for your backed-up data. The client resource already has a default browse policy of Month and a default retention policy of Year assigned.

The browse policy determines how long the client file index maintains a browsable entry. If the browse policy has not expired, you can view the data in a graphical representation of the filesystem backed up, using the nwrecover program. After the browse policy expires, you can still use save set recover or the scanner program to recover the data, because save set information is still stored in the media database.

The retention policy determines how long the save set information is stored in the media database and how long the file remains retrievable from the backup volume. After all the retention policies for the save sets on a volume and other dependent save sets stored on other volumes expire, the volume is given a recyclable status and is available for reuse by Backup. Until the volume is relabeled, you can still use the scanner command to recover the expired save sets.

Preconfigured Policies for Backup

Backup includes the preconfigured policies listed in Table 2-5, which you can apply to either the browse policy or the retention policy.

Table 2-5 Preconfigured Backup Policies


Policy Name	Backup Behavior
Decade	Available 10 years
Half Year	Available 6 months
Month	Available 1 month
Week	Available 1 week
Year	Available 1 year

For further details on how to manage save set life cycles, see "How to Specify How Long Backed-Up Data Is Kept".

Directives Resource

Directives contain instructions that can assist the backup process. For example, you can apply the Unix With Compression directive to compress data from a UNIX client machine before it is sent to media during a backup.

Preconfigured Directives Shipped with Backup

Backup ships with the preconfigured directives, as listed in Table 2-6, that cover the most important and most useful backup instructions.

Table 2-6 Preconfigured Directives


Directive	Description
UNIX standard (Can be modified but not deleted)	Use for most of your UNIX clients, and when you do not need one of the other specialized directives. This selection: Applies the directive "+null: core" to the root directory (/), thus skipping the backup of all core files. Contains a swapasm directive to back up the relevant information about all NFS-based and local swap files, but not the data in them. Contains a mailasm directive to ensure that your mail files are backed up but not marked as read, and logasm for directories containing log files.
UNIX standard with compression	Use to backup and compress your UNIX clients.
DOS standard	Use to back up your DOS clients.
DOS standard with compression	Use to back up and compress your DOS clients.
NetWare standard	Use to back up your NetWare clients.
NetWare standard with compression	Use to back up and compress your NetWare clients.
Windows NT standard	Use to back up your Windows NT clients.
Windows NT standard with compression	Use to back up and compress your Windows NT clients.
Index	Use to back up the client file index. This option is usually only used by the Backup `savegrp` program.

You can create your own directives to further increase the efficiency of client file backups. For further details, see "Creating Customized Directives ".

Notifications Resource

Backup provides several types of preconfigured notification messages that inform you about Backup activity: license status, client file index size, media attention, and the results of a scheduled backup.

Notifications are displayed in the Backup administration resource. They can also be sent to you through email or pager, or sent directly to a printer. Table 2-7 lists preconfigured notifications.

Table 2-7 Preconfigured Notifications


Notification	Backup Response
Bootstrap	Prints the bootstrap information on the Backup server's default printer.
Cleaning cartridge expired	Sends email to root: replace the expired cleaning cartridge.
Cleaning cartridge required	Sends email to root: insert a cleaning cartridge.
Device cleaned	Sends email to root: device cleaning is complete.
Device cleaning required	Sends email to root: clean the device.
Device disabled	Sends email to root: a device has been automatically disabled.
Index size	Sends email to root: check the size of the client file index because it will soon exceed the space available.
Log default	Directs the UNIX `syslog` facility (`/usr/bin/logger`) to log and distribute messages about all Backup events.
Migration attention	Sends email to root: check the status of a migration operation.
Migration completion	Sends email to root: a migration operation is complete.
Registration	Sends email to root: check the registration status.
Savegroup completion	Sends email to root: degree of success in completing scheduled backups, cloning, and archive operations.
Tape mount request 1 Tape mount request 2 Tape mount request 3	Requests media be mounted in a device: 1. Displays a pending message. 2. Sends email. 3. Logs a message to the syslog.

Backup Server Bootstrap Printout

When Backup finishes a scheduled backup that includes the Backup server, it creates a Failed Cross Reference Format save set, which contains the server index, media database, and Backup configuration files. The data in the bootstrap save set is the data you need to re-create your Backup server in case of a disaster. Backup writes the bootstrap file to media and automatically prints the bootstrap information to the default printer.

Caution -

Save your bootstrap file in a safe location. The bootstrap information is essential for recovery from a disaster. For more information, see the Solstice Backup 5.1 Disaster Recovery Guide.

Backup Administration Window Display

From the GUI version of the Backup administration program you can view progress messages and completion messages about the status of the backup.

For progress messages, watch the Sessions display in the Backup administration resource. The Sessions display information is also written to the daemon.log file in the /nsr/logs directory.
For completion messages, watch the Messages display in the Backup administration resource. The Messages display information is also written to the messages file in the /nsr/logs directory.
For information on why a backup cannot progress, view the messages in the Pending display. The Pending display shows requests to mount tapes and other conditions that require intervention.

The nsrwatch program also provides this information in a character-based format. For more information see "Server Status Resource for Character-Based Displays ".

Label Template Resource

Label templates provide a method to consistently name and label your backup volumes. Table 2-8 shows the preconfigured label templates that correspond with the preconfigured pools shipped with Backup. Backup automatically replaces server-name with your server's hostname. You can create a custom label template or let Backup create one for you when you create a custom pool.

Table 2-8 Preconfigured Label Template Settings


Pool Type	Preconfigured Setting
Default	`server-name.001`
Default clone	`server-name_c.001`
Archive	`server-name.archive.001`
Archive clone	`server-name_c.archive.001`
Migration	`server-name.migrate.001`
Migration clone	`server-name_c.migrate.001`

Use the Label Templates resource to create new label templates, which you can associate with a new pool or one that already exists. For further details, see "How to Customize Label Templates ".