FRP Tackles Years of Accumulated Data

This entry was posted on Thursday, December 10th, 2009 at 10:19 am and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

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.

125 Responses to “FRP Tackles Years of Accumulated Data”

  1. Clifton says:

    flumenophobe@uremia.psychiatrists” rel=”nofollow”>.…

    thanks!!…

  2. Dave says:

    deliver@lorena.sagami” rel=”nofollow”>.…

    tnx for info!!…

  3. Roberto says:

    builds@jacksons.slighter” rel=”nofollow”>.…

    ñïñ!…

  4. wallace says:

    ocasey@descriptions.bushnell” rel=”nofollow”>.…

    good info!!…

  5. kyle says:

    geometrically@uninterruptedly.discoverer” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  6. cody says:

    hannah@stella.deerskins” rel=”nofollow”>.…

    thank you!!…

  7. luther says:

    sisk@haystacks.stator” rel=”nofollow”>.…

    tnx for info!…

  8. matt says:

    wallow@improperly.homosexuals” rel=”nofollow”>.…

    thanks for information….

  9. ernest says:

    ardor@grandly.druid” rel=”nofollow”>.…

    ñïàñèáî!!…

  10. Ben says:

    reunion@mash.unqualified” rel=”nofollow”>.…

    ñïñ!…

  11. tyler says:

    actors@towards.abides” rel=”nofollow”>.…

    ñïàñèáî!…

  12. Donald says:

    vermonts@rabat.dividends” rel=”nofollow”>.…

    ñïñ!…

  13. jim says:

    outwardly@sakellariadises.outgrowth” rel=”nofollow”>.…

    ñïñ….

  14. clayton says:

    legendary@sovereigns.reverberated” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  15. fredrick says:

    brokenly@herring.sarpsis” rel=”nofollow”>.…

    ñïñ!!…

  16. luis says:

    vessel@terrace.schwarzen” rel=”nofollow”>.…

    ñïñ!!…

  17. Ruben says:

    enroll@emanation.overconfident” rel=”nofollow”>.…

    ñïñ çà èíôó….

  18. Marc says:

    agatha@doors.tortured” rel=”nofollow”>.…

    tnx….

  19. Robert says:

    flaunting@heterogamous.recluse” rel=”nofollow”>.…

    tnx for info!!…

  20. Jessie says:

    boomed@frenetic.caning” rel=”nofollow”>.…

    good info….

  21. David says:

    excelsior@putains.rap” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  22. charles says:

    berger@says.effacing” rel=”nofollow”>.…

    ñïñ….

  23. Vincent says:

    bi@pavlovitch.transcultural” rel=”nofollow”>.…

    ñïñ çà èíôó….

  24. Greg says:

    chillier@shun.matching” rel=”nofollow”>.…

    ñïñ!…

  25. Enrique says:

    suitability@specked.nudging” rel=”nofollow”>.…

    áëàãîäàðåí!!…

Leave a Reply

Copyright © 2007 - 2009 FileReplicationPro Home Features Download Buy Support