The DIVA Local Delete application monitors Oracle DIVAnet archived objects and deletes them only when various criteria have been met. Local Delete must be used with Oracle DIVAnet for proper operation.
See Appendix B Oracle DIVArchive options and licensing information.
You can run Local Delete on demand using a batch file (see Running Local Delete on Demand), or automatically as a Windows Service (see Installing Local Delete as a Service).
DIVA Local Delete is supported on 64-bit Microsoft Windows platforms and Oracle Linux 7 (x86_64, 64-bit) environments. Refer to the Linux installation instructions in the Oracle DIVArchive Installation and Configuration Guide in the Oracle DIVArchive Core Documentation library for Linux-specific directions concerning running DIVArchive components as services under Linux.
Local Delete enables two different types of delete operations:
Watermarked Disk Purge
Site Purge
Before objects can be deleted by Local Delete, they must meet the site verification criteria defined in the Local Delete configuration file. Each verification criteria is a constraint that must be met before objects are eligible for deletion. For example, you can create site verification criteria stating that an object must have one tape instance on a remote site before it can be deleted on the local site.
Watermarked Disk Purge deletes content from an DIVA-managed disk array when the disk reaches the high watermark. It only deletes content that fulfills the site verification criteria. Matching objects are deleted in the order they were archived on the site being purged, unless the purgeMostRecent flag is set. When deletes occur from the array, some matching objects may not be purged if the low watermark is reached before they can be processed.
Watermarked Disk Purge mode uses the configuration file lynxLocalDelete.conf.watermarked.ini (see Appendix A for a sample configuration file).
You must set the high and low watermarks to specify how full the disk must become before Local Delete deletes from a watermarked disk array. When the DIVArchive array becomes x% full (x being the high watermark), object instances are deleted from the array until the disk reaches y% full (y being the low watermark).
A Site Purge will delete all instances of a qualifying object on a particular site. It will begin to schedule deletes as soon as the site verification criteria has been fulfilled. Objects are deleted (by default) in the order they were archived on the site being purged.
As the user of Local Delete, suppose that you have a DIVAnet system with two sites, a local site and a remote site. You want to delete objects from the local site when they become archived to the remote site. To achieve this you can configure Local Delete in Site Purge mode and add site verification criteria for the remote site. The criteria is satisfied when the number of tape instances on the remote site becomes one or greater. The Local Delete configuration file for this would have the following parameters:
SiteToVerify.numSites=1 SiteToVerify.1.sitename=remote SiteToVerify.1.numTapeInstances=1 SiteToPurge.1.sitename=local SiteToPurge.1.purgeType=site