System backup for restoring to New Management VM

[KVC]

Hello All,

We've encountered an issue with the Management Server VM partition running R80.40, where both disks have the "boot" flag enabled, hindering the upgrade process to R81.20. To circumvent this, we're considering setting up a new Management Server VM with a single disk, also running R80.40, and then restoring the System Backup from the existing VM onto it. However, we're uncertain about whether this restore process will encompass all our policies, blade configurations, SIC connections to our Gateways, etc. It's important to note that the logs won't be included in this restore. Could someone provide guidance on what else might not be restored with a System Backup performed in this manner?

Additionally, we're exploring the possibility of taking a snapshot of the current Management Server VM (with its two disks and incorrect "boot" flag settings) and using it to restore onto the new Management Server VM with just one disk. Does this approach necessitate identical partition configurations during the restoration of the snapshot?

Any insights or guidance on these matters would be greatly appreciated.

Thank you.

K

[the_rock]

As long as new machine is on the SAME version, you can restore it. Also, make sure that all network interfaces match, otherwise, import will fail. Also, its worth pointing out that restore does NOT "transfer" the jumbo hotfix, but its not a big deal, you can install it later.

Best,

Andy

[KVC]

Hey Andy,

I'm really appreciative of your prompt response. I was hoping you could shed some light on the system backup restore process and its coverage. Specifically, I'm curious if it encompasses all our policies, blade configurations, SIC connections to our Gateways, and any other crucial elements. Is there anything that might slip through the cracks in terms of the Management Server's role?

Moreover, if the system backup does indeed restore everything related to the Management Server's role, I'm curious about the additional data that the "migrate_server" function would export in comparison to a standard system backup.

I'm eager to hear your insights on this matter.

Best regards,

K

[G_W_Albrecht]

Here: sk108902: Best Practices - Backup on Gaia OS

[the_rock]

Put it this way, here is my explanation in simple terms : - ). So when you do backup, it mostly takes care of OS settings side and sk @G_W_Albrecht provided is an excellent reference to that.

Now, as far as migrate_server, that will simply transfer the rules, objects, vpn communities, pretty much anything from smart console and you do NOT need to reset SIC again. By the way, keep in mind that migrate _server will override existing license, but would NOT "erase" existing IP and hostname, so if you go that route, I would give it appropriate hostname beforehand and also you can assign it same IP address, because it would not be in production until everything is moved over and policy applied from the new server.

Makes sense?

Best,

Andy

[KVC]

Hello Andy,

I appreciate your prompt and accommodating response. I hope I'm not sounding too repetitive with my inquiries.

Regarding our decision to explore the system backup approach, I wanted to clarify if it necessitates resetting the SIC once more?

Regards,
K

[the_rock]

Good morning,

Not repetitive, dont worry, questions are FREE ; - )

Every time I did restore in the past on the mgmt, I never had to reset the SIC. 

Best,

Andy

[KVC]

Hello Andy,

Thanks for the clarifications. Since we are restoring it on a new management server, i had doubts!

Regards,

K

[the_rock]

All good, we are here to help one another. No one is born knowing everything, as they say 🙂

You can ask anything you are not sure about mate.

Best,

Andy