Hello,

Do you mean the panel it self or additional sites?

For the panel it self it's pretty straight forward, you simply have 2 copies of Portal and enterprise, main thing to keep in mind is to put the scheduler service in Failover, so there's not 2 schedulers running at the same time.

For websites it's a bit more tricky as you will depend on a shared IIS config, so when a website is created on one server it is copied to the other server, other then that file replication will be most important. iscsi i wouldn't really recommend unless you plan for an expensive parallel file system. other network shares is a bit tricky too, due to permissions and segregation for your files.

a Failover setup is ofcourse possible, and less complex then a loadbalanced setup i described above.

Regards,

Marco

On previous deployment we had copy of virtual folders on same server.

Now my plan was exactly deploy additional server and just copy virtual folders from original server.

main thing to keep in mind is to put the scheduler service in Failover, so there’s not 2 schedulers running at the same time.

Is there any documentation or article about how to do this?

Ok,

And not really it's just Windows failover service, you need to have it installed via roles and features of windows.  You will need a quorum / 3rd vote on a seperated server (can't be an AD DC server), you can add the service via the failover gui.. it works pretty easy and i guess plenty of documentation about it if you google.

I've made this in other way.

I deployed second server. Copied there files for Portal and Enterprise server and created necessary IIS web sites. Between first and second server - configured WNLB.

Currently all works fine. I can log in, create objects, but customers accounts do not create properly and do not delete properly.

Is there something what i could miss?