One other convenient option is to use Cloverleaf’s ability to “forward” msg data to an alternate outbound thread. This alternate outbound forward thread can be set up as a file protocol (or possibly an alternate destination ip address). We’ve used this in the past and it helps to keep things flowing through the engine when we have an extended downtime on a receiving system. When everything comes back up, we can take the file created by the “forward” thread and resend it through the original outbound thread.
The hcidbdump and SMAT utilities can become very problematic when reading/writing/sorting large files. The “forward” feature is available on more current versions of Cloverleaf.
