Hello Aran,

Thank you for your reply.
Do you know what's about restoring databases. Is there any advantage?
I remember that I can't apply any logfiles if I restore the database with RMSE.
What's about RM in this case?

A Second question I have: Do RM supports SANCopy incremental?

Thanks in advance for your feedback.
Regards
Manfred

I started out using RMSE for cloning a SQL database on a cluster which worked fine if all I wanted to do was clone that one instance from that cluster only. But my end goal was to take snapshots of the clones and serve them up to multiple development servers on a daily basis for our development group. RMSE cannot accomplish this and I was stuck with creating a series of custom scripts to accomplish our needs.

Since the deployment was just a pilot and I wanted to scale out the concept above to multiple production SQL servers RM was the only choice. RMSE does not scale well and is difficult to use to manage multiple source servers. RM actually has the ability to take snaps of clones and scales out well.

I can't answer the question about restoring as I have not had to do that yet. Right now all we use it for is our development environment where I have sql scripts that attach to the data files on the dev server sql instances. I would think the behavior would be the same in RM as in RMSE.

RM does support SANCopy Incremental according to the documentation.

Aran

Thank you for your answer!

RM 5 has the ability to attach and restore any SQL instance in the mount operation. It works very nice and all our developers have been impressed with the technology. It will mount snaps or clones all the same