FAQ - ArcFM Geodatabase Replication - UncCopy vs BITS

Version 1


    What are the reasons to use UncCopy vs BITS when transferring updates to clients via ArcFM Geodatabase Replication?



    In general, we recommend customers use UncCopy with ArcFM Geodatabase Replication. BITS does have two notable advantages: Background Intelligent Transfer Service (BITS) is designed to only utilize "background" bandwidth for uploads and downloads, allowing other network operations to continue unhindered, and BITS is also capable of resuming file transfers after their failure without needing to resend anything.


    Despite this, we have seen multiple instances of BITS not utilizing all available bandwidth. BITS's criteria for selecting the "background" amount of bandwidth to use is outside of our software's control, and it can sometimes fail to recognize the full speed at which it can perform a transfer. This can result in a ten minute transfer when using a manual copy-paste or UncCopy instead taking upwards of two hours with BITS. In addition, BITS is a closed box for troubleshooting purposes, and a failure within BITS during a transfer can be very difficult to diagnose. Unless the network connection used by the field units to receive their geodatabase updates has very sporadic connectivity or requires other active transfers at the same time as ArcFM Geodatabase Replication's operations, such that BITS unique advantages are especially relevant to your organization, it is both easier and often more reliable to use the simpler UncCopy transfer method.