Terminología de caracterización y evaluación

Document

deletion When the retention period has expired, Archive Server allows the client to delete the document. The leading application must send the deletion request.

When the retention periods of documents have expired, documents can be deleted mainly to

• free storage space and thus to save costs,

• get rid of documents that might cause liability of the company.

In this case, the document has to be deleted as soon as possible after the retention period has expired. This case cannot be fulfilled immediately if the document is stored within a container like an ISO image, optical media, a Blob, a meta-document, or referenced by other objects (Single Instance Archiving).

The following retention independent settings can prevent deletion:

• Document deletion settings for the logical archive (see Document deletion on page 80) and

• The maintenance level of Archive Server (see “Setting the Operation Mode of Archive Server” on page 332).

Deletion process The deletion process has two aspects:

• Delete the document logically, that means: Delete the information on the

document from the archive database so that retrieval is not possible any longer.

Only the information that the document was deleted is kept. This step is executed as soon as the delete request arrives.

• Delete (= purge, remove) the document physically from the storage media. The time of this action depends on the storage method:

• Documents that are stored as single files can be deleted immediately.

• Documents that are stored in containers (ISO images, blobs, finalized and non-finalized IXW volumes) can be deleted physically only when the retention period of all documents in the container has expired and all documents are deleted logically. The Delete_Empty_Volumes job checks for such volumes and removes them if the underlying storage system does not prevent it.

For the concrete retention support of the storage system, refer to the Storage Release Notes.

Deletion

behavior The following lists the deletion behavior per pool type.

Deletion behavior per pool type ISO Images or Optical

Purging a document in an ISO image cannot be completed before all documents on the image have been deleted. Only after that, the ISO image file can be purged from the storage system.

Purging optical media can only be done by destroying the optical media after all documents on the media have been deleted. Whereas destroying refers to STORM.

Single Instance Archiving

Be careful when using single instance archiving (SIA) and retention periods; see also “Retention on Storage Systems” on page 72.

Example:

An email with an attachment is archived in 2005 with the retention period of 5 years. ISO images are used. The ISO image is stored as a file on the storage system with a retention period, which is the maximum of all documents in the ISO image. Assume the maximum is 2010.

Another email with the same attachment is archived in 2007 and retention period of 5 years.

The components cannot be deleted from Archive Server since they are belonging to a document with a proper retention. However, the image file on the storage system could be purged by tools of the storage system, as in 2010 the retention period of the ISO image expires.

5.1 Logical Archives

BLOB

Take care when using containers such as BLOBs. A BLOB has a retention which is the maximum retention of all documents within the BLOB.

Activating event-based for documents in a BLOB will lead to retention period of INFINITE for the whole BLOB on the storage system.

Single documents within a BLOB cannot be copied and nor be purged, BLOBs can only be copied or purged as a whole.

Purge process A document or component can be deleted after the retention of the document has expired or no retention has been applied.

The leading application can delete a single component or delete the document.

Deleting a document implies that all components are deleted and then the document itself. Due to the nature of storage, deletion cannot be handled within a transaction.

Purge process ISO, BLOB, WORM

Delete requests cannot be propagated to the storage system.

The document is deleted in Archive Server. The content remains on the storage system until all documents on the media or container have been deleted. The DELETE_EMPTY_VOLUMES job purges the container files on the storage system.

Single file pools

Delete requests for the components and documents initiate a synchronous purge request on the storage system.

The following error situation can arise:

Storage system reports an error when the document or component is to be deleted.

• For documents: The document information in Archive Server is deleted (as all component information is already deleted).

• For components: The component information in Archive Server is deleted.

Note: This is new for versions from 10.0 on. In former versions, the leading applications received an error message and the component information was not deleted.

The leading application gets a success message. In addition, an

administrative notification is sent. A job will regularly retry to purge the orphaned content on the storage system (version 9.7.0 or later).

If in doubt, contact OpenText Customer Support.

Purging content In single file archiving scenarios, the content on the storage system is purged during the delete command. Content on ISO images or optical WORMs cannot be purged, and an additional job is necessary to purge the content as soon as all content of the partition is deleted from Archive Server.

The purging capabilities depend on storage system and pool type. The following table lists the purge behavior depending on the pool type.

Table 5-4: Purging content

Pool Type Purge Content Destroy (overwrite)

Single File (VI) YES NO

ISO Not immediately

Use DELETE_EMPTY_-PARTITIONS job.

NO

DVDs have to be removed from the jukebox and destroyed.

Single File (FS) YES Destroy is propagated to the sto-rage system but not all stosto-rage systems will execute the destruc-tion.

Write

incre-mental (IXW) Not immediately Use DELETE_EMPTY_-PARTITIONS job.

Remove from jukebox and de-stroy.

Deletion on

backup media The deletion of documents, BLOBs and partitions is automatically propagated to backup volumes. Note that backup volumes must be online. The following table lists the deletion behavior depending on the pool type.

Table 5-5: Deletion on backup media

Pool Type Local backup Backup media (remote stand-by)

Single File (VI) Not supported Document delete requests and purge requests are asynchro-nously forwarded to the Remote Standby Server (SYNCHRO-NIZE_REPLICATES job).

ISO Call

DELETE_EMPTY_-VOLUMES job. Deletes all identical ISO images

Deletion of all identical ISO im-ages is automatically done by the SYNCHRONIZE_REPLICATES job.

Single File (FS) Not supported Document delete requests and purge requests are asynchro-nously forwarded to the Remote Standby Server (SYNCHRO-NIZE_REPLICATES job).

5.1 Logical Archives

Pool Type Local backup Backup media (remote stand-by)

Write

incre-mental (IXW) Call DELETE_EMPTY_-VOLUMES job. Deletes vo-lume and all backups of this volume

Deletion of all backups is auto-matically done by the SYN-CHRONIZE_REPLICATES job.

Note: If the document’s retention date has changed on the original server due to a migrate call, the new values are only held by Archive Server and not written to the ATTRIB.ATR file, which holds the technical metadata of the document. The ATTRIB.ATR file will only be updated if the document is updated, e.g., if a component is added on the original server or if the document is copied to a different volume.

As soon as the updated ATTRIB.ATR has been replicated to the Remote Standby Server, the new retention value will be known on the Remote Standby Server.