BackBox H4.00 User Manual

Configuration

57 BackBox H4.00 User Manual

EMS Extractors configuration

Each Guardian node where a BackBox virtual device is operating must run the EMS

Extractor program BBEXT as a permanent process.

BBEXT reads tape mounts messages from EMS events; forward them to the Domain

Manager. It also retries pending mount requests.

It regularly checks the MEDIACOM list of pending mounts to detect any new mount

missed if, for example, BBEXT was not running. This periodic check is executed every

failsafe-retry-interval.

When BBEXT receives a device busy reply (or similar error requiring quick retry), it

retries the load every busycheck-retry-interval seconds. The load is also attempted

when an unload EMS event is received.

When the max-busycheck-retries value is reached, the retries are executed only at

the failsafe timer.

When BBEXT receives a severe error in reply, it retries the load every failsafe-retry-

interval seconds.

The retries executed at failsafe timer stop when max-failsafe-retries is reached. A

new load attempt can only be manually executed, through the BackPak user

interface. Restarting BBEXT reset the loop of retries for all pending mounts.

BBEXT configuration file

BBEXT reads its configuration from its standard input file. The configuration file must

be updated by a text editor like TEDIT. The following XML syntax is expected:

<BACKBOX-EMS-EXT-CONFIG>

<awaitio-timeout>600</awaitio-timeout>

<max-failsafe-retries>-1</max-failsafe-retries>

<failsafe-retry-interval>600</failsafe-retry-interval>

<max-busycheck-retries>-1</max-busycheck-retries>

<busycheck-retry-interval>120</busycheck-retry-interval>

<BBSV-tcp-addr>127.0.0.1</BBSV-tcp-addr>

<BBSV-tcp-port>4561</BBSV-tcp-port>

<trace-on>0</trace-on>

<emsFilter>EMSFILT2</emsFilter>

<trace-file>BBEXTTRC</trace-file>

<name>=TCPIP^PROCESS^NAME</name>

</GuardianDefine>

</BACKBOX-EMS-EXT-CONFIG>