...
Transmissions are compressed to aid speed. Data transmission uses the FTP protocol to move the files around.
| Note |
|---|
- PostgreSQL database Views are NOT replicated. We would suggest not using Views for live Layers in iShare. If you decide to use Views then you will need to manually recreate these on the External Server.
- PostgreSQL
additional - new database Schemas are NOT replicated. If you decide to
use additional schemas - create a new schema(s) then you will need to manually recreate these on the External Server.
- PostgreSQL entities should not contain 'error' or 'failure' as part of their name as this will cause an error in the replication.
- PostgreSQL entities should not have duplicate names such as "Streets" and "streets" as this will cause replication to fail.
- Prior to V5.6.2 the FTP Replicator could not handle zipped file size greater than 4GB. You will need to bear this in mind if you have a large database to replicate. If you are already using the FTP Replicator and this problem arises then please ask your Astun Consultant to provide you with the latest ReplicationPy.zip file which you can then extract over your existing files.
Other considerations are: - Replication should be scheduled at times when there are no other Workflow Jobs in progress, also avoiding potential server down times such as server backups.
- Make sure any new symbols created are included in the FTP Replicator File Lists to Check including the corresponding symbols.sym file see Symbols & Styling.
- FTP Replication may fail if the Internal and External Servers become out of sync - see FTP Replicator Sync Issues for details.
|
Typical situation
The typical situation where FTP Replication is to be used will be the iShare Maps installation at a council. All configuration changes and source data changes occur on an internal protected server to which the general public has no access. This would be considered the LOCAL location.
...
