Enhance Archive & Cleanup to be multi-RT-single-HIS aware

Big Picture User Experience

Archive and Cleanup do work against the server configured as the Secondary Computer for the Archive service, even if the Secondary Computer is Hot for the Archive service.

Further, for Split Realtime systems, there needs to be a way to specify which system the JSH entry should launch these processes.

Background Research

The rts_cleanup.csc seems to look for the Primary Computer to execute the BLT against. This means if the Primary Computer is down, it is not possible to run cleanup. This also seems to be the case for rts_archive.csc. This means these jobs are not redundant.

For some customers, the RealTime and Historical/Archive services are on different systems (the reason being we have multiple RealTime systems pointing to a single Historical system), so they need to specify in JSH which system cleanup should run, otherwise it will look by default at its own system where there is no Archive service.

the real problem we are seeing is that rts_cleanup.csc cannot run properly if only the Archive Secondary Computer is up. It looks like the BLT cleanup can only be executed against the Archive Primary Computer’s BLTHost. If we run it against the Archive Secondary Computer (either by bringing down the Primary Computer or pointing it to the Secondary Computer with ‘-A’) we get an error and there is no record of cleanup running.

Detailed Description

To be confirmed.

As a SCADA administrator, I need archive to run against the hot Archive Service, regardless of which of the pair is HOT. I need this so that I do not have to fail over the Historical or Achive Service for the Archive and Cleanup processes to run.

As a SCADA administrator, I need to be able to specify the location of the output from the archive process.

Business Value

Customers with split systems need to be able to schedule archive correctly.

SQL infrastructure has evolved to where it is no longer the case that the archive device is only ever connected to one of the Historical nodes.

Target Version

ES24 or SP1

Customers System / Architecture

Size: Small, Med, Large and x-Large

Topology: Multi Site, Split system, and Custom Enterprise

Any Unique configuration to note?: Multiple RT to single HIS, but also the more regular topologies

Has this functionality been delivered before?: No