Posts Tagged ‘file replication’

Automatic Backup You Can Count On

Tuesday, December 22nd, 2009

Many utilities are built to perform their function and then report success or failure.

FRP was designed to be part of your data infrastructure.   FRP understands that you are assuming that your data moving infrastructure is fast and efficient.  That it is fault tolerant and will act persistently.

We assume that an announcement of failure is not what you want from your file replication software.  But if you use a computer, you know that things can and do go wrong. Transmission failures, network errors, internet timeouts, permissions issues – there’s always something that can go wrong. FRP has built in algorithms that adapt to the far from error-free environments of the internet, long distance communications and not so fast channels.

You need to be able to get perfect file synchronization and replication results even when the environment isn’t perfect.

Some utilities work fine as long as nothing goes wrong.  The intimate management of the communications channel allows FRP to recover from network errors, efficiently retry and restart failed actions and persistently push the data to completion.

Even when you’re not watching it.

FRP is Built for Speed: Fast File Transfer

Tuesday, December 15th, 2009

lightning_by_NivisTigris

Some tools are designed with lots of bells and whistles and end up being large and slow.  Think back on the last software package you bought. Chances are it did a lot of things you didn’t really need it to do. You installed it on your computer, opened it up, enjoyed the animated introduction and the cute sounds it made, and called your colleagues around to see the fun extra tricks it could do.

That’s fun for about twenty minutes. As you use the software every day, though, you begin to wish that it would just do the things you want it to do fast, without hogging your resources and making you choose among a range of options every time you start work.

In fact, a lot of us develop little tricks and workarounds to sidestep the fancy stuff our spreadsheet, word processing, or accounting programs do – so we can get our own work done without delays. Our software has trained us to do tricks.

FRP was designed from the ground up to be fast and efficient.  It is used on major servers, but can comfortably fit on your laptop. You add some files on one server, and in seconds they pop up on the other, in real time.  Large directories are compressed and streamed over, at high speed, with no impact on normal production server operations.  FRP’s multi tasked proprietary tcp/ip based communication engine will adapt to your com channels to maximize data transfer speed.

Users often share with us their surprise at how fast FRP is.  We’re not surprised; it’s fast because we made it that way.

FRP Tackles Years of Accumulated Data

Thursday, December 10th, 2009

dreamstimefree_2415850A new client came to us with a huge backlog of files. As a major international supplier of innovative communication intelligence and security products and systems, with 250 in staff on two continents, his company generated a lot of data, and security was of utmost importance. He had three terabytes of data he needed to replicate to a remote server. He also wanted to keep his remote server in sync with his server on a daily basis.

“It’s going to take months to get all the data onto the backup, right?” he frowned. “And until that’s done, I’m just getting further behind. It seems like a vicious circle.”

He’s right that he’s talking about an enormous job. With a 1.5Mb/sec line between the two servers, at a 70% effective rate, it takes over an hour to move 500MB which is 0.5GB and there are 3000GB to move. It will take 9 months to move all the data through this line.

But the real-world problem isn’t as bad as those numbers would suggest.  The main reason the client needs the server kept in sync is for the current action. The changes and additions to the repository being made now are the ones that are important on a day-to-day level.

The old files which aren’t changing can be replicated gradually.

Can FRP keep current changes in sync and slowly migrate the older files over?

Version 6.1 can.  FRP can now perform a copy or mirror of two servers capturing all current changes and ignoring all files older than a user supplied date.  So our client can tell FRP to migrate his last six months of data first.  Once that’s done, he can change the cutoff date to 12 months ago, and then 18, and so on. All the changes are replicated in real time, so his files stay up to date. The older files are replicated on his schedule, and eventually he’ll have remote backup for all the files.

What if the client needs to work with an older file before it’s replicated? No problem.  If the client changes a three year old file on the source server, FRP will see this as a current change and migrate that file over.  Only unchanged files will have to wait their turn.

If you’re not backing up your files to a remote server yet, you should get started on it as soon as possible. Data security is important for all organizations, and lost data – in any amount – can be a serious problem for your business, especially when data is your business. The good news is, even if you’ve dropped the ball on this in a big way, it’s not too late. Download FRP now and start taking care of the problem.

FRP Maximizes Workflow Options

Monday, October 12th, 2009

Boston City Flow

FRP moves data fast, with plenty of power and speed. It also gives you more than one route to getting the job done.

Say you need to copy a directory from server A to B so as to bring B up to date.  Folders A and B might be quite large and may have many files that are either equal or almost equal.  You simply want to take advantage of FRP’s speed and sophisticated synchronization capabilities to perform the one-time copy straight from the command line. You can do it with the newest update.

Or your company uses a central scheduler and you want to schedule FRP jobs via that tool rather than use the built in FRP scheduler. You can do it.

    After successful completion of a production job, you want to copy some directories to another server.  You can add the FRP copy command to the post production script. Perhaps you need FRP to collect data from one or more servers prior to starting a production job.  You can add that step to your pre production script.

    Now you’ve got that flexibility without sacrificing the speed and power.

    FRP Bridges the Language Gap

    Wednesday, September 9th, 2009

    metropolitainImagine a company providing business communication services, with offices in 50 cities on four continents.

    Certainly, they’re translating documents in a variety of languages. But they also provide a full range of language and business services including translation,interpretation, website globalization, subtitling, voiceovers, multicultural marketing, diversity and inclusion consulting, deposition services, and litigation support to multinational companies.

    A large volume of text documents and voice files have to be transferred every day among the offices, and to and from hundreds of clients. The recipients may not be able to understand the language of the document — and therefore can’t be expected to catch file transfer errors.

    This is a situation in which you have to be able to trust your file transfer solution.

    Fortunately, FRP is absolutely trustworthy. This company is able to use FRP to transfer documents of all kinds with complete confidence.

    FRP Keeps the Office Happy

    Thursday, September 3rd, 2009

    happyFileReplicationPro gives you power and speed at a great price, with economical use of resources.

    Still, there may be times when you have a lot of data to move and you want to avoid running those jobs during peak hours. You can use job exclusion periods for this purpose, but sometimes the sheer size of the job makes it hard to complete during the available time.

    There’s another possibility.

    Consider dividing your job up into two or more jobs that run in parallel in the same time window. FRP supports multiple jobs at the same time provided you have available bandwidth.

    The result: a happy organization.

    FRP Does More With Less

    Tuesday, September 1st, 2009

    Spacecraft monumentA major provider of payload processing and launch services for both commercial and government aeronautics companies was running tape backups of servers at their spaceport.

    This approach was slow and couldn’t operate in real time. With such essential services at stake, it was time to update to offsite server backup.

    They tried one replication software product but found that it was a resource hog. It also couldn’t operate in real time. They liked the concept, but it was still frustrating. They didn’t have margin for an almost-right solution.

    Finally, they tried FRP. It’s easy, with a free, fully-functional trial download, to test FRP and make sure it’s a good fit before you buy — and before you put in the time to implement it. You can try it in your workspace for 45 days and see how it works for you. They tried it out at the spaceport, and it was a perfect fit.

    FRP replicates files in real time, using less bandwidth, and fewer resources. FRP was the solution for this spaceport.

    FRP Does Double Duty

    Friday, August 28th, 2009

    rooA recruitment company for the design industry based in Melbourne, Australia, keeps two servers: one in-house at the office and one in a data center. They have a custom built, web-deployed CRM running on both. They were using MySQL to handle real-time replication at the database layer, but they needed to take care of the file system level replication. That is where FRP comes in.

    From within the office all requests get handled by the in-house server, for the sake of speed. However, if the CRM is accessed from outside the office, it hits the data center server. When files are uploaded, they need to be replicated from their initial server to the other one, in order that the two file systems stay in sync in real time. FileReplicationPro handles this perfectly.

    The company plans to expand to additional offices in other areas of Australia. They want all offices to be working from the same system and to have access to the same data, even though additional servers would be purchased for the additional offices. Fortunately, FRP can easily bring the new servers into the replication network.

    The company also uses FRP for basic nightly backup of share drives from the in-house server to the data center, for disaster recovery purposes. Since they already rely on FRP to take care of their replication needs, they’re glad to be able to use FRP for both roles.

    It’s a savings of time and money for this growing company.

    Copyright © 2007 - 2009 FileReplicationPro Home Features Download Buy Support