Previous Chapter : Next Chapter : Top
One of the most serious considerations facing every corporation is that of safeguarding vital information. The risk of losing data through machine failure, carelessness, or willful destruction must be minimized.
As a computer installation grows in size or scope, running backups and providing restore services becomes expensive in terms of time and resources, unless this operation can be automated. In a networked environment, these concerns become even more critical.
The BACKUP.UNET software package provides complete backup, restore, and storage media management for networked systems running a UNIX or UNIX like operating system.
BACKUP.UNET fully supports tar, cpio, cpio -c, ansi, and ansi magtape formats.
BACKUP.UNET allows you to initiate backups and restores from anywhere on the network. Files and directories can be stored on any device (for example 4mm, 8mm, 9 track tape, or tape cartridge) that is also part of the network. You can even do backups with users online. BACKUP.UNET can backup a network of mixed UNIX systems. For example, a user on a Sun workstation can back up files to a tape drive on a IBM AIX machine.
If you are running a UNIX operating system in a networked environment, you can count on BACKUP.UNET to make your network safer, your data more secure, and your job a lot easier.
The following BACKUP.UNET features can help streamline the performance of your backup operations.
Unlike other UNIX backup products, BACKUP.UNET does not rely on a central server for processing. Its unique distributed architecture ensures that there is no single point of failure when you are backing up data. You can use any UNIX system on the network to back up and restore any other UNIX system. Since the backup database is distributed across the network, no single system will become a processing or resource bottleneck.
You may have files written to your backup media in compressed or uncompressed form. Compressing your data allows you to store more files on fewer volumes.
The BACKUP.UNET compression capability reduces word processing documents, program source code files, and database files sometimes to half their original size. Actual results depend on the file contents and structure.
BACKUP.UNET reduces the time required to perform backup operations by using a sophisticated multi process architecture to perform backup I/O operations. This technique allows BACKUP.UNET processing to overlap disk, tape, network, and catalog processing efficiently.
An option is provided for users who want to turn off the BACKUP.UNET standard backup verification function. If your system provides hardware based I/O write verification, or if the volume of data to be backed up precludes re reading and verifying each volume, this option is for you. Network Service Features With BACKUP.UNET, you can optimize your network resources.
You decide exactly what parts of each file system to back up and when. BACKUP.UNET also lets you back up raw partitions, special device files, and files larger than a single volume. Multiple Backups Per Volume The append feature allows BACKUP.UNET to back up several host systems to a single tape volume. It also allows a host to put a series of backups, (for example, a single full backup and subsequent incremental backups) on one volume. The append feature works on high capacity tape drives that support tape positioning, such as 8mm, 4mm (DAT), 9 track, and some TK 50 devices.
Authorized users can operate and administer BACKUP.UNET from any participating host system. This includes the ability to:
Systems sharing I/O device resources on a central network may make simultaneous demands for backup and/or restore operations. BACKUP.UNET manages these demands based on priorities established when the system was installed.
When more than one suitable device is available, whether on a single system or multiple hosts, BACKUP.UNET selects a device and instructs the system operator to mount the requested volume on that device.
To simplify the operator's job and reduce free volume overhead, BACKUP.UNET can be configured to use a single media volume pool. Generally, a media volume pool is associated with each Input/Output Provider (IOP) or group of co located I/O Providers. In this case, all volumes in the shared media pool must be readable by all of the I/O Providers associated with that media pool.
Any or all of the hosts participating in a BACKUP.UNET system may be configured to perform any of the following functions:
If a normal backup I/O location becomes inoperative, backup/restore operations may be continued for requests subsequent to the one on the failed IOP, by using an alternate host's I/O devices.
This changeover is done with a single command or through the GUI window selection.
BACKUP.UNET gives you the option to simultaneously add or remove a user's operator or administrator privileges to or from every host in the BACKUP.UNET system or to specific hosts, one at a time. Thus, if you want a user to have privileges on one, a few, or all of the hosts in your BACKUP.UNET system, you can assign them easily and quickly.
Users can locate and request retrievals of their own files stored anywhere on the network. Users with administrator privileges can restore any files from anywhere on the network. BACKUP.UNET locates storage volumes automatically.
BACKUP.UNET provides you with many features that simplify backups and restores.
BACKUP.UNET uses a consistent graphical user interface (Motif, Graphical User Interface) and command line interface that operates on a wide variety of UNIX platforms.
BACKUP.UNET can write tapes in two formats tar and cpio. Therefore, you can read BACKUP.UNET tapes on other UNIX systems and even most non UNIX systems.
Backup searching allows BACKUP.UNET users to locate and restore the latest version of a file without having to specify an individual dump name.
If security requirements call for files to be encrypted before they are transmitted over the network, BACKUP.UNET calls a user supplied encryption program.
Many UNIX systems come with different manufacturers' I/O devices, including high capacity devices such as 8mm tape cartridges. Files and directories can be stored on any of the following devices: 4mm, 8mm, 9 track, cartridge, and gravity fed stackers.
Each time a backup is run, BACKUP.UNET generates catalog entries, available network wide, that show the storage location of all backed up files and directories. This makes it easier to find the files that needs to be restored. These catalog entries are part of the BACKUP.UNET database which is automatically backed up as part of each backup operation.
BACKUP.UNET also labels backup tapes. It also tells you which storage tape is ready to re use for a backup and checks to see that the correct tape is mounted. This feature protects against inadvertent over writing of backup volumes.
BACKUP.UNET is made up of several different components. These components are discussed in the following paragraphs.
A BACKUP.UNET system host is a participating computer system or machine that provides and/or uses BACKUP.UNET services. Each BACKUP.UNET host has a backup/restore processor or an I/O provider installed on it; it may have both. These hosts can also be designated as a syncro server, a special host type that is responsible for synchronizing the system wide tables used by BACKUP.UNET.
All BACKUP.UNET hosts report their own status in a log file; certain designated machines also receive and maintain a log file containing status information from other hosts in the BACKUP.UNET system. These machines are designated as reporting hosts.
Figure 1 1 shows a network and its BACKUP.UNET host designations.
Graphic: Figure 1-1. Sample BACKUP.UNET Network Configuration
A participating host that performs backup and restore operations has a BACKUP.UNET component called the Backup/Restore Processor (BRP). The BRP is a server daemon that allows both backup and restore operations to be initiated locally or remotely (from another host). The BRP maintains host system backup data information, performs full and incremental backups, and responds to requests for file restores.
A participating host with I/O devices, which is used remotely or locally by other BACKUP.UNET components, has an I/O Provider (IOP) daemon running on it. The IOP responds to requests from BRPs running locally or remotely for tape mounts and read or write operations.
A participating host that is designated as a BRP or an IOP can also be a syncro server. A syncro server host maintains and updates BACKUP.UNET global tables so that they are the same on every host; ensuring that each host has a consistent image of the BACKUP.UNET environment.
Each time a backup is run, BACKUP.UNET generates catalog entries, available network wide, that show the storage location of all backed up files and directories. This makes it easier to find the tape that needs to be restored. These catalog entries are part of the BACKUP.UNET database which is automatically backed up as part of each backup operation.
A backup media pool is a collection of volumes, such as tapes or removable disks, used specifically for backup purposes by BACKUP.UNET. Each media pool contains the same type of media; for example, one pool could contain 8mm tapes while another pool could contain TK 50 tapes.
BACKUP.UNET reads the files and backs them up to the backup media. Depending on how much data was backed up in a particular backup operation, there may be only one volume, or there may be several volumes. All backup volumes are automatically managed by BACKUP.UNET.
A backup volume is a single volume (for example a 9 track tape or an 8mm cartridge) that has been labelled by BACKUP.UNET. This type of label is created electronically at the beginning of the tape, and identifies and describes the data recorded on the tape. The volume's label protects it from being inadvertently overwritten by BACKUP.UNET.
Each BACKUP.UNET volume has a record in the volume table. In addition to the label, the volume table records how many blocks of a volume have been used and how many backup segments are on it.
Backup segments are created by using the append feature during backups. The append feature allows several host systems to be backed up to a single tape volume. It also allows a host to put a series of backups (for example, a single full backup and subsequent incremental backups) on one tape volume.
Note: Only 9 track, 8mm, 4mm (DAT), and some TK 50 devices can support the append feature.
During the first backup, the backup data is written to a BACKUP.UNET labeled tape (a tape that does not contain any backup data) followed by three tape marks (end of file or EOF marks). When the backup is complete, the tape contains a backup segment (the backed up data) and three tape marks.
When the second backup is started, BACKUP.UNET skips forward one segment, skips one tape mark, writes a tape mark, writes the second segment (the second backup data), and writes three tape marks. The tape now contains the first segment, two tape marks, the second segment, and three tape marks. The process continues for each subsequent appended backup.
A backup media pool is a collection of volumes, such as tapes or removable disks, used specifically for backup purposes by BACKUP.UNET. Each media pool contains the same type of media; for example, one pool could contain 8mm tapes while another pool could contain TK 50 tapes. Once you have defined a media pool, its backup volumes may be used by machines in a central location (for example, in a computer room) or by machines at remote locations.
The BACKUP.UNET media pools are managed by an IOP. Each IOP has one or more media pools assigned to it; media pool assignment, by IOP, is known to all participating systems so that any BRPs in your installation can use any media pool. There should be at least one media pool associated with each IOP, or a single media pool may be assigned to more than one IOP.
Access to BACKUP.UNET functions depends on whether you are a user, an operator, or an administrator. Privileges are hierarchical; users have the most restrictions while administrators have the most privileges.
Table 1-1 shows the functions associated with each privilege.
TABLE 1. Table 1-1. BACKUP.UNET Privileges
------------------------------------------------------------
AUTHORIZATION LEVEL
FUNCTION User Operator Administrat Operator/
or Administrato
r
------------------------------------------------------------
Backup Files 4* 4 4
Restore Files 4 4 4** 4
Update Network 4 4 4 4
Configuration
List Backed Up 4 4
Files
Edit Admin Files 4 4
Manage Media 4 4
Answer Requests 4 4
View Audit Trail 4 4 4 4
Recycle Dumps 4* 4 4
------------------------------------------------------------
*Configurable using message number 18 in the 'nbkMSGS' file. (Refer to the BACKUP.UNET Customization and Reference Guide for details.)
** Configurable using message number 19 in the 'nbkMSGS' file. (Refer to the BACKUP.UNET Customization and Reference Guide for details.)
The BACKUP.UNET Motif GUI is particularly helpful for users who are new to BACKUP.UNET or who have very little UNIX experience. Accessing BACKUP.UNET To access the BACKUP.UNET Motif GUI, at the system prompt enter:
xmnbk
The BACKUP.UNET main dialog is displayed. Access to the different functions depends on your BACKUP.UNET privileges.
To leave BACKUP.UNET, from the main dialog, choose Backup Exit to return to the system prompt.