Backup support for data retention, Troubleshooting data retention – HP StoreAll Storage User Manual

Page 293

Advertising
background image

When a legal hold is applied to a file, the legal hold is not replicated on the target. If the file
on the target should have a legal hold, you will also need to set the legal hold on that file.

If a file has been replicated to a target and you then change the file's retention expiration
time with the ibrix_reten_adm -e command, the new expiration time is not replicated to
the target. If necessary, also change the file's retention expiration time on the target.

Backup support for data retention

The supported method for backing up and restoring WORM/retained files is to use NDMP with
DMA applications. Other backup methods will back up the file data, but will lose the retention
configuration.

Troubleshooting data retention

Limitation on remote replication of retention-enabled file systems

When there is a large I/O load on the source file system and the auto-commit period is set to a
lower value, the following errors will display in the CRR logs:

Partial transfer: ibrcfrworker returned error 23 (Partial transfer), which
can be expected in retention-enabled (WORM) environments when CRR cannot modify a
retained file on the target cluster, or in environments where the filters on the target cluster are
different from the source cluster.

Data stream error: ibrcfrworker returned error 12 (RERR_STREAMIO), which
can be expected in retention-enabled environments (WORM) when CRR cannot modify a
retained file on the target cluster.

To avoid these errors, set the auto-commit period to a higher value (the minimum value is five
minutes and the maximum value is one year).

Attempts to edit retained files can create empty files

It you attempt to edit a WORM file in the retained state, applications such as the vi editor will be
unable to edit the file, but can leave empty temp files on the file system.

Applications such as vi can appear to update WORM files

If you use an application such as vi to edit a WORM file that is not in the retained state, the file
will be modified, and it will be retained with the default retention period. This is the expected
behavior. The file modification occurs because the editor edits a temporary copy of the file, tries
to rename it to the real file, and when that fails, deletes the original file and then does the rename,
which succeeds (because unretained WORM files are allowed to be deleted).

Cannot enable data retention on a file system with a bad segment

Data retention must be set on all segments of a file system to ensure that all files can be managed
properly. File systems with bad segments cannot be enabled for data retention. If a file system has
a bad segment, evacuate or remove the segment first, and then enable the file system.

Timeout may occur when performing administrative tasks on WORM/Retained
files through the GUI

If, when performing administrative tasks on WORM/Retained files using the GUI, the task may
time out. If this occurs, retry the task using the ibrix_reten_adm command. If you do not retry the
task using the CLI, the GUI task will only be partially successful.

Backup support for data retention 293

Advertising