This sounds like the Infor/Trend/SXE backup/AI management process.
Yes, it will still work. But there is no need to disable AI and, in reality, it's a kind of silly thing to be doing. Think about it. What's the point?
The whole point of after-imaging is to create logs that can be combined with previous backups to recreate a database that has somehow become corrupted or lost (perhaps because the building burned to the ground...) Routinely disabling and re-enabling AI does nothing to serve that purpose.
(There is a bug, now fixed, in some versions where you cannot roll forward extents whose sequence number is greater than 65535 -- but that's nearly 2 years of switching extents every 15 minutes.)
The most important question is -- where are those archived ai logs being kept?
The best answer is -- on a disk far, far away from the original database. Hopefully a disk in another building, preferably in another time zone.
The amount of time that passes between "rfutil dbname -C aimage new" and the copying of that extent to the offsite archive is the amount of data that you could lose in a catastrophe.
Backing up those extents on the same tape as a backup of the database kind of misses the point. If you've got a copy of the database what do you need the ai files for?
(There is a small amount of usefulness to those ai files -- the backed up db could be corrupt. But in the grand scheme of things that's far less likely than the backup not running because the server died -- and then you lose the backup and the ai files. There's also the "oops" programming mistake that deletes all your customers -- but you probably noticed that before the backup.)
