Insight to Data Synchronisation Introduction Replicating data accurately without any threat or interference between the Head Office

and its branches is the need of an organisation. This is achieved by using Synchronisation feature available in Tally.ERP 9. Data synchronisation is performed either by using Tally.NET a framework that works in the background or using Direct/IP Sync virtually creating a private network. While it is essential to configure client and server, data synchronisation happens at the click of a button. Insight to synchronisation is an elaborative document that comprehends the technical aspects of synchronisation. For an easy understanding we have broadly classified this document into the following categories. User Information Operating Information Precautions Technical Information Online help and Trouble Shooting User Information Synchronization is a process of replicating data between two or more computers using Tally.ERP 9 in a Client - Server environment. During synchronisation data is transferred from the client to the server and from the server to the client. Tally.ERP 9 offers control over the frequency of Synchronization, i.e., data can be replicated after each transaction or updated at specific intervals. Data can be sent over the Internet, or a private network system. Synchronization using Tally.NET Synchronization using Private Network / Direct and Server (IP) Sync@ Once Synchronization is set up at the Server and its Clients replicating data is a single-click activity. Synchronization using Tally.NET With a major Technological enhancement in Tally.ERP 9, data Synchronization is available through Tally.NET. In the current framework it is essential to connect to Tally.NET at the synchronisation server in order to synchronize data between Server and Client. Synchronization using Private Network / Direct and Server (IP) Sync From Tally.ERP 9 Direct Synchronisation/Synchronisation using Private network is available by default. This feature is also known as IP Sync. In Direct/IP Sync, data synchronization takes place between two or more computers in a Virtual Private Network. It is essential to provide the Synchronisation Server\'s IP Address in the Client Rule and the synchronisation server need not be connect to Tally.NET.

While the entire process of Synchronization using Tally.NET and Direct IP remains the same. The only differentiating factor between synchronising data using Tally.NET and Direct/IP Sync is the Account ID or the Serverfs IP Address and Port Number provided in the Client Rule. Based on the parameter provided, Tally.ERP 9 begins synchronisation using Tally.NET or Virtual Private Network.

Operating Information Before commencing data synchronisation either through Tally.NET or Direct IP Sync it is essential to configure the synchronisation server and clients by following steps shown: Synchronisation using Tally.NET Configure Synchronisation Server Configure Tally.NET Features on Server Connect Server Company to Tally.NET Configure Client for Synchronization Create Sync Rule on Client mentioning Serverfs Account ID Activate Rule from Client Activate/Enable Sync Rule on Server Synchronisation using Direct/IP Sync Configure Server for Synchronization Configure Client for Synchronization Create Sync Rule on Client providing Serverfs Static IP Address Activate Rule from Client Activate/Enable Sync Rule on Server @ Precautions Ensure that same set of F11: Features are activated on the Client and Server Company. Do not alter Accounting or Inventory masters. When the accounting or inventory master is altered, a new master is created at the other end on synchronizing data. E.g.: The accounting master Conveyance having a transaction for Rs. 3600/- is altered in the Client to Local Conveyance. A new entry is recorded for Rs. 2700/-, on synchronising data from the Client, Local Conveyance ledger has a balance of Rs. 6300/-. While Conveyance ledger balance on the Server is Rs. 3600/- and Local Conveyance Rs. 2700/-. Thus, when masters are altered, manual correction needs to done on the Server and Client systems. Do not alter default Voucher Type names available in Tally.ERP 9 Using automatic voucher numbering makes it difficult to trace vouchers on synchronisation, as each voucher is allotted a new voucher number. It is suggested to create specific voucher types at the client and server when using same

voucher types. Do not delete vouchers using ALT+D, cancel vouchers using ALT+X. This ensures that vouchers remain on the system. Identify and delete respective voucher from both Server and Client systems. Do not restore back-up of company created earlier at other location for synchronization. Data Synchronisation between two companies having the same GUID will not take place. Technical Information System Requirements Data can be synchronised from any computer without additional hardware. For quick and smooth synchronisation of data it is recommended to have systems with the following configuration: Pentium IV processor with Microsoft Windows 98/ME/NT/2000/2003/XP/ Vista/Windows 7. RAM size of 2GB on both Synchronization Server and Client. Broadband Internet connection with a minimum internet speed of 256kbps. Public IP on Server incase of Direct IP Synchronization (IP must be static). During synchronisation data is transferred in packets and each packet contains 200 vouchers.Where as the synchronisation performance solely depends on data size and Internet speed. Communication between Tally Server/Tally Client Data replication between the synchronisation server and client happens in a secured environment using Encrypted Format and Algorithm (Modified DES) which is proprietary in nature. These are understood exclusively by Tally.ERP 9 only. Data Synchronization in Tally.ERP 9 is not a web based communication. The data is exchanged using HTTP Protocol between synchronisation Client and Server through Encrypted XML over HTTP. While Synchronising data through Tally.NET the data is not stored anywhere on the Tally.NET server. Tally.NET acts a channel between the synchronisation client and server without storing the data on Tally.NET. The synchronization Client is authenticated on the synchronization Server by the rules created on Client. However, data transfer will not take place unless the rule is activated on the respective synchronization Server. The communication between the synchronization server and the client happens using a dedicated TCP port. By default Tally.ERP 9 communicates using port 9000. However, it is recommended to use a TCP port between 9000 and 65000. In case the computer is accessing internet through the Proxy Server. Tally.ERP 9 needs to be configured accordingly. Synchronisation supports Basic and NTLM scheme of Proxy authentication. Online help and Trouble Shooting For a detailed help on various aspects of synchronization it is recommended to read Tally.ERP 9 Reference Manual details the procedure to configure and synchronise Online Help details advanced topics such as FAQ\'s, Troubleshooting articles & other related issues.