Windows Server 2012 -- HyperV "replicatation" strategy ?

Below shows my Current and Desired setups.

What HyperV "replicatation" websites show how
to do the below "Desired Setup" #2 a and b
since I am trying to find out which option I want,
but I also want to keep 7+ days of nightly backups
so I can restore if someone deletes a file and fails
to tell me until days later ?
Current Setup
 1. two old EqualLogic SANs
      ** one at each location
 2. two old VMWare servers, switching to HyperV
      ** one at each location
 3. two old Windows 2003 servers
      ** one at each location
 4. nightly replication between SANs
      ** if one fails I can restore from another
Desired Setup
 1. two new Windows 2012 servers
      ** one at each location
 2. use "Windows 2012" built-in HyperV replication
      ** replicate file and file level security
         ever 5 minutes to one of the below
            a) on-site
                 ** on standby server
                 ** on a SAN
            b) off-site
                 ** other site I have, on standby server
                 ** other site I have, on a SAN
                 ** via cloud, on standby server
                 ** via cloud, on a SAN
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Every five minutes seems alot, why not use SAN to SAN replication? This cause alot of disk i/o and VM snapshots....

and setup backups via SAN Snapshots see my EE Article

HOW TO:  Add a Dell EqualLogic PS Series Array (SAN) to System Center Virtual Machine Manager 2012 SP1 as a SMP Provider
Cliff GaliherCommented:
In my opinion, hyper-v replica and backups are complementary, not competitive features. You don't implement one or the other. You implement both to seeve different purposes.

With that said, your option a and b are slightly wrong when it comes to replica. Hyper-V replica is *always* between two hyper-v servers. They may use direct attached storage or may be attached to a SAN, but two servers are always involved. You wouldn't send a replica "direct" to a SAN as you imply.

Now, if it were me and if the equalogics are as old as the question implies, warranty becomes a real concern. The whole point of replica is to minimize downtime, so relying on hardware that you can't quickly get a warrant part for seems counterintuitive to that goal.

So if it were me I'd use 2012 R2 and its three-tier replica support. Replica 1 onsite to a standby server. Replica 2 to an offsite server since that seems to be an option. And then a nightly backup running on the offsite server to guarantee your 7+ day (or more complex) backup strategy.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.