Working with ITS

MiServer or MiDatabase should reduce the amount of effort it takes to set-up and maintain a server or database. ITS makes it easy to get started, whether you work directly with ITS professionals in the ITS Shared Services roll-out or use the self-service features of the new Michigan IT Services portal.

The ITS Shared Services roll-out incorporates multiple workstreams, including MiServer and MiDatabase. Units getting started through this path will partner with ITS through the MiWorkspace engagement and technical discovery activities. Anyone who requests MiServer or Database services, regardless of their path to getting started, has two options for establishing service.

Establishing Service

Depending on your specific needs, you may launch your MiServer or MiDatabase service request in one of two ways:

  1. Establish new servers or databases or
  2. Migrate data from existing servers

ITS will work with you to get you up-and-running as soon as possible and with minimal disruption. Read more about the ITS approach below:

New Servers or Databases

Anyone with a new server or database request may be able to get started right away. Whether your need is identified during the ITS Shared Services Roll-out or through an alternate path, ITS can provision a new server or database immediately after you've submitted your request. Our automated processes mean you can get back to work quickly! For any delays, ITS will communicate with you from the moment we receive your request.

Units in the ITS Shared Services roll-out will work directly with an ITS team, while those outside this path may request a new server directly through the Michigan IT Services Portal.

Read more about your options for getting started.

Migrate Existing Servers

Depending on the complexity of existing data, you may be able to make the switch on your own or engage ITS for assistance. For those who require additional support transferring their data, ITS offers a migration service.

In this option, ITS will work directly with you or your unit IT staff to plan and migrate your data to the new services. The amount of effort and time required to fully transition servers to MiServer or MiDatabase may vary. Although the actual time to migrate a server is short (a few days at most), the coordination and scheduling with your unit may last a few weeks.

Units moving existing servers to MiServer and MiDatabase as part of the ITS Shared Services roll-out will use the migration service, which closely aligns with other technical changes in your unit.

There are five key stages in the migration process (Show All):

The technical discovery process is shared by the unit or individual and ITS's MiServer and MiDatabase teams. This collaborative discovery team identifies servers appropriate to move to the new services. Early discovery looks at the size of your servers, as well as the type of server (e.g. virtual vs. physical). Secondary discovery activities look at your unit's business processes and other dependencies.

The team will then determine the most cost-effective and appropriate disposition for any physical servers, and recommend the best configuration for your virtual server and/or databases.

The outcome of the discovery effort will determine the specific approach the team will take to implement the services and to forecast a timeline. The ITS team takes into consideration your business cycles and other dependencies and works directly with you and your unit to create an approach that ensures the least amount of disruption and downtime.

Immediately prior to the agreed upon migration date, the target servers are placed in a "freeze" state to ensure a neutral state during the scheduled migration, which lessen any chance of data loss. Testing activities may also occur during this time period.

This is the official transfer of server or database data into the ITS-managed environment. The ITS team and your unit IT leads work together to ensure the best timing for the migration, and actively communicate during the migration to ensure its success. This activity usually occurs in the off-hours or over a weekend.

Once the migration is complete, the stabilization period begins. This period immediately following the migration should be business-as-usual. The transition to the new services should be transparent to all end-users, and any residual issues will be addressed by the MiServer and MiDatabase team.

Read more about your options for getting started.