Recommendations for network use
ORCA AVA works in a network mode with a central database and a decentralized database engine installed on each client. The engine loads the information from the central database to the client. On the client, the information is processed and then stored back in the central database.
All users need read and write permissions to the central data directory (Central Settings).
The network architecture and the data connection between client and server have a significant influence on the performance of the program. When working with ORCA AVA in network installations (client/server architecture), we recommend using secure data connections as a rule, e.g. company-internal permanent lines or VPN connections.
Please note the following basic information on the use of data connections and cloud services for remote data transfer.
VPN Connections
VPN (Virtual Private Network) refers to an encrypted connection via a data network, e.g. the Internet. You can find more information at: https://de.wikipedia.org/wiki/Virtual_Private_Network.
- Fast VPN connections ≥ 100 Mbit/s (e.g., also fast synchronous permanent line).
Using a 100 Mbit/s synchronous line (upload/download same speed), it should be possible to work with ORCA AVA without using additional network services for the data connection. Important: The connection must be fast at both locations.
- Slow VPN connections < 100 Mbit/s (e.g. DSL, LTE, UMTS)
As a rule, a VPN connection <100 Mbit/s is too slow and unstable for working with ORCA AVA. The upload speed of a DSL connection is not sufficiently performant for working in the database. Delays in saving data make it impossible to work smoothly. Timeouts can lead to program crashes.
We therefore do not recommend this type of VPN connection!
Remote Desktop (RDP)
For slow data connections, performance can be improved by using network services. A popular service is RDP (Remote Desktop Protocol) on clients or RDS (Remote Desktop Services) on servers, e.g. Microsoft Remote Desktop/App. RDP/RDS reduce the amount of data to be exchanged: Instead of sending whole files, only screen and control signals are transmitted.
More information can be found at: https://de.wikipedia.org/wiki/Remote_Desktop_Protocol
ORCA realizes via VPN connections with RDP or RDS e.g. the work with ORCA AVA for employees in remote offices. Many of our customers also use RDP/RDS, e.g. to connect construction site offices to their company network. RDP is integrated into Windows operating systems by default.
Other remote control programs are also feasible for this scenario, e.g. TeamViewer, or PCAnywhere.
Cloud Computing - IaaS / SaaS
For editing, files must NOT be in a cloud (OneDrive, Dropbox, ...). Clouds are only suitable as a storage location for data backups.
In cloud computing, infrastructure such as processing power or software is no longer purchased in the traditional way, but provided by a service provider 'on demand'. The user pays for the use of the services provided: SaaS/IaaS - Software as a Service / Infrastructure as a Service.
For more information, please visit: https://de.wikipedia.org/wiki/Everything_as_a_Service.
In this scenario, both the ORCA software and the created data are stored on a cloud server. All clients at all locations access the cloud server and work directly on the server in the cloud. So no data is exchanged between server and client, only screen and control information.
Virus scanner
In network installations, virus scanners can greatly delay the launch of ORCA AVA. Also, the access to project files, which are stored on a server or a network resource, can be strongly slowed down or made impossible by virus scanners. Depending on local conditions in the network, a message may be issued by ORCA AVA, e.g. 3045 - access denied.
This behavior can also occur with a single-user installation if your data is located on a network directory.
Server settings
Depending on the software and configuration used, it may be necessary to set an exception for all directories on the server or network resource where clients read and write data with ORCA SOLUTIONS, e.g. C:\[share]\ORCA\***.
Such an exception can be e.g. the entry in an access list. Access to the file types *.MDB and *.AVA must also be allowed. Depending on the antivirus software used, it is possible to extract the affected directories from the log files as the cause of the delay.
Client settings
Whether further adjustments are necessary on client side (i.e. the workstation computers in the network) is best discussed with your IT or your administrator or with the support of your antivirus provider.
Real-time synchronization
A backup of your project files is not recommended while the application is running, because ORCA AVA needs exclusive access to its databases. At the moment of the backup, the backup software also needs exclusive access. Consequently, the functionality may be limited.
DFS replications
It is not recommended to use replication for ORCA AVA files. Databases often remain open for a long period of time while being accessed via a client. This prevents the files from being replicated by DFS replication because they have to be closed first. This can cause errors in network operations, depending on local conditions.
DFS namespaces can be used.
