Backup > Offsite Servers
Use Offsite Replication to safely and securely transfer backup images from the LAN to a remote location. Typically all machines on a LAN have their Image Location set to store backup images on a LAN based file server. Designating that file server to be the Local Server tells the agent on that file server to push all new backup image data to an Offsite Server on a transfer schedule you define.
The offsite server listens on any TCP port you specify. The offsite server is always running and listening for connections from local servers. The TCP port may not already be in use on that machine.
Any machine ID may act as an offsite server. You may also have as many offsite servers as you like. Example Offsite Replication configurations include:
One global offsite server - a local server at each managed LAN pushes data to the global offsite server.
Multiple offsite servers - several local servers are assigned to each offsite server. Multiple offsite servers used for load balancing reasons.
Cross offsite server - Support offsite replication for companies with multiple locations. The backup data from one company site is offsited to a second company site. Backup data from the second company site is offsited back to the first site.
The offsite server stores data received from the local servers in the directory specified. Data from each individual local server is stored in a sub-directory named after the machine ID of the local server. The offsite server directory may be a UNC path pointing to a directory on a network file share. The offsite server must have a credential set in order to access the network. The following diagram illustrates a typical offsite server directory structure.
Offsite Server Path
localserver.company1
machine1.company1
machine2.company1
machine3.company1
localserver.company2
machine1.company2
machine2.company2
machine3.company2
localserver.company3
machine1.company3
machine2.company3
machine3.company3
NOTE: The Offsite Server requires a credential be set to operate correctly.
Only file changes are pushed to the offsite server. Interrupted file transfers are picked up where they left off the next time the local server component runs. Offsite replication uses the same communications technology used in the agent/server communications. All traffic is 256-bit encrypted. Broken file transfers are automatically restarted at the point the left off. Restarting the file transfer from the beginning is not required.
WARNING: You may assign the offsite server to be the same machine as the local server. This is NOT recommended but is allowed to support copying image data to secondary disk drives.