RM is a stand alone product that is licensed by host. You would need one license for the RM server, and one license for each production host and mount host. RM comes standard with SQL, Exhcange, Oracle, and file system agents so you dont't need to purchase anything extra to get the functionality you are looking for.  Personally I am a big fan of RM. My company develops an in-house application that uses a SQL backend. Needless to say we have a lot of development, candidate, and test environments which are all copies of production databases. With our largest SQL databases we got to a point where we were unable to restore the databases to development environments in a timely manner (over 24 hours to restore a 4TB database). RM solved that headache in a big way. For example for one of the large production databases I have a RM job that synchs a BCV nightly against the production database, then it kicks off 6 snap jobs the create a TF/Snap of the BCV volumes and then mounts the snaps to 6 different development environments. When the job finishes mounting the snaps it runs a SQL script that attaches the databases to development instances. For development and candidate environments that don't need daily refreshes I have clones that run on weekly or quarterly schedules. All automated. Once I set the jobs up and ensure they work I rarely have to tourch RM again.
2 Questions:  1) after "Create" and "Activate" symclone commands, the target SQL server host can be started to use the targer Device on symatrix? 2) when do we need to use "consistency" with TF/Clone?
TF/Clone for MS sql server