Step 0: Before the Redeploy
Before you so much as glance at an upgrade button, ensure your backup monitor is as quiet as a library at midnight. No active backups should be running—otherwise, you’re asking for trouble. Wait it out. Those backups are your safety net.
Likewise, make sure all your credentials are saved before starting the upgrade. Record your root username and password, and double-check your “Users” menu. If you’ve integrated an identity provider or customized settings, save those details too. Next, prowl through your general settings. Is a proxy configured? Jot it down! Using a custom SSL certificate? Guard those CRT and key files with your life. You’ll need to reapply them post-upgrade.
Here’s the unbreakable rule: Never, ever upgrade without an escape plan. In this upgrade saga, your snapshot is your golden ticket. Head into the Azure Portal, find your beloved N2W server, and create a snapshot of your data disk (not the Marketplace’s volume; you want your unique data). As for the approach—creating a new resource group for the new install is optional but highly recommended. Keeping environments isolated wards off confusion and gives you a safe fallback if disaster strikes.
Bringing Your New AMI to Life
With your snapshot tucked safely away, it’s showtime. Deploy the latest N2W AMI from the Azure Marketplace. Double-check you’ve chosen the correct resource group—otherwise, your precious data disk may play hide and seek.
When configuring your virtual machine, don’t let Azure’s defaults steer you astray! The username must be cpmuser (all lowercase), not the generic suggestion. Set up the root volume to mirror your previous machine, replicate the networking configuration, and—here’s a big one—enable system identity. This allows your VM to access the necessary permissions for backup and recovery.
Roles and Permissions
Ready for some Azure magic? Head to the N2W support website, grab the recommended permissions documentation, and create a new custom IAM role by importing their JSON directly. Don’t skip this! Assign it to your subscription, add a version tag, and let Azure propagate it through the digital ether.
Be patient—roles in Azure can be slow to appear (think of it as brewing a fine cup of coffee). Once visible, assign the role to your new VM. Only proceed when you see the role listed or your VM will be powerless.
Final Steps
At last, it’s time for the configuration wizard. Grab your VM’s IP, load it over HTTPS (brace for the self-signed certificate warning), and begin entering your resource ID. Choose the correct license option—if you’re upgrading, you already have one. Pop in your credentials (same as before), and you’re on your way to a fully upgraded N2W server.
With this methodical approach, you’ll tame the AMI upgrade and keep your data—and your sanity—safe. Now, go forth and upgrade like the cloud superhero you are!
