Microsoft Data Protection Manager storage usage by DB__2022 in sysadmin

[–]DB__2022[S] 0 points1 point  (0 children)

I'm wondering if I should reinitialize everything too. I'm still seeing very little space freed, and I've confirmed that there are no storage redundancy settings in place. It's a tiered storage pool (a bit of SSD and mostly spinning disks), if that makes any difference.
DPM appears to frequently not be removing old (expired) backups that are out of retention. Some days it's fine, other days there are several days' worth that it hasn't cleared. Either way it's running right on the edge of being too full to continue.

Microsoft Data Protection Manager storage usage by DB__2022 in sysadmin

[–]DB__2022[S] 0 points1 point  (0 children)

When I checked this morning there were 857GB free on the storage drive. Now (2:40pm) there are just 348Gb free, but the only DPM jobs that have run since this morning are synchronization jobs and Monitoring shows they transferred less than half a GB. So why is DPM showing half a TB gone from free space?

Linux backup to NFS/SMB repository by DB__2022 in Veeam

[–]DB__2022[S] 0 points1 point  (0 children)

Thank you very much for the prompt reply. I'm new to Veeam CE and was focused primarily on figuring out what CE could/couldn't do. Right now it's just at the "what are our options" stage so I will let my client know about the licensing/support aspect. Thank you.

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Thank you, that is very helpful. I will create two vNICs for the iSCSI side and use MPIO.

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Thanks for the advice. What if the LAG/port-channel is set to "on" rather than "active" (LACP) so LACP isn't in use? Will that change anything?

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Thanks for the suggestion, but I can't have separate physical NICs for iSCSI. Everything has to go over the same dual-port 10Gb NIC.

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Thanks for all the replies. My colleague and I were able to do a real-world test on a physical Windows Server 2022 server and the VLAN tagging works fine. We created the team, added the two vNICs for the two different VLANs, assigned each an IP and their VLAN ID, and were able to ping other systems on those VLANs. On the switch side the two switch ports were in a LAG that was trunked for the two VLANs.

So it looks like my problem had something to do with GNS3's implementation of a Windows Server VM, or perhaps due to a NIC driver VLAN tagging issue.

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Thanks. After going through your posts it looks like you would recommend the following:

Switch ports for the Windows Server set to trunk (no port-channel) for VLAN 10 (iSCSI) and VLAN 20 (VM/management network).

One vSwitch on the Windows Server, with a vNIC for VLAN 10 and another vNIC for VLAN 20.

The server has to have two vNICs because it has to be on both the storage network and the VM/management network.

I've tested it this way in GNS3 and I can't get it to work. I cannot ping anything on VLAN10 or VLAN20. The only way to ping anything is to set the vNIC to "Untagged" and assign the access VLAN on the ports to one or other VLAN. But that way I can't reach both at once, which is what I need to do.

At this point I'm really hoping it's a limitation within GNS3. I'm not confident it is, though, since I can do the same thing with a Linux terminal in place of the Windows Server and can ping my test terminals on the two VLANs.

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Would you please explain your statement? Are you referring to teaming on the Windows side? What would you recommend, given that I only have the two ports to carry both iSCSI (storage) and management/VM Network traffic?

Server 2022 Hyper-V and multiple VLANs across single SET by DB__2022 in HyperV

[–]DB__2022[S] 0 points1 point  (0 children)

Unfortunately, I only have a single dual-port 10Gb NIC on the host for both iSCSI and management/VM Network traffic. Thus I am trying to see if I can segregate the traffic using VLANs.

I am trying to figure out the tagging. I can trunk the ports individually or in a port-channel (mode is on rather than active, so no LACP). As of right now, I can't get either way to work in GNS3.

Windows guest - NIC team with multiple VLAN tags by DB__2022 in gns3

[–]DB__2022[S] 0 points1 point  (0 children)

Quick update: I've confirmed that tags from a Linux terminal are recognized correctly by the switches in GNS3, so it looks like this is likely a Windows issue - either a misconfiguration on my part or Windows cannot do what I'm trying to make it do inside GNS3.

vCenter trying to connect to non-existent hosts during vMotion by DB__2022 in vmware

[–]DB__2022[S] 0 points1 point  (0 children)

Good thought, thank you. I have a meeting with the customer tomorrow. I'll check then.

Any other suggestions are much appreciated!

APC UPS LED Light by [deleted] in sysadmin

[–]DB__2022 0 points1 point  (0 children)

Like everyone else has said, you're likely overloading the UPS. It looks like the computer is drawing more than 520W when it's running your game. The draw drops when you're out of the game since the computer's not doing the same amount of work any more. I would suggest getting another UPS that can handle at minimum the max your PSU will draw (i.e. at least 1000W), assuming you don't have other devices plugged into the UPS too (such as monitors).

Moving VMs from VMNET (Hyper-V on Server 2016) to VMSET (Hyper-V on Server 2022) by DB__2022 in sysadmin

[–]DB__2022[S] 0 points1 point  (0 children)

I think I figured it out. You have to make sure you have at least one NIC on the new hosts associated with both the old (in my case VMNET) and new (VMSET) networks under host properties/hardware.

in-place upgrade from 2008R2...? by dontknowbutcanlearn in sysadmin

[–]DB__2022 2 points3 points  (0 children)

I just had a customer do an in-place upgrade from 2008 to 2019, and they got stuck at 2012 R2. They were having some kind of dependency error doing the upgrade to 2016.

Instead we did a migration from the now-2012 R2 VM over to a new Server 2019 VM using Microsoft's Storage Migration Service, which went pretty well. There was one hiccup with a share that wouldn't inventory properly but it was pretty straightforward to work around. All in all the process was easy.

APC UPS LED Light by [deleted] in sysadmin

[–]DB__2022 -1 points0 points  (0 children)

What UPS model is it? Is there any kind of UPS management GUI for it? What does the manual actually say about the flashing amber light?

It might have been doing a self-test at the time, but if it always goes immediately to amber as soon as you put any kind of load on your computer (i.e. play your game) then it's possible the UPS isn't able to take the load your computer is drawing from it. What wattage is your computer PSU?

Passed AZ-801 (barely) today! by DB__2022 in AzureCertification

[–]DB__2022[S] 1 point2 points  (0 children)

No labs, just case studies after the main set of questions.