Properly organizing your devices ensures that your backups are easy to find and that your alerting is targeted to the right teams. In the IronDiff local setup, this is managed through Agent Sites, Sites, and Groups.
Agent Site (Identification)
In Section 2 of the local web interface setup, you will find the Agent Site field.
The Agent Site is a unique identifier for that specific Docker container. If you deploy multiple IronDiff agents across different physical locations or client networks, the Agent Site name helps you recognize which agent is performing the backups in the Cloud Portal.
- Example:
Westminster-DataCenter-01,London-Office-Edge.
Organizing with Sites (Buckets)
In Section 3 of the device assignment process, you assign each device to a Site.
Sites act as “buckets” in the Cloud Portal. When you view your backup history, devices are grouped by these Sites. Most commonly, each Site represents a customer or company whose devices you manage.
- How it works: A device assigned to Site “Acme Co” will appear in the “Acme Co” bucket in your dashboard.
- Best Practice: Use Sites to represent individual customers or business entities. Each customer’s devices stay grouped together for easy access.
Labeling with Groups (Tags)
Also in Section 3, you can assign devices to a Group.
While Sites are the primary organization bucket, Groups act as Tags. This allows for a second layer of filtering and metadata.
- How it works: If you have multiple firewalls across different customers, you might put them all in a Group called “Firewalls”. In the portal, you can then filter by the “Firewalls” tag to see their status across all customers.
- Example Groups:
Core-Switches,Edge-Routers,Branch-Office.
Workflow Summary
- Identity: Name your Agent Site (Section 2) so you know which Docker instance is which.
- Bucket: Assign devices to a Site (Section 3) to place them under the correct customer or company.
- Tag: Assign devices to a Group (Section 3) for easy filtering and categorized alerting.