home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: SysTools
/
SysTools.zip
/
backres.zip
/
PSNS.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1999-04-08
|
90KB
|
1,595 lines
ΓòÉΓòÉΓòÉ 1. OS/2 Warp Server Backup/Restore ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore User's Guide
OS/2 Warp Server Backup/Restore is a powerful backup utility that lets you
safe-guard your OS/2 system against loss of data. It allows you to set up a
Backup Strategy for each activity you perform on your machine. The strategy,
once employed, provides protection against all of the likely causes of
data-loss: user errors, hardware malfunctions, malicious damage and disasters.
The program supports all the features of the OS/2 file systems, including:
Long file names
Extended Attributes
Network Access Permissions
OS/2 Warp Server Backup/Restore is compatible with the IBM ADSTAR Distributed
Storage Manager, IBM's flagship data storage management system.
Using OS/2 Warp Server Backup/Restore, you can create backups for
Local Hard Disks
Remote Hard Disks accessed with a Logical Drive Letter
It allows you to store backups into a Backup Set which can reside on any of
the following Storage Devices:
Tape Drives
Hard Disks
Removable Drives
Diskette Drives
LAN Alias Drives
Remote Drives
Optical Drives
IBM ADSTAR Distributed Storage Manager (ADSM)
OS/2 Warp Server Backup/Restore uses a Backup Method to control each backup.
Backup Methods contain all the information needed to execute the backup: which
files and folders to back up, and where and how to store them.
You can restore data simply by selecting the files or folders you want
restored - OS/2 Warp Server Backup/Restore carries out all management
functions necessary to retrieve data from the backups. OS/2 Warp Server
Backup/Restore keeps an inventory of all the files that have backups,
including information about where the file is stored, its attributes, how many
versions exist, and so on. This makes restoring lost or damaged data simple
and easy because it does not rely on you to catalog and organize the backup
media.
This User Guide is divided into 5 sections:
This introduction
Running Your First Backup
Setting Up a Backup Strategy
List of Supported Devices
Frequently Asked Questions
ΓòÉΓòÉΓòÉ 1.1. Version Notice ΓòÉΓòÉΓòÉ
Version 6.01 (August 1998)
It is possible that this product may contain reference to, or information
about, concurrent products (machines or programs), programming or services that
are not announced in your country. Such references or information must not be
construed to mean that IBM will announce such IBM products, programming or
services in your country.
This product may contain examples of data used in daily business correspondence
and operations. In these examples we use names of hypothetical businesses and
persons. These names are fictitious and any similarity to names of actual
businesses and persons is purely coincidental.
This product could contain technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of this product.
Requests for copies of this product and for technical information about the
system should be made to your authorised IBM Personal Computer dealer.
(C) Copyright IBM 1990, 1998. All rights reserved.
ΓòÉΓòÉΓòÉ 1.2. Notices ΓòÉΓòÉΓòÉ
References in this publication to IBM products, programs or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
of IBM's intellectual property rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, is the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents.
ΓòÉΓòÉΓòÉ 2. Running Your First Backup ΓòÉΓòÉΓòÉ
To run OS/2 Warp Server Backup/Restore double-click on the folder icon: This
opens the container with the OS/2 Warp Server Backup/Restore utilities. Now
double-click on the program icon to start the application.
The Guide panel will appear, and give a selection of tasks to carry out. It is
wise to do two things the first time you run OS/2 Warp Server Backup/Restore:
1. Verify that the Storage Devices you plan to use are correctly configured
2. Set up your machine for Disaster Recovery
ΓòÉΓòÉΓòÉ 2.1. Verifying Storage Devices are Available ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore does not back up directly to Storage Devices.
Instead it backs up to Backup Sets:
A Backup Set is a collection of data files related to one or more applications
that you want to consider together for the purpose of backup and restore. The
backed up data for a Backup Set is written and read using either one or two
Storage Devices. Normally, a Backup Set resides on a single Storage Device, but
you may use two Storage Devices if you want to handle the data for full backups
of a Backup Set using a different device than that used for incremental
backups; such a Backup Set is known as a Dual Device Backup Set.
OS/2 Warp Server Backup/Restore manages each Backup Set individually. This
allows each different activity that a particular machine is supporting to be
backed up and restored separately, greatly simplifying common tasks such as
recovering single lost or corrupted files and transfering data between
machines. This also provides a robust framework for Disaster Recovery. By
keeping track of the most recent versions of backup data, you need not worry
about creating your own cataloging scheme for the backup media. This also
saves time-consuming human intervention to find the right file on the right
backup volume.
To verify that you can back up to a Storage Device, you need to have a Backup
Set defined such that it exists on the desired Storage Device. Fortunately,
OS/2 Warp Server Backup/Restore automatically creates default Backup Sets for
each Storage Device it finds the first time it is run. These can be used for
testing purposes, or for occasional one-time backups. A default backup set
created on a given storage device has the same name as the storage device. It
is possible to use the initially created Backup Sets for all backups, however
we do not recommend it. Instead, it is much better to create new Backup Sets
which accurately describe the data they contain. For example, a Backup Set
called Project HyperGlotz (Day-to-Day to C:) will be much easier to recognize
than the default Drive C.
To verify that the Storage Devices you want to use are available, select the
Perform a simple test backup button on the Welcome to OS/2 Warp Server
Backup/Restore panel.
A panel appears which explains what the test will do, and gives a list of the
Backup Sets that have been automatically created. According to the Storage
Devices attached to the machine, you should find some, all or more of the
following Backup Sets:
Diskette A (3.5")
Drive C
SCSI Tape (0:3)
Removable Drive G
Note: SCSI Tape will be replaced by the manufacturer's name of the tape drive
attached to the machine, together with the SCSI adapter number and the
physical unit number.
If the Storage Device you are looking for does not appear on the list refer to
List of Supported Devices and How do I install support for a Storage Device?
in this Guide.
Select the Backup Set you want to back up to, and then press Backup to start
the backup. If the backup completes successfully, you will see a few lines of
status messages in the OS/2 Warp Server Backup/Restore main window:
Last backup:
used method (manual)
completed at (time) on (date)
n objects all backed up OK.
If there are any problems during the backup then an error message appears
(and, if you have multimedia support, a warning message is played). To find
out what has happened refer to How do I find out what error occured during a
failed backup?.
ΓòÉΓòÉΓòÉ 3. Setting Up a Backup Strategy ΓòÉΓòÉΓòÉ
To protect the data on your machine it is important to have a Backup Strategy.
A well planned Backup Strategy will help you save time and effort when backing
up, can help you work more efficiently, and will enable you to recover from
disasters. OS/2 Warp Server Backup/Restore makes it easy to create a complete
Backup Strategy, using either the Backup Guide, or the OS/2 Warp Server
Backup/Restore tools.
ΓòÉΓòÉΓòÉ 3.1. Considerations for a Backup Strategy ΓòÉΓòÉΓòÉ
Before using OS/2 Warp Server Backup/Restore to define your Backup Strategy you
must have clearly in mind answers to the following three questions:
1. What data should I backup?
2. When, or how often should the backup occur?
3. Where should the backup data be stored?
Sometimes it is difficult to answer these questions directly because the
answers require a detailed knowledge of how the machine is used. So let's
step back for a moment and ask the questions in a slightly different way that
will take us closer to defining an actual Backup Strategy.
What activities are performed using the machine?
Typical activities are:
- Working on projects (which produce word processor files,
spreadsheets, plans and so on).
- Personal time management (for example, using an address book and
diary)
- File serving - allowing other machines to access data on the machine
- Basic operating system activities (for example, navigating the
desktop and printing)
Each of these activities involves using or producing data in varying
ways. Each should have a strategy designed for optimal protection
according to the use.
For example, a project's data tends to change frequently, and therefore
should be backed up more often than the base OS/2 system which will
change rarely (if ever).
What activities are most important?
By identifying which activities are essential, it is possible to decide
how data should be backed up. For example, if the machine contains data
for an active project, then the two key resources may be the base
operating system (which is needed to run the programs) and the
applications and data used in the project. It may be reasonable to
recover the rest of the data on the machine over the course of a few
days, as long as the key applications can be recovered instantly.
What devices can hold the backups?
Once you have decided what activities you want to back up, and how
quickly you want to be able to restore them, you should consider where
you want to back up the data. Different Storage Devices are suitable for
different types of backup. For example:
Fast access Hard Disk or LAN Alias
Large capacity Tape or Read/Write optical
Cheap storage for small and medium amounts of data Diskette or Removable
Drive
Centrally managed within a network IBM ADSTAR Distributed Storage Manager
Once you have chosen where you want to store the data, you should
consider what this implies for the Backup Strategy. For example, if you
are backing up to tape it will probably be inconvenient to have many
different backups running frequently, because of the effort involved in
continually swapping tapes. If you are backing up to diskette, keeping
the amount of data backed up to a minimum saves needlessly using many
diskettes.
In a complete Backup Strategy activities will frequently overlap. For
example, you might back up an active project to LAN drive during the day
and then take a complete system backup (including all the project files)
to tape overnight. In this case, files accidentally deleted during the
day can be recovered immediately from the LAN alias and the entire system
can be recovered from tape if something catastrophic happens.
How often should the backup occur?
If the data in a project is changing all the time, then it may be useful
to have data backed up frequently (perhaps once an hour), so that an
accident can be recovered as quickly as possible.
If the data changes rarely then it should be backed up less frequently.
Using a Dual Device Backup Set
If the data you wish to backup consists mostly of stable data to which a
relatively low volume of changes are made, you should consider using a
Dual Device Backup Set. This type of Backup Set allows you to store the
large volume of stable data on a large capacity device, such as a tape,
and the changes on a smaller capacity, faster access device, such as a
diskette or a Removable Drive. This gives you the benefit of low cost
storage for the bulk of the data, at the same time as fast access to
restore the changed data.
ΓòÉΓòÉΓòÉ 3.2. Extending Your Backup Strategy with the ADSM ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore by itself can be used to efficiently backup
single machines and small groups of machines connected via a LAN. However, you
may find that your computer network is beginning to grow beyond your ability to
easily manage backup of all the data. Remember, the most successful Backup
Strategy is one which requires little or no human intervention and that stores
data in the most secure place possible. A network of computers poses unique,
and sometimes frustrating, problems to keeping its data safe and secure.
You should consider using IBM ADSTAR Distributed Storage Manager (ADSM) as an
integral part of your Backup Strategy. It makes backing up a network of
computers easy and efficient through its centrally managed "client/server"
design. ADSM can also be of great help when you find that your network includes
some computers that run operating systems other than OS/2. ADSM features a
unique open-system design that allows you to easily manage the storage
requirements of many different operating environments (such as Apple MacIntosh,
Microsoft Windows, and DEC VMS, to name a few).
ΓòÉΓòÉΓòÉ 3.3. How to Define a Backup Strategy Using OS/2 Warp Server Backup/Restore ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore provides facilities to let you implement your
Backup Strategy. The Backup Guide will take you step-by-step through the setup
of a Backup Strategy for a particular activity, allowing you to define what is
backed up and where and when it is backed up. We must emphasize, however, that
the guide assumes you have already carefully considered all the activities you
perform on the machine and the Storage Devices that are available with the
machine to hold backup data.
The following examples describe strategies to cover two common activities
performed on server machines:
1. Backing Up a File Server
2. Backing Up Programming Projects
ΓòÉΓòÉΓòÉ 3.3.1. Backing Up a File Server ΓòÉΓòÉΓòÉ
Objective:
Backup a file server such that it can be recovered as quickly as possible, even
in the event of a Catastrophic Failure.
Considerations:
1. Disaster Recovery
You must create bootable diskettes using the OS/2 Warp Server
Backup/Restore Disaster Recovery support so that the machine can be
recovered even if the drive containing the operating system is damaged.
You must also create a full backup of the machine to use as the base, or
starting point, of the recovery.
2. Frequency of backup
Ask yourself, "How often do changes occur to the file server such that it
would be difficult or time-consuming to manually recreate the change?"
Remember that while it's possible to create backups that cover every
change to the file server, minute-by-minute, it is often not desirable
considering the amount of machine processing time and backup storage
space that such a strategy would consume. Instead, you might consider
the interval of time between significant changes to the server as an
alternative.
3. Where to store backup data
Ask yourself, "How fast do I need to restore the data and how important
is it to have absolute data integrity?" If you need to restore data very
fast, then you should use either a hard disk or a LAN alias to backup the
data. Otherwise, use a tape or optical device. If absolute data
integrity is an important consideration, yet you need the speed of a hard
disk, consider taking a dual backup - one to hard disk and a second to
tape - to protect against a failure of the hard disk that holds the
primary backup data.
ΓòÉΓòÉΓòÉ 3.3.2. Backing Up a Programming Project Server ΓòÉΓòÉΓòÉ
Objective:
Backup a server that contains files being created and changed as part of a
programming project such that the project files can be recovered in as little
time as possible. Take into account that corrupted files may find their way
into the backed up data before it is realized they are corrupt. Also allow for
snapshots of the project's progress to be taken eiter periodically or on
demand.
Considerations:
1. What data to backup
This sample assumes that files on the server that the project uses but
does not change are covered under a separate strategy for protecting a
file server. Therefore, this strategy should identify only the files
actually created and changed by the project.
2. Frequency of backup
Ask yourself, "How often do changes occur to the project files such that
it would be difficult or time-consuming to manually recreate the change?"
Remember that while it's possible to create backups that cover every
change to every file, minute-by-minute, it is often not desirable
considering the amount of machine processing time and backup storage
space that such a strategy would consume. Instead, you might consider
the interval of time between significant changes to the project files as
an alternative.
3. Number of versions
As with many kinds of data that are frequently changed directly by
humans, your strategy should provide for and protect against corrupt
files finding their way into the backup data. An example of a corrupt
file is a program source file containing a section of declaratives that
was accidentally deleted before the file was saved.
The number of versions, or generations, of the file you keep in the
Backup Set should be chosen, together with the interval of time between
each backup, to provide an adequate opportunity for the project members
to discover a corrupt file and retrieve an intact version of it from the
backup.
You may also want to keep multiple versions of the entire project backed
up. An example of this is a project that plans 2 test releases of its
product, followed by a final release marking the end of the project. To
handle this scenario, create a separate Backup Set that allows 3
generations of backup data. You could then take full manual backups into
this Backup Set at the first, second and final release of the project's
product.
4. Where to store backup data
Your strategy should provide for retrieval of individual files on as
rapid a basis as possible. For this, you need to use either a hard disk
or a LAN alias to backup the data. However, you should also protect
against failure of the primary backup data by periodically backing up the
entire project to removable media, such as tape or optical disk.
ΓòÉΓòÉΓòÉ 4. Frequently Asked Questions ΓòÉΓòÉΓòÉ
This section provides answers to some of the most commonly asked questions
about OS/2 Warp Server Backup/Restore.
A more comprehensive and up-to-date set of frequently asked questions and their
answers is available on:
http://www.software.ibm.com/os/warp/library/backfaq/index.html
Commonly used terms - what do they all mean?
How do I install support for new Storage Devices?
How do I find out what error occured during a failed backup?
How does OS/2 Warp Server Backup/Restore handle network access control
lists (ACLs)?
How does the program estimate how much time a backup will take?
How can I set up a weekly cycle of full system backups that uses the same
tape over and over?
How can I automatically stop an OS/2 program so its data can be backed
up?
What do I do if my tape drive is not detected?
What do I do if OS/2 Warp Server Backup/Restore cannot access a tape
drive?
How can I use OS/2 Warp Server Backup/Restore to control my DB/2 backups?
Performance hints and tips
ΓòÉΓòÉΓòÉ 4.1. Commonly used terms - what do they all mean? ΓòÉΓòÉΓòÉ
What is a backup set?
What is a file filter?
What is a rule book?
ΓòÉΓòÉΓòÉ 4.1.1. What is a backup set? ΓòÉΓòÉΓòÉ
Data is backed up to backup sets. A backup set is a collection of data which
resides on a particular storage device (You may have several backup sets stored
on the same storage device). Physically it is the set of storage volumes to
which successive backups have been made. Logically it is the collection of
related files for which you create a particular backup strategy. A backup set
might be a set of tapes containing a complete system image for disaster
recovery purposes or the data relating to a particular project on diskette.
OS/2 Warp Server Backup/Restore manages these backups as a group, which means
that if you ever need to recover data, you just need to ask OS/2 Warp Server
Backup/Restore for the file you want. The program will know precisely where the
data was backed up and how to retrieve it.
Hint!
When you have finished working on a particular project you can ask OS/2 Warp
Server Backup/Restore to Transfer Out the project backup set.
ΓòÉΓòÉΓòÉ 4.1.2. What is a file filter? ΓòÉΓòÉΓòÉ
File filters allow you to define which files and folders to back up. These can
be defined in two ways:
Tree-based
Rule-based
Tree-based file filters
Tree-based file filters allow you to define a set of files and folders by
selecting these objects from a tree view of the directory structure. When you
create a new tree-based file filter the program scans your system and displays
its directory structure. (In fact you can restrict the scan to only certain
drives. For example, you may only want local drives to be scanned for backup.)
The display is like the tree view that you see when you open an OS/2 drive
icon. You can expand it to see sub directories and OS/2 Warp Server
Backup/Restore gives you a list of the files contained in each directory in a
separate window. You can then select files and folders by clicking with the
mouse and see the results of your selections at a glance. You may decide to
select only those files that belong to a particular project. You can then save
the file filter, give it an appropriate name, and use it when you create
backup methods for your project data.
Rule-based file filters
Rule-based file filters offer a more powerful way of defining a set of files
and folders for backup. In this case you write a series of rules that
determine whether a given file is included or excluded from the set. The rules
take the form of wildcard templates. For example, if you want to include all
the files in the OS2 directory and the config.sys file you would define rules
as follows:
include *:\OS2\* \*
include *:\CONFIG.SYS
exclude - any files not matched above
When OS/2 Warp Server Backup/Restore scans your system it compares each file
and folder name with the rules in your file filter starting with the first one
and working down. As soon as it finds a match it uses the rule to determine
whether to include or exclude the file. Just as with tree-based file filters
you can save the filter and use it when you create backup methods.
Converting Tree-based file filters into Rule-based ones
Once you have created a tree-based file filter you can convert it into a
rule-based one by selecting File filters from the Tools menu and opening the
pop-up menu for the file filter. Change type is one of the options. Any
tree-based filter can be converted to a rule based one but you may loose
information if you convert a rule-based file filter to a tree-based one.
ΓòÉΓòÉΓòÉ 4.1.3. What is a rule book? ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore allows you to choose how many generations of a
file you want to keep when you run successive backups. It also allows you to
choose whether a file should be compressed before it is stored on the backup
medium. You can choose a number of generations and whether to compress data
when you create a backup method. These choices are then applied to all files
selected.
Rulebooks provide a way of applying different policies to different sets of
files. A rule book is a series of rules very like a rule based file filter. An
example follows:
*:\*\*.zip - (2, No Compression)
*:\*\*.mpg - (2, No Compression)
When the program scans the system for backup it compares each file and folder
name with the rules in your rulebook starting with the first and working down.
If it finds a match it uses the rule to determine how many generations to keep
and whether to apply compression.
OS/2 Warp Server Backup/Restore provides a sample rule book called 'Don't
compress compressed files'. As the name suggests, this switches off compression
of files that have already been compressed by a standard compression algorithm.
You may want to create other rulebooks such as one that selects particular word
processing files and keeps them for more than the default number of
generations.
ΓòÉΓòÉΓòÉ 4.2. How do I install support for new Storage Devices? ΓòÉΓòÉΓòÉ
You can add support for new Storage Devices using the Control Panel. From the
OS/2 Warp Server Backup/Restore main window, select Tools, followed by Storage
Devices. In the Storage Devices container, press Mouse Button 2 to activate the
pop-up menu. Select New, followed by the kind of Storage Device you want to
add. Fill in or select the appropriate values and then select OK.
ΓòÉΓòÉΓòÉ 4.3. How do I find out what error occured during a failed backup? ΓòÉΓòÉΓòÉ
The backup log contains a complete history of the events which occur during a
backup. You can edit the log and see any error or warning messages that
occurred while the backup was running.
To do this, open Backup Sets container by selecting Backup Sets from the Tools
pull-down menu on the OS/2 Warp Server Backup/Restore main window. In the
Backup Sets container, click Mouse Button 2 on the Backup Set you were backing
up to, and select View log.
ΓòÉΓòÉΓòÉ 4.4. How does OS/2 Warp Server Backup/Restore handle network access control lists (ACLs)? ΓòÉΓòÉΓòÉ
OS/2 LAN Server stores its user account database in a file called NET.ACC in
the \IBMLAN\ACCOUNTS directory. Access Control Lists for directories and files
on FAT or JFS partitions are also stored in this file but those for directories
and files on a 386HPFS partition are stored in the file system itself. Since
this data is not contained in an ordinary file it has to be handled in a
special way. OS/2 Warp Server Backup/Restore manages this for you by invoking
two utilities that are supplied as part of LAN Server: BACKACC and RESTACC.
To enable backup and restore of ACLs simply select the check box on the ACLs
page of the control panel.
Backing up ACLs
Before you backup NET.ACC and ACL data on a 386HPFS system you need to:
1. Log on to the LAN domain controller as the administrator.
2. Run 'net use' to check that all the 386HPFS directory resources on the
domain controller and other additional servers are allocated a drive
letter. In other words, check that all the directories on the LAN whose
ACLs you want to backup appear as LAN alias drives on the domain
controller.
3. Open the Backup/Restore Source Drives container and ensure that all the
drives that represent 386HPFS resources appear in the Source drives
checked for backup section of the container.
4. Perform a backup of the \IBMLAN\ACCOUNTS\NET.ACC file. During this
operation a file called NET.ACC is created on the backup media which is
bigger than the original NET.ACC in the operational \IBMLAN\ACCOUNTS
subdirectory. This is normal. It is created by bundling together the
NETACC.BKP file, produced when the program runs the BACKACC utility,
along with ACL information for each of the defined LAN resources.
Note:
a. You will thus not normally see a file called NETACC.BKP when you
view data backed up to a storage media (You will only see this file
if you run BACKACC independently of OS/2 Warp Server Backup/Restore
or if you have run OS/2 Warp Server Backup/Restore to restore
NET.ACC without renaming the NETACC.BKP file that is created to
NET.ACC. Its presence on the backup media is not critical to the
restore process).
b. It is recommended that you check to ensure that the NET.ACC file
stored on the media is in fact bigger than the original.
Restoring ACLs
1. Log on to the domain controller as the LAN administrator.
2. Create a restore method called 'Restore net.acc' that selects the file
that the program calls NET.ACC from the backup set and restores it to its
original location in \IBMLAN\ACCOUNTS.
3. Ensure that all the 386HPFS directory resources for which you want to
restore ACL information are associated with the same drive letter as they
were during the backup by performing NET USE commands.
4. Run the 'Restore net.acc' method. During this process the program
attempts to perform three steps:
a. It unbundles the file that it calls NET.ACC to reveal the NETACC.BKP
file and the ACL information in the original \IBMLAN\ACCOUNTS
directory.
b. It tries to copy the NETACC.BKP file over the current NET.ACC,
however this does not succeed when it is running normally because
the current NET.ACC is locked open by LAN Server. You see the
following message:
Backup/Restore Information. The restored user accounts database
is netacc.bkp. To replace your current user accounts database,
boot from diskette and copy netacc.bkp over net.acc. You should
then use Backup/Restore to restore net.acc again in order to
restore the Access Control Lists.
c. It propagates the ACLs through the file system by running RESTACC.
This works because LAN Server is currently running. However RESTACC
performs the propagation of ACLs in a way that is consistent with
the version of the user accounts data base (NET.ACC) that it can
currently see. This is still the unrestored one. If you have deleted
a user account since you took the backup, the ACL information that
RESTACC propagates may refer to a user account that doesn't exist in
the current NET.ACC. In this case, RESTACC will ignore these
references.
5. Reboot to a command line from startup diskettes and copy the NETACC.BKP
file over the NET.ACC file in \IBMLAN\ACCOUNTS.
6. Restart the system from the hard drive.
7. Run the 'Restore net.acc' restore method again. The program attempts the
same three steps as before.
8. It unbundles the file that it calls NET.ACC to reveal the NETACC.BKP file
and the ACL information in the original \IBMLAN\ACCOUNTS directory.
9. It attempts to copy the NETACC.BKP file over the current NET.ACC. This
fails for the same reason as before but this time the failure doesn't
matter because the NETACC.BKP and \IBMLAN\ACCOUNTS\NET.ACC files are now
identical (You just copied one over the other manually).
10. It propagates the ACLs through the file system by running RESTACC. This
time the propagation is consistent with the restored user accounts
database.
How restore works during disaster recovery
When you restore your entire system in disaster recovery mode, the program
performs the same steps as before:
1. It unbundles the file that it calls NET.ACC to reveal the NETACC.BKP file
and the ACL information in the original \IBMLAN\ACCOUNTS directory.
2. It copies the NETACC.BKP file over the current NET.ACC. This works
because LAN Server has not yet locked open the NET.ACC file.
3. It attempts to propagate the ACLs through the file system by running
RESTACC. This fails because LAN Server is not available and RESTACC
cannot run.
4. When you have booted your system successfully, you must run the 'Restore
net.acc' method to complete the recovery. This propagates the restored
ACLs.
ΓòÉΓòÉΓòÉ 4.5. How does the program estimate how much time a backup will take? ΓòÉΓòÉΓòÉ
To estimate how much time a backup will take, the program uses information
about elapsed time for previous backups. A weighted-average bytes per second is
calculated based on earlier backups which used the same Storage Device. This
calculated transfer rate is then applied to the currently requested backup.
ΓòÉΓòÉΓòÉ 4.6. How can I set up a weekly cycle of full system backups that uses the same tape over and over? ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore never knowingly overwrites a backup. When it
performs successive backups to the same backup set it appends the data to that
of the last backup. If your backups are large, a tape may fill after only a
few repeated backups. This may be inconvenient.
If you want to force the program to write over and over to the same tape you
can use the following procedure.
This assumes that a full backup followed by a week of incremental backups will
fit on to one tape and that you have two tapes that are to be used for
alternate weeks.
1. Create a backup set called 'Full'.
2. Create a backup method that selects all the files on your system and
performs an incremental backup to the 'Full' backup set.
3. Create a tape volume for the 'Full' backup set using the Create new
volume option. This will be called 'Full -1'.
4. Schedule the method to run every night and leave the tape in the drive
for the whole week. The first backup will be a complete one. Subsequent
ones will only select changed files.
5. On Monday morning:
a. Remove the tape
b. Empty the 'Full' backup set.
c. Select Tools and then Backup sets to open the backup set container.
d. Select the 'Full' backup set and right click to see the menu of
options.
e. Select the Empty option. This deletes the index to the backups but
not the data itself. If you later want to restore data from the
'Full' backup set you will have to use the Transfer in option to
rebuild the index.
f. Insert a new tape in the drive and label it.
g. Select the Create new volume option from the menu of options for the
backup set.
6. Allow the second week's backups to run to this second tape. On the next
Monday, repeat the process of emptying the backup set, inserting the
first tape again and using the Create new volume option to label it.
Both tapes will be called 'Full-1' so you have to remember to swap them.
ΓòÉΓòÉΓòÉ 4.7. How can I automatically stop an OS/2 program so its data can be backed up? ΓòÉΓòÉΓòÉ
Using the Control Panel, you can name a command for OS/2 Warp Server
Backup/Restore that is executed before a backup begins and after a backup
finishes. Using this technique, it is possible to write, for instance, a REXX
program that shuts down the desired OS/2 systems, lets the backup run, then
re-activates the systems.
To do this, select Control Panel... from the Tools pull-down menu on the OS/2
Warp Server Backup/Restore main window. Then select User Exits from the
notebook tab, enable the Enable backup user exit and Enable restore user exit
check-boxes, and type in the names of the REXX programs you want to use.
Two example programs: BkpExit.CMD and RstExit.CMD are provided. You will find
these programs in OS/2 Warp Server Backup/Restore directory - usually PSNS.
ΓòÉΓòÉΓòÉ 4.8. What do I do if my tape drive is not detected? ΓòÉΓòÉΓòÉ
The tape drive auto-detection depends on an OS/2 device driver supplied with
OS/2 Warp Server Backup/Restore called ADSMSDID.SYS. It provides SCSI device
detection services to OS/2 Warp Server Backup/Restore.
The first time the program is run, or whenever you select Refresh from the
Storage Devices container, the program asks the driver to report any SCSI
devices present. It filters out any device which is not in the list of
supported devices, then checks to see if the device is already listed in the
Storage Devices container, and adds it if it is not.
If for any reason this is not loaded, the autodection will fail. At install
time, the following lines should have been added to CONFIG.SYS (assuming you
installed to C:\PSNS):
DEVICE=C:\PSNS\ADSMTAPE.SYS
DEVICE=C:\PSNS\ADSMSDID.SYS
If this has not happened, or if you have not rebooted since you installed, or
if the file C:\PSNS\ADSMSDID.SYS is not present, the driver will not be loaded.
In the former two cases, you can add the above lines to CONFIG.SYS manually and
reboot. In the latter case, you will have to reinstall OS/2 Warp Server
Backup/Restore and reboot. Before you do this however, read on.
The second reason why auto-detection might fail is that your drive is simply
not supported. This is not as obvious as it seems because many drives are just
rebadged versions of other manufacturers drives, and so will report a name
different from the one on the box.
All is not lost if the above prescriptions fail to get your tape drive
recognised - you can always configure a new Storage Device manually. To do
this, you need to find the logical unit number of your SCSI adapter, and the
physical unit number of the tape drive. These can often be found by using the
'System Information Tool' found in the 'System Setup' folder off 'OS/2 System'.
Selecting New and SCSI tape drive from the Storage Devices container will bring
up a settings panel with fields for the adpater number and unit number of the
tape drive. After you press OK on the panel, the program will attempt to access
the device in order to query its name. If the device fails to open at this
stage, it will fail to open for backup or restore, and so the configuration
will not be accepted. If this happens and you are sure that you have the
correct configuration, see What do I do if OS/2 Warp Server Backup/Restore
cannot access a tape drive?.
Note: The above procedure may allow you to install a tape drive not officially
supported. If this happens, there is a chance that you will be able to use it
successfully because SCSI support is largely standardized, but we cannot
guarantee that there will be no problems.
ΓòÉΓòÉΓòÉ 4.9. What do I do if OS/2 Warp Server Backup/Restore cannot access a tape drive? ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore uses the OS/2 device driver ADSMTAPE.SYS (which
should be installed along with the rest of the application) to communicate with
tape drives. It in turn uses the general SCSI services provided by OS2SCSI.DMD,
which will use the adapter driver that goes with your SCSI adapter:
IBM2SCSI.ADD for example. You need to check that all these pieces are in place,
and also that there is a file called DEVSTAPE.DLL in the same directory as
PSNS.EXE.
If all these files are present, and OS/2 Warp Server Backup/Restore has the
correct configuration for the device, and it is a supported device, then it
should be recognized by OS/2 Warp Server Backup/Restore.
In testing we have found that the following steps should allow your tape drive
to be detected:
1. Check that OS/2 is successfully communicating with the tape drive by
checking its status in the OS/2 System Information Tool.
2. Remove any other tape device drivers installed in CONFIG.SYS
3. If you are sharing devices on the SCSI Adapter, try re-ordering them -
sometimes other devices will conflict with the detection calls.
ΓòÉΓòÉΓòÉ 4.10. How can I use OS/2 Warp Server Backup/Restore to control my DB/2 backups? ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore is supplied with a sample user exit program
DbExit.CMD, which will create a backup of the DB/2 Sample database in a
directory below C:\DBBACK. To back up the database, take the following steps.
1. Create a Backup method called Database which backs up all subdirectories
below C:\DBBACK.
2. From the Control Panel, enable the Enable backup user exit check-box, and
type DbExit in the entry field.
3. Run the Backup method.
When the Backup method is run, the user exit will create a file containing a
snapshot of the database, OS/2 Warp Server Backup/Restore will back up that
file, and the user exit will then delete it.
ΓòÉΓòÉΓòÉ 4.11. Performance hints and tips ΓòÉΓòÉΓòÉ
This section contains performance related information about the following:
Installation
Improving the performance of scheduled backups
What data rate can I expect when backing up to tape?
What data rate can I expect when backing up to ADSM?
What is the maximum amount of data that OS/2 Warp Server Backup/Restore
can handle in a single backup?
ΓòÉΓòÉΓòÉ 4.11.1. Installation ΓòÉΓòÉΓòÉ
You should install OS/2 Warp Server Backup/Restore on an JFS or HPFS partition.
OS/2 Warp Server Backup/Restore builds an index to your backed up data which
consists of many small files. These are stored beneath the directory in which
you installed OS/2 Warp Server Backup/Restore. Index searches will be very slow
if this directory is on a FAT partition.
If you backup data to a hard disk make sure that it is a JFS or HPFS partition.
The backed up data is stored as many small files and accessing these will be
slow if they are on a FAT partition.
ΓòÉΓòÉΓòÉ 4.11.2. Improving the performance of scheduled backups ΓòÉΓòÉΓòÉ
Scheduled backups run as background tasks. You can increase the priority of
these by changing the setting in the control panel (TOOLS->CONTROL
PANEL->PRIORITIES). Obviously the performance depends on which other processes
are running on your system during the backup. If performance is relatively poor
even with the priority of the automatic backups set to 'high', you may want to
use a system monitor to see which processes are competing for use of resources.
As a last resort try giving the focus to the OS/2 Warp Server Backup/Restore
window when a backup is due to run and leave the monitor switched on.
ΓòÉΓòÉΓòÉ 4.11.3. What data rate can I expect when backing up to tape? ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore writes data to tape at 15 MB/minute, provided
the particular drive is capable of accepting data at this rate. (The majority
of tape drives are actually able to sustain significantly higher rates.)
ΓòÉΓòÉΓòÉ 4.11.4. What data rate can I expect when backing up to ADSM? ΓòÉΓòÉΓòÉ
The data rate when backing up to ADSM depends on several variables; the speed
of the network, the network protocol used and the configuration of the ADSM
server. The maximum data rate that can be achieved is 15 MB/minute. You should
talk to your ADSM server administrator if the rate you achieve is much lower
than this.
ΓòÉΓòÉΓòÉ 4.11.5. What is the maximum amount of data that OS/2 Warp Server Backup/Restore can handle in a single backup? ΓòÉΓòÉΓòÉ
The key to good overall performance is a well planned backup strategy. In most
situations, we recommend that no single backup set is used to backup more than
2GB of data or 50,000 files. You might have one backup set for your system
partition that you can use for recovering a bootable system in a disaster, and
additional backup sets for each logical group of data. Creating one backup set
for each drive is often a reasonable way of working.
You may create backup sets that contain considerably more data that 2GB if the
number of files is small. (The JFS file system allows applications to create
individual files that are larger than 2GB.) It is certainly sensible to backup
these extremely large files to a separate backup set. This way the very large
files will not distort the time required to back up sets of more normally sized
files.
The second tip is always to use backup methods with the 'changed files only'
option switched on. The first time the method runs it will backup all your
data. The second and subsequent times it runs, it will get only the small
number of changed files. This obviously minimises the amount of data that is
stored each time. If you are worried about the speed of restoring changed
files, you should consider using a Dual Device Backup Set. Even your disaster
recovery backups can be handled this way. When you perform a disaster recovery
restore OS/2 Warp Server Backup/Restore will automatically get the most recent
version of every file.
ΓòÉΓòÉΓòÉ 5. Storage Devices Supported by OS/2 Warp Server Backup/Restore ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore supports backup to the following Storage
Devices:
Tape Drives
Hard Disks
Removable Drives
Diskette Drives
LAN Alias Drives
Remote Drives
Optical Drives
IBM ADSTAR Distributed Storage Manager (ADSM)
ΓòÉΓòÉΓòÉ 5.1. Locally Attached Hard Disks ΓòÉΓòÉΓòÉ
Any hard disk that is locally attached to the machine and formatted for one of
the the supported file systems
ΓòÉΓòÉΓòÉ 5.2. Removable Drives ΓòÉΓòÉΓòÉ
Any removable drive that is locally attached to the machine, supported by the
installed version of OS/2 and formatted for one of the supported file systems.
This Storage Device allows Backup Sets to span more than one volume. Removable
drives may also be used with the Hard Disk Storage Device provided they are
supported as such by the installed version of OS/2; in this case a Backup Set
may not span more than one volume.
Note: In order to format a removable volume for HPFS or JFS the installed
version of OS/2 must include support for Partitioned Removable Media and the
drive must be included in that support.
ΓòÉΓòÉΓòÉ 5.3. Diskette Drives ΓòÉΓòÉΓòÉ
Any locally attached diskette drive supported by OS/2. Diskettes must be
formatted for the FAT file system.
ΓòÉΓòÉΓòÉ 5.4. LAN Alias Drives ΓòÉΓòÉΓòÉ
LAN Alias drives supported by OS/2 Warp Server, or any previous version of LAN
Server are supported.
ΓòÉΓòÉΓòÉ 5.5. Remote Drives ΓòÉΓòÉΓòÉ
Remote drives available by drive letter are supported. They must be compatible
with the FAT file system.
ΓòÉΓòÉΓòÉ 5.6. Read/Write Optical Drives ΓòÉΓòÉΓòÉ
Any read/write optical drive supported by the installed version of OS/2 can be
used. The optical disk must be formatted for one of the supported file systems.
ΓòÉΓòÉΓòÉ 5.7. IBM IBM ADSTAR Distributed Storage Manager (ADSM) ΓòÉΓòÉΓòÉ
Support is included for storing backup data using the IBM IBM ADSTAR
Distributed Storage Manager (ADSM). ADSM is a complete client/server storage
management system that uses a central server to store data. The central server
can run on the same machine as OS/2 Warp Server Backup/Restore or on an
entirely different machine, such as an IBM System/390, IBM AS/400, or IBM
RiscSystem/6000.
ΓòÉΓòÉΓòÉ 5.8. Tape Drives ΓòÉΓòÉΓòÉ
The following locally attached tape drives are supported:
Note: The OS/2 Warp Server Backup/Restore tape device driver only supports
SCSI II hardware.
8mm Tape Drives
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Device Name Γöé Supported Formats Γöé Estimated Capacity Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Andataco Encore 8205 Γöé 8200, 8200C Γöé 2.3 GB* Γöé
Γöé Andataco Encore 8505 Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Contemporary Cybernetics CY-8205 Γöé 8200, 8200C Γöé 2.3 GB* Γöé
Γöé Contemporary Cybernetics CY-8500 Γöé 8200, 8500 Γöé 5.0 GB Γöé
Γöé Contemporary Cybernetics CY-8505 Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Dynatek HSB 2300 Γöé 8200, 8200C Γöé 2.3 GB* Γöé
Γöé Dynatek HSB 5000 Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Dynatek HSB 10.0 Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Exabyte EXB-8200 Γöé 8200 Γöé 2.3 GB Γöé
Γöé Exabyte EXB-8205 Γöé 8200, 8200C Γöé 2.3 GB* Γöé
Γöé Exabyte EXB-8205XL Γöé 8200, 8200C Γöé 3.5 GB* Γöé
Γöé Exabyte EXB-8500 Γöé 8200, 8500 Γöé 5.0 GB Γöé
Γöé Exabyte EXB-8500C Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Exabyte EXB-8505 Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Exabyte EXB-8505XL Γöé 8200, 8200C, 8500, 8500C Γöé 7.0 GB* Γöé
Γöé Exabyte EXB-8700LT Γöé 8500, 8500c Γöé 7.0 GB* Γöé
Γöé Exabyte Eliant 820 Γöé Γöé 7.0 GB* Γöé
Γöé Exabyte Exb-8900 Γöé 8900 Γöé 20.0 GB* Γöé
Γöé IBM 3532-023 Γöé 8200 Γöé 2.3 GB Γöé
Γöé IBM 3445-001 Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* Γöé
Γöé IBM 76H0485 Γöé 8900 Γöé 20.0 GB* Γöé
Γöé Sun 8505XL Γöé 8200, 8200C, 8500, 8500C Γöé 7.0 GB* Γöé
Γöé Transitional Technologies, Inc. CTS-8000H Γöé 8500, 8500C Γöé 5.0 GB* Γöé
Γöé Transitional Technologies, Inc. CTS-8519H Γöé 8200, 8200C, 8500, 8500C Γöé 5.0 GB* ** Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
* Greater capacity might be achieved with compression
** OS/2 Warp Server Backup/Restore only supports mirrored mode operations.
4mm Tape Drives
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Device Name Γöé Supported Formats Γöé Estimated Capacity Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ADIC DATa 8000 Γöé DDS1, DDS1C Γöé 2.0 GB Γöé
Γöé ADIC DATa 8008 Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé ADIC DATa 8008i Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé ADIC DATa 8008E Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé ARCHIVE 4326NP/RP Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé ARCHIVE 4586NP/RP Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé ARCHIVE Python Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé Hewlett-Packard 35470A Γöé DDS1 Γöé 2.0 GB Γöé
Γöé Hewlett-Packard 35480A Γöé DDS1, DDS1C Γöé 2.0 GB* Γöé
Γöé Hewlett-Packard C1533A Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé Hewlett-Packard C1537A Γöé DDS3, DDS3C Γöé 12.0 GB* Γöé
Γöé Hewlett-Packard Jetstore 2000e Γöé DDS1 Γöé 2.0 GB Γöé
Γöé Hewlett-Packard Jetstore 5000e Γöé DDS1, DDS1C Γöé 2.0 GB* Γöé
Γöé Hewlett-Packard Jetstore 6000e Γöé DDS1, DDS1C Γöé 4.0 GB* Γöé
Γöé Hewlett-Packard SureStore DAT24e Γöé Γöé 12.0 GB* Γöé
Γöé Hewlett-Packard SureStore DAT24i Γöé Γöé 12.0 GB* Γöé
Γöé IBM 3440-001 Γöé DDS1, DDS1C Γöé 2.0 GB Γöé
Γöé IBM 4326NP/RP Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé IBM 4586NP/RP Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé IBM 3.5 Internal 4mm (74G8632/8191339) Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé IBM 5.25 Internal 4mm (74G8631/8191359) Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé IBM 12/24 GB DDS3 4mm Γöé DDS2, DDS2C, DDS3, DDS3C Γöé 12.0 GB* Γöé
Γöé Seagate STD224000N 4mm Γöé DDS2, DDS2C, DDS3, DDS3C Γöé 12.0 GB* Γöé
Γöé Sony SDT-5000 Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
Γöé Sony SDT-7000 Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 8.0 GB* Γöé
Γöé Sony SDT-9000 Γöé DDS2, DDS2C, DDS3, DDS3C Γöé 12.0 GB* Γöé
Γöé WangDAT 3300DX Γöé DDS1, DDS2 Γöé 2.0 GB Γöé
Γöé WangDAT 3400DX Γöé DDS1, DDS1C, DDS2, DDS2C Γöé 4.0 GB* Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
* Greater capacity might be achieved with compression
QIC and Travan Tape Drives
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ-----------
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Device Name Γöé Supported Formats Γöé Estimated Capacity Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé HP SurestoreT4i Γöé TR-40, HP Colorado 5gb Γöé 4 GB* Γöé
Γöé IBM 3450-001 Γöé QIC120 QIC150 QIC525 QIC1000 Γöé 1.19 GB Γöé
Γöé IBM 10/20gb NS Γöé TR-5/NS20 Γöé 10 GB* Γöé
Γöé (01K1319) Γöé Γöé Γöé
Γöé Tecmar QT525ES Γöé QIC525 Γöé 525 MB Γöé
Γöé Tandberg 4100 Γöé QIC120 to QIC1000 Γöé 120MB - 1.2GB Γöé
Γöé Tandberg 4200 Γöé QIC120 to QIC1000 Γöé 120MB - 2.5GB Γöé
Γöé Tandberg 4222 Γöé QIC120 to QIC2GB Γöé 120MB - 5.0GB Γöé
Γöé Wangtek 5525ES Γöé QIC525 Γöé 525 MB Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
DLT Tape Drives
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Device Name Γöé Supported Formats Γöé Estimated Capacity Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ADIC DS9200 Γöé DLT10 DLT10C Γöé 10 GB* Γöé
Γöé ADIC DS9400 Γöé DLT10 DLT10C DLT20 DLT20C ** Γöé 20 GB* Γöé
Γöé DEC TZ87/TZ87N Γöé Γöé 10 GB* Γöé
Γöé DEC TZ88/TZ88N Γöé Γöé 20 GB* Γöé
Γöé IBM 20/40GB DLT Γöé DLT Tape IV Γöé 20 GB* Γöé
Γöé (01K1320) Γöé Γöé Γöé
Γöé IBM 35/70GB DLT Γöé DLT35, DLT35C ** Γöé 35 GB* Γöé
Γöé Quantum DLT-2000 Γöé DLT10 DLT10C Γöé 10 GB* Γöé
Γöé Quantum DLT-4000 Γöé DLT10 DLT10C DLT20 DLT20C ** Γöé 20 GB* Γöé
Γöé Quantum DLT-7000 Γöé DLT35, DLT35C ** Γöé 35 GB* Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
* Greater capacity might be achieved with compression
** DLT20, DLT20C, DLT35 and DLT35C formats can only be used with CompacTape IV cartridges.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
An Active Event is a Scheduled Event that will occur at the appointed time.
Contrast this with an Inactive Event.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
IBM ADSTAR Distributed Storage Manager (ADSM) is a client/server based storage
management system. It provides advanced functions for storage management - data
backup, restore, migration and archive. When OS/2 Warp Server Backup/Restore is
used with ADSM, data is sent to a central server rather than being stored on a
locally attached device. Once there, it is centrally managed and protected
along with an enterprise's other corporate data, regardless of whether it
originated on a personal computer, mid-range computer or mainframe.
ADSM clients and servers run on a wide range of popular machines, including
Apple, AT&T, DEC, HP, Microsoft, NEC, Novell, SCO, Siemens, Silicon Graphics,
SUN, and of course IBM.
ADSM is the first and only storage management product on the market today that
lets you backup your Lotus Notes servers online, incrementally down to the
individual note level. Similar features are available for storage management
of DB/2 and Oracle databases.
For more details about ADSM, refer to Upgrading to ADSM from Help on the OS/2
Warp Server Backup/Restore main menu.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
An Archive is a collection of data which has been saved for future reference or
for recovery purposes. You can use the Transfer Out function in OS/2 Warp
Server Backup/Restore to archive Backup Sets, allowing you to delete the
original files when you no longer need them.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore is able to play audio files when certain events
occur. Standard '.WAV' files are used, and you can replace them with your own
sounds.
To change the sounds available, select Sounds from the Tools on the OS/2 Warp
Server Backup/Restore main window.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The Backup Guide is a feature of OS/2 Warp Server Backup/Restore that leads you
through the steps of creating a Backup Strategy. Until you become familar with
navigating the OS/2 Warp Server Backup/Restore setup panels, we recommend that
you use the Backup Guide to establish your backup strategies.
To access the Backup Guide, from the OS/2 Warp Server Backup/Restore main
window, you can get to the Backup Guide by selecting Tools on the OS/2 Warp
Server Backup/Restore main window, then selecting Guides... and Backup
Guide....
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Backup Set is a logical collection of backed up files. OS/2 Warp Server
Backup/Restore manages these backups as a group, which means that if you ever
need to recover data, then you just need to ask OS/2 Warp Server Backup/Restore
for the file you want, and the program will know where the file resides
(diskette, tape, optical disk, LAN drive, and so on) and will restore it for
you.
We recommend that that you define a separate Backup Set for each project or
application, so that you can manage your backups independently and efficiently.
For example by asking OS/2 Warp Server Backup/Restore to Transfer Out a Backup
Set when a project has finished, you can remove the media used for the project
from the active collection of data that OS/2 Warp Server Backup/Restore
manages.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Backup Strategy consists of a set of Backup Methods scheduled to happen at
particular times.
By running different methods at different times it is possible to provide
appropriate protection for all of the activities that a PC is supporting.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A catastrophic failure (also referred to as a Disaster), is when a machine
suffers a failure such that it cannot be restarted. This usually means a
failure in the hard drive that contains the operating system.
OS/2 Warp Server Backup/Restore provides special functions called Disaster
Recovery that let you create backups specifically designed to recover from
catastrophes. These functions allow you to create bootable media that
understands how to access backed up data for the machine, independant of the
operating system configuration usually running on the machine.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The Context Menu of a container is a menu of actions which may be carried out
on the container and the objects within it.
To display a container's Context Menu click the right mouse button on part of
the container not occupied by another object, or press the Alt button when the
container has focus.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore compresses files as they are backed up so that
less space is used on the media.
The compression method used by OS/2 Warp Server Backup/Restore is a specially
developed version of the Arithmetic Coding algorithm.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Context Menu is a menu of actions which may be carried out on an object.
To display an object's Context Menu click the right mouse button on the object
icon, or select the object using the cursor keys and press Shift+F10.
Note: Clicking on an empty space in a container will bring up the Context Menu
for the container.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Container is an object which contains other objects. Some of the objects
found in containers in OS/2 Warp Server Backup/Restore are:
Backup Methods
Backup Sets
File Filters
Volumes
Sounds
To look at all the instances of a particular type of object you must open its
container either by selecting the icon on the Toolbar or by selecting the
appropriate item from the Tools menu.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
When OS/2 Warp Server Backup/Restore finds the <Default> item selected, it will
refer to the default you have set in the Control Panel.
Using defaults allows you to make changes which affect the way the whole of
OS/2 Warp Server Backup/Restore works. For example, if you make <Default> the
destination for your backups and the source for you restores, you can change
the default Backup Set in the Control Panel and all actions will start using
this new Backup Set.
<Default> can be used in the following objects:
Backup Methods
Restore Methods
Workplace Shell Backup Objects
Workplace Shell Restore Objects
Rulebooks
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The Details View of a container arranges all the objects into a single list
with the icon and name to the left and all relevant information in columns to
the right.
In OS/2 Warp Server Backup/Restore you can change the view of most containers
by selecting their Context Menu.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Storage Device is a functional unit into which data can be placed, in which
it can be retained, and from which it can be retrieved.
Storage Devices fall into two categories, those that have Removable Volumes,
(for example diskette and tape drives), and those that have Fixed Volumes (for
example local hard disks and LAN drives).
OS/2 Warp Server Backup/Restore supports a unique storage device called ADSM.
When using this device, OS/2 Warp Server Backup/Restore sends data across a
communications link to an IBM ADSTAR Distributed Storage Manager server. While
OS/2 Warp Server Backup/Restore treats this device as a single, Fixed Volume,
in actuality the ADSM server stores the data into a hierarchy of one or more
physical storage volumes, as defined by the central storage administrator.
For more details about ADSM, refer to Upgrading to ADSM from Help on the OS/2
Warp Server Backup/Restore main menu.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
If you choose to Drop an object from a Backup Set then all Generations of that
object will be deleted and it will not be available for restore.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Dual Device Backup Set is a Backup Set that uses different Storage Devices
for full and incremental backups.
For example, you could use a SCSI Tape Storage Device for full backups and a
Removable Drive Storage Device for incremental backups.
Consider using Dual Device Backup Sets for data collections where the same
relatively few files change between backups. Backups and most restores will be
performed efficiently to the smaller capacity, direct access media, while the
full backups to large capacity, sequential access media can be stored off-site.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Extended Attributes are additional information that the system or a program
associates with a file or folder. An Extended Attribute can be any format, for
example text, a bit map, or binary data.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
If you wish to use a Backup Set on a different machine, or you want to archive
the data it contains, you can Transfer Out the Backup Set. This will make the
Backup Set unavailable for backup on the current machine, and available to be
Transferred In on another machine (or back to the original machine).
Once a Backup Set has been Transferred In, the data in it can be restored, and
it can be used for further backups.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A File Pattern is a piece of text that matches one or more files. OS/2 Warp
Server Backup/Restore uses patterns in exactly the same way as the pattern used
on a DIR command under DOS or OS/2.
The default * will include all the objects in the directory you have selected.
To back up folder information, your File Pattern should match with the file "."
- therefore *.* will back up folder information, but FRED.* will not.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore supports backup to and from the following file
systems:
FAT
JFS
HPFS
386 HPFS
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Fixed Volumes are media which are not removed from the device that reads and
writes them. Examples of Fixed Volumes are hard disks and LAN aliases. Contrast
this with non-fixed volumes, called Removable Volumes.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Generation is one version of a backup copy of a file or folder. If there is
more than one Generation, the most recent version is the first Generation, the
second most recent is the second Generation, and so on.
When the number of Generations of a file or folder exceeds the maximum
specified, the oldest Generation is lost.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Guide is a panel or series of panels which allow you perform a common task in
a simple way. Guides are especially useful for setting up OS/2 Warp Server
Backup/Restore when you first start to use it.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
386 HPFS is an advanced version of the HPFS file system which is supplied with
OS/2 Warp Server. It is not compatible with the normal HPFS file system or with
the JFS file system as it includes extra information about access control. You
cannot access a drive which uses 386 HPFS with the normal HPFS file system.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
An Inactive Event is a Scheduled Event that will not occur at the appointed
time. Contrast this with an Active Event.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
An Incremental backup is a backup of files and folders which have been altered
since the previous backup. OS/2 Warp Server Backup/Restore compares each file
and folder with its previous backup to the same Backup Set. This ensures that
the Backup Set contains a consistent set of data.
Incremental backups save time and space, and should always be used when data is
being regularly backed up.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Backup Set Index Files are a set of files managed by OS/2 Warp Server
Backup/Restore which store information describing the files and folders which
have been backed up to a particular Backup Set. Keeping an Index allows OS/2
Warp Server Backup/Restore to provide full information about what is stored in
the Backup Set, making it easy to restore data.
The Index is an integral part of a Backup Set, and is backed up at the end of a
backup to the set, normally to the same location as the backups.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Log File is a record of operations which have been carried out on a Backup
Set. The following operations are recorded in the Log File:
Back up of files and folders
Restore of files and folders
Dropping of files and folders from the Archives
Each operation is individually time-stamped, and any errors are recorded and
explained.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Logical Drive Letters allow you to refer to disks on other machines using a
standard drive letter. For example, OS/2 Warp Server allows client machines to
access drives and directories on the Server as logical drives. OS/2 Warp Server
Backup/Restore supports backup both to and from these logical drives.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
When you carry out a Backup or Restore, OS/2 Warp Server Backup/Restore allows
you to preview the operation.
If you choose to preview, you will be presented with a tree view of all the
objects which are currently selected for backup and restore. It is also
possible to find out how much data is going to be processed and also how long
this is likely to take. The preview will also allow you to deselect particular
objects which you decide you don't really want to backup or restore.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Removable Volumes are media which can be removed from the device that reads and
writes them. Examples of removable volumes are diskettes, optical disks and
tapes. Contrast this with non-removable volumes, called Fixed Volumes.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Rules allow you to define an action on a set of files or folders. They are used
in Rule-based Filters to define which files and folders are included or
excluded from backup, and in Rulebooks to define how files and folders are
backed up.
A Rule uses wildcards to determine which files and folders they apply to. These
are extensions of the wildcards used in standard OS/2 commands such as DIR and
COPY which allow the wildcard to apply to directories as well as files. For
example, the OS/2 Warp Server Backup/Restore wildcard C:\*\*.EXE refers to all
files with extension .EXE on the C drive.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore allows you to automate your Backup Strategy by
defining a Schedule of Backup Events. A Backup Event is the execution of a
Backup Method at a particular time.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
OS/2 Warp Server Backup/Restore allows you to select objects in two ways:
From a list Click on the down arrow to the right of the list and select the
chosen item from this list.
By dragging objects To do this:
1. Open the objects' container by clicking on the button to the right of
the selection field.
2. Select the object and drag it onto the selection field using the right
hand mouse button.
This method allows you to create new objects and modify existing ones in the
normal way before making the selection.
Shortcut:
The selected object in the field can be edited directly by double clicking on
it.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Spin Buttons are a quick way to set the value of a numeric field using the
mouse. Click on the upwards arrow to increase the value or on the downwards
arrow to decrease it.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A template. is an object that you can use as a model to create additional
objects. When you drag a template you create another of the original object, as
though you were peeling one of the objects off a stack.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A container may be viewed in two ways:
Icon View This displays the only the object's name and icon. It is a very
compact way of displaying the objects.
Details View As well as showing the name and icon of an object this also
displays other details which are relevant to that object, for
example a description.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A Volume is an item of backup media, for example a diskette, hard disk, tape or
optical disk.
Removable Volumes (such as tape and diskette) can only contain data for a
single Backup Set, while Fixed Volumes (such as hard disk) can contain data for
multiple Backup Sets.