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 ".