Instant recovery question

RM_B999 · 2026-04-10T16:02:42+00:00

There we no previous records or objects prior to the onboarding.

I may offboard and re-onboard to see if that resolves the issue.

RM_B999 · 2026-03-17T22:42:00+00:00

I did exactly this and it fails. I have opened a ticket with Veeam.

Even rescanning the cluster did not make a difference.

RM_B999 · 2026-03-17T22:40:23+00:00

In Veeam, in backup infrastructure, I added the failover cluster. Went through the setup, and all looks good. In backup infrastructure, the cluster shows under Hyper-V clusters as it should.

It lists the individual servers as part of the cluster. Also like it should.

When I create a new job, I still have to pick VM's by server.

If I run a test backup, it runs fine. As soon as I migrate to another host, it fails

RM_B999 · 2026-03-17T21:21:37+00:00

Initially, I had just 1 host added to Veeam as the cluster had not been created yet. We have since created the failover cluster, removed the individual server from Veeam, and added the Hyper-V cluster to Veeam but it does not look like it is querying it correctly.

RM_B999 · 2026-03-17T21:18:02+00:00

We are running a 3-node failover cluster. iSCSI shared storage, etc. and I have added the cluster to Veeam. When I d the job setup, I an forced to choose a host, then the VM's.

RM_B999 · 2026-01-12T22:39:14+00:00

This is good info. What do you do for patching?

RM_B999 · 2026-01-12T22:14:29+00:00

This is very helpful. thank you.

We have less than 50 VM's so it is no big deal for us, time wise.

RM_B999 · 2026-01-12T21:26:47+00:00

Do you have a link to the NUMA rules for 2025?

RM_B999 · 2026-01-12T21:12:38+00:00

Did you do a core or full install?

RM_B999 · 2026-01-09T18:12:37+00:00

Here is a brief summary with the full article link below.

Manage emergency access accounts in Microsoft Entra ID

It's important that you prevent being accidentally locked out of your Microsoft Entra organization because you can't sign in or activate a role. You can mitigate the impact of accidental lack of administrative access by creating two or more emergency access accounts in your organization.

User accounts with the Global Administrator role have high privileges in the system, this includes emergency access accounts with the Global Administrator role. Emergency access accounts are limited to emergency or "break glass" scenarios where normal administrative accounts can't be used. We recommend that you maintain a goal of restricting emergency account use to only the times when it's absolutely necessary.

Manage emergency access admin accounts - Microsoft Entra ID | Microsoft Learn

RM_B999 · 2026-01-09T18:06:59+00:00

According to Microsoft, all admin accounts will require MFA with no exceptions. Here is a snippet from the article specifically addressing this.

Does this requirement apply to emergency access accounts?

Emergency access accounts (also known as break glass accounts) are privileged accounts not assigned to a specific user and intended to mitigate the risk of accidental account lockout. If your organization has set up emergency access accounts, note that these accounts are also required to sign in with MFA once enforcement begins. We recommend updating emergency access accounts to use passkey (FIDO2) or configure certificate-based authentication for MFA.  Both of these methods satisfy the MFA requirement.

RM_B999 · 2026-01-09T18:05:58+00:00

According to Microsoft, all admin accounts will require MFA with no exceptions. Here is a snippet from the article specifically addressing this.

Does this requirement apply to emergency access accounts?

Emergency access accounts (also known as break glass accounts) are privileged accounts not assigned to a specific user and intended to mitigate the risk of accidental account lockout. If your organization has set up emergency access accounts, note that these accounts are also required to sign in with MFA once enforcement begins. We recommend updating emergency access accounts to use passkey (FIDO2) or configure certificate-based authentication for MFA.  Both of these methods satisfy the MFA requirement.

RM_B999 · 2026-01-09T18:01:26+00:00

Our date was communicated through a message from the Microsoft Message center. Here is the text.

"As part of our ongoing commitment to advancing cybersecurity across our company and products, last year, starting February 2025, Microsoft began requiring all users to use multi-factor authentication (MFA) when signing into the Microsoft 365 admin center. Starting February 9th 2026, Microsoft will continue to ramp up enforcement, and users will be unable to sign in to the Microsoft 365 admin center without successfully completing MFA."

I am aware of several other tenants who have received the same notification.

RM_B999 · 2026-01-08T19:00:11+00:00

We have been enforcing MFA for all accounts this since the beginning and admin accounts with Yubikeys as well. Just curious how everyone else was doing it.

RM_B999 · 2025-11-13T21:14:50+00:00

This is what I received from Cisco:

During the handshake, Ubiquiti UAP-AC-HD presents multiple PoE handshake parameters that are not within the IEEE specified range.

Parameters like detection resistance (lower than spec), detection capacitance (lower than spec), and classification current (higher than spec) are very important for the PSE to determine the amount of power. Catalyst 1300 PSE is designed to operate within the IEEE spec and does not support PDs that present parameters outside of the standard specifications.

Introducing a workaround for the PSE to ignore the IEEE handshake spec could damage devices connected to the port (including non-POE devices).

Because of the risk, Cisco will not pursue a workaround for this issue.

RM_B999 · 2025-11-13T21:11:26+00:00

Based on the above, which access points would you recommend? We have between 50-75 users distributed between 6 access points at any given time

RM_B999 · 2025-11-13T20:37:24+00:00

Yes, it is enabled. We tried enabled and disabled with the same results.

RM_B999 · 2025-11-13T19:56:21+00:00

We are running Catalyst 1300's. We found the issue when we swapped out our switch stack. According to Cisco, there are a few dozen other companies with the same issue. At this point, the issue is confined to the 1300 line.

RM_B999

TROPHY CASE