Running Backup Operations - IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

Implementation guide
Table of Contents

Advertisement

11.1 Running backup operations

To start backing up a file, directory, or the whole machine, use the incremental
command, which is the default option from the GUI. This command backs up all
new or changed files in your default client domain, or in the file systems specified
that are not excluded from backup operations.
An alternative backup command is the selective command (option Always
backup from the GUI). During a selective backup, Tivoli Storage Manager sends
copies of files to the server, regardless of whether they have changed since the
last backup. This might result in having more than one copy of the same file
version on the server. If that occurs, you might not have as many different file
copy versions on the server as you intended. Your version limit might consist of
identical files. To avoid that, you should normally use the incremental command
to back up only changed and new files. However, you could consider doing a
periodic selective backup operation to regroup all the files of one machine onto
one tape. This might be helpful if you are not collocating data, or as an
alternative to the backup set functionality. We recommend that the Tivoli Storage
Manager administrator defines appropriate collocation settings for the target
storage pools, so you do not need to run selective backups. Remember that the
backup set functionality usually performs this task more efficiently, as it is done
entirely within the server and without requiring resending of any client data to the
server.
You can also back up one or more volumes or RAW volumes as a single object
by using the backup image command. Image backups are much faster than full
file system backups. They also occupy less space on the Tivoli Storage Manager
server database since only one object entry is required to represent the whole
image. You can perform a static image backup, which unmounts and remounts
the volume as read-only to prevent applications from accessing it during the
backup process. If you do not want to remount the volume as read-only, you can
perform a dynamic image backup.
A set of files that are on different file spaces can also be backed up to one virtual
file space on the Tivoli Storage Manager server. The backup group command
allows you to create a consistent point-in-time backup of a group of files that is
managed as a single logical entity.
Journal-based backup is supported on Windows and AIX (at V5.3.3.0 and later)
clients. If the journal engine service is installed and running, then by default,
incremental backups will automatically perform journal-based backup on the
selected file systems that are monitored by the journal engine service.
328
IBM Tivoli Storage Manager Implementation Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Tivoli storage manager

Table of Contents