Configuring DAGs in Exchange 2010

One of the new features and advantages that Exchange offers us 2010 is the possibility of having a high availability system in a simple way, being easy to implement, at any time and above all the simplicity of administration. It is based on the implementation of DAG or Database Availability Group, by mounting a replica of the databases between the different Mailbox servers (or on the same computer if we have all the roles on the same server), so this replaces the old Exchange clusters 2007, SCR and CSF; and therefore now we will simply need two servers and not three or more as required in Exchange 2007!

Setting up an HP Lefthand array

In this document you will see certain generic configurations that allow these HP SAN arrays called HP Lefthand, this case is carried out by means of virtual arrays under a VMware environment, as they allow you to work perfectly in a much more flexible laboratory environment. HP has several models of physical Lefthand arrays, all with the same system, but with different capacities, Disc Models, Ethernet Mouths… would be the HP LeftHand P4500 and HP LeftHand P4300 series. But also for production environments there is the HP LeftHand P4000 Virtual SAN Appliance or VSA. In this document we will see the main characteristics of the cabins, such as storage clustering (gives greater performance and capacity), Network RAID (Increased data availability), Thin provisioning (Reduces costs and improves disk capacity utilization), iSCSI (Ethernet network technology) Snapshots and Replication using Remote Copy (for local replication […]

Setting up Microsoft Exchange 2007 with SCC (Single Copy Cluster) on Windows Server 2008

In this document, we will see how to set up a high availability cluster for our Microsoft Exchange mail server 2007 Server with the Microsoft Windows Server operating system 2008, in this case we will set up a cluster system called SCC (Single Copy Cluster o Clúster de Copia Única). In this previous document the rest of the possibilities that we would have are described, we may be more interested in one system than another (HTTP://www.bujarra.com/?p=2362). As discussed above, SCC is the cluster that we can know from previous editions of Microsoft Exchange, is a shared storage failover cluster system, This is, we will have several nodes with the 'Mailbox function' one of them being active and the rest passive. Storage must be shared, Databases must be in an array or remote storage system, iSCSI, fibre... When the active node fails, One of the nodes in a passive state […]

Different types of Microsoft Exchange high availability 2007 (CCR, SCC, CSF & SCR)

Well, After a long time out, with a lot of work, I had time to look at myself and wrestle with the different types of high availability that Microsoft Exchange gives us 2007 to date. Unlike Microsoft Exchange 2003, This version, brings more possibilities to have a high availability of our mail server, having different methods, some cheaper than others and more or less complex. In principle, we have: CCR (Cluster Continuous Replication o Replicación Continua en Clúster) SCC (Single Copy Cluster o Clúster de Copia Única) CSF (Local Continuous Replication o Replicación Continua Local) SCR (Standby Continuous Replication o Replicación Continua en Espera)

Creating a High Availability Cluster on Microsoft Windows Server 2008

After viewing a document on how to create shared storage for a cluster, Why not create one? Well, the process is similar to Windows 2003, now we will do it for Windows 2008, A new cluster, and it will be for a file server, failover clustering, The process for another type of cluster is similar. With this we will achieve high availability, that if one of the servers falls (node) Don't worry., since there are other nodes that can take the resources and lift the services so that users can work practically without noticing the fall of the node they were working against. Also comment that maintaining a cluster is expensive, This is, We will always keep in mind that both servers will have the same applications installed, in the same way and with the same versions, all this to avoid future problems. It is also advisable to balance the cluster […]

Connectivity balancing in Fortigate

If we want to configure the firewall for when an internet connection goes down, it automatically goes out with another and the users “almost” do not realize it you have to follow the steps of this procedure. It is applicable to any Fortigate, Logically, what you have to have is two connections from different suppliers in the organization, for example, we can have Timofonica on the WAN1 and Güanadú on the WAN2, in case the Timofonica connection drops (something quite frequent) that the connection we have with Güanadú be lifted.

Citrix WI and PNA Balancing with NLB: Configuring Web Interface and Program Neighborhood Agent Groups for Balancing with Network Load Balancing

This document is quite useful if what we have is several servers with the Web Interface service or with the Program Neighborhood Agent and what we want is to balance between them, that is, if one of the servers goes down or we turn it off, we don't have to do anything on the users' PCs so that they continue to work normally. To do this, it will be necessary to configure it on servers that have W.I.. a cluster with NLB, I mean, create an IP address “virtual” to which clients will connect and this IP address “virtual” connect to hosts that are lifted, to one server or another; both for W.I. How to stop PNA.