Computer Associates BABWBN2900E20 Clients Agents Guide - Page 45

Snapshot and Direct I/O Support for UNIX, Snapshot and Direct I/O Descriptions - 11

Get Computer Associates BABWBN2900E20 - BRIGHTSTOR ARC BACKUP V9 CLIENT PDF manuals and user guides
UPC - 757943261059
View all Computer Associates BABWBN2900E20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

UNIX, Linux, and Mac OS X Client Agent Configuration Snapshot and Direct I/O Support for UNIX UNIX client agents support the Snapshot and Direct I/O features. To take advantage of these features, one of the following environments must exist on the machine running the UNIX client agent: Feature Snapshot Snapshot Direct I/O Direct I/O Platform Solaris HP-UX 11.0 Solaris HP-UX 11.0 Software Requirements UFS file system with the fssnap package installed (Solaris 8 and 9) or the advanced version of VxFS file system. Advanced version of VxFS file system or Online Journaling File System (JFS). UFS file system or VxFS file system. Advanced version of VxFS file system or Online JFS. Snapshot and Direct I/O Descriptions With Direct I/O, the client agent takes a snapshot on advanced versions of VxFS, Online JFS (HP-UX), and UFS with fssnap installed on Solaris. The client agent mounts the snapshot to a temporary directory created in the root volume, and then generates the snapshot backup. After the snapshot backup is complete, the client agent dismounts from the temporary directory and deletes the snapshot. To perform a snapshot backup, you must specify a snapshot buffer. A snapshot buffer is the disk space used to store the original data before it is overwritten in the snapped volume. Remember these considerations when using the snapshot buffer: ■ The snapshot buffer needs to be large enough to store all the data that changes in the snapped volume for the duration of the backup. If the snapshot buffer runs out of space, the snapshot becomes invalid and the backup fails. ■ The snapped volume and the snapshot buffer should not be on the same file system. ■ For better performance, the snapped volume and the snapshot buffer should be on separate physical disks. ■ For UFS on the Solaris platform (using fssnap), the snapshot buffer can be a file name, a directory name, or a raw partition. Chapter 3: Adding and Configuring the Client Agents 45

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
UNIX, Linux, and Mac OS X Client Agent Configuration
Chapter 3: Adding and Configuring the Client Agents
45
Snapshot and Direct I/O Support for UNIX
UNIX client agents support the Snapshot and Direct I/O features. To take
advantage of these features, one of the following environments must exist on
the machine running the UNIX client agent:
Feature
Platform
Software Requirements
Snapshot
Solaris
UFS file system with the fssnap package
installed (Solaris 8 and 9) or the advanced
version of VxFS file system.
Snapshot
HP-UX 11.0
Advanced version of VxFS file system or
Online Journaling File System (JFS).
Direct I/O
Solaris
UFS file system or VxFS file system.
Direct I/O
HP-UX 11.0
Advanced version of VxFS file system or
Online JFS.
Snapshot and Direct I/O Descriptions
With Direct I/O, the client agent takes a snapshot on advanced versions of VxFS,
Online JFS (HP-UX), and UFS with fssnap installed on Solaris. The client agent
mounts the snapshot to a temporary directory created in the root volume, and
then generates the snapshot backup. After the snapshot backup is complete, the
client agent dismounts from the temporary directory and deletes the snapshot.
To perform a snapshot backup, you must specify a snapshot buffer. A snapshot
buffer is the disk space used to store the original data before it is overwritten in
the snapped volume. Remember these considerations when using the snapshot
buffer:
■
The snapshot buffer needs to be large enough to store all the data that
changes in the snapped volume for the duration of the backup. If the
snapshot buffer runs out of space, the snapshot becomes invalid and the
backup fails.
■
The snapped volume and the snapshot buffer should not be on the same file
system.
■
For better performance, the snapped volume and the snapshot buffer should
be on separate physical disks.
■
For UFS on the Solaris platform (using fssnap), the snapshot buffer can be a
file name, a directory name, or a raw partition.