IBM TotalStorage Network Attached Storage 300G, Справочник пользователя, Страница: 35 / 86

one-time events or regularly repeated events. You access the Persistent Storage
Manager in the Disks and Volumes task group found within the Windows 2000 for
Network Attached Storage user interface.
Once you create a persistent image, it appears as a directory on the original drive.
Each persistent image is mounted as a volume on the file system. Access rights
and permissions from the original drive are inherited by the persistent image.
Persistent images are used the same as read-only system drives. However, unlike
conventional drives, persistent images are static records of the content of the
originating drive at the time you created the persistent image. Persistent images are
retained following shutdown and reboot.
To set up a persistent image, click on Persistent Storage Manager. Detailed
descriptions and instructions for each of the control panels and topics are contained
in the online help. In general, here are some important points about persistent
images:
v
In the Persistent Storage Manager, you can
– Add persistent images
– Delete persistent images
– Schedule a persistent image independently of the backup and restore
functions.
– Set the persistent image to span multiple volumes.
– Customize persistent images on a per-drive basis. For instance, you could set
a persistent image for one drive to occur every hour, and for another drive to
occur only once a day.
– Change the properties of persistent images, such as start time, repetition rate,
the drive, and so on.
– Configure attributes of the persistent image system, such as maximum
number of persistent images (up to 250), cache-full warning threshold, cache
size, persistent image directory name, and so on.
– List the persistent images that have been taken, and then delete, configure, or
create new ones.
– Take an immediate persistent image.
v
Give end-users access to files in the persistent images. For example, this would
be helpful to a user who has accidentally corrupted a file and needs to get an
uncorrupted copy of that file.
v
As mentioned, you can take and keep a maximum of 250 persistent images.
These can be taken on local drives, or drives over a SAN that are logically local.
Note that on various panels, such as the Schedule New Persistent Image panel,
you will see a field, Keep the last: (number of persistent images) . The total
number of persistent images that you enter in these fields will not override the
maximum number of persistent images that you set in the Configuration panel.
For example, if your maximum number of persistent images is 10, and you enter
in numbers in other fields that add up to greater than 10, only 10 persistent
images will be taken.
v
You cannot take a persistent image of the maintenance drive. Hence, you will not
see it as a choice in the Schedule New Persistent Image Panel.
v
The first persistent image ever taken will take longer than succeeding persistent
images because the cache file will need to be created. After this a persistent
images directory is established and future persistent images take place quickly.
v
The warnings that are issued when the cache is approaching a full state are sent
to the system log. You will not see pop-up warnings.
Chapter 4. Advanced administrative functions
23