Let’s be real—backing up cloud resources shouldn’t feel like a three-hour jigsaw puzzle with missing pieces. And yet, for many IT admins and architects, the whole process of clicking, selecting, and double-checking every virtual machine (VM), disk, or server can make even the calmest among us want to run for the hills (or at least for a coffee refill).
But suppose we told you that there’s a method to automate all of this, to tag the resources you want protected and let the system handle the rest? There is and here’s how:
Enabling Scanned Resources
Navigate to the “Accounts” section in N2W. Choose the AWS or Azure account you’re working with, and hit “Edit.” Here’s where the magic starts: flick on “Scanned Resources,” choose all the resource types you want included, and save. Congratulations, you’ve set the stage for seamless backup automation. No more hunting for lost VMs or hidden disks—the system’s got your back (literally).
Goodbye, Manual Selection—Hello, Tag-Based Policies
If you’ve ever grumbled about manual resource selection, you’ll love the “Add by Tag” approach. Traditionally, you’d click “Add Resources,” dig up your desired VM, and manually add it to your backup policy. But let’s face it: Who has time for that?
Instead, Cynthia Santos shows us the smart way. Create a new Azure backup policy—call it something memorable, like “Tag Test.” Assign your account and subscription, set your schedule (daily backup? Sure!), and critically, leave the resource selection blank. The brilliance happens with tags, not clicks.
Meet Your New Best Friend: The cpm_backup Tag
Here’s where you trade in your magnifying glass for a magic wand. Instead of manually linking each asset, you slap a tag onto your resource—the cpm_backup tag, to be precise. The tag’s value? That’s your policy name (“Tag Test,” in our example). Apply the tag. That’s it.
You can roll this out across any Azure resource you want: VMs, disks, SQL servers—if it’s in the cloud and you want it backed up, just tag it! The system does the rest, retroactively collecting every tagged resource under the protective umbrella of your backup policy.
Flip the Switch: Enabling Tag Scanning and Automation
Here’s a secret: Tag scanning isn’t automatically enabled (we like to give you the controls!). Head to the server settings, find the “tag scanning” switch, and turn it on. By default, N2W will scan every six hours for newly tagged resources. Feeling impatient? You can trigger a scan immediately and see your shiny new tagged resources appear in your backup targets faster than you can refresh your browser.
Save your settings and watch backup automation unfold. The next time you check your policy’s backup targets, voilà! Every tagged VM and disk is safely under its protective backup shield. If you’ve tagged several instances, they’ll all join the backup parade without you lifting another finger.
Wrapping Up: Tag, Scan, Back Up, Repeat
To sum it all up: ditch the spreadsheets and the endless lists. Give your resources the cpm_backup tag, set your policy, and let the system work its magic. The result? Automated, reliable backups in Azure with significantly less effort and hassle. Now you’ve got time left over—for more strategic work, maybe, or just a well-deserved snack break.
