Home > Articles > Operating Systems, Server > Microsoft Servers

  • Print
  • + Share This
From the author of

Exploring the Business Benefits of SureSync

Any modern business needs to satisfy its user base as often as is feasibly possible by providing a reliable and fast application. In this age of more and more users becoming further and further away from application servers, delivering large documents is becoming more of an issue.

Let's take a look at company ABC, Inc., which is a globally reaching organization with offices in more than five countries. ABC has many publishers in the U.S. that update new content regularly through an application that they have custom configured. Part of this process is to develop Word and Excel documents for staff training that can be put up on their intranet servers (and employees can then download them). These documents are very large because they contain many graphics, and because they are training manuals, they have large amounts of content.

Recently, the users in New Zealand have been complaining about performance. The documents are taking too long to download from the States, especially when there are more and more people coming online.

After some consideration, you decide to put a server in New Zealand so that the documents that are published during the day in the U.S. can be sent to New Zealand during their downtime. Thus, when users come online, they can download local copies rather than traversing the network to retrieve the documents from remote Web servers. But how do you keep the server in New Zealand up-to-date with the content that the publishers in the U.S. are pushing through?

SureSync allows you to easily add the server into the New Zealand network and deploy documents to it through regular batch runs. These batch runs can be scheduled to run at times that are the least disruptive to the New Zealand users (during New Zealand's night hours). And best of all, unlike other file-replication tools such as XCOPY and SCOPY, SureSync only deploys the deltas (or changes) to the store (although this can be configured differently), thus reducing the amount of documents that need to be deployed to only those that have changed.

Commercially sensitive documents can be secured with standard Window NTFS Security, and you can rest assured that the permissions associated with that document will still be associated with the document when it reaches the New Zealand server (as long as they are on the same domain, of course!).

Now isn't this beginning to sound like common sense?

  • + Share This
  • 🔖 Save To Your Account