You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This assumes you have Windows Server 2022 Gen2 VM running on hyper-v that uses gen2 with UEFI and Secure Boot - it should work for win11 but i haven't tested that. This has only tested with a vanilla windows server 2022 VM so far (three times to write guide). I will comment this gist when i manage to move one of my domain controllers.
I suggest creating a fresh test windows VM and use this procedure on that test VM long before you try this on a production VM.
And repeat after me 'i will backup all VMs with snapshots AND will backup with backup application before i do this`... ok...
Configuring CephFS to store ISOs for VMs and Templates for Containers
This gist assume you have setup Ceph as per earlier gist in this sequence
I found it annoying to upload ISO to each node in the cluster, download CT templates to each node.
I thought setting up cedph for these would be a great idea (and it is).
As such please refer to that for pictures, here i will capture the command lines I used as i sequence the commands a little differently so it makes more logic to me.
This gists assumes you are not running ZFS and are not passing any other PCIE devices (as both of these can require addtional steps - see Derek's blog for more info)
This gist assumes you are not running proxmox in UEFI Secure boot - if you are please refer entirely to dereks blog.
the account name is anything useful to you - i recommend using something like <mydomain>-<tld>-acme where mydomain is your DNS domain prefix and tld is the suffice (like com or net etc) so mydomain-com-acme
setup promox backup server and synology as data store over SMB
Proxmox Backup
At this time proxmox backup only backs up VM and Containers - ths guide covers that.
What i didn't realize is the backup job is still defined on the cluster and PBS provides a new storage type that dedupes and managed all the vzdump files created - which is cool.
I decided to run proxmox backup on my Synology NAS where it has more reliable connection to the NAS (i.e. via memory) for doing deduple, garbage collection, prune, verification etc. However the steps here generally remain true.
Once again i used one of Derek Seaman's Awesome Blogs for the basis of this - but with my own tweaks (like using SMB instead of CIFS. As of 9/21 my tweaks are signifcnant, in the original blog it is missing steps to enable encoding acceleration in CTs and VMs.
This gist assumes a working Azure AD (not Azure AD-DS is already up and fully configured)
This gist assumes working DNS / name resolution on your internal network.
setup an smtp smarthost/relay that can send mail to Exchange Online 365 Office Outlook M365 (they keep renaming it)
setup postfix each proxmox host and backup server to use this relay
require the relay does authentications from devices like pve and pbs - having an open SMTP relay inside the network is not something i can bring myself to do
And incidentally document the istall of a HA LXC based on debian
Also i am aware i probably over engineered this - after i had done this i realized postfix as shipped in PVE and PBS was attmepting to contact a variety of servers in my network based on DNS - i still haven't figured the logic out for that.... maybe all i needed was a relay and an MX record (and no config on PVE and PBS?)
Only reason vhdx import wouldn't work is becuause i mis-documented the command as qm import.. when it is qm disk import
I could easily have imported the vhdx all along.... learn my lesson padawan
original gist content
Random Notes (stream of real-time conciousness) on Migrating Windows Server Core 2019 based AD domain controler
tl;dr it worked - but due to an issue with the disk I had to use the synology bare metal restore into the VM and then use the disk shuffle approach i outlined in the parent gist to this one