Add ability to honor archive list file locations when adding new server to PI HA Collective
When adding a new server to a PI HA Collective, all archive files selected to be included in the initialization are copied and registered with the new server in one defined location in collective manager. This can create more manual work for organizations who wish to have all servers have similar file structures. If the primary server has archive files registered across multiple locations, these locations should be honored and attempt to move files to these locations first, then if a drive is not available fall back to the default location.
This feature would be very helpful and would facilitate the synchro process of a secondary server in a collective.
Actually, we need to synchro the file in the main archive location, then unregister all the others, move them manually to their final destination on secondary, register all on primary and secondary