SBAdmin User Guide Version 8.
Trademarks and Copyrights © Copyright Storix, Inc. 1999-2014 USA Storix is a registered trademark of Storix, Inc. in the USA SBAdmin is a trademark of Storix, Inc in the USA and other countries Linux is a registered trademark of Linus Torvalds. Intel, Pentium, IA32, Itanium, Celeron and IA64 are registered trademarks of Intel Corporation. AMD, Opteron, and Athlon are registered trademarks of Advanced Micro Devices.
*Encryption Software System Backup Administrator Backup Data Encryption Feature has a cryptographic component, using Advanced Encryption Standard (AES) "Rijndael" encryption algorithm in Cipher Block Feedback (stream) mode (CFB-128), supporting 128, 192 and 256-bit keys. It is not for export or redistribution to any of what are called the "T-10 Terrorist States" as determined by the U.S. Department of State. System Backup Administrator Backup Data Encryption Feature has been registered with U.S.
Table of Contents 1. Getting Started .................................................................................................. 10 Supported Operating Systems & Hardware ............................................................................................... 10 Software and License Requirements ......................................................................................................... 10 Evaluation License Key .....................................................................
Adding a Backup Media Server ................................................................................................................. 38 Adding a Server Configured in Another Group...................................................................................... 39 Group(s) allowed access to this server................................................................................................. 39 Adding Access to a Remote Group...............................................................
Restoring from Incremental Backups.................................................................................................... 63 Changing a Backup Profile ........................................................................................................................ 64 Removing a Profile.................................................................................................................................... 64 11. Random Tape Libraries ...........................................
Place a Job on Hold ............................................................................................................................. 94 Restart a Job ....................................................................................................................................... 95 Remove a Job from the Queue............................................................................................................. 95 Show Status/Output ...................................................
Operating Systems Support ................................................................................................................134 Sound On/Off ......................................................................................................................................134 Fonts & Colors ....................................................................................................................................134 Check for Updates ..................................................
Index .................................................................................................................... 166 Storix System Backup Administrator 9 Version 8.
1. Getting Started Supported Operating Systems & Hardware At the time of this publication, the software is supported on the following systems: AIX: All IBM RS/6000, System p, System i, OpenPower and JS/20 systems running AIX Version 5.1 and later (currently 7.1).
Network Edition The Network Edition license is only installed onto the system from which network backups will be centrally managed. This system is known as the Network Administrator. Typically, there is a single Network Administrator in a backup environment. This system may also be a client or backup server, but this is not a requirement.
Software Installation and Configuration The following instructions may be used to install the software from either software packages downloaded from the Storix Software web site (http://www.storix.com) or from a System Backup Administrator installation CDROM: Downloading and Installing from the Website 1. Select the software package you wish to download from the website based on your operating system type, machine type and desired software configuration. Be sure to download the file in BINARY.
To update the software with access to the internet, you may automatically check, download and apply updates directly from the Storix website by selecting Help!Download Software Updates from the user interface. A screen similar to the following will appear (note the option for client updates only appears on Network and TSM Editions): You will have an option of checking for updates only and/or downloading and installing updates.
When multiple groups or users configured, you can specify the group or user/password at the command-line with the following flags: # sbadmin –G group –U user/passwd For more information see the SBAdmin Commands Reference. Refer to Configuring Users and Configuring Groups chapters for more information. When starting the GUI interface, the Main Screen will appear. Web-Based Interface – This interface is accessed through a web browser and is designed to be similar in use and function to the GUI interface.
the Main Screen. Refer to Software License in the Preferences section for details on viewing and changing the license options. Initial TSM Setup This document describes TSM client backups only as used with the optional TSM Client Backup Feature for SBAdmin Network Edition. If using SBAdmin TSM Edition, refer to the SBAdmin TSM Edition User Guide instead. TSM Server The TSM Server software must be at level 5.2 or later.
2. Introduction System Backup Administrator (SBAdmin) is designed to simplify the administration of backups on the local system or client backups in a networked environment. It does so by combining powerful backup tools with an easy-to-use graphical or web-based interface for administering backups, boot media, clients, servers and backup devices. Backups created by the Backup Administrator application may include single directories or entire systems (operating system and data).
Note: When using Workstation Edition, the admin system will always act as the backup server. Therefore, references to the backup server in this manual refer also to the admin system. • Client - This is the system from which backups will be made. The admin system or any backup server may also be configured as a client, since they also need to be backed up. Any client may also be configured as a server. A client will be defined as an AIX, Solaris or Linux (UNIX) client.
Tape Devices A tape backup device may consist of a single tape in a single tape drive, multiple tapes from a single tape drive, or multiple tapes from multiple tape drives. For simplicity, the term "tape" or "tape backup" may refer to any of these. When writing backups to tape, each filesystem or raw storage device (partition, logical volume, metadisk, ZFS device, etc) is stored in a separate backup image. This allows tapes to be quickly forwarded to the desired data for faster restores.
choose to use a name such as “ClientSystemBackups” if the directory will be used solely for System Backups of clients, which may be used as network install images. Each backup job will be assigned a unique Backup ID, and each client backup within the job will have a unique backup sequence number. Unlike tape backups, each disk backup will have a unique name, so there is no danger of overwriting a prior backup. Instead, the user must expire disk backups manually to prevent excessive use of disk space.
Each backup job will be assigned a unique Backup ID, and each client backup within the job will have a unique backup sequence number. Each TSM backup will have a unique name on the server, so there is no danger of overwriting a prior backup. Instead, the user must expire TSM backups manually to prevent excessive use of disk space. When doing so, not only the backup labels, but also the actual backup objects are removed from the TSM server.
8. Meta-disk Backup (Linux and Solaris systems only) – Meta-disks are often referred to as Software RAID devices and MDs, multi-disks and meta-devices. This option is only available for Linux if Software RAID support is installed on the system, and only available on Solaris if Solaris Volume Manager is installed on the system. This option will provide the ability to backup specific meta-disks, regardless of the type of device the meta-disk is built on.
3. The Backup Administrator User Interface The Backup Administrator User Interface is used for all configuration options, including servers, clients, devices, jobs, profiles, etc. It is also used for the monitoring of job queues, displaying job status, backup output messages, generating reports and backup history. Scheduled backup jobs will continue to run even if the SBAdmin interface is not running.
A client may be selected by clicking the left mouse button on the icon next to the client hostname. Likewise, a server may be selected by clicking the mouse button on the server icon. When you click on a server, a list of backup devices configured for that server will appear. The selected client, server, and device will appear with a highlighted background. The action buttons at the bottom of the screen apply to the selected client, server or device.
When you click on a queue, the selected queue is highlighted, and the jobs in the selected queue are displayed in the middle display area. You may then click on a particular job to display the job information, including the status of the job. Both the queue and job icons represent the status of the job. The Queue Actions buttons at the bottom of the screen may be used to manipulate the selected job.
4. Users When you first installed SBAdmin, an “admin” user was created and you were prompted to provide a password for this user. The admin user is given authority to all (System Admin) functions within the SBAdmin application, including configuring other users. If there is only one user configured, and you are logged onto the system as “root”, you are logged into the application under this user by default. You will not need to provide a username or password at the command-line.
From this screen, type the user name in the User name: entry field. When adding a new user you must also specify the Default Group, User Password, and Select the access level for this user section. Press the Save button to add the newly configured user. When finished, press the Cancel button at the bottom. • User name – This field indicates the username within the SBAdmin program. This does not need to be a user defined on the Unix/Linux system.
Users with access lower than Group Admin will only have the ability to change their password. All other fields will be disabled. When finished, press the Cancel button at the bottom. Changing your User Information Only a user with System Admin access can add, change or remove other users. Other users can change their own information by selecting Configure!User Information or File!User Information (for users with only Backup User access).
5. Groups To configure Groups you must be logged into SBAdmin as a User with “System Admin” privilege. When SBAdmin was first installed the group “main” was created. The “main” group will function as the default group and no further group configuration is required. You may choose to configure groups to assist with the organization or security of your backup environment.
Changing a Group Click Configure!Groups. Select the name of the group you wish to change from the Group name: drop-down arrow to the right. You may now edit the Description and New group name fields or select/deselect users from the Users who can access this group box. Once you have made the appropriate changes press the Save button to update the group. The “Group ID” field will never change. Once a group has been configured this value will always be used to identify the group.
Using Groups The following diagram illustrates how two groups may be configured on a single Administrator to isolate clients and servers from two separate environments. For security reasons clients from the Development group will not have access to backups performed by clients of the Production group and vice-versa. Clients may ONLY belong to one group but a server can be shared among multiple groups.
In this example, the SharedServer has a directory device configured containing both %G and %C notation. This means only the original client and group will have access to the backup. See Configuring Servers for further detail. After the first group is configured, the SBAdmin interface can either be switched to group Development or a second instance of the interface can be started (by typing “sbadmin –G Development“), allowing simultaneous access to both groups.
6. Clients This section only applies to the Network Edition license option. A client is defined as any system that will be backed up using the Backup Administrator. If backups are to be performed of the backup administrator itself, or any backup servers, they should also be configured as clients. Any number of clients may be added to the administrator as long as the total number of unique clients and servers does not exceed the number of clients licensed to the network administrator.
To add a new client, enter the hostname of the client in the entry field at the top. Note that the hostname you enter may be a simple hostname (i.e. LinuxServer), a full domain name (LinuxServer.storix.com) or IP Address as known to the admin system. Then select any optional features that apply to this client. The optional features will only be selectable if you have installed a software license for that feature. If so, you may select the option for only the number of clients the feature is licensed for.
For most options, you can simply use the defaults shown. Other options are TSM-specific and described in detail in the TSM documentation. However, you can also use the right mouse button over any option to display the QuickHelp containing more information • TSM Node Name and Password You must enter the nodename of the client in the NODEname field. This is the name of the client system as registered with the TSM server.
data, for any client type, may be encrypted using 128, 192, or 256-bit AES encryption. You may only select this button for the number of clients your encryption license supports. Enabling data encryption for a client does not cause all backups to be encrypted automatically. It only designates which clients will support encryption. For clients that support encryption, the encryption option becomes available when configuring backup jobs.
Local System Backup Options The options in this section may be used to configure devices on the client that may be used as backup media for system backups of the client. These devices would be used in lieu of writing to a device on a backup server. Only system backups may be written to these devices. Refer to Creating a Local System Backup in the job configuration for more details.
The client icon will be removed from the Main Screen when Clients, Servers & Devices are displayed. Storix System Backup Administrator 37 Version 8.
7. Servers A backup media server, also referred to simply as the backup server, SBAdmin server, or just server, is defined as any system to which backups will be sent to and stored. This type of server will have SBAdmin software installed, and all network data transfer between a client and the server will be performed using SBAdmin network communication programs.
another group you may continue to Group(s) allowed to access this server. If this server is already defined, continue with the next paragraph. Adding a Server Configured in Another Group When adding a server that is defined in another group, you may be presented with the following message. “This server was previously configured from another group. Although you have been granted access to define or un-define this server to your group, you will not be able to change the settings.
Here you will need to enter the Group ID as defined on the remote Administrator that will be accessing the server (see Configuring Group to determine Group ID), and the hostname or IP of the remote Administrator. Now that the server has been shared on the first Administrator, the remote Administrator will have to add the shared server. To do so, refer to Adding a Server.
Hosts with Access to All Groups When using a Shared Server, it is often useful to define a client with access to all groups. If a remote Administrator copies a client’s backup to a shared server, the original client will not have access to the backup on the Shared server (since he is not part of that group). A client with access to all groups will be the only way to restore from these backups the Shared Server.
NFS Server Name The NFS Server Name field is a unique name that you will use to identify this server’s configuration. You may configure any number of servers, and may specify the same physical NFS server multiple times by using a different name. NFS Server IP Address In the NFS Server IP Address field, enter the IP address of the NFS server that is exporting the share. NFS Version 4 The NFS Version 4 option allows you to indicate whether the NFS share that is to be mounted is a NFS v4 share.
You should refer to your TSM documentation for information on the additional fields which are normally specified in your TSM system user options (dsm.sys) file. You may use the right-click button over any field to show the QuickHelp information on each field, so information is not detailed here.
COMMMethod This will be displayed as “TCPIP”, which is the only option supported. The only other TSM option is “shared” (shared memory), which can only be used when backing up the server itself. The shared memory option provides no significant performance increase and is not supported by SBAdmin. COMPRESSion A selection of “yes” simply indicates that TSM will compress backup data on the client before sending to the server.
Select a server icon from the Main Screen when the Clients, Servers and Devices are displayed, then press the Remove Server button at the bottom of the main screen. Storix System Backup Administrator 45 Version 8.
8. Backup Devices Before any backups may be performed, you must define the backup devices to be used on the local system (Workstation Edition) or on each server (Network Edition). This includes both tape devices (standalone drives, libraries or autoloaders) as well as backup directories on disk. A backup “device” can be named anything you wish, but typically a single tape drive would be simply called by its physical device name (i.e.
By default, the Physical Device Type field will be set to “Tape/Library”. If you want to create a directory-based device for writing backups to disk on the server, select “Disk/Directory” instead. The remaining options will differ depending on the device type you are configuring: Tape Devices The physical tape drives available on the server will be shown in the listbox. Most often a single tape drive is used independently. In this case, just select a single tape drive from the list.
The sequential data is written to the first tape in the first drive until it fills up. Then, the backup continues onto the next drive in the list, etc. Only when all tapes in all drives are filled will the user be prompted to change volumes. Then, the backup continues again with the first drive and so forth. The volumes are numbered in sequential order.
tape in the magazine. The backup or restore will continue automatically when the new tape is inserted. When starting a backup or restore, if the tape is not already inserted in the drive, SBAdmin will grab and insert the tape automatically. The tape to grab must be set in the Set/Reset Next Tape for Backup/Restore option. After selecting “Yes”, the drop-down list will be enabled. Here you must select the name of the tape library configuration to use.
The %G will be replaced by the Group ID of the group, thereby storing backups for different groups in different directories. It also prevents a client from one group from accessing backups of a different group. If you want all backups from different groups stored in the same directory, remove the %G notation. Likewise, the %C notation will be replaced by the client name. Again, this will store each client’s backups in its own directory, and will prevent a client from accessing another client’s backups.
Default Directory Devices For Network Edition, each time a server is added, three directory devices are automatically configured. This is mainly done to provide default backup options that illustrate the special naming convention for the physical directories and how that affects the location and sharing of the backup files. Those directories are: • /backups/data/%G/%C Non-system backups placed in a private directory for each group and client. These backups are not shared among clients.
9. Local System Backup Device System Backups are primarily used for full system recovery of a client, or for cloning new systems from a backup of another client. This option allows a client or workstation to perform a full system backup to a device local to the client or workstation. No backup media server is required when performing a backup to a Local System Backup Device. There are 3 types of Local System Backup Devices: Disk, NFS, and Tape.
In the Disk(s) for Local System Backups field, select the arrow to the right to display and select one or more disks to use. When selecting more than one disk Volume Groups or Zpools will be used to combine the disks into a single device. If disks are to be used in rotation they must be configured individually. If no disks appear in the list, then there are no spare disks available on the system. Those disks which appear in the list are those believed to be unused by other data.
When you have finished your selections, press the Save button at the bottom of the screen. The messages indicating the progress of this configuration process will be displayed. If you wish to physically remove the disk from the system, use the Eject button at the bottom of the screen. This will make the disk safe for removal. Ejecting will retain all information on the disk, and allow you to configure a second disk to be used in rotation.
In the NFS Server (hostname or IP) field, enter the hostname or IP address of the NFS server that is exporting the share. In the Share on NFS Server (directory) field, enter the directory path of the share on the NFS server. The NFS Version 4 Share option allows you to indicate whether the NFS share that is to be mounted is a NFS v4 share. This is necessary because depending on the operating system type, special handling may be required for NFS v4.
10. Backup Profile A backup profile is used to set default backup selections commonly used when performing different types of backups. Assigning a backup profile to a backup job alleviates the need to repeatedly answer the same questions every time a new job is added. At least one profile must be created for each backup type to be performed. When the software is first installed, a set of pre-defined backup profiles, one for each backup type, is automatically installed.
To add a new profile, enter a new profile name in the entry field at the top of the screen, then select the type of backup for this profile by pressing one of the buttons in the Backup Type section. A profile name may consist of any characters except a colon (:) or space (spaces will be changed to underscores). Use QuickHelp at any time to display a description or instructions for a particular option. Also note that a profile will be assigned to each backup job.
If any items within the data list do not apply to a client, the item will simply be ignored. For example, using a filesystem profile containing “/var /tmp /home”, a client without a /tmp filesystem will only backup “/var” and “/home”.
Note that the option for running “Programs prior to or after creation of snapshot” is only available with backups that are performing snapshots. Using the web interface is slightly different. You will notice the option to configure pre and post backup programs directly from the main profile configuration screen: The pre-backup and post-backup programs will be executed with ROOT USER authority.
Exit code 0 Exit code 1 Exit code 2 Exit code 3 or higher Pre-backup Program Client will be backed up and the job will continue normally. Client will not be backed up and the backup job will be terminated with an error message Client will not be backed up. If there are other clients to backup, the job will continue normally. However the job will complete with warning messages. Client will be backed up and the job will continue normally. However, the job will complete with warning messages.
Backup Server Pre & Post Backup Job programs Server pre and post-backup programs are only available with Network Edition, but will be ignored for backup jobs sent to a TSM Server. When a backup job using a profile containing a server pre-backup or post-backup job program is run, the system will attempt to execute the specified program on the server before the first client backup (pre) or after the last client backup (post).
The software is installed with sample script programs that may be used for any client or server pre-backup, post-backup or pre/post snapshot program. The programs are called “prepost.sample” and "prepostsnap.sample" and will simply display the values of all of the above variables when the backup job is run. You may edit or view the contents of this script file (contained in the DATADIR/custom directory), which contains additional details on the use of this option.
a. On the first day of every month, regardless of the day of the week, a full incremental backup is performed. b. The next day, an incremental level 4 will be performed (if Friday) or an incremental level 7 will be performed (if Monday through Thursday) In this example, keep in mind that it is not necessary to perform a level 1 backup after a level 0, since each level (1-9) will backup the data from the last prior-level backup performed, even if it was several levels prior.
Changing a Backup Profile The information for an existing profile may be changed by selecting Configure!Backup Profiles from the menu bar. The profile options screen will then appear. Either enter the name of the profile in the field at the top of the screen or select the arrow button to the right of the entry field and select an existing profile from the list. The profile settings will then be displayed.
11. Random Tape Libraries A tape library is a device that contains one or more tape drives and is capable of moving tapes between the tape drives and various tape storage slots. Most libraries can be configured either as a sequential autoloader or a random library. If it’s set to sequential mode, you don’t need to configure it as a random tape library in SBAdmin. But to use it was a sequential autoloader, you need to create a tape backup device and indicate that it is contained within an autoloader.
Multiple Drive Libraries A multiple drive library configuration can use two or more drives which are used concurrently for a single backup job. The following picture illustrates the three different tape device configurations, each using a twodrive library. In each case, the same tapes are assigned to the same drives, but the numbers indicate the volume numbers of the backup if all tapes were used. See Tape Write Policy for more information on multidrive configurations.
To create a new library definition, enter a unique name of the library in the Library Name field. You must then enter information in each of the remaining fields and define the library tape drives and tape slots. If you want to add a new library from a list of predefined libraries, select the Predefined button and search for the library that best fits your environment.
Custom Library Commands You may choose to use or create different tape utility commands than the standard “mtx” and “tapeutil” commands that SBAdmin recognizes. However, you must add the names of the commands to execute to a configuration file on the server (if remote) to which the library is attached. To add a new tape library command, edit the /storix/config/library_cmds file (where /storix is replaced with your data directory if configured differently), and add the name of the library command.
Define Drive/Tape Slots On the Library Configuration screen, select the Define Drive/Tape Slots button. When you do so, a Define Library Drive and Tape Slots screen similar to the following example will appear. The slot positions referred to are the physical slot or element location that the library uses to reference the positions of tapes and drives. The location you provide will determine what tape position is assigned for each tape used with SBAdmin.
12. Exclude Lists Exclude lists are used to exclude certain files, directories, or devices (such as partitions or logical volumes) from backup jobs. You may create any number of different exclude lists, and assign one or more exclude lists to a particular backup job. You may also select which clients the exclude list will apply to. This allows you to use an exclude list for a job, but still have it only apply to certain clients if multiple clients are backed up by the same job.
The Clients listbox will only appear when using Network Edition and TSM Edition. You may enter a new exclude list name in the entry field at the top of the screen, or select an existing exclude list name using the arrow button to the left of the entry field. When doing so, the current settings for the selected exclude list, if any, are displayed.
removing an exclude list that is assigned to current backup jobs, the exclude list will be removed from the job configuration. You will be informed if the exclude list is assigned to any jobs before proceeding. Storix System Backup Administrator 72 Version 8.
13. Backup Jobs A backup job must be created before any backup may be performed by the admin system. A job is not required when running a backup from the client using the stbackup command. The job information will identify the backup server, one or more clients to backup (when using Network Edition), the backup profile, and the device on the backup server to send the backup to.
To create a new backup job, enter the Backup Job ID in the entry field at the top. The Job ID is used as unique identifier for this job, and may consist of any letters or numbers except for a colon (:) or space (spaces will be automatically replaced with an underscore). Next, if you are using Network Edition, you must select a server using the arrow button next to the Server Name field. When using Network Edition, you may also choose “local (client tape/disk/nfs)” for the Server.
If you selected “local (disk/tape/nfs)” in the Server field, then you may only select one client from the list, since that client will be sending the backup to its own local media.
Additional Options Answers to the following question buttons may be used to override the default actions taken during a backup: • Use alternate server network: This option only appears for Network Edition, and is only enabled if one or more alternate IPs/hostnames were configured for the backup server. To set the alternate IP address or hostname for a server, refer to the server configuration.
• Verify backup when complete: If you want to automatically verify a backup by re-reading the data on the backup media once the backup completes, check this button. Note, however, that an automatic verify will not be performed if you are using a single tape drive or Sequential Autoloader and the backup has spanned more than one tape volume. This is because user-intervention would be required to begin the verify process at the first volume.
Creating a Local System Backup Using Network Edition, it is possible to setup a backup job to perform a System Backup of a client to its own locally-attached backup media (Local System Backup Device).
1. Select Configure!Backup Jobs from the menu bar, then type or select the Job ID at the top of the screen. 2. If the Job Information is displayed on the Main Screen, select the icon for the job to change and press the Change button at the bottom of the screen. The current job settings for the selected job will appear. Make all desired changes to the information on the screen, then press the Save button to save the changes clear the selections.
Running a Backup Job on Demand Any backup job, whether it is currently scheduled or not, may be run at any time. There are several ways to start a job running: 1. Select Configure!Backup Jobs or Actions!Run a Backup Job from the menu bar, then select the Job ID at the top of the screen and press the Run Now button. 2. If the Job Information is displayed on the Main Screen, select the icon for the job to run and press the Run button at the bottom of the screen. 3.
Copying Backups to Different Media, but this requires you to manually select a backup that was previously created. If configured, a new copy backup job is created after the backup job completes. This job is treated the same as other backup jobs and may be rescheduled or run on demand. However, once run, this copy job is permanently deleted, but will be re-created each time the original backup job completes. Refer to The Copy Backup Job below for more information.
Host Read Permission For backups to a directory on a backup media server, setting this option will ensure that only the original client can read the backup. If you inadvertently set the permission incorrectly, you can later change the read permission of an existing backup by selecting the Change Read Permission of a Disk Backup.
1. Immediately after backup: If selected, a new copy backup job will be created and placed in the Job Queue immediately after successful completion of the backup job. 2. Hrs/mins after backup: If selected, you must enter the number of hours and minutes after the backup job completes that you want the copy backup job to begin. You may want to use this option if you simply want to push the copy process into the future rather than run immediately.
14. Holidays There may be days of the year, even days of the month, that you don’t want any of your backup jobs to run. On holidays, for instance, there may have been no activity on the system, and there may not be anyone available to insert new backup cartridges in the tape drive. You may schedule Backup Exceptions or “Holidays” from performing backups. There are actually two ways to do this, on a job-by-job basis, or for all backup jobs.
When using the web interface the screen presented will look slightly different. To add a holiday, simply click on the date from the calendar. The date will be added to the list on the right. Any dates appearing on the right are automatically saved. To remove a holiday, simply click the X next to the date. In the Backup Schedule Exceptions (by job) window, the following options may also be selected: 1.
15. Snapshot Backups Snapshot feature is available only for AIX systems running AIX 6.1 and later, for Linux data contained in LVM logical volumes, and Solaris data contained in ZFS datasets. SBAdmin provides an option of creating a “point-in-time” backup of data contained in logical volumes and ZFS datasets. This is typically referred to as a snapshot backup.
If using Workstation Edition, the Client entry box at the top does not appear. If using Network Edition, you must select the client for which to configure snapshots by pressing the arrow next to the Client name field. After doing so, a list of logical volumes or ZFS datasets on that system will be displayed in the second listbox. You must either select the individual logical volumes or ZFS datasets for which snapshots may be created, or select “all”.
original data is changed, which may have a greater impact on system performance during the backup. The default of 64 Kbytes is sufficient for most purposes. 3. When backing up this client, create snapshots of filesystems: a. One at a time (sequentially). Select this option if a snapshot should be created individually when the data in that logical volume (or filesystem) is to be backed up. When the backup of this LV completes, the snapshot is removed (resynced).
16. Job Queues When jobs are run, they are actually placed in a job queue. A job queue will exist for each device on each server, and a "disk" queue will exist for each server with backups directories defined. The job queues are used to prevent multiple jobs from attempting to write to the same device at the same time. The jobs in a particular queue will be run in the order in which they were placed in the queue. The Job Queue Display Job queues may only be displayed or manipulated from the Main Screen.
The center area contains the jobs currently in the queue. The jobs are placed, and will be run, in the order they were added to the queue. To show a summary of the information for a job, click on the icon corresponding to the Job ID. The job information will appear in the display area to the right and the selected job icon will be highlighted. The status bar at the upper-right also shows the status of jobs in the queue. If the Running light is green, at least one backup job is currently running.
The Job ID, Server (if Network Edition) and Device are shown at the top of the screen. The middle section will contain a set of boxes for each client in the job. If using Workstation Edition, the Client column will not appear, and only one progress line will be shown. The corresponding client is indicated in the button at the far left. These client buttons may be used to display the progress bar or backup output for a particular client.
Scrollbars are provided to the right of each display panel in case the output exceeds the size of the panel. The Job ID, server, device, and client are shown at the top of the screen. To view the backup output for a different client, select the desired client button on the status report screen. You may press the cancel button at the bottom to close this window. It may be redisplayed at any time, even after the backup has completed.
The Job Message Screen Since many jobs run automatically after being scheduled to run at a certain date and time, there may not always be a person watching the screen when a job is started. Therefore, as jobs are run, the queuing system keeps an updated list of messages on the screen, showing which jobs have run, which have completed, and which jobs have failed (and why). The Job Message screen will only appear if the SBAdmin user interface is running.
A scrollbar is provided to the right to scroll up and down the messages. This screen may only be displayed if the Backup Administrator application is running. When you Close this window, the messages will be removed from the log and cannot be displayed again. If a job completes successfully, or if it fails after having begun the backup, a Label button will appear within the text of the message.
Restart a Job A job which is either on hold, had previously failed, or had been killed, may be started, or restarted, by pressing the Restart button from the Main Screen when the Job Queues are displayed. Jobs that are restarted after they have failed or had been killed will restart from the beginning of the job, even if one or more of the client backups had completed.
17. Backup Labels A backup label is generated for each backup that is started at the beginning of a tape as well as for any backups stored to disk files. These labels are used to keep track of the contents of the backup for use when verifying or restoring data at a later time. The backup label contains a summary of the contents of the backup media, which may include multiple backup jobs and multiple client backups (if Network Edition) within each job.
The Tape Label ID for each volume is shown at the bottom. The tape label IDs will be shown in the backup label if a previous backup containing tape labels overwritten by this backup, or if the option to Write a Tape Label ID to Tape was used prior to writing this set of backups. Use the Print button to send a copy of the backup label to the printer. You will always know the contents of the tape without reading it if you have a copy of the label with each backup tape.
View by Backup ID Select View!Backup Labels!By Backup ID from the menu bar. A list of all labels will be displayed as shown below: This list could become very lengthy if there are a lot of labels on file. To display the detailed label information, click on the button to the left of the desired Backup ID. View by Disk Label ID To display a backup label in which a Local system backup disk was used, select View!Backup Labels!By Disk Label ID from the menu bar.
To view the backup label, select the button on the line with the corresponding backup id. View by Tape Label ID To display the backup label in which a physical tape was used, select View!Backup Labels!By Tape Label ID from the menu bar. A list of tape labels currently associated with backup labels is displayed.
Select the server and device from the list by clicking on the button to the left. Once you do so, a list of backups for the selected server and device is displayed, as shown below: Note that the color of the button represents whether the backup was successful (green) or failed (red). A yellow button indicates that the job completed successfully, but with warning messages. The Job ID, date and time, and a list of clients on the media are displayed for each label in the list.
Select the desired job. An additional list will display, showing the dates the job has been run: Note that the color of the button represents whether the backup was successful (green) or failed (red). The Job ID, date and time, and a list of clients on the media are displayed for each label in the list. To display a label, select a specific run date from the list. The label will be displayed (see above). If you want to return to the job display screen to select a different job, press the Go Back button.
Select the button next to the client and backup type you wish to display. An additional list of specific backup dates for the selected client and backup data will be shown: Note that the color of the button represents whether the backup was successful (green) or failed (red). The Job ID, date and time, and a list of clients on the media are displayed for each label in the list. To display a label, select a specific run date from the list. The label will be displayed (see above).
2. Use the arrow button to select a Server Name (if Network Edition). 3. Use the arrow button to select the Backup Device. 4. If you selected a directory from the list, a list of backup images in the selected directory is displayed. Select a backup image to read. 5. Select the Read Label button. The tape or disk image is read and the label information will be displayed if it exists. If a Backup ID exists on the tape, but the label information for the label is not found, an error message will appear.
Once a backup label has been expired, it will not be possible to verify or restore data from this backup using the Backup Administrator application. However, you will still be able to reinstall a system from a System Backup even if it has been expired. If a backup has been expired or the label history has been inadvertently removed from the system, it is still possible to rebuild this information. Refer to Rebuild (unexpire) a Backup Label for details.
18. Backup Job Status & Output History The job status and backup output, which may be displayed while a backup is running, is kept on file as long as the backup label for the job exists. It is therefore possible to view this information long after the backup has completed.
The desired job status for completed (or failed) jobs may be obtained in each of the following ways: View by Server This option is not available when using Workstation Edition. Select View!Backup Status/Output!By Server from the menu bar. A list of servers and backup devices is displayed as in the same screen available when selecting to View Backup Labels by Server. Select the server and device from the list by clicking on the button to the left.
Note that the color of the button represents whether the backup was successful (green) or failed (red). The Job ID, date and time, and a list of clients on the media are displayed for each label in the list. To display the Backup Status Report, select a specific run date from the list. The Status Report Screen will be displayed (see above). If you want to return to the job display screen to select a different job, press the Go Back button. Otherwise press the cancel button to close this window.
19. Verify a Backup After a backup job has complete, it is often a good precaution to verify the backup to ensure the data on the backup media is complete and readable. The verify process reads all of the data on the backups and verifies it is in the correct format. The backup job may have included multiple clients. For tape backups, there may also be multiple jobs stacked on the same tape or set of tapes.
7. If the selected device is tape, the tape will be automatically read and the backup label ID will be displayed Backup ID field. Press the Begin Verify button to continue. 8. If you selected to verify a backup written to a disk directory, you will be provided a list of backup jobs in the selected directory, similar to the following example: Select the specific backup job to verify by clicking on the button to the left of the desired job. 9.
Using an Alternate Network to Verify from the Server When using Network Edition, it may at time be desirable to have the client read the data using a different network to communicate with the server than is used by default.
If the verify is of any backup type other than a raw device backup (such as a logical volume or meta-disk), a list of files on the backup will be displayed as each file is read. This screen may be closed and redisplayed at any time, even after the verify completes, as long as the Verify Status Report screen has not been closed.
20. Recreate Volume Groups, Logical Volumes or Filesystems The options described in this chapter are supported for AIX systems only. Due to the complexity of Linux and Solaris configurations, allowing creation of devices onto other devices (i.e. meta-disks on logical volumes or ZFS volumes on slices, etc), this feature is not available for Linux or Solaris at this time.
1. If using Network Edition license, select the Server Name. 2. If using a Network Edition license, select the Server Name. When using Network Edition, you can also choose “local (client tape/disk)” for the Server. By selecting this option, you indicate that you want to read the backup information from a disk (directory) or a tape drive attached to a client system, rather than a device configured on a server. 3. If you selected a Backup Media Server, select the Backup Device. or 4.
backups, there may be multiple jobs on the media. In this case, the list will contain all of the backups, even those from different jobs. The information about the backup will be preceded by the backup sequence number, starting with 1 and ending with the last backup on the media. The following is a sample of this screen: You may select the backup from which to recreate the VG by clicking on the button to the left of the desired selection and a checkmark will appear in the button.
If there are changes required to make the selected volume group fit onto the current system, the Edit and Fix buttons will become available. If there are no problems found, the Create button will be available. a. The Check button may be used to check the LVM information again. This is automatically performed when you initially display this screen and any time you change the volume group, logical volume or filesystem information. b.
8. If using a Network Edition license, select the Server Name. When using Network Edition, you can also choose “local (client tape/disk)” for the Server. By selecting this option, you indicate that you want to read the backup information from a disk (directory) or a tape drive attached to a client system, rather than a device configured on a server. 9. If you selected a Backup Media Server, select the Backup Device. or 10.
even those from different jobs. The information about the backup will be preceded by the backup sequence number, starting with 1 and ending with the last backup on the media. The following is a sample of this screen: You may select the backup from which to recreate the LV or filesystem by clicking on the button to the left of the desired selection and a checkmark will appear in the button. Only one selection may be made.
a. The Check button may be used to check the LVM information again. This is automatically performed when you initially display this screen and any time you change the volume group, logical volume or filesystem information. b. The Edit button may be used to change any of the volume group, logical volume or filesystem information defined on the backup in order to make the volume group conform to the current system configuration.
21. Restore Data from a Backup Data may be restored from any backup server to any client using SBAdmin. Using a Network Edition license, a backup taken from one client may also be restored to another client, unless it is a disk backup and, for security reasons, you chose (in the backup profile) not to allow a client to read a backup on the backup server's disk that belonged to a different client. Any type of data contained on a backup may be restored.
5. If you selected a TSM Server, select the Original Client (owner) of the backup. 6. If the selected device is tape, the tape will be automatically read and the backup label ID will be displayed Backup ID field. Press the Begin Restore button to continue. 7.
Selecting Restore Options After selecting the backup media to restore from, you will be returned to the previous window, where you may enter or select the following restore options: The following options may differ depending on the type of backup to restore from and the type of data to be restored. 1. Client to restore data to: This option does not appear on Workstation Edition systems. The client from which the backup originated will be displayed.
Backup Type Restore Data Type(s) Destination Type(s) System Backup Volume Groups (Linux/AIX) Zpools (Solaris) Filesystems Directories Regular Files Logical Volumes ZFS Volumes Meta-disks (Linux) Partitions (Linux) Volume Group Zpools Filesystem, Directory Directory Directory Logical Volume XFS Volume Meta-disk Partition Volume Group (Linux/AIX) Volume Groups Filesystems Directories Regular Files Logical Volumes Volume Group Filesystem, Directory Directory Directory Logical Volume Zpool (Solaris) Z
surrounded by quotes to preserve the space in the filename. Note that you can use wildcards (*) to restore multiple files with similar names or locations. Refer to Restoring Files Using Wildcards below. Search/Select by Name When restoring directories and regular files, you may press this button to view a complete list of files, select one or more files or directories from the list, select a group of files or directories, or search the list using a string or characters or wildcards (*).
From this popup window you may select one or more files to restore. After selecting the Submit button you will be returned to the main screen and can begin the restore. Select Using File Tree Also, when selecting to restore regular files or directories, you can press this button to view a drop-down file-tree list of files or directories, and select from the list.
From this window, you may: 1. Click on any folder or file icon to select that directory or file. Note that when selecting a directory, all files and directories beneath become un-selected as they will be restored automatically as part of their parent directory. Click a selected folder or file to de-select. Note that the full path of selected files or directories will appear in the box below the file tree. 2.
/home/picture.gif /home/anthony/myfiles/picture.gif These are not found because these files are not in a single sub-directory of /home as indicated by the wildcard filename (/home/*/*.gif). To restore these files you would need to also include “/home/*.gif” and “/home/*/*/*.gif” in the list of files to restore. To understand the use of wildcards in the restore, you need only understand how to list files on the system. Any files that are listed on the system when you type: ls /home/*/*.
Displaying the Status and Output of the Restore The restore will begin, and the status report screen, as shown below, will appear automatically. Listed on the screen will be a status line for the backup previously selected. Information pertaining to the progress and performance of the restore will be updated as the data from the backup is read. If the backup selected was not the first backup on the media, the process will need to fast-forward over the prior backups before reading the data.
closed and redisplayed at any time, even after the restore completes, as long as the Restore Status Report screen has not been closed. In addition to the restore output, summary information for the selected backup may be displayed by selecting the Backup Info button. A screen similar to the following example will appear. Simply press the Dismiss button to close this window. Storix System Backup Administrator 128 Version 8.
22. Copying Backups to Different Media This feature may be used to copy any backup from a local or remote (when using Network Administrator) system to any backup media (disk or tape) on the local or another remote system. When copying a backup, the data within the backup is unchanged, this providing you with two working copies from which to restore from. Common uses This option may be used to serve many purposes, for example: 1.
Source Media The source media may be any tape or directory device. Use the arrow to the right of the Device entry field to select a device to copy from. Only directory-based devices containing current backups will be shown.
You may also alter the buffer size of the backup by entering a buffer size (in Kbytes) in the Buffer size field. This is quite useful in increasing the performance of backups when writing to different media. For example, the default 128K buffer size may be adequate when you wrote your original disk backup file, but when copying to a high-speed tape drive or disk, a higher buffer size (i.e. 256K to 1024K) may provide much greater backup performance.
23. Preferences In this section, options that affect the overall operation or appearance of the application are discussed. To change the user preferences, select File"Preferences on the menu bar. Software License This option may be used to display a screen used to reconfigure your Administrator license or add or change Optional Features. To view or change the license information, select File"Preferences"Software License from the menu bar.
3. You purchased a Network Edition for 10 clients, and now want to add support for another 6 clients. 4. You wish to install a new optional feature. Administrator License When the software is initially installed, you indicated the type of administrator you would be installing. This was Workstation, Network, or TSM Edition.
The Interface Options define the features and appearance of the SBAdmin GUI interface: Operating Systems Support This option will not appear if using Workstation Edition. By default, when the Backup Administrator software is first installed, only support for the operating system running on the Network Administrator system is enabled. If, for instance, the Network Administrator is running AIX, the only options that appear in the application will be applicable to AIX systems.
are available. To change these preferences, select File!Preference!General Preferences, press the Configure Button next to Fonts & Colors. The following screen will appear: This screen will always be displayed using the Storix color theme, even when another theme has been applied to other screens.
Winter Classic Storix (default) To change the Font Name, Size or Style, click the arrow button next to the desired selection, then select an option from the list. The sample box will be changed to show your selections. To change the 3D Effect and the Width/Size of Borders, select the option or adjust the values to the desired settings. The sample box will be changed to show your selections. Once you’re satisfied with your selections, press the Save button to save the changes.
Network Timeout For SBAdmin to perform any operations on a client, from querying it’s availability to starting a backup job, it must execute a remote command. By default, if the admin system cannot contact the client within 10 seconds, it is assumed that the client is unavailable. This is adequate in most cases. However, if your network is slow to respond, perhaps due to slow hostname resolution, you may need to increase this value.
To define a new printer, enter the name of your printer in the box at the top of the screen. To change an existing printer definition, either type its name or select it using the arrow button to the right of the entry field. If configuring a new printer, the name you enter may be any name you choose, not necessarily the name of the printer queue as defined to Linux or Solaris. The name you choose will be presented when you select a printer from any of the other SBAdmin printer list options.
go back to using the default adapter (according to the primary hostname of the system), simply remove any entry from this field. The network adapter selected will be used to pass information between the admin system and clients or backup servers, such as backup status messages, command output, and for polling the system availability. It is NOT used to pass the actual backup data, which is sent directly from the clients to the backup servers even if the admin system is the backup server.
It is common to lower this value if you do not want your backups to run as the same priority as other applications. This will usually cause the backup process to have less affect on the performance of other applications, but the backup could run a bit slower. You might consider setting this value to 3 to give backup processes a lower priority, but not so low that the backup takes too much longer.
Backup Retention Policy The backup retention policy (also referred to as the overwrite policy) determines whether or not a new backup should be allowed to write over (thereby destroying) a current backup. A current backup is defined as one with a backup label currently on record. The default policy for tape backups is to prevent accidental overwriting by requiring the user to manually expire a current backup before the same tape may be reused.
days, the backup will not be overwritten and the user will be required to expire the backup manually before proceeding. Refer to Expiring a Backup for the steps to manually expire a backup. These global retention policies may be overridden for specific jobs by changing the Retain option in the job settings. Disk or TSM Backups Backups written to disk (or a TSM server) are never overwritten by a new backup since each backup has a different filename (constructed using the backup Label ID, job ID, etc).
Press the Save button to save your selections and close this window, or press the Cancel button to cancel changes. Backup Status Notifications Because scheduled backups may be running even when the Backup Administrator is not running, it is necessary to provide a method by which the system administrator is informed of the status of backups.
reported using the alternate notification method. Selecting this option is equivalent to using the first option when the Administrator is not running. 4. Do not show on screen, do not use alternate notification If selected, the messages will not pop-up on the screen and will not be sent to the alternate notification. The messages are still logged for displaying on the screen at a later time.
SBA JOBSTART: 000003 June 17 16:50:04 PDT 1999 Job 000003 has been started. Backup Device: rmt1 Backup Server: spiderman Job Clients: mickey minnie goofy --------------------------------------------------------------SBA JOBERR: 000003 June 17 16:53:44 PDT 1999 Job 000003 cannot be written to the tape. Backup Device: rmt1 Backup Server: spiderman Job clients: mickey minnie goofy Error Message: The tape currently in the drive contains a current backup label (929523610).
To view or change the error handling setting, select File!Preferences!Device Error handling from the menu bar. When you do so, a Device Error Handling screen similar to the following example will appear: By default, the backup server and device availability is checked before a backup job is started. The first option, Do not check device before starting job, allows a backup to begin without first checking the availability.
24. Calendar When a backup job is scheduled via the job configuration screen, an entry is created in the systems crontab configuration. All scheduled backup jobs are started using the cron daemon. You can view the backup schedule for a particular month, week, or day in a calendar view by selecting View from the menu bar and selecting Calendar. This feature is only available using the Web Interface The default view for the calendar is the Monthly view of scheduled jobs for that month.
25. Reports When you select Reports from the menu bar, you may further select from a list of reports that may be viewed and/or printed. Refer to Report Preferences for information on configuring printers, files and email addresses for reporting. Each time a report option is selected, a screen similar to the following will be presented: The above example is used when print a “Backup Job History” report.
Clients & Servers This option is not available when using Workstation Edition. Select Reports!Clients & Servers to print a list of the clients and servers configured on the system. Refer to the main Reports section above for details on the Print and Preview options. When selecting this option, an additional option is provided: • Show Server’s device details: Check this box if you want to also show a list of the devices configured for each server listed.
When using Workstation Edition, this report is always run in order of backup job. The option of running by client is not available. Running the report by client: Select Reports!Backup History!By Client. You may select one or more clients for which to print the report or, by not specifying any clients, the report will be reported for all clients. The report may be printed even for clients that are no longer configured by manually typing the client name in the entry box.
3. The retention period in the job settings (number of days) has passed since the backup was performed. 4. You specify a reporting date in the future at which time the backup will have expired. Note that the changing the backup retention period for a job will not change the retention period of backups that have already been performed. Network Install Clients This option is not available when using Workstation Edition.
26. Utilities This section provides instruction on the use of the utilities that are not typically used on a day-to-day basis but provide useful features or the ability to tailor the behavior of the application. Create/Manage Boot Media System Installation media is bootable media which may be used to boot the system to the SBAdmin System Installation process.
Remote Installation Manager (RIM) After a client system is booted from the SBAdmin System Installation Media, the installation process may be performed remotely from any compatible “ssh” client program. SBAdmin includes an ssh client for this purpose, allowing you to display, manage and perform the system installation of the client directly from the SBAdmin user interface on the admin system.
First, the tape will be read to ensure that there is not already a current backup on the media. Because this process will write a new label, overwriting any previous backup contents, you may not overwrite a current backup. If a current backup is found on the tape, you will be given the option of automatically expiring this backup and overwriting the tape contents with the new tape label. The process will then write the tape label to the tape, which usually takes only a few seconds.
2. Rewind/Eject: Rewinds, then ejects the tape from the device. 3. Check if Available: Displays a message indicating whether or not the device is available and a tape is inserted. 4. Check if Writable: Displays a message indicating whether or not the device is available, a tape is inserted and whether or not the write-protect tab on the tape has been set. 5. Check if Currently Rewound: Displays a message indicating whether or not the tape is currently rewound, or at beginning of media. 6.
This option is used to set the next tape number in the library that will be used for the next backup or restore process. To use the option, select Utilities!Perform Tape Library Operations!Set/Reset Next Tape for Backup/Restore from the menu bar. After doing so, the following will be displayed: Select the Library Name by pressing the arrow button to the right of the entry field. Entry boxes will become available for the number of drives that are configured for this library.
After making your selections, press the Move button to begin the operation. If any of the entries are not valid according to the library configuration, an error message will be displayed. Also, if a move operation error occurs, the message will be displayed. Display Library Media Inventory This option may be used to display the media inventory of the library using the Command to Inventory configured in the Configure Random Library configuration screen.
This option will read through the contents of the backup and rebuild the label, one backup at a time. Once that is accomplished, you may restore from the tape just as you could before making this terrible blunder. This option will allow you to select disk backup files, although this is typically only done with tapes. When a backup label is expired for a disk backup, the actual disk backup is normally removed as well.
Read Error Settings This section provides information on the options for controlling the way read errors are handled when reading from the backup media. Although the Backup Administrator itself provides a reliable backup, the media on which the backup is placed can sometimes become corrupt. These options will allow you to select how much work the application should try to recover from errors reading from a corrupt tape.
4. Pad missing data blocks with nulls?: When a data sync error occurs, assuming the reading is setup to continue, the missing data will be padded with NULL bytes by default (the field is set to yes). This is to ensure that, although the data has been altered, it remains in the correct alignment. It is very important for the data to remain in the correct alignment when restoring raw device backups (logical/ZFS volumes, slices or meta-disks).
backup job. In this case, you must select the specific client backup (sequence number) to change from the list. After doing so, the Backup ID and the Backup Seq# will be displayed. You may change the following options: • Owner (client) – This is the name of the client from which the backup originated. This will have no relevance if the access permission of the backup allows Any client/server to read it.
27. Network Security SBAdmin was created with safeguards in place to prevent breaches in security without disrupting the security and integrity of the remaining network. This section outlines the flow of network traffic, the security measures that have been implemented, and what steps need to be taken by security personnel to insure that your software will function properly between network firewalls.
All remote commands are executed using the “strexec” executable, which may be executed only by the root user on the system. All attempts to run remote commands are checked on the remote system for authenticity as follows: In the following, $STXPATH designates your SBAdmin data directory chosen when installing the software (default is /storix), and $STXINSTPATH is the SBAdmin application directory (/opt/storix for Linux & Solaris or /usr/lpp/storix for AIX). 1.
been configured, a password has been set, and the client is booted to the system installation process, there is little security risk, but it is worth noting that the remote user will have access to all system installation process options and installation media available to the client system. RIM access is only provided after booting from SBAdmin system installation boot media and either: a. Enabling RIM access within the system installation menus from the client or b.
28. Getting Help QuickHelp If you are uncertain of the use of a particular button, listbox or entry field, you may at any time move the cursor over the object in question and press the right mouse button. A popup message will appear on top of the object with information on its use and any options, warnings or special instructions that might apply. Information is provided for every selectable object in the application.
Index running from command line, 80 on demand, 80 scheduling, 77 scheduling and running, 73 status and output history, 105 view by client, 107 by job ID, 106 by server, 106 status screen, 90 verify, 108 backup label, 18, 96 backup ID, 96 backup retention policy, 141 expiring, 97, 103 print, 97 rebuild/unexpire, 157 sequence number.
pre- and post-backup programs, 61 removing, 44 report, 149 backup types, 20 boot media system installation, 152 boot server, 151, 152 bootloader, 152 buffer size backup copy, 81 backup profile, 57 copy backups, 131 volume size, 50 write policy, 49 disk local system backup, 36 system install boot disks, 54 disk backup. See directory device disk backup file, 18 changing access permission, 160 overwrite/retention policy, 104, 142 disk label viewing backup labels by, 98 display queues, 89 dsm.opt, 43 dsm.
G operating system support option, 134 setting default printer, 137 snapshot backups, 86 supported software levels, 10 LinuxPPC supported software levels, 10 Local System Backup, 78 logical volume backup type, 20 exclude list, 70, 71 recreate, 112 snapshot backups, 86 system recovery disks, 53 LVM system recovery disks, 53 groups, 13, 25, 28 adding, 28 admin user, 25 backup directories, 49, 50 changing, 29 example, 30 group ID, 28 optional host access, 41 remote groups, 39 removing, 29 server access, 39 s
share, 42 notification. See backup status reporting backup jobs, 149 backup profiles, 149 clients & servers, 149 devices, 149 exclude lists, 149 network install clients, 151 preview, 148 printer, 148 restore history, 150 restore incremental backups, 63 restore history report, 150 restoring a backup, 119 destination, 126 options screen, 121 search pattern, 123 selecting backup to restore, 119 specific data, 21 status and output, 127 using an alternate network, 126 using wildcards, 125 retention.
exclude list, 71 snapshot backups, 86 chunk size, 87 concurrent, 88 enabling, 86 enabling per job, 76 mirroring issues, 88 pre- and post-snapshot programs, 60 sequential, 88 snapshot LV size, 87 software installation, 12 license options, 10 operating system support, 10 starting, 13 updating, 12 software RAID.
users, 25 access level, 26 adding, 25 changing, 26 levels, 25 removing, 26 utilities forward a tape, 155 read error settings, 159 rebuild backup label, 157 show block size, 155 tape library operations, 155 tape operations, 154 write a tape label, 153 recreate, 112 system recovery disks, 53 volume size directory device, 50 W wildcards in exclude lists, 70 restoring files or directories, 125 write policy directory device, 49 tape device, 47 Z V ZFS filesystem backup, 20 operating system support option, 134
