Oracle® DIVArchive

Local Delete User's Guide

Release 7.3

E64052-03

April 2016

Oracle DIVArchive Local Delete User's Guide, Release 7.3

E64052-03

Copyright © 2015, 2016, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Lou Bonaventura

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

List of Figures

Preface

- Audience

- Documentation Accessibility

- Conventions

1 System Overview

- ASAP Purge Mode (default)

- Delayed Purge Mode

- Setting the Watermark for Delayed Mode

- Setting Site Verification Criteria for Delayed Mode

- Sample Local Delete Workflow

2 Installation and Configuration

- Prerequisites for Installation

- Configuring Local Delete

- Configuring ASAP Purge Mode

- ASAP Configuration Parameters

- Configuring Delayed Purge Mode

- Delayed Purge Mode Configuration Parameters

- Running Local Delete Using the Batch File

- Installing or Uninstalling Local Delete as a Windows Service

3 Troubleshooting

A ASAP Mode (Default) Configuration File

B Delayed Mode Configuration File

List of Figures

- 1-1 Standard Local Delete Workflow

Preface

This guide describes the installation, configuration, and use of the Oracle DIVArchive Local Delete functionality for the Oracle DIVArchive 7.3 system.

Audience

This document guides System Administrators through Local Delete configuration, and users through Local Delete operational processes and functionality.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Emphasizes critical meaning.

italic

Emphasizes a term or variable.

monospace

Used for system screen output and system commands.

%DIVA_HOME%

The convention used for file paths or variables. The example shows the root path on the file system where DIVArchive is installed.

1 System Overview

Oracle DIVArchive Local Delete is an application that monitors Oracle DIVAnet objects and deletes the objects locally after they have been replicated to a remote DIVArchive site.

Note:
The system tracks all instances of an object that exist on all sites and prevents you from deleting the last instance of an object.

You can run Local Delete on demand using a batch file (see Running Local Delete Using the Batch File), or automatically as a Windows Service (see Installing or Uninstalling Local Delete as a Windows Service).

Local Delete operates in one of two modes:

- ASAP Purge Mode (default)

- Delayed Purge Mode

ASAP Purge Mode (default)

ASAP Mode deletes local objects immediately after they are copied to another DIVArchive site. The ASAP configuration file (lynxLocalDelete.conf.ASAP.ini) is similar to the legacy Local Delete configuration file (see Appendix A for the default configuration file).

To configure ASAP Mode, see Configuring ASAP Purge Mode.

Delayed Purge Mode

Delayed mode deletes content based on the storage space of the disk and site verification criteria. Local Delete purges objects in the order in which they were archived to the local site.

Delayed mode uses the configuration file lynxLocalDelete.conf.delayed.ini (see Appendix B for a sample configuration file).

Note:
Delayed Purge Mode can only monitor a single DIVArchive disk array. To purge from multiple arrays, you must run multiple instances of Local Delete.

To configure Delayed mode, see Configuring Delayed Purge Mode.

Setting the Watermark for Delayed Mode

You must set the high and low watermarks to specify how full the disk must be before Local Delete deletes content. 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).

See Site to Purge Configuration Parameters for more information on the watermark configuration file parameters.

Setting Site Verification Criteria for Delayed Mode

You can set verification criteria in the configuration file. The system only considers deleting an object if all of the criteria are true and the disk array has reached the high watermark. Since the utility deletes objects in the order in which they were archived, Local Delete might stop deleting (because it reaches the low watermark) before it deletes all objects that meet the criteria.

See Site Verification Criteria Configuration Parameters for more information on the site verification configuration file parameters.

Sample Local Delete Workflow

The sample Local Delete workflow in Figure 1-1 applies to both newly archived objects and previously archived objects.

Figure 1-1 Standard Local Delete Workflow

2 Installation and Configuration

- Prerequisites for Installation

- Configuring Local Delete

- Configuring ASAP Purge Mode

- Configuring Delayed Purge Mode

- Running Local Delete Using the Batch File

- Installing or Uninstalling Local Delete as a Windows Service

Prerequisites for Installation

To install Local Delete, upgrade all components of the DIVArchive System to the proper release.

- At least two (one local and one remote) DIVArchive Managers (release 6.5 or later) must be installed and properly configured.

- DIVAnet (release 6.5 or later) must be installed and properly configured to operate with at least two DIVArchive Managers.

- To run in Delayed mode, DIVAnet must be running release 7.3 or later.

Configuring Local Delete

You must complete the following steps before starting Local Delete.

1. Open the DIVAnet Configuration File (router.xml) and verify that it contains the following:
<message class=".DeleteInstanceMessage" messageProcessorClass=".SelectiveRoutingMessageProcessor" instance="instance"/>

2. Navigate to the directory containing the Local Delete configuration files (%DIVA_HOME%\Program\conf\lynxLocalDelete\).

3. Create a Local Delete configuration file. The format is different depending on the desired mode:

- Configuring ASAP Purge Mode

- Configuring Delayed Purge Mode

Configuring ASAP Purge Mode

1. Rename the lynxLocalDelete.conf.ASAP file to lynxLocalDelete.conf.

2. Open the lynxLocalDelete.conf file and enter the correct values for each of the configuration parameters (see ASAP Configuration Parameters).

Note:
The parameters and values for this mode are case-sensitive.

3. Restart the Local Delete service.

ASAP Configuration Parameters

The following table describes the lynxLocalDelete.conf.ASAP configuration parameters. See Appendix A for a sample configuration file.

ASAP Parameter

Description

Default Value

Required

DIVANET_IP=Address

Address is IP address used for the DIVAnet Access Gateway (AG) connection.

127.0.0.1

Yes

DIVANET_PORT=Num

Num is a positive integer, which indicates the Port used for the DIVAnet AG connection.

9500

Yes

DIVANET_USER_NAME=UserName

UserName is the username used for the DIVAnet AG connection.

admin

Yes

DIVANET_USER_PASSWORD=Password

Password is the password for the DIVAnet AG connection.

none

No

LOCAL_DIVARCHIVE_NAME=LocalName

LocalName is a string, which indicates the name of the Local Delete DIVArchive System used in the DIVAnet AG.

none

Yes

LYNX_DIVARCHIVE_NAME=DisRecName

DisRecName is a string, which indicates the name of the disaster recovery DIVArchive system used in the DIVAnet AG. Only one disaster recovery name may appear.

none

Yes

DIVANET_SYNC_DELAY=Num

Num is an integer (1 to MAX_VALUE), which is a hidden parameter that defines the delay in minutes for syncing site through DIVAnet.
DIVAnet needs time to synchronize its object instances information on the different DIVArchive sites. Until it does, DeleteInstance requests from Local Delete may be rejected.

To avoid this situation, Local Delete checks objects for the MODIFIED_SINCE value to verify that it is greater than the DIVANET_SYNC_DELAY parameter.

20

No

CHECK_START_TIME=
MM/DD/YYYY

MM/DD/YYYY is the date in US standard format. The application will check only those objects which were modified in the lynxDR system since that date.
If a -1 value is provided, the application will use its start time as the initial date.

If a 0 value is provided, the application will check all objects in system.

1/1/2000

Yes

CHECK_END_TIME=MM/DD/YYYY

MM/DD/YYYY is the date in US standard format. The application will check only those objects which were modified in the disaster recovery system before that date.

none

No

CHECK_INTERVAL=Minutes

Minutes is a positive integer, which indicates the interval (in minutes) between 2 consecutive Local Delete checks.

2

Yes

CATEGORY_TEMPLATE.#=Category

# is an integer, which starts at 1 and increments by 1 for each additional category template.
Category is a string. Wildcards (asterisks *) are allowed. To use all categories, provide only an asterisk (*) for the value.

The category template parameters create the Category List handled by the Local Delete workflow. Ensure the format is compatible with the getObjectDetailsList parameter.

Example: CATEGORY_TEMPLATE.1=News,Post,Movie*,Film?

*

Yes

LYNX_INSTANCES_COUNT=Num

Num is a positive integer, which indicates the number of object instances to be created on the disaster recovery systems before the local object instance is marked for deletion.

2

Yes

LOCAL_MEDIA_TYPE=Type

Type can be DISK or ALL, which defines the local instances to delete when content has been successfully replicated to the disaster recovery system.
DISK triggers the automatic deletion of disk-only local instances.

ALL triggers the automatic deletion of all local instances on both disk and tape.

DISK

Yes

DELETE_REQUEST_PRIORITY=Num

Num is an integer (1 to 100), which defines the priority used for delete requests.

50

No

SIMULATENEOUS_DELETE_OPERATIONS=Num

Num is an integer (1 to 10), which defines the maximum simultaneous delete operations allowed.

3

Yes

MAX_OBJECTS_PER_CYCLE=Num

Num is a positive integer, which indicates the maximum number of objects to check per cycle.

1000

No

EXCLUDE_MEDIA_TYPE=MediaType

MediaType is a string, which specifies a media type (Tape Group or Disk Array name).
If the object has an instance of the specified media type, the object will not be deleted.

none

No

Configuring Delayed Purge Mode

1. Rename the lynxLocalDelete.conf.delayed file to lynxLocalDelete.conf.

2. Open the lynxLocalDelete.conf file and enter the correct values for each of the configuration parameters (see Delayed Purge Mode Configuration Parameters).

Note:
The parameter names for this mode are not case-sensitive, but the values are case-sensitive.

3. Restart the Local Delete service.

Delayed Purge Mode Configuration Parameters

The following tables describe the lynxLocalDelete.conf.delayed configuration parameters. See Appendix B for a sample configuration file.

Top Level Configuration Parameters

Top Level Parameter

Description

Default Value

Required

PurgeMode=Mode

Mode can be ASAP or delayed, which indicates the purge mode in effect. Only one mode can be in effect at a time.

ASAP, but use delayed to select the Delayed Purge Mode.

No

DeleteRequestPriority=Num

Num is an integer (1 to 100), which indicates the DIVArchive delete request priority.

50

No

SimultaneousDeleteOperations
=Num

Num is an integer, which indicates the number of simultaneous deletes that can be processed by the application.

none

Yes

Site Verification Criteria Configuration Parameters

Site verification is optional. The parameters specify what to verify before purging. You can provide multiple criteria by creating criteria groups.

Note:
You can only specify one of the following per criteria group: media, numTapeInstance, or numInstances.

Creating a Criteria Group:

The criteria group number distinguishes one group of related parameters from another. For instance:

SiteToVerify.1.sitename=lynxDR
SiteToVerify.1.numTapeInstances=1

SiteToVerify.2.sitename=local
SiteToVerify.2.media=remoteArray

In the previous example, the SiteToVerify.1 parameters are in a criteria group, while the SiteToVerify.2 parameters are in another group. Local Delete will verify there is one tape instance on the disaster recovery site and one instance on a local array called remoteArray.

Site Verification Parameter

Description

Default Value

Required

SiteToVerify.#.sitename=Site

# is the criteria group number.
Site is a string, which indicates the DIVArchive sitename. This is DIVAnet sitename of a remote DIVA site or local to indicate the local site.

None

No

SiteToVerify.#.media=
MediaType

# is the criteria group number.
MediaType is a string. If specified, an instance with this media must be present on the site.

None

No

SiteToVerify.#.numTapeInstances=Num

# is the criteria group number.
Num is an integer (1 to 100). If specified, the site must contain at least this many tape instances of the object.

None

No

SiteToVerify.#.numInstances=Num

# is the criteria group number.
Num is an integer (1 to 100). If specified, the site must contain at least this many total instances of the object.

None

No

Site to Purge Configuration Parameters

You must specify the site name and array name to purge from. The site number distinguishes one group of related parameters from another. For DIVArchive 7.3, only one array may be monitored, therefore the site number would be 1 (for example SiteToPurge.1.sitename=local).

Site to Purge Parameter

Description

Default Value

Required

SiteToPurge.#.sitename=Site

# is the site number
Site is a string, which indicates the DIVAnet sitename of the local DIVArchive system.

none

Yes

SiteToPurge.#.watermarkedArrayName=ArrayName

# is the site number
ArrayName is a string, which indicates the name of the array to monitor and purge from.

none

Yes

SiteToPurge.#.highWatermark=Num

# is the site number
Num is an integer (1 to 100), which indicates the percentage an array must be full to start the purge process.

none

Yes

SiteToPurge.#.lowWatermark=Num

# is the site number
Num is an integer (1 to 100), which indicates the percentage an array must be full to stop a purge process that is already active.

none

Yes

Categories Configuration Parameters

Specifying categories is optional. This parameter specifies the categories of objects to consider for deletion. If not specified, the default is all categories.

Categories Parameter

Description

Default Value

Required

CategoryIncludeFilter.#
=Category

# is an integer, which starts at 1 and increments by 1 for each additional filter.
Category is a string. Any purged object must match one of these categories. Wildcards (asterisks *) are allowed.

All

Yes

DIVAnet Configuration Parameters

This information is required to connect to DIVAnet.

DIVAnet Parameter

Description

Default Value

Required

Divanet.address=Address

Address is the IP address of the DIVAnet server.

none

Yes

Divanet.port=Num

Num is a positive integer, which indicates the port of the DIVAnet server.

none

Yes

Divanet.user=UserName

UserName is the user name for the DIVAnet API connection.,

none

Yes

Divanet.password=Password

Password is the password for the DIVAnet API connection.

none

Yes

DIVAnet Database Configuration Parameters

This information is required to connect to the DIVAnet database.

DIVAnet Database Parameter

Description

Default Value

Required

DivanetDb.address=Address

Address is the IP address of the DIVAnet database.

none

Yes

DivanetDb.port=Num

Num is a positive integer, which indicates the port of the DIVAnet database.

1521

No

DivanetDb.user=UserName

UserName is the user name for the DIVAnet database.

none

Yes

DivanetDb.password=Password

Password is the password for the DIVAnet database.

none

Yes

DivanetDb.sid=Database_sid

Database_sid is the SID of the DIVAnet database.

lib5

No

Local DIVArchive Database Configuration Parameters

This information is required to connect to the local DIVArchive database.

Local DIVA Database Parameter

Description

Default Value

Required

LocalDivaDb.address=Address

Address is the IP address of the local DIVArchive database (the Manager database).

none

Yes

LocalDivaDb.port=Num

Num is a positive integer, which indicates the port of the local DIVArchive database.

1521

No

LocalDivaDb.user=UserName

UserName is the user name for the local DIVArchive database.

none

Yes

LocalDivaDb.password=Password

Password is the password for the local DIVArchive database.

none

Yes

LocalDivaDb.sid=Database_sid

Database_sid is the SID of the local DIVArchive database.

lib5

No

Running Local Delete Using the Batch File

Note:
The Windows command line console must remain open while Local Delete is running. Closing the window will stop Local Delete.

1. Open a Windows Command prompt (Click Start, and then Run, then enter cmd).

2. Change to the following folder:
cd %DIVA_HOME%\Program\Utilities\bin

3. Execute the batch file without any command line parameters to start Local Delete.
lynxLocalDelete.bat

4. If you see Local Delete Utility is running, the module started successfully.

Installing or Uninstalling Local Delete as a Windows Service

Oracle recommends installing Local Delete as a Windows Service. lynxLocalDelete.bat supports the installation and uninstallation of the Local Delete service using the -i and -u options, respectively.

Note:
The Local Delete service will be installed using the configuration file found in the %DIVA_HOME%\conf\lynxlocaldelete\ folder.
If you use a configuration file other than the default, specify the file with the -conf or -f options.

1. Open a Windows Command prompt (Click Start, and then Run, then enter cmd).

2. Change to the following folder:
cd %DIVA_HOME%\Program\Utilities\bin

3. Execute the batch file with the -i option (to install) or -u option (to uninstall). For example, to install Local Delete as a service:
lynxLocalDelete.bat -i

3 Troubleshooting

Scenario

Description

Local Delete cannot connect to the DIVAnet AG on start up.

An error message will be written to the log file and a reconnection attempt will be made after the period specified in the Check_Interval parameter in configuration file.

Connection to DIVAnet AG is lost.

An error message will be written to the log file and a reconnection attempt will be made after the period specified in the Check_Interval parameter in configuration file.

DIVAnet returns a DIVA_ERROR as a response to a getObjectDetailsList request.

The error is logged and the current processing cycle is interrupted by Local Delete. After the configured amount of time specified in the Check_Interval parameter in configuration file has passed, a new processing cycle is started using the initialTime parameter value for the last cleaned object (this time is stored in a separate file each time when an object is cleaned).

Delete request failed.

Local Delete will wait for the delete operation to finish. In case the delete request fails, the error will be logged and Local Delete will not attempt to retry the failed delete request.

Power Failure, Operational System Crash, and so on.

The customer is responsible for configuring the Windows Scheduled Task for Local Delete that will restart the application.

Local Delete cannot read from, or write to, the file that stores the creation date of last cleaned object.

The error is logged and Local Delete will periodically try to repeat the IO operation.

Limitation: Only one instance of Local Delete can be run at a time in ASAP Mode.

Only one instance of Local Delete can be run in ASAP Mode. It is possible to run multiple Local Delete instances in Delayed Purge Mode if unique Windows Services names are provided. The customer is responsible for following these limitations.

The configuration file is not accessible.

The error is logged and Local Delete is stopped.

The configuration file is not valid.

The error is logged and Local Delete is stopped.

A ASAP Mode (Default) Configuration File

# Name for Local Delete Windows Service
LYNX_SERVICE_NAME=

# DIVAnet AG IP address
DIVANET_IP=127.0.0.1

# DIVAnet AG port
DIVANET_PORT=9500

# DIVAnet AG user name
DIVANET_USER_NAME=admin

# DIVAnet AG user password
DIVANET_USER_PASSWORD=diva

# Local DIVArchive Name
LOCAL_DIVARCHIVE_NAME=diva_local

# LYNXdr DIVArchive Name
LYNX_DIVARCHIVE_NAME.1=diva_lynxDr_1

# This parameter defines delay in minutes. It ensures that LYNX
# Local Delete will always check for objects modified at least
# DIVANET_SYNC_DELAY minutes ago, so that DIVAnet will have time to
# update info about new objects instances in its database.
# WARNING: This parameter's value should always be greater then godlFetchThreshold parameter value from DIVAnet configuration.
DIVANET_SYNC_DELAY=20

# Start Time for checking. Date in US format: MM/DD/YYYY
# DEFAULT: 01/01/2000
# PLEASE NOTE THAT ONCE STARTED, THIS PROPERTY WILL NOT BE APPLIED
# AGAIN
CHECK_START_TIME=01/01/2000

# End Time for checking. Date in US format: MM/DD/YYYY
# Empty for no End Time definition
# DEFAULT: empty
CHECK_END_TIME=

# Interval in minutes between two consecutive Local Delete
# checks. Actual interval may be larger than CHECK_INTERVAL since
# program will do check and deletes between intervals
CHECK_INTERVAL=1

# Category list handled by Local Delete workflow
# Should be in the format compatible with the getObjectDetailsList
# If you want allow all categories then use following template:
# CATEGORY_TEMPLATE.1=*
CATEGORY_TEMPLATE.1=lynx
CATEGORY_TEMPLATE.2=test*
CATEGORY_TEMPLATE.3=movies
CATEGORY_TEMPLATE.4=news

# Number of object instances to be created in LYNXdr before local
# object instances deletion
# Default: 2
LYNX_INSTANCES_COUNT=2

# Define which local instances to delete when content has been
# successfully replicated to LYNXdr
# "DISK" triggers the automatic deletion of disk-only local
# instances
# "ALL" triggers the automatic deletion of all local instance (disk
# & tape)
LOCAL_MEDIA_TYPE=ALL

# Priority used for delete requests.
# Default: 50
DELETE_REQUEST_PRIORITY=50

# Number of simultaneous deletes allowed
# Acceptable values: 1 – 10, Default: 3

SIMULTANEOUS_DELETE_OPERATIONS=3

#******************************************************************
#Wrapper Properties
#******************************************************************

# Java Application

wrapper.java.command=$JAVA_HOME/bin/java

# Java Main class.  This class must implement the WrapperListener
# interface or guarantee that the WrapperManager class is
# initialized.  Helper classes are provided to do this for you.
# See the Integration section of the documentation for details.

wrapper.java.mainclass=com.storagetek.diva.lynxLocalDelete.control.TanukiLauncher

# Java Classpath (include wrapper.jar)  Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../../../Program/Utilities/lib/*.jar

#Wrapper application parameters
wrapper.java.app.parameter.1=
wrapper.java.app.parameter.2=
wrapper.java.app.parameter.3=
wrapper.java.app.parameter.4=

# Java Library Path (location of Wrapper.DLL or libwrapper.so)

wrapper.java.library.path.1=.

# Java Additional Parameters

#wrapper.java.additional.1=

# Initial Java Heap Size (in MB)

wrapper.java.initmemory=256

# Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=256

# Application parameters.  Add parameters as needed starting from 1

#******************************************************************

# Wrapper Logging Properties

#******************************************************************

# Format of output for the console.  (See docs for formats)

wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)

wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.

wrapper.logfile=

# Format of output for the log file.  (See docs for formats)

wrapper.logfile.format=LPTM

# Log Level for log file output.  (See docs for log levels)

wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes.  The default value
# of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix.  For example: 10m = 10 megabytes.

wrapper.logfile.maxsize=10m

# Maximum number of rolled log files which will be allowed before
# old files are deleted.  The default value of 0 implies no limit.

wrapper.logfile.maxfiles=4

# Log Level for sys/event log output.  (See docs for log levels)

wrapper.syslog.loglevel=NONE

#******************************************************************
# Wrapper Windows Properties
#******************************************************************

# Title to use when running as a console

wrapper.console.title=DIVArchive LYNXLocalDelete

#******************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#******************************************************************

# WARNING - Do not modify any of these properties when an
# application using this configuration file has been installed as a
# service.
# Please uninstall the service before modifying this section.  The
# service can then be reinstalled.

# Name of the service

wrapper.ntservice.name=DivaLld

# Display name of the service

wrapper.ntservice.displayname=DIVArchive LYNXLocalDelete Service

# Description of the service

wrapper.ntservice.description=DIVArchive Lynx Local Delete provides cleaning service for local environment from objects which are stored on remote environments

# Service dependencies.  Add dependencies as needed starting from 1

wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START

wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.

wrapper.ntservice.interactive=false

B Delayed Mode Configuration File

# The parameters at the very bottom of the file are to control the
# service and logging. The parameters are set to their recommended
# values, and should not be changed without consulting an Oracle
# representative.
#
PurgeMode=delayed
DeleteRequestPriority=70
SimultaneousDeleteOperations=25

# 2. Site Verify Criteria (here, we must have 1 tape instance on
# the DR site, and one instance on a local array called
# "remoteArray".)
SiteToVerify.1.sitename=lynxDR
SiteToVerify.1.numTapeInstances=1
SiteToVerify.2.sitename=local
SiteToVerify.2.media=remoteArray

# 3. Site to Purge parameters:
SiteToPurge.1.sitename=local
SiteToPurge.1.watermarkedArrayName=localArray1
SiteToPurge.1.highWatermark=70
SiteToPurge.1.lowWatermark=50

# 4. Category Include Filter parameters:
CategoryIncludeFilter.1= MOVIE*
CategoryIncludeFilter.2= AVID

# 5. DIVAnet Access Gateway parameters:
Divanet.address=127.0.0.1
Divanet.port=9500
Divanet.username=diva
Divanet.password=diva

# 6. DIVAnet Database parameters:
DivanetDb.address=127.0.0.1
DivanetDb.port=1521
DivanetDb.user=diva
DivanetDb.password=diva
DivanetDb.sid=lib5

# 7. Local Database parameters:   (defaults to diva/lib5, with
# sid=lib5)
LocalDivaDb.address=168.45.34.23
LocalDivaDb.port=9000

#******************************************************************
# The rest of the parameters are to control the service and
# logging.
# These parameters are set to the recommended default values and
# should not be changed without consulting with a Front Porch
# Digital representative.
#
#******************************************************************

# Java Application
wrapper.java.command=$JAVA_HOME/bin/java

# Java Main class. This class must implement the WrapperListener
# interface or guarantee that the WrapperManager class is
# initialized. Helper classes are provided to do this for you. See
# the Integration section of the documentation for details.
wrapper.java.mainclass=com.storagetek.diva.lynxLocalDelete.control.TanukiLauncher

# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../../../Program/Utilities/lib/*.jar

#Wrapper application parameters
wrapper.java.app.parameter.1=
wrapper.java.app.parameter.2=
wrapper.java.app.parameter.3=
wrapper.java.app.parameter.4=

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=.

# Java Additional Parameters

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=256
#******************************************************************
# Wrapper Logging Properties
#******************************************************************

# Format of output for the console. (See docs for formats)
wrapper.console.format=PM

# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=

# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM

# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=10m

# Maximum number of rolled log files which will be allowed before
# old files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=4

# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE

#******************************************************************
# Wrapper Windows Properties
#******************************************************************
# Title to use when running as a console
wrapper.console.title=DIVArchive LYNXLocalDelete

#******************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#******************************************************************

# WARNING - Do not modify any of these properties when an
# application using this configuration file has been installed as a
# service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.

# Name of the service
wrapper.ntservice.name=DivaLld

# Display name of the service
wrapper.ntservice.displayname=DIVArchive LYNXLocalDelete Service

# Description of the service
wrapper.ntservice.description=DIVArchive Lynx Local Delete provides cleaning service for local environment from objects which are stored on remote environments

# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=

# Mode in which the service is installed. AUTO_START or
# DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.