At Aspyn Information Services, we frequently assist our clients in optimizing their backup strategies to ensure seamless data protection. Recently, while deploying Veeam Backup & Replication 13, our team encountered an interesting challenge regarding the management of physical machines.
When working with Protection Groups in Veeam 13, the workflow you choose when creating backup jobs can cause some interesting behavior! Here is the recommended best practice for ensuring your backups run without a hitch.
The Challenge: Protection Groups vs. Individual Computers
In Veeam 13, you have the option to add individual physical machines to your inventory, or you can manage them via Protection Groups. While it might seem intuitive to add a specific machine directly, doing so when that machine is already part of a Protection Group can lead to configuration conflicts and backup job issues. Protection groups can be scanned periodically to ensure the group members are ready for backup with no issues.
The Recommended Workflow
To keep your environment stable and your backups predictable, please follow this standardized approach:
1. Set Up Your Protection Group
Ensure your workstations are correctly organized within their respective Protection Groups under Inventory > Physical and Cloud.
These groups are designed to handle the heavy lifting of discovery and status monitoring. By default, your Protection Group is set to rescan every Friday at 5:00 AM. This rescan process does not trigger a backup; rather, it checks for agent updates and verifies that the client has a healthy connection to the backup server, ensuring the machine is ready for its next backup task.
2. Creating Your Backup Job
When you are ready to create or modify a backup job, navigate to Home > Backup Job.
Select Veeam Protection Group
The Key Step:
* When selecting the source for your backup job, always select the Protection Group first.
* Once the group is selected, use the dropdown menu to highlight the specific PC you wish to back up.
* Important: Avoid selecting the individual computer directly from the “Individual Computer” list if that machine is already managed by a Protection Group. Choosing the machine individually while it is also managed by a group can cause synchronization issues within the Veeam database.
By always pointing your backup jobs to the Protection Group, you ensure that Veeam maintains a single source of truth for the machine’s configuration and agent status.
Proactive IT Management
Simple adjustments to your backup configuration can save hours of troubleshooting down the road. At Aspyn, we believe in getting the details right the first time so our clients can focus on what they do best: running their business.
For more insights on keeping your IT systems running smoothly, check out our recent posts on maintaining efficient development environments (https://aspyn.com/blog/) and our guide to virtualizing physical servers (https://aspyn.com/2026/04/08/
Need assistance with your Veeam deployment or looking to audit your current backup strategy? Contact Aspyn Information Services for affordable Managed IT Services, IT Support, Custom Scripting, and Process Streamlining!
