Hello and welcome to this. The second part of a very brief look at some of the exciting new features of DP A version 6.2. In part one, we looked at the administrative logins licensing the unified dashboard and the new object search. In this part, we shall consider how we may more easily generate a support bundle. We look at enhancements to data domain analysis and reporting a great leap forward in the use of smart groups and just one or two tweaks to the use of properties dialogue. The all important supporting documentation is as usual available from the link shown including the release notes. As in part one, please take a moment to pause and review the extensive list of technical differences and new features included in DP A 6.2.
In earlier versions of DP A satisfying requests by E MC support personnel for DP A configurations may have required downloading and using a rest client. The administrator may have been unfamiliar with the operation and use of rest requiring perhaps lengthy interaction between support and the user. Indeed, the use of rest clients may not always have been supported by corporate policy in version 6.2 the need for a rest client has been eliminated for this purpose by providing a single button click from within the DP UI. This also removes the need to log on to the DP server host. So let's now take a quick look at this much requested feature which is now available through the admin system, configure system settings, server path in the UI on clicking the generate support bundle button, you will be asked to where the bundle is to be saved and a zip file of the required files will be saved to that location.
This may then be added to the service request. Please note at present the generate support bundle collects that data previously available only through the rest API A future service pack will incorporate inclusion of the remaining basic log collections thereby making this facility a one stop shop for collection of the standard support requirements. The advent of DP version 6.2 has given us the opportunity to introduce a much deeper dive into the internal functions and activity of a data domain object, specifically client aggregation and aged file analyses. This however comes with a resource overhead which is needed to process the huge amounts of data generated and which may not be required by all users.
Therefore, a separate tool, the data domain data processor tool has been created running this tool places a data collection burden on both the data domain and the DP application server and therefore should not be run as a matter of daily routine and probably should only be run when concerns are raised regarding the efficiency of operation of the data domain. With special regard to the logical space occupancy on the data domain for aar networker net backup and a man the installation and use of this tool is fully documented in the installation and administration guide, but it is appropriate to fin out just one or two of the additional reports which may be generated thee reports will only be visible in the menus. Once the tool has been run, let's first look at under resource utilization storage, the data domain file distribution by count when run, this will give a representation of files by age.
This information could be invaluable to determine if the data domain contains stale data or in comparing the file utilization profiles of several data domains. Another most useful report facilitated by the data domain data processor tool is the clients with low D dupe ratio where we can display and further investigate those clients which are presenting a lower than expected de dupe capability. The innate capability of allowing users to drag and drop objects into logical but static groupings was further improved in DP six to introduce the concept of the smart group in DP 6.2. This has been further enhanced due in part to use a request to provide multi level smart groups creating multiple layers of child objects within a single smart group.
This goes further permitting the user to configure the fields used and the type of objects created without limiting the number of configured levels, tracking of changes to smart groups is also performed if the enable history feature is switched on this feature along with the application of charge back and protection policies to different levels allows the user to run historical reports against the smart groups. Let's take a brief overview of what this looks like. OK. So first of all, let's create a static group called my smart groups. And under this, we shall select to create a smart group here. You will see that. In addition to the single level smart group, we now have the multilevel option in selecting configure smart group level, we may select a report forming the basis of the smart group. And here we shall select backup clients configuration report and apply this to a scope.
Here, we shall select the EMC network backup service and a time period of now as we are going to run this on demand. In this case, in the departure from the single level smart groups, we can now select via the check boxes, multiple report fields, selecting the client and the OS. On reviewing the smart group, we can see that the client field has been allocated tree level one and the OS as tree level two. But this may be changed by using the move up, move down buttons to change the ordering of the folder. The field type may be modified by employing the appropriate drop down. But in this case, we shall stick with the backup client type with the linked field of server returning to the properties panel. We'll give this smart group a meaningful name of all clients by OS and a frequency of on demand or indeed a user selected schedule. The enable history is set to off in the inventory on expanding our newly created all clients B OS smart group.
This shows that we have both Linux and Windows clients available. We may now report against these smart groups or extend the operation further by applying different policies to each of the discovered sub groups. Let's enter policies, charge back policies and apply the silver policy to our Linux members and the gold policy to our Windows members on doing so. We may now run a charge back summary report against our smart group and this will show the split of charge back B OS type. You should now see that by using the multilevel hierarchical smart groups, this will facilitate creation of some quite sophisticated reporting structures. And finally, the user properties dialogue has a redesigned appearance under DP version 6.2. This now splits the preferences tab into two components, the preferences and the new report preferences.
The effect being to reduce the apparent complexity and size of the previous panel under report preferences. This now contains the many parameters the user may specify for their own reporting requirements. The preferences tab now shows the parameters for the general viewing of DP including the tree lo depth. That is the displayed expansion of the scope and the home group that is from which point in the inventory, the expansions will be shown. Thank you for watching.
