Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

Storage Checkpoints also keep track of the block change information that enables
incremental database backup at the block level.
Storage Checkpoints are writable, and can be created, mounted, and removed.
Performance enhancements in maintaining Data Storage Checkpoints (Storage
Checkpoints that are complete images of the file system) makes using the Storage
Rollback feature easier and more efficient, therefore more viable for backing up
large databases.
Multi-Volume File System (MVS) Storage Checkpoint creation allows database
backups without having to shut down the database.
MVSs provide the ability to create and administer Storage Checkpoint allocation
policies. Storage Checkpoint allocation policies specify a list of volumes and the
order in which Storage Checkpoint data is allocated to them. These allocation
policies can be used to control where a Storage Checkpoint is created, allowing
for separating Storage Checkpoint metadata and data onto different volumes.
They can also be used to isolate data allocated to a Storage Checkpoint from the
primary file system, which can help prevent the Storage Checkpoint from
fragmenting space in the primary file system.
See “About Storage Checkpoints and Storage Rollback” on page 149.
About restoring file systems using Storage Checkpoints
Storage Checkpoints can be used by backup and restore applications to restore
either individual files or an entire file system. Restoring from Storage Checkpoints
can recover data from incorrectly modified files, but typically cannot be used to
recover from hardware damage or other file system integrity problems. File
restoration can be done using the fsckpt_restore(1M) command.
See the Veritas File System Administrator's Guide.
About quotas
VxFS supports quotas, which allocate per-user and per-group quotas and limit
the use of two principal resources: files and data blocks. You can assign quotas
for each of these resources.
Each quota consists of two limits for each resource:
■ The hard limit represents an absolute limit on data blocks or files. A user can
never exceed the hard limit under any circumstances.
■ The soft limit is lower than the hard limit and can be exceeded for a limited
amount of time. This allows users to temporarily exceed limits as long as they
fall under those limits before the allotted time expires.
Introducing Veritas Storage Foundation for Oracle
How Veritas File System works
36