Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
Overview
The X9000 software snapshot feature allows you to capture a point-in-time copy of a file system or
directory. Snapshots are taken at the directory level. You can take snapshots of up to 1024 directories
per X9000 file system, and up to 1024 snapshots can be taken of each directory. An X9000 system
supports up to 255 file systems.
Although snapshots are managed at the directory level, they are implemented per file. The metadata
of a snapped file has pointers to all file system blocks referenced by the current version of the file, and
also has pointers to any blocks referenced by snapshots, including blocks that may no longer be part
of the current version of the file.
You can take snapshots of files created on X9000 File Serving Software 6.0 or later. Files created
under an earlier release cannot be snapped. However, old and new files can coexist in the same file
system.
Managing snapshots
Snapshot management includes the following steps:
•
Create snap trees for file systems or directories. Before taking snapshots of a file system or directory,
you must enable the directory tree for snapshots. An enabled directory tree is called a snap tree.
Snapshots snap all files, subdirectories, and files in subdirectories from the top of the snap tree
to the bottom. Snap trees cannot be nested. For example, if directory /ibfs1/dir1/dir2 is a
snap tree, you cannot later make directory /ibfs1/dir1 a separate snap tree.
•
Define snapshot schedules for snap trees. The schedule specifies the frequency for taking snapshots
(hourly, daily, weekly, monthly) and determines how many snapshots to retain on the system.
•
Create on demand snapshots as necessary.
•
Delete snapshots that are no longer needed.
•
Reclaim space previously used by snapshots that have been deleted. Deleting a snapshot does
not free the space that was occupied by the snapshot. To free the space, run a snapshot space
reclamation task. Two reclamation strategies are available:
◦
maxspace: frees space used by entire files or parts of files (individual blocks) that are no
longer referenced by any snapshots. This is the default.
◦
maxspeed: frees space used by entire files that are no longer referenced by any snapshots.
This method is faster than maxspace.
The amount of space reclaimed is also affected by the following:
◦
If all blocks in a snapshot are also referenced by other snapshots, there is no space to free
when the snapshot is deleted.
◦
If blocks are unique to the deleted snapshot, a snapshot space reclamation task can reclaim
the space used by those blocks.
◦
If a file is deleted but all blocks in the file are still referenced by snapshots, no space is
available to be freed. To reclaim all of the space used by a snapped file, first delete the file,
delete all snapshots referencing the file, and then run a snapshot space reclamation task.
◦
If a file is modified such that certain blocks referenced by the file are only in snapshots, and
those snapshots are then deleted, a snapshot space reclamation task can reclaim the space.
Space reclamation is an intensive file system task and should be run at a quiet time when possible.
Automating snapshot management
You can use the X9000 CLI and GUI to manage snapshots. To automate snapshot management, create
schedules to create and retain snapshots for each snap tree. Also create a space reclamation schedule
for each file system containing snap trees.
Overview
3
... Ce manuel est également adapté pour les modèles :
données dispositifs de traitement - HP IBRIX X9320 10GbE Performance Block (365.39 kb)
données dispositifs de traitement - HP IBRIX X9320 IB Performance Block (365.39 kb)
données dispositifs de traitement - HP StoreAll 8800 Storage Node (365.39 kb)
données dispositifs de traitement - HP StoreAll 9320 1GbE Storage Node Pair (365.39 kb)