Having read a few of the stories on here about EDC running in spool mode, someones wrong actions and possible loss of transactions, it made me think.
It would be simple to setup a batch file and scheduler process or even use a program like rsync to essentially back up any .spl files on the master terminal (.spl files are only created on the master terminal.... right?) on a regular basis. Say once every 15 minutes. The process would only be triggered when Aloha was spooling and that is easy enough to test for.
It could all be accomplished with a batch file or with a little more work a vbs script.
Since the info on the spl file is encrypted would having an archive containing all the .spl files for a particular day backed up on the BOH be any violation of PCI-DSS rules. I would only keep these backups for a few days then automatically delete them.
It would be simple to setup a batch file and scheduler process or even use a program like rsync to essentially back up any .spl files on the master terminal (.spl files are only created on the master terminal.... right?) on a regular basis. Say once every 15 minutes. The process would only be triggered when Aloha was spooling and that is easy enough to test for.
It could all be accomplished with a batch file or with a little more work a vbs script.
Since the info on the spl file is encrypted would having an archive containing all the .spl files for a particular day backed up on the BOH be any violation of PCI-DSS rules. I would only keep these backups for a few days then automatically delete them.