How To Repair Or Replace A Failing Server Without Sacrificing Productivity Or Losing Valuable Data

Servers crashing and rebooting without warning?
Frequent error messages on your network?
Database access times increasing unexpectedly?

These could be signs that your servers are failing.

Are your servers are more than five years old? Then you could have volumes of sensitive client information and essential Customer Relationship Management data at risk. But how do you repair or replace your servers without crippling your day-to-day operations in the process?

Our team of network engineers at MainBrain recommend a process, called “Swing Migration,” to solve the problem.

Swing Migration is generally used to upgrade server software to a new version. But it is also a valuable tool when a server needs to be replaced. The beauty of swing migration is that you can move the data on the server without giving up the domain, the server name, or the Exchange Information Store in the process, all while working offline with an open time line.

With swing migration, you get a clean server installation that retains all the critical Active Directory domain information and predictable results. It’s the most transparent method for upgrading all versions of Windows Small Business Server, NT4, Windows 2000, or Windows 2003-based domains as upgrades to SBS 2003. This method works for non-SBS projects as well. In fact, the process is flexible enough for most any project in any production environment regardless of the hardware changes involved. This is especially important if you have to port data from enterprise CRM programs such as Blackberry’s Enterprise Server.

Swing Migration solves technical issues without creating operational interruptions and scheduling problems. Construction of the new server environment is performed almost entirely offline, with an open-ended time line. No additional repairs are needed if for some reason a problem halts the upgrade. Swing migration also minimizes the preparations and changes to the production server, and the old server remains in operation during the upgrade. Only during the final transition are the data and Exchange Stores moved to the new server, which you then slide into service to replace the old one. The domain accounts remain unchanged, you can keep the server name, and alternate paths in the process use the previous hardware until you’re done.

Want to stop dealing with the threat of data loss and downtime? Call MainBrain toll-free now at 1-86-MyMainBrain or schedule a free consultation by filling out the form below: