Orchestrator ships with this scope, and anything discovered lands in it first. To decide what each team can view and work with, Administrators place items into further scopes.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains Default Scope in context, with comparison tables and the common traps.
Terms in this definition
- Orchestrator
Software, Kubernetes being an example, that looks after large numbers of containers throughout their life by scheduling, scaling, repairing and updating them.
- Scope
Where an access or policy assignment takes effect. It can be set on a single resource, a resource group, a subscription or a management group, and settings flow down from higher levels.
- FIRST
A DAX function available only inside visual calculations. It fetches the value at the start of one axis of the visual's matrix, which makes it handy for comparing each point with the first; its opposite is LAST.
- View
Shows a system through one chosen group of related concerns. No view is generic; each one is tied to whichever architecture it depicts.
Related terms
- default lab group
A lab group that an Administrator creates in a DataLab belonging to a scope other than the Default Scope. It comes preselected and boots ahead of other lab groups; Plan Authors and Plan Operators may test with it but cannot change it. Lab groups in Default Scope DataLabs do not count.
- Orchestrator scope
Decides what people holding a role are able to see in Orchestrator, for example credentials, DataLabs, YARA rules, template jobs, inventory groups, plan steps and recovery locations. A fresh install has just the Default Scope. Unrelated to scopes in Azure management.