CDR - Any Issues?

[hutchingsp]

We've used Commvault for a few years so it seemed the obvious choice to "keep it under one roof" when we wanted to replicate data from our main server to a server in our DR site (which is on the end of a multi-gbps LAN link).

I've finally got downtime scheduled tomorrow to install CDR and any updates and do the required reboot.

Other than the obvious RTFM, is there anything I should be acutely aware of with CDR or is it really just a case of setup a replication pair, setup source and destination sets and leave it to it?

 

[CraigMcGill]

CDR is a lot more stable than when it was first introduced. In the early days, CV would only let their own staff perform the installations as the company had copped a lot of flack from people that had implemented it badly (and discovered its shortcomings). However, as I said, it's come along way since then. I think it's really neat that it's database aware (Exchange, Oracle, etc).

See if you can find out the registry keys that apply to CDR - they tweak various things (eg. replications trigger points, such as amount of data change and elapsed time).

Sure go ahead and install it, but once it's in, you might like to experiment with its functions and features (and discover any shortcomings) before you rely on it.

 

[hutchingsp]

Interesting - granted Books Online is never exactly a "fun" read but it made it sound fairly straightforward or is that as you say mainly with the later versions?

To expand a little, we're not looking to do mission critical absolute real-time replication, but we have a bunch of storage and a server "off site" and it makes sense to have a near real-time replica of our main file server LUNs on it as having some access even will be better than "Well there's the box of LTO3 tapes".