Almost every time I'm discussing with someone (individuals, students,...) about importance of good backups, disaster recovery procedures and of course tested procedures for disaster recovery (make sure that you actually test your backups, disaster recovery procedures on regular basis) I ask a question: "If your location goes down because of natural disaster, fire,..., are you able to rebuild your whole location or infrastructure (in the case of single location) from offsite backups?"
Answers are:
- Eventually, I guess
- We don't have offsite backups
- Probably, we have disaster recovery procedure but we never tested it
- In some rare cases I actually hear that there are good disaster recovery procedures in place which is actually tested! (offsite backups, procedures for restoring every server, testing DR procedure on regular basis)
I'm really worried about that just to many people don't take backups seriously enough until it's to late. In most cases disaster recovery goes like Dilbert's one.
As a regular reader of Internet Storm Center I came across a must read link The Tao Of Backup! :)
This is one "simple" error I come across when installing on Windows Server 2008 RC1.
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1976). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
In my case solution was really simple. Between the tests I disabled IPv6 support on network card. I enable it back, re-run setup and everything was fine...
This is second part of upgrading procedure for Exchange Server 2007 SP1. In first part we looked into necessary steps for getting Windows ready, preparing Active Directory and upgrading Client Access Server (CAS) role to Exchange Server 2007 SP1.
In this part we will look into upgrading HUB Transport Server role to SP1. Procedure is almost identical than in first part (upgrading CAS to SP1) but purpose of this part is looking into Unattended Setup.
Prior installing SP1 read carefully section with prerequisites (install necessary components and updates on Windows Server, upgrade antivirus software for Exchange Server) from my previous post Upgrading Exchange 2007 to SP1 (Part 1)!
Installing Service Pack 1 in Unattended Mode
It's time for Service Pack installation. ;-)
Run following command from location with extracted Exchange Server 2007 SP1 files:
setup /mode:upgrade
Procedure is the same as in graphical mode. First step is is Prerequisite check.
Note that I cheated just a little bit. ;-) I had other roles on this server, not just HUB role. When running setup /mode:upgrade you receive the list of roles that will be upgraded. You can use this steps (and steps for preparing Active Directory) for upgrading single server installation.
If no critical errors were found setup continue with Configuring steps (Preparing Setup, Removing Exchange Files, Preparing Files,...). In Unattended Mode you also have a progress bar just like in graphical mode.
And a final screen after successful Service Pack 1 installation.
Check Event Viewer and Exchange functionality to verify that everything is working as expected.
In following articles we will dive into cluster (Single Copy Cluster - SCC, Cluster Continuous Replication - CCR) upgrading and some new high availability features in SP1.
Related: