Re: vHMC vs Backup HMC Data

[Yvan Janssens <friedkiwi@xxxxxxxx>]

That's indeed a typo - I used them interchangeably.

What I meant was to use both the built-in backup functionality and the one from the hypervisor, and store them separately.

/y

On 07/09/2023, 17:08, "MIDRANGE-L on behalf of Rob Berendt" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of robertowenberendt@xxxxxxxxx <mailto:robertowenberendt@xxxxxxxxx>> wrote:


Was that a typo? Do you need the Save Upgrade Data or the "Backup HMC
data"?


On Thu, Sep 7, 2023 at 9:03 AM Yvan Janssens <friedkiwi@xxxxxxxx <mailto:friedkiwi@xxxxxxxx>> wrote:


> It's not obsolete, just different kinds of backups. A VM snapshot allows
> you to easily revert from eg a failed upgrade, but if you lose the
> ESX/vsphere host or data store due to it being infected with ransomware or
> a catastrophic hardware failure, you need the 'Save Upgrade Data' to
> restore a blank vHMC image.
>
> It's still a good thing to do, because it adds layers to your DR
> procedure, and allows you to recover from different kinds of incidents.
>
> /y
>
> On 07/09/2023, 13:42, "MIDRANGE-L on behalf of Rob Berendt" <
> midrange-l-bounces@xxxxxxxxxxxxxxxxxx <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> <mailto:
> midrange-l-bounces@xxxxxxxxxxxxxxxxxx <mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of
> robertowenberendt@xxxxxxxxx <mailto:robertowenberendt@xxxxxxxxx> <mailto:robertowenberendt@xxxxxxxxx <mailto:robertowenberendt@xxxxxxxxx>>> wrote:
>
>
> I get that as part of upgrading or updating HMC code one should reboot
> first and Save Upgrade Data. However with vHMC and the ability to take a
> snapshot is "Backup HMC Data" prior to the upgrade obsolete?
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx <mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> <mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx <mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>>
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l <https://lists.midrange.com/mailman/listinfo/midrange-l> <
> https://lists.midrange.com/mailman/listinfo/midrange-l> <https://lists.midrange.com/mailman/listinfo/midrange-l&gt;>
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx <mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx> <mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx <mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>>
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l <https://archive.midrange.com/midrange-l> <
> https://archive.midrange.com/midrange-l> <https://archive.midrange.com/midrange-l&gt;>.
>
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx <mailto:support@xxxxxxxxxxxxxxxxxxxx> <mailto:
> support@xxxxxxxxxxxxxxxxxxxx <mailto:support@xxxxxxxxxxxxxxxxxxxx>> for any subscription related questions.
>
>
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx <mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l <https://lists.midrange.com/mailman/listinfo/midrange-l>
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx <mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l <https://archive.midrange.com/midrange-l>.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx <mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
> questions.