The Clients menu provides access to command windows for adding, configuring, and monitoring NetWorker clients and their associated save sets.
Use the Clients window for applying configurations directly to each client. These configuration settings include schedules, browse and retention policies, directives, and groups. The Clients window also provides the flexibility of scheduling large client filesystems individually and the ability to restrict access to client files.
The Indexes window provides information about backed-up files for each client, called save sets. Each time a client file is backed up, NetWorker creates an index entry for the file in the online file index. The Indexes window allows you to monitor and manage the size of the online file index for each client.
|Caution: You must have administrator privileges to add a client to NetWorker's backups or change settings in the Clients window.|
NetWorker provides preconfigured settings for backing up clients. These settings also apply to the server, which automatically becomes a client of itself. You may use these preconfigured settings or create your own and apply them to clients in the Clients window. For more information on the preconfigured settings available, refer to Appendix A in the Installation and Maintenance Guide.
This section describes the items contained in the Clients window and how to use them to configure clients.
Open the Clients window by choosing Client Setup from the Clients menu. The Clients window appears, with the preconfigured settings as shown.
|Note: The server becomes a client of itself when you install NetWorker. NetWorker automatically adds the server hostname to the Clients scrolling list and provides the preconfigured settings shown above. You must enable the Autostart feature in the Groups window for NetWorker to back up the server automatically.|
The following list describes items contained in the Clients window. The preconfigured settings described are automatically applied to the NetWorker server and newly created clients, unless you choose to make new settings.
Clients scrolling list—displays an alphabetical list of hostnames for NetWorker clients of the selected server. Since the NetWorker server is a client of itself, its hostname appears in the Clients list when you open the Clients window for that server.
Name field—displays the name of the selected client. To add a client: click the Create button, enter the name of the client in the Name field, select the appropriate settings, and then click Apply.
Server field—displays the name of the NetWorker server currently in use.
Archive services choices—allows enabling or disabling of archive services for clients. This option is available only with purchase of the optional NetWorker Archive Application. Backup clients are automatically enabled for archive services upon installation. Refer to Chapter 8, “Archive Application,” for more information.
Schedule field—displays the assigned schedule for the selected client. Click the arrow button to access the Schedule scrolling list, which displays schedules included with NetWorker and any new schedules you create in the Schedules window.
One of the preconfigured Schedule settings included with NetWorker is Default, which performs a full backup every Sunday and an incremental backup every other day of the week.
Browse policy field—displays the chosen browse policy for the selected client. Click the arrow button to access the Browse policy scrolling list containing the policies included with NetWorker and any new policies you create in the Policies window.
The default browse policy setting is Month. Entries for the client files backed up remain in the file index for one month. Backed-up files can be browsed and recovered in the NetWorker Recover window for one month.
Retention policy field—displays the retention policy for the selected client. The retention policy determines how long the save sets on a volume will be recoverable before the volume is available for recycling. Click the arrow button to access the Retention policy scrolling list containing the policies included with NetWorker and any new policies you create in the Policies window.
The default retention policy setting is Year. The names of the backup volumes are retained for one year in the media index. Files can be recovered from the backup volumes for up to one year, unless the volumes are overwritten.
|Note: NetWorker prevents you from setting a browse policy that exceeds a client's retention policy. For example, a browse policy of one month with a retention policy of one week results in an error message. A volume is usually recycled once its retention has expired, when online file index entries are no longer valid.|
Directive field—displays the directives recognized by the NetWorker server. The Directive field is blank, by default. Click the arrow button to access the Directive scrolling list containing the directives included with NetWorker and any new directives you create in the Directives window.
Group choices—displays all backup groups known to the current NetWorker server. To enable scheduled backups for the selected group, you must highlight the group name in the Groups window, then click the Enabled button for the Autostart feature.
Networker provides a preconfigured group named Default, which starts a backup daily at 3:33 a.m. Additional backup group settings are displayed in the Clients window once they have been set up within the Groups window. You can assign a client to as many groups as you want.
Save set field—displays individual client save sets (typically comprising one or more client filesystems) for the selected NetWorker client. The Save set scrolling list displays all filesystems entered for the client. To back up data from a single client filesystem, enter the filesystem name (as a mount point). Save set defaults to All, which backs up all local filesystems for the selected client.
Use the scrollbar to access the lower portion of the Clients window, as shown in Figure 2-2.
Remote access field—displays the remote access permission assigned to the selected client. A blank field indicates that only the client itself can recover its backed-up files. If you want specific users or other clients to have access to data for another client, enter their user@hostname or netgroup name in this field.
Remote user field—use this field to restrict client permissions by entering the client user name. NetWorker uses the user name in this field to execute save and savefs on a client during a scheduled backup. When this field is blank, the user name, by default, is root.
Password field—use this field only if the client is a PC running NetWare, to include the PC client in a scheduled backup. Enter the password used by the NetWorker server to log into the client system in the Password field and press [Enter].
|Note: If you enter a password in this field, you must also enter a user name in the Remote user field.|
Backup command field—enter the name of a program file you create that includes commands to execute before and after NetWorker backs up client data. Create the file in the directory where the save command is installed. See section “Using the Pre- and Post- Processing Backup Command” for details.
Aliases field—use this field to enter an unlimited number of aliases for a selected NetWorker client. Client names may be in simple local name format (for example, myclient) or fully qualified DNS format (for example, myclient.acme.com). List all aliases for the client to help eliminate failed saves due to unrecognized or mismatched client names on the network.
Archive users field—you can only access this field if the optional Archive Application is enabled on your NetWorker server. Refer to Chapter 8, “Archive Application,” for more information.
The Backup command field provides a method for customizing client backups. This field allows you to enter the name of a program you create that affects the way client data backs up. For example, you can create a program that shuts down either a mail server or database before a NetWorker backup and then restarts it after the backup completes. The program can be a binary executable or a UNIX shell script.
The backup command is executed once by each save set defined for the client, not on a per-client basis. If you specify All as the save set, the backup command runs the same number of times as the number of filesystems on the client. The backup command must follow these conventions:
The program name must begin with prefix save or nsr and cannot exceed 64 characters.
The program file must reside in the same directory as save, /usr/etc by default.
The save command must be included in the program to ensure data is properly backed up.
All commands within the program file must execute successfully, otherwise NetWorker cannot complete the remaining instructions.
Use your favorite text editor to create a program file in the directory where the save command resides, usually /usr/etc. You can provide commands to execute either before or after the save command, if you do not need both. For example, your program may contain commands in the following order:
command(s) to execute before a client backup
command to back up the client data (save command)
command(s) to execute after a client backup
Enter the program name in the Backup command field in the Clients window. When NetWorker begins a backup, it checks for an entry in the Backup command field for the client. If a command is present, NetWorker runs that command instead of the save command normally used to back up client data. Since NetWorker does not run the standard save command when a backup command is indicated, you must include the save command in your program. If you do not include the save command in the program, NetWorker will not back up the data.
The following is an example of a valid Backup command program named savemsg. This program prints a message before save begins, executes save on the client data (retaining output in a temporary file), then prints a message after save completes. All output goes into the savegroup completion notice, usually e-mailed to the administrator.
#!/bin/sh case $0 in /* ) PATH=/bin:/usr/etc:`/bin/dirname $0` c=`/bin/basename $0` ;; * ) PATH=/bin:/usr/etc:/usr/sbin c=$0 ;; esac export PATH # print message at start of backup echo "$c": backup started at `date` # perform backup on client save "[email protected]" > /tmp/saveout$$ 2>&1 # print message at completion of backup echo "$c": backup complete at `date` # now include save output for savegrp completion notice cat /tmp/saveout$$ rm -f /tmp/saveout$$ exit 0
Silicon Graphics strongly recommends that you immediately try backing up a client once you have created your program. This ensures that the backup command created does not prevent the client from backing up successfully during unattended backup sessions. Click the Start button in the Group Control window to start an immediate backup.
Before a client can back up to a NetWorker server, the client software must be installed. The software can be installed locally on the client disk or NFS® mounted over the network. After the software is successfully installed on the client, add the client to your NetWorker backups in the Clients window.
See the IRIX NetWorker Installation Guide for installation instructions.
NetWorker clients can manually back up and recover files from a NetWorker server and browse the online file index entries for files. Clients normally back up during a regularly scheduled network-wide backup.
To configure a client, make a selection for each of the following items:
NetWorker server, if you have more than one
browse and retention policies
backup group (one or many)
individual client filesystems (rather than all filesystems for the client)
To add and configure a new NetWorker client, follow these steps:
Open the Clients window.
Click the Create button.
Enter the new client hostname in the Name field.
Add the client to one or more backup groups by selecting the group(s) you want from the Group choices.
Select a schedule from the Schedule choices.
Select both a browse and a retention policy for the client indexes. You may use the existing policies of Month for the browse policy and Year for the retention policy.
Select a set of directives for the client.
Add client aliases, if any, in the Aliases field.
|Note: For details on how to add groups of clients who share common settings, see the instructions in “Create Multiple Button” of this guide.|
If you try to add clients beyond the number of connections you purchased for your NetWorker server, you receive the error message “Too many clients—maximum is number.”
Next, choose the files you want NetWorker to back up for the client.
|Tip: If you want all files for the client backed up, enter All in the Save set field and skip the instructions for backing up specific filesystems.|
Follow these steps to back up a specific filesystem:
Select All in the Save set scrolling list.
Click the delete button.
Enter the pathname (as a mount point, not a device name) into the Save set field for each filesystem that you want backed up. For an example see Figure 2-3.
Click the add button to add the client filesystem. The pathname you typed appears in the Save set scrolling list.
This feature allows you to back up scheduled filesystems at different times. For example, if a client has a large amount of data, you may want to schedule its filesystems separately for backups. For details, see “Scheduling Large Client Filesystems”.
By default, NetWorker clients can browse or recover only their own files. If your organization is concerned about security, Silicon Graphics recommends that you not change the remote access for any clients.
To give other machines access to the files of another client, follow these steps:
Enter the hostname of the client machine (or netgroup name, if you are using NIS) in the Remote access field, as shown in Figure 2-4.
Click the add button next to the Remote access scrolling list.
The hostnames or netgroup names added to the Remote access field appear in the Remote access scrolling list for the client.
Decide whether to use the Remote user and Password fields. See “Navigating the Clients Window” for details.
Enter all aliases for the client in the Aliases field, including the client's fully qualified domain name (for example, venus.company.com).
|Caution: If you do not enter all aliases for a client, you increase the risk of a failed backup because of unrecognized or mismatched client names on your network.|
Click the Apply button to apply the settings and to add the new client to the NetWorker server. The new client appears in the Clients scrolling list. If you make a mistake, click the Reset button to display your previous set of choices.
Using a moderate backup rate of 300 kilobytes per second, a full backup for a client with 5 gigabytes of data would take about 5 hours to complete. Consequently, it may not be convenient to complete a scheduled, unattended, full backup for this client because of the amount of time it will take.
You can, however, schedule the client filesystems to be backed up at different times. Splitting filesystem backups for a client enables you to save all files for that client without trying to do a time-consuming full backup of all of the local filesystems at one time.
The Save set scrolling list in the Clients window displays the filesystems that NetWorker backs up for a client. All of the local filesystems for a client are backed up at the same time, as long as the keyword All remains in the list.
To back up filesystems individually, add and configure the same client twice in the Clients window. Configure the first client to back up half its local filesystems with one backup schedule in one group. Configure the duplicate client to back up the other half of its local filesystems with a second backup schedule in another group.
The following example illustrates how to divide up the client filesystems so they back up at different times.
Find the names and sizes of the local client filesystems using the df command.
% df -k Filesystem Type kbytes use avail %use Mounted on /dev/root efs 966304 619623 346681 65 / /dev/dsk/dks0d2s7 efs 1966304 1573043 393261 80 /home /dev/dsk/dks0d3s7 efs 966304 434836 531468 45 /nsr /dev/dsk/dks0d4s7 efs 1210250 822970 387280 68 /export /dev/dsk/dks0d5s7 efs 1210250 919790 290460 76 /var /dev/dsk/dks0d6s7 efs 1210250 1077122 133128 89 /home/atlas
The largest filesystem in this example is /home, with 1,966,304 KB of space.
Estimate how long it will take to back up the largest filesystem, using the following example:
1966304 kbytes ÷ 300 kbytes/second = 6554.34 seconds 6554.34 seconds ÷ 60 seconds/minute = 109.23 minutes
Repeat the same exercise for each filesystem to determine how to divide them into different backup schedules.
Choose Schedules from the Customize menu and create two new backup schedules:
“Monday Full,” which performs a full backup on Mondays and incremental backups the rest of the week.
“Wednesday Full,” which performs a full backup on Wednesdays and incremental backups the rest of the week.
Each full backup in our example should take less than three hours to complete.
Use the Clients window to configure the client:
Open the Clients window.
Select the client from the Clients scrolling list whose filesystems you plan to divide into different backup schedules. If the client has not already been added to the scrolling list, click Create to add the new client.
Configure the client by choosing a backup group, a directive, a policy, and the Monday Full schedule.
Delete All from the Save set list and add each filesystem you want to back up with the Monday Full schedule, one at a time.
Apply the Monday Full schedule to the following filesystems:
/dev/root efs 966304 619623 346681 65 / /dev/dsk/dks0d2s7 efs 1966304 1573043 393261 80 /home /dev/dsk/dks0d3s7 efs 966304 434836 531468 45 /nsr
Click the Apply button.
Follow the same procedure for the remaining filesystems you want to back up with the Wednesday Full schedule.
Click the Create button to add the duplicate client.
Configure the client by choosing a backup group, directive, policy, and the Wednesday Full schedule.
Delete All from the Save set field, and enter each filesystem you want to back up on the Wednesday Full schedule. Apply the Wednesday Full schedule to the three other filesystems, as shown in Figure 2-5:
/dev/dsk/dks0d4s7 efs 1210250 822970 387280 68 /export /dev/dsk/dks0d5s7 efs 1210250 919790 290460 76 /var /dev/dsk/dks0d6s7 efs 1210250 1077122 133128 89 /home/atlas
Click the Apply button in the Clients window.
NetWorker backs up the filesystems on the client disk using two separate schedules, making it possible to run unattended full backups on this client.
|Caution: When you schedule the filesystems, make sure you do not omit any of them from the Save set scrolling list. Any filesystem left off the list will not be backed up.|
To remove a client from the Clients window, follow these steps:
Select the name of the client in the Clients scrolling list.
Click the Delete button. NetWorker asks for confirmation to delete the client.
Deleting a client means it cannot back up or recover its files from the NetWorker server. The backup history for the client still remains in the file and media indexes until you specifically remove the entries. See “Removing a Backup Volume” for instructions on how to remove the index entries for a NetWorker client.
When NetWorker runs the save, savefs, and recover programs on a client, the programs attempt to establish a connection with the server. Before accepting the connection, the NetWorker server verifies that the user initiating the programs has the necessary permissions. The programs must meet the following conditions for the server to accept the connection:
The request for the connection must be made from a secure port on the machine requesting the connection. A secure port can be opened only by root, so the save, savefs, and recover programs run setuid to root.
The server verifies that the user executing the programs at the machine has permission to save or recover client files. One of the following criteria must be met for a user to have permission:
The machine name for the user is equivalent to the client name.
The user attempting to establish a connection must be a member of the Remote access list in the Clients window.
Once a connection has been established, the client programs save and recover set their effective user ID (UID) to the UID of the user who initiated the program. This ensures that all local filesystem and system call access is done as that user, preventing other users from recovering or backing up files to which they do not have access. The exception to this rule is that the user name operator, and users in the group operator, have filesystem access privileges of root. This allows the administrator to set up a login or group for the operators who initiate backups and recovers on behalf of other users, without giving the operators root access to client machines. For more information about security, refer to the nsr(1M) reference page.
NetWorker's preconfigured settings allow clients to browse and recover only their own files. To give other clients recover access to files on another client, the administrator must explicitly add the access to the Remote access list in the Clients window. See “Configuring Clients” in this chapter for more information.
You can further tighten the access control for client programs by turning off the set-uid bit. This restricts the use of the save, savefs, and recover programs on client machines to root. To allow access by root and operator, but not by other users, change the group ownership of these programs to operator and set the mode bits to allow execution by owner and group.
The savegrp command initiates the savefs command on each client machine in a backup group by sending a remote command request to the nsrexecd program.
The nsrexecd program runs on NetWorker client machines. This program provides a secure and restrictive way for NetWorker to start automatic backups on clients. The nsrexecd program allows you to restrict access to a select set of NetWorker servers. When you install NetWorker on a client, chkconfig automatically turns NetWorker on, so nsrexecd will be started each time the client reboots.
The NetWorker Hierarchical Storage Management Application (HSM) provides file migration and recall services to a range of client machines. If you have purchased this optional extension for your Legato NetWorker server, the Migration Setup choice on the Client menu is enabled.
For complete instructions on the use of the NetWorker HSM Application, see the chapter on Hierarchical Storage Management in the Legato documentation.
This section describes NetWorker's powerful index management features for manually managing the online indexes. You can also automatically manage your indexes by using the different index policies in the Policies window.
|Note: See “Creating a New Policy” for more information on automatic index management.|
Every time a backup completes, NetWorker creates entries for backed-up files for each client in the online file indexes. The indexes require disk space and must be monitored to ensure they do not become too large.
The remainder of this chapter provides a description of the following elements of online index management:
online file and media indexes
four online index actions
The remainder of this chapter also includes instructions on manually managing the indexes and backup volumes:
how to generate reports about the contents of the file index
how to remove the oldest cycle and reclaim index space from the file index
how to manage backup volumes by changing the mode of a volume or by removing a volume from the media index
NetWorker maintains two types of indexes: a file index and a media index. The file index stores information about the files backed up by NetWorker. The media index stores information about NetWorker media and the save sets stored on the media. NetWorker uses these online indexes to locate files requested for recovery. NetWorker determines which volume to mount for recovering a file by mapping the saved files to their backup volumes.
Each entry in the file index typically includes the following information for a backed-up file: filename, number of blocks, access permissions, number of links, owner, group, size, last modified time, and backup time. The file index grows with each backup, as entries are added for the newly backed-up files. As long as an index entry for a file remains in the file index, you may recover the file by using the NetWorker Recover window.
The media index is usually much smaller than the file index because each volume contains many saved files. The size of an index is proportional to the number of save set entries it contains.
Save sets are groups of files, usually contained in a single filesystem, that have been backed up by NetWorker. Save sets are created each time a backup is started. Generating a save set creates one or more entries in both the file and media indexes.
To conserve both index and backup volume space, NetWorker provides a variety of backup levels. For example, a full backup contains all files in a given filesystem, while an incremental backup contains only the files that have changed since the previous backup. Since directories often contain files that do not change along with files that do change, incremental backups conserve both index and volume space.
For information on different backup levels, see the section “Understanding Backup Schedules”.
You need files from both the incremental and full backups to recover a complete directory. Without the underlying full backup, you cannot completely recover the directory. Without the incremental backups, you can recover only the last full backup of the directory, which would not include any incremental changes since the full backup occurred. The incremental backup depends on the full backup. Since both the full and incremental backups are needed to recover the complete directory, NetWorker checks these dependencies when removing save sets from the indexes, either manually or automatically.
Figure 2-6 shows the relationship between incremental and full backups.
|Note: Incremental backups depend upon the previous full backup. NetWorker does not remove a save set until all of its dependent save sets have been removed.|
There are four actions NetWorker performs on an index: inserting entries, browsing file and media entries, removing entries, and reclaiming space.
Inserting entries in the file index occurs during a backup. If the index has no free space, NetWorker acquires more space from the filesystem to hold the new entries.
Browsing neither increases nor decreases the size of an index. When you browse an index, you simply look through the index for information about your saved files or the contents of your backup volumes.
Browsing the media index occurs in the Volumes window where you view the save sets on the backup volume.
Browsing the file index occurs when you use the NetWorker Recover window to locate a file. You may also browse save sets that contain the files you see in the NetWorker Recover window by using the Indexes window.
Removing entries frees up space in the index. NetWorker uses the free space to insert new entries. The Browse and Retention policies determine when entries get removed from the index automatically. You may also remove them manually by selecting Remove oldest cycle in the Indexes window or by choosing Remove from the Volume menu in the Volumes window.
Reclaiming space returns empty space to the filesystem. Empty space is created when entries are deleted from the index, and removed when you click the Reclaim space button in the Indexes window.
|Note: Remember to reclaim space after removing cycles.|
NetWorker provides the ability to generate a report detailing the contents of the file index. The report shows current file index information for the backup namespace of all clients of the server. You can use command-line options to see details about file index contents for a specific client, backup time, or namespace. You can choose to view the report on your screen, print it out, or redirect it to a file.
See the nsrinfo(1M) and mminfo(1M) reference pages for more details on command line options used to customize the file index report.
The following example generates a report on the file index contents for /var backed up during the past week for a specific client. The output of the report is redirected to a file.
Enter the mminfo command at the system prompt to list backup times, in GMT (Greenwich Mean Time), for the specific client save set during the last week:
% mminfo -r nsavetime -N save_set -t 'one week ago' -c client_name
The backup times returned by the nsavetime option are in GMT seconds format. Choose the time you want to use for the nsrinfo time entry.
Enter the nsrinfo command at the system prompt:
% nsrinfo -vV -t time client_name > report_file
The report appears similar to the example below, showing the following information for each file found: file type, path, file ID, file size, offset, file length, and namespace.
scanning client `cl' for savetime 811756903 (Fri Sep 22 01:01:43 1995) from the backup namespace UNIX ASDF file `/var/adm/wtmp', fid = 5383.2066, file size=105408, off=6105488, len=105672, app=backup(1) 1 file found
|Note: Queries for a specific time can take a while to complete because of the file index structure.|
This section describes the Indexes window, its contents, and how to use the window to manage the online file index.
To open the Indexes window, click the Indexes speedbar button (see Figure 2-7) or choose Indexes from the Clients menu.
The Indexes window appears, as shown in Figure 2-8.
The Indexes window contains the following items:
Clients scrolling list—contains client names and client file index information:
Name—indicates the NetWorker client name.
Size—the allocated size of the client file index. The allocated disk space automatically grows as the index size increases.
Used—the percentage of the index file in use. If listed as 100%, the index has completely filled the allocated disk space and there is very little, if any, disk space to reclaim. The smaller the percentage, the more disk space there is to reclaim because the index is not using all of the currently allocated disk space.
If the percentage is less than 100%, you can reduce the size of the index by first selecting the client and then clicking the Reclaim space button. This removes any holes in the file index created by removing index entries. NetWorker automatically removes index entries based on the browse and retention policies you selected for managing online indexes.
Reclaim space button—click to decrease the size of the client file index. NetWorker compresses the space in the index left by removed entries, thus freeing up disk space. A confirmation box appears when a reclaim space operation begins. Click OK to proceed or Cancel to discontinue.
The Save Sets scrolling list—displays the save sets contained in the file index for the selected client. The save sets are grouped according to their unique save set names. For example, all backups of /usr in a client file index are grouped under the save set named /usr.
Name—shows client save set names.
Size—displays an estimate of the amount of index space used by the save set group in the client file index.
Cycles—displays the number of cycles for the save set group contained in the client file index. One cycle starts with a full backup and ends with the next full backup. A cycle includes the incremental and level 1-9 backups, if any exist. See “Selecting the Backup Levels” for a description of NetWorker's backup levels.
Remove oldest cycle button—used to remove the oldest cycle for the save set, if the index requires further reduction. Select the save set, then click the Remove oldest cycle button. After removing a save set, click Reclaim space to remove the holes left by removing the oldest cycle. A confirmation box appears once the removal of an oldest cycle has begun.
Instances button—used to display entries contained in the file index for the selected save set. Instances are displayed in order, starting with the oldest entry. The Instances dialog box displays the save set ID, number of files, size, date backed up, and backup level for each occurrence of the selected save set. Click the Print button to print a copy of the information displayed. Click the Save button to save a copy of the current save set information to a separate disk file.
This section provides instructions for removing the oldest full-to-full cycle of a group of save sets from the client file index.
To remove the oldest cycle from the a client index:
Open the Indexes window by choosing Indexes from the Clients menu.
Select the client from the Clients scrolling list.
Select the save set group from the Save Sets scrolling list.
Click the Remove oldest cycle button to remove the oldest cycle for the save set group. A confirmation box appears, prompting you to confirm that you want to remove the oldest cycle of the selected save set.
Click Ok in the confirmation box to proceed or click Cancel to discontinue the operation.
|Caution: If you do not select a save set in the Save sets scrolling list, NetWorker removes all the oldest cycles of all the save sets displayed in the scrolling list for the client selected in the Clients scrolling list.|
Removing the oldest cycle opens up index space so that other entries can fit into the empty space without increasing the size of the index.
Figure 2-9 illustrates what happens when you remove the oldest cycle from the index.
Note that removing index entries does not decrease the size of the file index, so it still takes up as much space as it did before. To decrease the amount of space the index uses, use the Reclaim space button.
|Note: The last full cycle cannot be removed using the Remove oldest cycle button because it might be needed for recovery.|
Use the instructions in this section to reclaim empty space in the file index created when entries are automatically or manually removed.
Open the Indexes window by choosing Indexes from the Clients menu.
Click the Reclaim Space button. You do not need to select individual clients or save set groups from the scrolling lists.
The Reclaim Space dialog box appears, as shown in Figure 2-10.
Click the Ok button, to start the reclaim space operation.
The Reclaim Space dialog box changes. The Progress bar moves to indicate the progress of the index operation. When an index is busy, the Ok button is disabled.
Click the Cancel button to dismiss the dialog box. The reclaim space operation continues in the background. You can check the progress of the operation at any time by clicking the Reclaim space button to redisplay the confirmation box.
The index is rewritten without the deleted entries, shrinking its size and opening up space for new entries. The reclaimed space is returned to the filesystem.
Figure 2-11 illustrates what happens when you use the Reclaim Space button.
You may not simultaneously reclaim space and remove an oldest cycle for one client. The index is busy during both operations.
After either the reclaim space or remove oldest cycle operations have finished, the statistics in the Indexes window are updated to reflect the current state of the file index.
NetWorker provides you with more detailed information about save sets in the Instances dialog box.
The Instances dialog box contains information on the number of files in a save set, its size, the date it was backed up, and the level of the save set: full, incr (incremental), or level.
You can use the information in this dialog box to determine how your resources are being used. For example, you may need to see how large a save set is so you can plan the amount of disk space you need for the online indexes. Or you may need to generate a report that details your NetWorker client backups to fulfill administrative requirements. Follow these steps to view the Instances dialog box:
The Instances window appears, as shown in Figure 2-12.
The title bar for the Instances window displays the name of the currently selected save set. The Instances scrolling list contains the following information:
Id—internal NetWorker identification number for the save set.
Files—number of files in the save set.
Size—size of the save set.
Date—date the save set was backed up.
Level—level of backup: full, incr, or level.