ibex backup during install

ibex backup is a slow part of the install, copying old installation to scratch area. Some of this may be related to zipping? Could this be better managed with an unzipped robocopied tree on the network that could be updated incrementally and then deploy would be quick as likely only a few changes. Ideally you;d want a 3 copy with source,destination,reference where reference is common original install. Adding all local changes to the instruent git and pushing that maybe, but we don;t have that for client etc. may just be we need to have periodically syncde robocopy as scheduled task for a quick later deploy.

Start by tracing the current IBEX install backup and deployment entry points, especially where the old installation is copied to the scratch area and where zipping occurs. Compare the proposed unzipped robocopy tree, incremental reference copy, and scheduled-sync alternatives; done means a chosen design measurably reduces backup and later deployment time without losing local changes.

Written by the indexing model from the issue text.