AEM_Version Purging Basics

 

The Purge Version tool is intended for purging the versions of a node or a hierarchy of nodes in your repository.

 Its primary purpose is to help you reduce the size of your repository by removing old versions of your nodes.

Overview

The Purge Versions tool is available in the Tools console under Versioning or directly at:

http://localhost:4502/etc/versioning/purge.html

Start Path

• An absolute path on which the purge must be done. 
• You can select the Start Path by clicking the repository tree navigator.

Recursive

• When purging data you can choose between performing the operation on one node or on a whole hierarchy by selecting Recursive. 
• In the last case the given path defines the root node of the hierarchy.

Maximum versions to keep

• The maximum number of versions to be kept for a node. 
• When these number exceeds this value, the oldest versions are purged.

Maximum version age

• The maximum age of the version of a node. 
• When the age of a version exceeds this value, it is purged.

Dry Run

• Because removing versions of your content is definite and can not be reverted without restoring a backup, 
• thePurge Versions tool provides a dry run mode that allows you to preview the purged versions. 
• To launch a dry run of the purge process, click Dry Run.

Purge

• Launch the purge of the versions on the node defined by the Start Path.

AEM_How to Purge Versions of a Web Site

Solution :

To purge versions of a web site, proceed as follows:

• Navigate to the  Tools console  http://localhost:4502/misccadmin#  and select Versioning and double-click Purge Versions.
• Set the start path of the content to be purged (e.g. /content/geometrixx-outdoors).

                     a. If you want to only purge the node defined by your path,                                   unselect Recursive.
                     b. If you want to purge the node defined by your path and its                              descendants select Recursive.

• Set the maximum number of versions (for each node) that you want to keep. Leave empty to not use this setting.
• Set the maximun version age in days (for each node) that you want to keep. Leave empty to not use this setting.
• Click Dry Run to preview what the purge process would do.
• Click Purge to launch the process.

Caution:
Purged nodes can not be reverted without restoring the repository. You should take care of your configuration, so we recommend you to always perform a dry run before purging.

AEM_interpretation of Version purging results

Analyzing the Console

The Dry Run and Purge processes list all the nodes that have been processed. During the process, a node can have one of the following status:

• ignore (not versionnable): the node does not support versioning and is ignored during the process.
• ignore (no version): the node does not have any version and is ignored during the process.
• retained: the node is not purged.
• purged: the node is purged.

Moreover the console provides useful information about the versions:

• V 1.0: the version number.
• V 1.0.1*: the star indicates that the version is the current one.
• Thu Mar 15 2012 08:37:32 GMT+0100: the date of the version.

In the above screenshot example:

• The Shirts versions are purged because their version age is greater than 2 days.
• The Tonga Fashions! versions are purged because their number of versions is greater than 5.