question

QX0232176-7884 avatar image
0 Votes"
QX0232176-7884 asked AndrewHaverland-7865 commented

MECM's "Site backup and restore"

I want to know more about MECM's "Site backup and restore".

I plan to migrate MECM servers to another environment using the "Site backup and restore" feature.

The configuration of MECM is as follows.
-MP runs on one server.
-DB runs on one server.
-SUP / DP / FSP runs on the same server. (This is a site server.)
-In addition, DP exist at each of the two bases.
This DP does not migrate. Use as it is at the current base.

I would like to know the following three points.

1.
How is MP migrated when migrating using the "Site backup and restore" feature?

I think that only the site server (SUP / DP / FSP) and DB server will be migrated by the "Site backup and restore" function.
I want to know how MP can be migrated.

2.
The disk capacity of the site server (SUP / DP / FSP) is large, about 3TB. Can all data be migrated when migrating using the "Site backup and restore" function?
Or is not all data migrating, only configuration information migrating?

Doesn't it include update information downloaded from the MS update site?

3.
If the answer to NO.2 is not all data, how do you migrate the rest of the data?
Is it a Windows feature robocopy command?

mem-cm-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jason-MSFT avatar image
1 Vote"
Jason-MSFT answered QX0232176-7884 commented

Site backup and restore has nothing to do with any site roles and there's no way or reason to back them or restore them All roles are completely stateless and thus there is no value in backing them or restoring. For a complete DR scenario, you would redeploy them if necessary to new site systems if necessary.

The only thing a site backup truly backs up is the site's configuration which is entirely encapsulated in the DB. There are additional items you should be backing up though including your source repository and content library. Optionally, you can also back up the WSUS DB, the reporting services DB, custom reports (in their raw RDL format), and the configuration.mof (if you've made customizations).

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for your reply.

Do the tasks and order I have to perform match below?

1.
Perform MECM "Site backup" on the existing site server.
Make a backup of the existing DB server.
(Obtained by SQL Server function or DPM)
2.
Build a server on AWS with the same host name as the existing environment, and install MECM in that environment.
3.
Restore the DB server.
4.
Restore the site server.
5.
Copy other required files from the existing environment to the new environment.

0 Votes 0 ·
Jason-MSFT avatar image
0 Votes"
Jason-MSFT answered AndrewHaverland-7865 commented

You need to start with the official docs: https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/backup-and-recovery

Here's a fairly detailed list of steps that I created and used in the past: https://home.memftw.com/configmgr-site-backup-restore/

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I am trying to weigh my options for migrating MECM to new OS and Hardware. I found an article you had written several years back and I am wondering if there are any updates to your considerations of the best migration path (https://home.memftw.com/configmgr-site-server-os-instance-change/). Even after reading your article I am still leaning toward a site-to-site migration to avoid downtime and correct any unknown configurations in the MECM, SQL and general server setup (SCCM was shoehorned into our environment with little planning and did not follow ore standards). I am wondering if a migration would be considered best to get to a known good state or if a backup/restore would still make sense and then discover and cleanup any bad configuration (FYI, drives, install directories and content locations would need to change)? What is an average downtime of a backup/restore of MECM? I was also wondering if HA has become a more viable migration option (our SQL database needs to move off its current hardware too)?

0 Votes 0 ·
Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered

Hi,

Haven't heard from you for some time, is Jason's answer helpful to you? If it is helpful, please accept answer. It will make someone who has the similar issue easily find the answer.

If you have any other issues, please don't hesitate to let us know.

Thanks and have a nice day.

Best regards,
Amanda

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.