Chapter 9. Recovering and Cloning Save Sets
Prev |  | Next

## Chapter 9. Recovering and Cloning Save Sets

Save sets are a set of files or a filesystem that you define for NetWorker backup. This chapter explains recovering and cloning save sets:

- recover save sets to retrieve data whose index entries have expired and to quickly restore large amounts of data

- clone save sets to make identical copies of selected data for storing off-site, send data to another location, or verify backed-up data

| Note: Besides cloning individual save sets, NetWorker also clones entire backup volumes for offsite storage. See “Cloning Backup Volumes” in Chapter 7 for instructions.

## Shortcuts

Use these shortcuts if you are an experienced NetWorker user, or after you have reviewed the examples in this chapter.

### Recovering Save Sets

Follow these steps:

1. Select “Recover” from the Save Set menu. The Save Set Recover window appears.

2. Enter or select the client system whose save sets you wish to recover.

3. Select the versions of the save sets you wish to recover from the Instances scrolling list. You probably want the last full and any subsequent incrementals to recover the latest version of the files.

4. Click the Recover button. The Save Set Recover Status window appears. If you need to relocate the files, click the Options button, and enter a path in the Relocate recovered data to field, then click Ok. If you want to recover a specific directory or file, enter the complete pathname in the File to recover field. If you enter nothing, the entire save set is recovered.

5. Click the Recover button to begin recovery. Unless you chose to relocate the recovered save set, the data is restored to its original location. You are notified if any file conflicts occur.

Many variables exist for recovering save sets. The steps above are the minimal number of steps required for recovering a save set.

### Cloning Save Sets

Follow these steps:

1. Select “Clone” from the Save Set menu. The Save Set Clone window appears.

2. Enter or select the criteria you wish to use for browsing save sets.

3. Click the Query button; the save set scrolling list displays all of the save sets that meet the criteria you entered.

4. Select the save sets you wish to clone from the Save Set scrolling list.

5. Click the Clone button. The Save Set Status Clone window appears.

6. Click the Start button in the Save Set Status Clone window.

| Tip: Automatic cloning is accomplished in the Groups window. Select “Yes” to clone a group's data, and enter or select the name of the Clone pool.

## Recovering Save Sets

Index entries that have been removed from the online file index have passed their browse period. Consequently, their data is no longer available for recovery through the NetWorker Recover window. However, if the media where the files were originally backed up have not been relabeled, the data might still be available for recovery. If the file index entries have expired, you can use the Save Set Recover window to recover the data from the media.

Recovering by save set also makes the process of restoring large amounts of data or data that has been lost due to a disk crash efficient and straightforward. System administrators who are familiar with the setup of their system's disks can easily determine which save sets they need to recover a disk partition or an entire disk.

Note these advantages of recovering save sets:

- reducing index entries

  Files recovered with the save set recovery feature do not include the file's index entries. Consequently, the file index is not repopulated with old entries. Thus the amount of disk space required to maintain the online file index is reduced. NetWorker generates new index entries the next time it backs up the recovered save sets.

  You do not need to keep index entries online any longer than necessary because you can easily retrieve the data directly from the backup volume with the save set recovery feature. By removing index entries sooner, you free more disk space and keep your online indexes from growing too large.

- preserving access control lists

  NetWorker preserves your operating system's access control list when it backs up and recovers files. NetWorker restores the access control list as long as you recover a save set to the same type of filesystem from which it was backed up.

  | Note: If you do not recover a save set to the same type of filesystem from which it was backed up, NetWorker does not preserve the access control list.

- recovering unbrowsable data

  Save set recovery provides an effective method for retrieving data whose index entries are no longer browsable in the online file index.

  All data backed up by NetWorker has both a browse and retention policy. The browse policy determines how long index entries for backed-up files will remain available in the file index. The retention policy determines how long a file will be tracked in the media index and recoverable from the backup media. For more information on browse and retention policies, see “Determining Browse and Retention Policies (Index Policies)” in Chapter 5.

  | Tip: The `scanner` command also recovers data from the media whose entries have been removed from the file index. The `scanner` command gives you the choice of scanning in data only, data and index entries, or just index entries. For more information on the `scanner` command, refer to the reference page.

- recovering large amounts of data

  Save set recovery helps streamline the recovery process for large amounts of data needed for recovering a damaged disk or disk partition.

  System administrators who are familiar with their system's disks can easily determine which save sets they need in order to recover a disk partition or an entire disk. Typically, a save set is comprised of data from a single disk partition because NetWorker does not automatically cross over mount points when it backs up data. Consequently, often only a single save set is required to restore a disk partition. Depending upon the setup of your disk, you might need only two or three save sets to restore the entire disk.

  If the index entries are still in the file index, you do not need to recover by save set to retrieve data. However, when you are restoring large amounts of data, save set recovery is a more straightforward process. NetWorker simply needs to locate the individual save sets to accomplish the recovery, rather than having to search through and select every single file and directory from the file index.

  | Note: For more information on the NetWorker Recover program, refer to Chapter 4 in the User's Guide.

| Tip: Recover data whose entries have been removed from the online file index with the NetWorker Administrator program (`nwadmin` command). Recover data whose index entries are still in the online file index with the NetWorker Recover program (`nwrecover` command).

This section explains

- using the save set recover windows

- examples

### Using the Save Set Recover Windows

This section describes the contents of the Save Set Recover window, its associated windows, and how to use them.

To open the Save Set Recover window, select the “Recover” command from the Save Set menu, as shown in Figure 9-1.

Figure 9-1. Opening the Save Set Window

The Save Set Recover window appears, as shown in Figure 9-2.

Figure 9-2. Save Set Recover Window

Use features of the Save Set Recover window as follows:

Client field |  | Enter the name of the client system for which you wish to recover a save set, or use the arrow button to select the client from the Client scrolling list. The list contains the clients known to the current NetWorker server. If you do not enter a client name, NetWorker searches for all of the client's save sets.
Save Set scrolling list |  | View the names of the selected client's save sets. Click one save set at a time to see its versions in the Instances scrolling list.
Instances scrolling list |  | View a list of versions of the selected save set. The list includes the save set Date, Level, Size, and Status. The save set status also includes clone information. If the save set has a clone, it is marked “has clones,” and the actual cloned copy is marked “cloned date time.” To select a save set, click once. To deselect a save set, click once again. The seven save set status variations are as follows: browsable: The save set still has an entry in the online file index. recoverable: The entry for the save set has been removed from the client file index, but is still recoverable from the media. recyclable: All the save sets have passed both the Browse and Retention policy time periods and the volume is available for relabeling and overwriting. The data is still recoverable as long as the volume has not been relabeled. scanned-in: The save set was scanned in using the scanner command. in-progress: The save set is in the process of being backed up. aborted: the save set was aborted manually by the administrator during backup or by a system crash. suspect: A previous recovery attempt failed. You can select an unlimited number of versions for the same save set for recovery at the same time. If you do not choose a save set, NetWorker automatically selects the last save set version from the bottom of the Instances scrolling list.
Details button |  | Click to open the Save Set Recover Details window for more detailed information on a specific save set version. Details for the last save set selected are displayed.
Recover button |  | Click to open the Save Set Recover Status window to begin the save set recover process.

### Save Set Recover Details Window

The Save Set Recover Details window provides more detailed information, including the size of the data you are recovering and the name and location of the backup volume. To open the Save Set Recover Details window, click the Details button in the Save Set Recover window.

Figure 9-3 shows the Save Set Recover Details window.

Figure 9-3. Save Set Recover Details Window

Features of the Save Set Recover Details window are display:

name |  | Save set name.
date |  | Day and time the save set was backed up.
files |  | Number of files in the save set. The number could be zero if the save set was an incremental backup and the files did not change since the last backup.
ssid |  | Internal number assigned to the save set by NetWorker for purposes of tracking the data.
size |  | Size of the save set.
pool |  | Name of the pool to which the backup volume belongs.
status |  | Status of the save set.
volume |  | Backup volume name and its location, if it has one.

#### Save Set Recover Status Window

The Save Set Recover Status window allows you to customize save set recoveries further. Use it to select individual files rather than whole save sets and to determine where and how you will locate the recovered data. To open the Save Set Recover Status window, click the Recover button in the Save Set Recover window.

Figure 9-4 shows the Save Set Recover Status window.

Figure 9-4. Save Set Recover Status Window

Use features of the Save Set Recover Status window as follows:

Save Sets scrolling list |  | View a list of save sets selected for recovery. After you have opened the Recover Save Set Status window, you can continue adding or deleting save sets to the Save Sets scrolling list by selecting and deselecting them from the Instances scrolling list in the Save Set Recover window.
Paths to recover field |  | Recover individual files or directories by entering their complete pathnames. Press `<Enter>` to add them to the Paths to recover scrolling list. Entering an individual file or directory automatically excludes all other data in the save set from being recovered. For example: The save set pathname in the Save Sets field is `/usr/src/release/nsr/4.0.4`. You need to recover only a single file named `help` from the save set. To recover the file `help`, enter the following in the Paths to recover scrolling list: `/usr/src/release/nsr/4.0.4/help` Press `<Enter>`. NetWorker recovers only the file `help`. For example: The save set pathname in the Save Sets field is `/usr/src/pubs`. You want to recover only the directory `Templates` from the save set. To recover the directory `Templates`, enter the following in the Paths to recover field: `/usr/src/pubs/Templates` Press `<Enter>`. NetWorker recovers the `Templates` directory and all of its data, including any directories and files. It does not recover any data above the `Templates` directory.
Delete button |  | Click to delete a file or directory you have selected from the Paths to recover scrolling list.
Status scrolling list |  | View messages that report on the status of the recovery. The Messages display of the NetWorker Administrator window displays the same information.
Recover button |  | Click to start a recovery
Volumes button |  | Click to open the Save Set Recover Volumes Required window to determine which backup volumes are needed to recover the data. All of the volumes required for all of the save sets listed in the save sets scrolling list will be displayed. This information may be useful especially if you discover that the backup volume is located offsite, and need to make special arrangements to retrieve it. Figure 9-5 shows this window. Figure 9-5. Save Set Recover Volumes Required Window
Options button |  | Click to open the Save Set Recover Options window. Use this window to determine where and how you will recover data. Figure 9-6 shows this window. Figure 9-6. Save Set Recover Options Window

Use features of the Save Set Recover Options window as follows:

Relocate recovered data to field |  | Enter the full pathname of the directory where you wish to locate the recovered data. If you do not enter a pathname, NetWorker automatically recovers the data to its original location.
Duplicate file resolution choices |  | Select an item to determine what NetWorker should do if a file with the same name already exists. If you do not select one of the choices, NetWorker automatically selects the “Rename recovered file” choice. Rename recovered file: renames the recovered file with a .R extension when a filename conflict occurs. If the .R file exists, NetWorker adds another .R. For example, a file named `document.R` will be renamed to `document.R.R`. Discard recovered file: discards the recovered file. The existing file remains current Overwrite existing file: replaces the existing file with the recovered file. The existing file is lost and the recovered file becomes current.
Always prompt toggle button |  | Select to be prompted when there is a filename conflict, and turn off if you do not wish to be prompted when there is a filename conflict. If the toggle button is not selected, the “Duplicate file resolution” choice is applied without confirmation.

### Examples

This section contains two examples of how and why to recover a save set.

#### Example 1: Recovering Individual Files

In this example a user needs to recover several files and has not been able to locate them in the NetWorker Recover window. The files have passed their browse period, so they are no longer included in the online file index. Consequently, the files do not appear in the NetWorker Recover window. The user wants to know if the files still exist and whether or not the system administrator can recover them.

Before the search can begin, the user needs to provide the administrator with the name of the filesystems, the filenames, and the dates of the save sets to be recovered.

The system administrator follows these steps to recover the needed files:

1. Open the Save Set Recover window by selecting “Recover” from the Save Set menu.

2. Enter the name of the client system in the Client field, or click on the arrow button to select a client from the Client scrolling list.

   | Note: If the system administrator cannot find the client that needs to have files recovered in the Client scrolling list, the client is backed up by another NetWorker server. Open the Change Server dialog box from the Server menu and select the correct server.

3. Select the save set in the Save Sets scrolling list that contains the appropriate filesystem. Once selected, different versions of the save set appear in the Instances scrolling list.

4. Select the save sets with the correct dates from the Instances scrolling list.

5. Click the Details button to see how many files are in the save set. Click Ok when finished with the window.

The system administrator continues the recovery process by opening the Save Set Recover Status window.

1. Click the Recover button. The Save Set Recover Status window appears.

2. Enter the entire pathname of each file to be recovered in the Paths to recover field. The user does not need to recover the entire save set, only a number of files. Press `<Enter>` to add the file to the Paths to recover scrolling list.

3. Click the Volumes button to determine the backup volumes needed for recovery.

4. Click the Options button. Enter the full pathname of the user's home directory in the Relocate recovered data to field.

5. Select “Rename recovered file” or “Discard recovered file” from the Duplicate file resolution choices to prevent any files still existing from being overwritten with recovered files. Click the Always prompt button to be notified every time NetWorker finds an existing file with the same name. Click Ok to apply the choices and to close the window.

   | Note: If you are uncertain about which files you want, select the “Rename recovered file” option to get all of the files back during recovery.

6. Begin the recovery process by clicking the Ok button in the Save Set Recovery Status window.

   As the recovery process begins, messages appear in the Status display that provide information on the progress of the recovery.

#### Example 2: Recovering a Disk Partition

An engineering company has developed software for a federal government project with the hopes of signing a lucrative contract. The project was cancelled because an agreement could not be reached on the terms of the contract. The engineering team was uncertain about when or if the project would resume. Consequently, the engineering team had the company's MIS personnel back up the project files and remove the original data from the disk.

Six months later, an agreement has been reached over the terms of the contract. The project has been rescheduled, and the engineering team now needs to retrieve the data so it can finish developing the project software.

The MIS personnel follow these steps to recover the data back to the original location on the disk partition:

1. Properly prepare the NetWorker client disk partition where the data was originally located.

2. Open the Save Set Recover window by selecting “Recover” from the Save Set menu.

3. Enter the name of the NetWorker client where the data was originally located in the Client field.

4. Select the save set that contains the original project software from the Save Set scrolling list. Different versions of the save set appear in the Instances scrolling list.

   | Tip: Typically, a save set is comprised of data from a single disk partition because NetWorker does not automatically cross over mount points when it backs up data.

5. Choose the most recent full backup and any incremental backups performed since the last full backup from the Instances scrolling list. The incrementals are necessary because the engineering team needs any changes to the software since the last full backup.

6. Click the Details button for one save set at a time to determine its size and the number of files it contains. The Save Set Recover Details window appears. Click Ok to close the window.

The MIS personnel continue the recovery process by opening the Save Set Recover Status window and following these steps:

1. Click the Recover button. The Save Set Recover Status window appears. The Save Sets scrolling list contains the save sets selected for recovery. Do not enter a specific file or directory name in the Paths to recover field because the entire save set is needed for recovery.

2. Click the Volumes button to determine which volume(s) is needed for recovery. The Volumes Required for Recovery window appears. Click Ok to close the window.

3. Click the Options button. The Save Set Recover Options window appears.

4. Enter the full pathname of the disk partition in the Relocate recovered data to field where the files will be recovered. Enter nothing if you want to recover the files to their original location.

5. Select “Overwrite existing file” from the Duplicate file resolution choices to overwrite any files that still exist on the original disk partition.

6. Deselect the Always prompt button. There is no need to be notified every time NetWorker finds an existing file with the same name.

7. Click Ok to apply the choices and to close the Save Set Recover Options window.

8. Begin the recovery process by clicking the Ok button in the Save Set Recovery Status window.

   As the recovery process begins, messages appear in the Status display that provide information on the progress of the recovery.

## Cloning Save Sets

Cloning data provides additional security for backing up and recovering data across your network by creating identical copies of your backed-up files. You might want identical copies of your data for storing off-site, or for sharing valuable engineering data with another company location. You can automatically clone save sets immediately after a backup completes, or manually on an as-needed basis. Both procedures are explained in this section.

NetWorker assures the safety of your data by copying each clone of the same save set to a different backup volume. The original backup volume is the source volume, and the volume to which you clone the data is the destination volume. NetWorker individually tracks cloned save sets and their destination volumes and marks them as cloned in the media index. More specifically, NetWorker indicates the cloned data in the windows displaying volume and save set information, which are the Volume Management, Save Set Recover, and Save Set Clone windows.

Note these features of cloning save sets:

- volume sizes for cloning save sets

  Source and destination media can be of different types and capacities, and cloned save sets can span destination volumes just as they span source volumes. Save sets that fit on one backup volume might spill over to two backup volumes because the destination volume has a different capacity. However, the opposite is also possible: for the original save sets requiring two volumes, the cloned save sets might require only one volume.

- retention policies for cloned save sets

  By default, save sets on the source and destination volumes have the same retention policies. However, you can override the preselected retention policy by applying the man mode to the cloned volume in the Volume Management window. When you apply the man mode to a volume, you must change a volume manually to the recyclable mode before NetWorker can overwrite the backup volume. This procedure is explained in this section.

- timing the cloning operation

  To help minimize network traffic, NetWorker clones save sets after a backup is complete. You should take into account the time to complete the cloning process before scheduling another backup. Providing adequate time to complete either backing up or cloning of data helps reduce the amount of network traffic.

  Typically, it takes the same amount of time to back up and to clone data. The cloning process might take less time because the tape drive does not have to wait for the client disk to send data. CPU speed and the operations taking place on the NetWorker server can affect the time required for cloning data. However, generally it is the backup device that controls the speed with which data is backed up or cloned. For example, cloning data to a 5 GB tape on an 8-mm tape drive, backing up at a rate of 500 KB per second, should take approximately 2 3/4 hours.

- index entries for cloned save sets

  NetWorker does not create an additional set of index entries for either online index. Both the original and cloned volumes use the same set of file and media index entries. Consequently, if you eliminate either the cloned or original volume from the media index, NetWorker does not let you remove the index entries as long as one of the volumes still exists.

- using cloning to verify data integrity

  You can use data cloning to help verify the integrity of backed-up data. After the cloning process has completed, a message informs you which save sets could not be read, if any. If NetWorker performed an automatic clone, a message would appear in the savegroup completion e-mail. If NetWorker performed a manual clone, a message would appear in the Status portion of the Save Set Clone Status window.

| Note: For more information on cloning entire backup volumes, see “Cloning Backup Volumes” in Chapter 7.

This section explains

- requirements for cloning save sets

- using clone pools

- using the save set clone windows

- using automatic cloning

- examples

### Requirements for Cloning Save Sets

Cloning save sets requires the following:

- NetWorker release 4.1.1 or greater (this software allows you to clone save sets created prior to release 4.1.1)

- NetWorker TurboPak

- multiple backup devices

- source and destination volumes

- clone pools

The volumes chosen as cloning destinations must belong to a clone pool. Assigning cloned volumes and nonclone volumes to separate pools helps you manage and identify cloned and noncloned data.

The default NetWorker pool type for cloned volumes is the preconfigured Backup Clone pool. The Backup Clone pool is listed as one of the choices in the Pool type scrolling list in the Pools window. The Pools window also allows you to create your own clone pools if you do not want to use the preconfigured Backup Clone pool. Use descriptive names for the clone pools you create to help identify the data they contain.

| Note: For complete instructions on creating volume pools, see “Using Volume Pools” in Chapter 7.

### Using the Save Set Clone Windows

This section describes the contents of the Save Set Clone window, its associated windows, and how to use them.

| Note: Use the Save Set Clone window to clone save sets manually. Use the Groups window to enable automatic cloning, as explained later in this chapter.

Use the Save Set Clone windows for browsing and selecting individual save sets for cloning. To open the Save Set Clone window select “Clone” from the Save Set menu, as shown in Figure 9-7.

Figure 9-7. Opening the Save Set Clone Window

Figure 9-8 shows the Save Set Clone window.

Figure 9-8. Save Set Clone Window

The upper portion of the window contains fields for selecting the save sets you wish to browse. You can fine-tune the saves sets you select by entering information in as many fields as necessary. The more fields you use for selecting save sets for browsing, the faster NetWorker locates and displays the selected save sets. If you do not enter specific values in the fields, NetWorker displays all of the client save sets.

The lower portion of the window displays the save sets selected for browsing. This portion of the window also contains buttons for initiating the browsing process, for viewing details, and for cloning save sets.

Use the features of the Save Set Clone window as follows:

Client field |  | Enter the client name whose save sets you wish to browse. If you do not enter a client name, NetWorker locates and displays all of the client save sets.
Save Set field |  | Enter the name of the save set you wish to browse.
Volume field |  | Enter the name of the volume whose save sets you wish to browse.
Date field |  | Enter the range of dates on which the save set was created. By default NetWorker has yesterday's date in the Start field, and today's date in the End field. Enter the date on which you want to begin the search in the Start field and the date on which you want to end the search in the End field. You can enter the dates as follows: completely written out: March 1, 1994 numerical format: 3/1/94 phrase: for example, two weeks ago, three days ago
| Tip: Open the Volume Management window to locate the information for the Save Set, Volume, and Date fields.
More button |  | Click for additional browsing choices in the Save Set Clone window. The window changes by adding more choices for selecting criteria for browsing. See “Viewing Additional Browsing Choices” in this chapter for more information.
Query button |  | Click to display the save sets chosen for browsing in the Save Sets scrolling list.
| Note: The save sets selected for browsing will not appear in the Save Sets scrolling list until you click the Query button.
Save Sets scrolling list |  | View the save sets currently selected for browsing, including the Client name, Volume name, Date, Level, and Save Set name. To select a save set, click on it once. To deselect a save set version, click on it once again.
Details button |  | Click to open the Save Set Cloning Details window to view more details about a specific save set before cloning.
Clone button |  | Click to clone the save sets you have selected in the Save Set scrolling list. The Save Set Clone Status window appears. You can clone an unlimited number of save sets at the same time.

#### Using the Save Set Clone Details Window

Use the Save Set Clone Details window to see more detailed information about the save set selected in the Save Sets scrolling list. Select only one save set at a time to view its details. The window displays information for the last save set selected. The information in the Save Set Clone Details window helps you better prepare for cloning selected save sets.

Figure 9-9 shows the Save Set Clone Details window.

Figure 9-9. Save Set Clone Details Window

The features of the Save Set Clone Details window display:

name |  | Save set name.
date |  | Time and day the save set was backed up.
files |  | Number of files in the save set.
| Note: The number of files could be zero if the save set was an incremental backup and the files have not changed since the last backup.
ssid (save set ID) |  | Internal number assigned to the save set by NetWorker for purposes of tracking the data.
size |  | Size of the save set.
pool |  | Name of the pool to which the backup volume belongs.
status |  | Status of the save set, which also indicates if a save set is a clone or has clones.
volume |  | Backup volume name and its location.

#### Using the Save Set Clone Status Window

The Save Set Clone Status window displays the save set selected for cloning. Use this window to enter the name of the clone pool to which the data will be cloned and to view the progress of the cloning operation.

| Note: Volumes used for cloned data must belong to a clone pool. Use either the preconfigured Backup Clone pool, or a clone pool you have created yourself.

Figure 9-10 shows the Save Set Clone Status window.

Figure 9-10. Save Set Clone Status Window

Use the features of the Save Set Clone Status window as follows:

Save Sets scrolling list1 |  | View save sets selected for cloning.
Clone Pool field |  | Enter the name of the clone pool. If a pool is not entered, NetWorker uses the default Backup Clone pool.
Status scrolling list |  | View the status of the cloning operation.
Start button |  | Click to start the cloning operation.

#### Viewing Additional Browsing Choices

To view additional browsing choices, click the More button in the Save Set Clone window. Figure 9-11 shows the additional fields.

Figure 9-11. Additional Fields in the Save Set Clone Window

Use these additional choices for selecting save sets for browsing as follows:

Pool field |  | Enter the name of the pool whose save sets you wish to browse.
Status choices |  | Choose the status of the save sets you wish to browse. By default Browsable, Recyclable, Scanned-in, and Recoverable are already chosen. The seven save set status variations are as follows: Browsable: The save set still has an entry in the online file index. Recyclable: All the save sets have passed both the Browse and Retention policy time periods and the volume is available for relabeling and overwriting. Scanned-in: The save set was scanned in using the scanner command. Recoverable: The entry for the save set has been removed from the client file index, but still available for recovery from the media. In-progress: The save set is in the process of being backed up. Aborted: the save set was aborted manually by the administrator during backup or the system crashed. Suspect: A previous recovery attempt failed.
| Note: The Status choices, by default, already have Browsable, Recyclable, Scanned-in, and Recoverable chosen for selecting save sets. If you do not select any Status choices, NetWorker selects all of the client's save sets for browsing. You can only browse In-progress and Aborted save sets; you cannot clone them.
Maximum Level choices |  | Choose the levels of the save sets you wish to browse. By default, “incr” is chosen, which searches for all levels of backups. NetWorker searches for and displays all the levels dependent upon your level choice. For example, if you select level 5, NetWorker browses and displays the save set levels full, one, two, three, four, and five. If you select full, NetWorker searches for and displays only level fulls. You must always have at least one level selected, but you cannot select more than one level at a time.
Sort by field |  | Click one or more of these buttons to sort the save sets listed in the Save Sets scrolling list. NetWorker displays the selections you made in the “Sort by” field and sorts the save sets in that order. Figure 9-12 shows the buttons. Figure 9-12. Sort by Buttons

Try entering information in the different fields, clicking buttons, and selecting save sets to become familiar with the Save Set Clone window.

### Using Automatic Cloning

Use the Schedules and Groups windows to determine the number and kinds of save sets you clone.

| Tip: Automatic cloning is accomplished in the Groups window; see “Configuring Backup Groups” in Chapter 6 for instructions. Select “Yes” to clone a group's data, and enter or select the name of the Clone pool. “Example 3: Automatically Clone Several Clients” later in this chapter gives example instructions for automatic cloning.

Consider these suggestions for setting up your groups with the aid of different backup schedules for accomplishing automatic cloning:

- Set up a group with only those clients whose data you want to clone every day of the week.

- Set up a group whose clients perform full backups and clones one day a week and another group whose clients perform incremental backups every other day of the week.

- Set up a group whose clients back up and clone specific save sets every day of the week.

You can create a variety of backup schedules and groups that help in the configuration of automatic cloning. By following the suggestions above or by developing your own configurations, you can easily accomplish automatic cloning of selected save sets.

### Examples

This section contains three examples of how and why to clone save sets.

#### Example 1: Manually Cloning Save Sets

In this example, a user has requested the NetWorker administrator to manually clone several save sets that are not included in an automatic cloning schedule.

The user needs to send the data to another company location out of state that also uses NetWorker to back up their network data. The NetWorker administrator needs to clone the most recent full backup and any incrementals since the last full to make sure that the most current data is sent.

| Note: The company location receiving the cloned data must use the `scanner` command to retrieve the data. See the reference page for more information about the `scanner` command.

To clone the save set for the user, the NetWorker administrator must have the following information:

- NetWorker client name

- name of the filesystem or directory

- date of the backup to be cloned

The NetWorker administrator follows these instructions to clone the individual save sets:

1. Open the Save Set Clone window by selecting “Clone” from the Save Set menu.

2. Enter the following: client name in the Client field, filesystem name in the Save Set field, and starting and ending dates for which you wish to search in the Date field.

   By default Browsable, Recoverable, Recyclable, and Scanned-in are already selected from the Status choices. There is no need to change or select different status choices.

After selecting criteria for browsing, the NetWorker administrator sorts, views details, and selects the save sets for cloning.

1. Click the Query button; the Save Sets scrolling list displays all save sets that meet the criteria entered in the upper portion of the window.

2. To make sure that the correct dates have been selected, sort the save sets by date by clicking the Date button in the Sort by field.

3. Select the save set versions for cloning.

4. Click the Details button to determine the size of the data and which backup volume contains the save sets.

5. Click the Clone button. The Save Set Status Clone window appears.

6. Enter the name of the clone pool to which the backup volumes will belong. Click the Clone button in the Save Set Status Clone window. The Status field displays the progress of the cloning process.

The Save Set Clone window is useful for occasionally cloning individual save sets or for cloning a small number of save sets on an ongoing basis.

#### Example 2: Automatically Clone One Client

In this example, a system administrator wants to clone data automatically every day for a new system, shakespeare, that manages the company's electronic documentation. shakespeare performs an incremental backup every night of the week, except on Friday when it performs a full backup.

The tasks the system administrator must accomplish these tasks:

- Create a group named Documents to which the client shakespeare will belong.

- Make the appropriate selections for the client shakespeare, which includes assigning it to the group Documents.

The system administrator follows these steps below to automatically clone shakespeare's data:

1. Open the Groups window by choosing “Groups” from the Customize menu.

2. Create the group Documents. See the section“Configuring Backup Groups” in Chapter 6 for more information.

3. Select the appropriate choices in the Groups window. The critical choices are

   - Autostart choices: Enabled

   - Clones choices: Yes

   - Clone pool field: Backup Clone

4. Open the Clients window by selecting “Client Setup” from the Clients menu.

5. Select the appropriate choices for shakespeare. The critical choices are

   - Schedule field: Full Every Friday

   - Group choices: Documents

Following these steps, the system administrator creates a group for just one client so only that client's data is cloned daily.

#### Example 3: Automatically Clone Several Clients

This example illustrates the level of control you can achieve cloning data with NetWorker. You can create an unlimited number of automatic cloning configurations using the Groups, Schedules, and Clients windows.

In this example, the system administrator wants to automatically clone the data for a small group of NetWorker clients that have valuable accounting information. The administrator wants to clone only full backups to store in an offsite vault. Two different groups and schedules need to be created and applied to two identical sets of individual clients in the Clients window.

The system administrator must accomplish these tasks:

- Create two schedules: one to perform incremental backups for the clients and one to perform full backups and clones. Create one schedule named Acct Incr and another schedule named Acct Full+Clone. Table 9-1 summarizes these schedules.

  Table 9-1. Acct Incr and Acct Full+Clone Schedules

  Schedule | Sun | Mon | Tue | Wed | Thu | Fri | Sat
  --- | --- | --- | --- | --- | --- | --- | ---
  Acct Incr | Skip | incr | incr | incr | incr | incr | incr
  Acct Full+Clone | Full | skip | skip | skip | skip | skip | skip

  The system administrator avoids cloning all of the incremental backups by creating two schedules and selecting them for the appropriate set of clients.

- Create two groups: Create one group named Acct Incr and another group named Acct Full+Clone.

  Cloning is applied to a group. Consequently, two groups are necessary: Acct Full+Clone group for performing full backups and clones and Acct Incr group for performing incremental backups.

- Add each client name twice to the Clients window. Two names are needed because only one schedule can be applied to a NetWorker client at one time. One set of clients uses the Acct Incr schedule, and the other identical set of clients uses the Acct Full+Clone schedule.

- Select the appropriate group and schedule for each set of clients in the Clients window.

Figure 9-13 diagrams the automatic cloning procedure for this example.

Figure 9-13. Automatic Cloning Scheme

To clone data automatically, follow these steps:

1. Open the Schedules window by clicking on “Schedules” in the Customize pulldown menu. For complete instructions on creating schedules, see “Setting Up the Backup Schedules” in Chapter 6.

   The schedule Acct Incr performs incremental backups every day of the week, except Sunday when it skips the backup. Figure 9-14 shows this schedule.

   Figure 9-14. Schedule for Acct Incr

   The second schedule, Acct Full+Clone, skips a backup every day of the week but performs a full backup and clones the data automatically on Sunday. Figure 9-15 shows this schedule.

   Figure 9-15. Schedule for Acct Full+Clone

2. After the two schedules have been created, open the Groups window by selecting “Groups” from the Customize menu.

3. Create the first group, Acct Incr. For detailed instructions on creating a group see “Configuring Backup Groups” in Chapter 6. The critical choices are

   - Autostart choices: Enabled

   - Clones choices: No

   The window with the Acct Incr group looks similar to Figure 9-16.

   Figure 9-16. Acct Incr in the Groups Window

4. Create the second group, Acct Full+Clone. The critical choices are

   - Autostart choices: Enabled

   - Clones choices: Yes

   - Clone pool field: Backup Clone

   | Tip: Using two different Start times for the backups helps reduce network traffic.

   The Acct Full+Clone group looks similar to Figure 9-17.

   Figure 9-17. Acct Incr in the Groups Window

The system administrator now creates two sets of identical clients and selects their schedules and groups.

1. Open the Clients window by selecting Client Setup from the Clients menu. See “Adding a New Client” in Chapter 6 for complete instructions.

2. Select the first set of clients one at a time and assign them to the Acct Incr group. Make the other appropriate selections in the Clients window The critical choices are

   - Schedule scrolling list: Acct Incr

   - Group choices: Acct Incr

3. Click the Apply button after making the choices for each client.

4. Select the duplicate set of clients one at a time and assign them to the Acct Full+Clone group. Make the other appropriate selections in the Clients window. The critical choices are

   - Schedule scrolling list: Acct Full+Clone

   - Group choices: Acct Full+Clone

5. Click the Apply button, after making the choices for each client.

The instructions above comprise just one example of how to fulfill automatic cloning requirements.

Prev | Table of Contents | Next
Chapter 8. NetWorker Operations |  | Chapter 10. Configuring and Scheduling Archive Requests