Hello. As per support case 07787737 have been advised to request enhanced and scalable reporting int he Orchestrator suite. As part of our managed service DR testing is a legal requirement and suitable evidence has to be supplied. At the moment the out of box reporting offering is insufficient and we require a Monthly round up of all tested and recovered workloads so we can add this to our monthly service reviews to the customer. Daily reports from the plans is too much.
As Veeam One is bundled in albeit stripped back I would have expected the reporting features to be available but they are not and we will have to code our own evidence collection which will be a pain.
Additionally the documentation for Orchestrator, a convoluted and bemusing product in itself, is a maze or back and fore between multiple documents none of which answer the basic questions I have come across in order to get it to work. Please, Please sort this out, it needs more detail on each requirement and a flow chart to creating a plan, step by step.
Many thanks
-
- Service Provider
- Posts: 23
- Liked: 1 time
- Joined: Jan 31, 2018 2:45 pm
- Full Name: Jason Field
- Contact:
-
- VP, Product Management
- Posts: 1571
- Liked: 422 times
- Joined: Jan 01, 2006 1:01 am
- Location: Prague, CZ
- Contact:
Re: Feature Request: reporting in Orchestrator
Hello,
Thank you for the feedback and in fact I agree with you about the documentation; currently it is more of a reference manual for configuring VRO, and doesn't contain the workflow- or task-driven instruction I believe you are looking for. A full review of the User Guide will be conducted for the major release later this year and we will be adding those elements. In the meantime I hope we can help with your questions here in the forums!
VRO reporting is focused on checking and maintaining Recovery Plans; every day readiness checks confirm RPO is achievable, for example. The Plan Definition report tracks all plan settings and changes.
Additionally there is a full report for every plan execution or test, which produces a comprehensive list of all recovery actions and the result for every VM.
In the current release we don't have any monthly reports, however there is a monthly audit report planned for the next release which will detail all plan actions (tests, checks, executions, malware scans etc) and the outcomes.
Of course Veeam ONE has many very detailed and customisable reports, although you are correct that the 'embedded' version of ONE on a VRO server is used for data collection only. To use the full power of Veeam ONE would require adding license points (as you are an MSP I assume you are using rental licensing)
Regarding the inital configuration of VRO, here are a few bullets -
Thank you for the feedback and in fact I agree with you about the documentation; currently it is more of a reference manual for configuring VRO, and doesn't contain the workflow- or task-driven instruction I believe you are looking for. A full review of the User Guide will be conducted for the major release later this year and we will be adding those elements. In the meantime I hope we can help with your questions here in the forums!
VRO reporting is focused on checking and maintaining Recovery Plans; every day readiness checks confirm RPO is achievable, for example. The Plan Definition report tracks all plan settings and changes.
Additionally there is a full report for every plan execution or test, which produces a comprehensive list of all recovery actions and the result for every VM.
In the current release we don't have any monthly reports, however there is a monthly audit report planned for the next release which will detail all plan actions (tests, checks, executions, malware scans etc) and the outcomes.
Of course Veeam ONE has many very detailed and customisable reports, although you are correct that the 'embedded' version of ONE on a VRO server is used for data collection only. To use the full power of Veeam ONE would require adding license points (as you are an MSP I assume you are using rental licensing)
Regarding the inital configuration of VRO, here are a few bullets -
- The first task is to connect VRO to Veeam Backup servers and other recovery infrastructure such as VMware vCenter, Hyper-V clusters, etc
- This will give VRO an Inventory - groups of VMs that can be added to recovery plans, and target infrastructure that can be used to create Recovery Locations
- As soon as you have some inventory groups, you can create a plan (go to Inventory page in VRO UI, right-click a group and Add to Plan)
- You will only be able to restore to Original VM Location until you create a VRO recovery location - a target for restore (such as vCenter), and all associated settings (such as network mappings)
- Once you have created a plan, and pointed it to a recovery location, and enabled it, your daily readiness checks will start.
- Reports can be run manually or scheduled, and are available in Summary or Full format, and custom subscriptions can be made for specific report types from specific scopes.
Alec King
Vice President, Product Management
Veeam Software
Vice President, Product Management
Veeam Software
Who is online
Users browsing this forum: No registered users and 1 guest