Files
network/veeam.md
T
dohertj2 14cc4faa28 Delete the Plex VM disks
Completes section 9 step 3. govc vm.destroy Plex removed the inventory
entry and the [NVME_1] Plex/ folder; datastore free space went
1,619.8 -> 1,756.1 GB (+136.3 GB). 10.100.0.24 / 10.50.0.31 and MACs
00:0c:29:4a:ef:3d / 00:0c:29:4a:ef:47 are now free for reuse.

Done on 2026-09-17 rather than the planned ~2026-10-15. Checking the
plan's own Veeam precondition inverted its assumption: the Backup VMs
job has EnableDeletedVmDataRetention set to False with Simple retention
of 7 restore points, so a VM removed from the job has its points pruned
as the remaining VMs roll the chain - Plex's are due to age out around
2026-09-24, about three weeks before the disks were scheduled for
deletion. Deleting while a good restore point still existed (2026-09-17
03:01, consistent) was safer than deleting later with none.

Recovery position is now: Veeam image restore until ~2026-09-24, then
only the pre-migration library DB at
/mnt/share/backups/plex-migration-2026-09-16/, which rebuilds a Plex
install but not the VM.

veeam.md gains the retention gotcha, since it applies to any future
decommission and the 30-day DeletedVmsDataRetentionPeriodDays value is
misleading while the toggle is off.

Also flags in esxi.md that its VM tables are incomplete: the host has 10
VMs, WW_DEV_VM / Rockwell_Win10 / TCBSD are absent, and DevVM is powered
off rather than on. Left the tables themselves alone as out of scope.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-17 12:12:20 -04:00

2.8 KiB

Veeam Backup Server

Access

  • Hostname: VEEAM
  • IP: 10.100.0.30 (LAN_100) / 10.50.0.32 (DATA_50)
  • OS: Windows Server 2025 Standard (Build 26100), 64-bit
  • Credentials: dohertj2 / Sonamu8901!
  • SSH: ssh dohertj2@10.100.0.30 (passwordless, key in C:\ProgramData\ssh\administrators_authorized_keys)
  • For PowerShell: ssh dohertj2@10.100.0.30 "powershell -Command '...'"

Hardware (VM on ESXi)

  • CPU: 2x Intel Xeon E5-2697 v4 @ 2.30GHz (8 vCPUs)
  • RAM: 8 GB
  • Disk: C: 127.2 GB NTFS (59.3 GB free)

Network

Adapter Description MAC IP Subnet Speed
LAN_100 vmxnet3 Ethernet Adapter #2 00-0C-29-33-76-AF 10.100.0.30/24 LAN_100 25 Gbps
DATA_50 vmxnet3 Ethernet Adapter 00-0C-29-33-76-A5 10.50.0.32/24 DATA_50 25 Gbps
  • Default gateway: 10.100.0.1 (via LAN_100)
  • DNS: 10.100.0.1

Veeam Backup & Replication

  • Version: 12.3.0.310
  • Install path: C:\Program Files\Veeam\Backup and Replication\Backup\
  • All 24 Veeam services running

Managed Infrastructure

Server Type
Veeam (local) Windows Server
10.2.0.10 ESXi (old server, kept for reference)
10.2.0.12 ESXi

Backup Repositories

Name Path Type Total (TB) Free (TB)
NAS_NFS nfs41://10.2.0.25:/mnt/mypool/veeam NFS 65.6 63.7
NAS nfs41://10.50.0.25:/mnt/mypool/veeam NFS 93.1 69.7

Backup Jobs

Job Type Scheduled Last Result
Backup VMs Backup Yes Success
Backup WW_DEV_VM Backup Yes Success
Backup workstation Endpoint Agent Yes Warning
Backup Joes Macbook Endpoint Agent Yes Warning

Backup VMs includes: Ignition, HA, DOCKER. Deployarr and Plex are explicitly excluded (Plex removed 2026-09-17 on decommission; Veeam converts a removed include into an explicit exclude rather than dropping the entry, so the tombstone is expected). /opt/plex is now covered by the DOCKER VM backup.

Retention gotcha: this job has EnableDeletedVmDataRetention: False with Simple retention of 7 restore points. A VM removed from the job stops generating restore points and its existing data is pruned as the remaining VMs roll the chain — it is not kept for DeletedVmsDataRetentionPeriodDays (30), because that setting is disabled. Plex's points (newest 2026-09-17 03:01) are expected to age out around 2026-09-24. Before decommissioning any VM, export its restore point to a standalone full backup if a long-lived image copy is wanted.

Backup WW_DEV_VM includes: WW_DEV_VM (Wonderware dev VM, ~256 GB increments).

SMB Mappings

Drive Remote Path Status
Z: \\10.100.0.25\Share Unavailable