• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 2656 views
  • Users 0 members are here
Options
Related

make initial replication size as small as possible

jordanl
over 3 years ago

We've got a new email server (Exchange  2016) and it's not being replicated yet.   I'd like to attempt to just replicate the whole thing without doing a seed drive.  BUT I know I need to make the initial replication as small as possible. I don't need to replicate all the recovery points.  What's the best way to go about doing this?  

Total recovery points:46 - Total protected data:5.04 TB

actual amount of data 2.2 TB.

Transferring 2 TB is going to be a lot, transferring 5 TB is not happening!

any advice is appreciated,

  • 0 over 3 years ago

    The simply answer is, you can't. Replication MUST initial mark each recovery point as sent, rather through the wire, or through a seed. There is no way around that. The source core has to flag each recovery point as 'sent' in the db at least once. Once it is sync'ed at least once, then you can set dis-similar retention and such, but it has to match at least once. 

  • 0 over 3 years ago in reply to support_89498

    ok, so maybe I could create a custom retention policy, bring down to like 1 day.  (which should drastically reduce the size), then replicate it?

  • 0 over 3 years ago in reply to jordanl

    That could work, obviously you will lose your retention for that period of time (make sure to set it back when you're finished). That can work. Keep in mind that the RR DP knows that those RPs haven't been replicated, so before you set a smaller retention you will have to first remove just that 1 node from outgoing replication, otherwise the RPs will never go away. The RR DB knows that they weren't replicated, so rollups will not delete them. So you'll first have to remove that one node from outgoing replication, then shorten the retention, let the rollups run, then re-add it.