I. If you are running a Release 9.0 CommCell then please follow these auditing steps... 2

Transcription

1 June 29, 2011 As a CommVault capacity licensing customer, we are notifying you of the following updated features in the Capacity Licensing Program related to audit reporting. Customers covered by an Auditing capacity licensing agreement are bound by periodic reporting procedures to validate all licensed CommCells are within the licensed usage levels and initiate required reconciliation of excess usage. In an effort to automate and streamline the Capacity Licensing Program we have introduced several new options within the Simpana 9.0 platform to help automate the reporting process. This document provides new guidelines and recommendations for those users. We would like to remind all Simpana 9.0 CLA customers currently in an Audit capacity licensing agreement that a reporting-free option exists in the Capacity Licensing Program which utilizes the automatic capacity measurement and alerting controls in the Simpana 9.0 platform. An option exists for CommCell IDs to be provisioned with the licensed quantity and no expiration windows will be applied to the licensed software. This option will eliminate the need for periodic reporting and reconciliation; rather the customer can track usage using the software capacity measurement tool and alerts and contact the account team when new capacity is desired. Please contact the CLA-Help alias for more details on that program. Please forward any questions to CLA-Help@Commvault.com. Thank You, CommVault Licensing Team Recommendations I. If you are running a Release 9.0 CommCell then please follow these auditing steps Release 9: Detailed Usage Reporting from the License Summary Report... 2 II. If you are running a Release 8.0 CommCell then please follow these auditing steps III. If you are running a Release 7.0 CommCell then please follow these auditing steps IV. Data Usage Reporting Rules... 7 Updates to the Data Protection Usage Algorithm... 7 Updates to the Reporting Utility... 8 Reviewing the Output to find Older or Orphaned Policies to Filter... 8 V. Capacity Program Reporting Rules Data Protection Usage Rules Data Archive Usage Rules... 12

2 I. If you are running a Release 9.0 CommCell then please follow these auditing steps. This procedure can be used to measure the active capacity usage on a 9.0 CommCell for sizing or audit purposes. As of 9.0 SP2A (May), new automated reporting options are now available to the user to simplify audit needs. The audit report can be run directly from the CommCell reporting features eliminating the need to run any qscript routines. The CommCell License summary report now includes an option to report on the capacity usage levels, which include the client level details. The user can create a scheduled report job to run automatically at each defined audit period and direct the report output to an addressed to the CLA help alias. The report action details are outlined below or please follow this BOL link for guided steps: (Create/Template/Schedule a license summary report for CLA Usage ) The License Administration / Capacity Dashboard view shows a summary of active usage at any point in time. This is active on all 9.0 SP2A CommCells. The graphical report view can be saved as a report file and used for audit purposes. Please follow the steps outlined under this books-on-line link (Release 9.0 Capacity License Dashboard) to monitor the active levels at all times. Release 9: Detailed Usage Reporting from the License Summary Report Determining the current CommCell actual usage is now available directly off the CommCell License Summary report. When you select the include Capacity Usage option on the summary report it will automatically include the detailed current usage report in the output. This new enhancement was introduced with 9.0 SP2 (May 2010) and it replaces the need to run the external reporting script on a 9.0 active CommCell. Please note that a special reporting option exists in this report to include Imported Jobs (EDC) in the output. This is used with the External Data Connector use-case when third party backup server jobs have been ingested for reporting purposes. Clients/jobs associated with the EDC process are normally imported in the deconfigured state (license-free) and, by default, those jobs are excluded from capacity usage reporting. In this special use-case it can be quite helpful to use the capacity report to help size and scope a site level migration Page 2 CommVault Capacity Licensing Program: Audit Reporting Recommendations

3 opportunity after the external clients and job details have been imported into the CommCell. This option is designed to over-ride the normal reporting filter and include the usage details on the deconfigured clients; this option should not be used with a CLA audit report. In all other normal CommCell operations that option should be left blank. Page 3 CommVault Capacity Licensing Program: Audit Reporting Recommendations

4 II. If you are running a Release 8.0 CommCell then please follow these auditing steps. This procedure can be used to measure the active capacity usage on an 8.0 CommCell for sizing or audit purposes. The output text file will provide a detailed listing of the client policy usage charges including a summary of the Cell-level usage charges at the bottom of the report. Begin by downloading and applying update or 8.0 SP6 1 to the CommServe machine; this update can be downloaded from the Maintenance Advantage or Automatic Updates site. The update installs the current qscript reporting utility to the match the latest algorithm and filter features. After installing 8.0 SP5 and update 19650, the user should log onto the CommServe windows server, open a command prompt and follow these simple steps to produce the usage report. 1. Change to the <BASE> directory under the Programs\Simpana (or OEM equivalent) 2. Login using the Qlogin command, specify an CV Administrator username and password Using the Qlogin command, you can start a User login session, removing the need to log in for every command. You will need to sign-in using a CommCell Administrator user profile. If you are running on a Windows2008 server you may need to run the command line session with the Windows Administrator privileges. Once the Qlogin command is successful, the login session for all computers remains valid until you explicitly log out using the Qlogout command. This is true for all command sessions, not just the one for which the login took place. If you have an error logging in, then you may already have a session open. Try using the Qlogout command and retry the Qlogin sequence. 3. Use the qoperation execscript command to run the reporting routine and create the results output file. This script is used to summarize the overall current data usage across the entire CommCell. The report includes Data Protection and Data Archive usage for the and Core categories. qoperation.exe execscript -sn CommCellAverageDataTransfer.sql >> F txt The reporting logic will analyze all the active jobs on file CommCell and produce a summary report for current capacity usage under the Data Protection and Data Archive rules based on each unique, active Client\Agent\DataSet\Subclient policy within the CommCell SP6 was released June 20, 2010 and this includes the prior update. Page 4 CommVault Capacity Licensing Program: Audit Reporting Recommendations

5 qoperation.exe execscript -sn CommCellAverageDataTransfer.sql si HideClientName >> F txt An additional option is now available to hide the client name property in the output results. When this option is set the client name field will contain XXX. This can be used with security conscious customers who wish to hide the common display name of the client from the job results output. To engage this feature, add the -si HideClientName option to the script input. The results will be posted to a text based output file as designated by the qscript command. We recommend that users should name that file with CommCell ID and the run date to help tracking and auditing. Enter your command line script with the correct qualifiers and it will run and produce the output file. The output file now lists the JobID to identify the job that qualified for usage measurement based on the rules, only FULL or SYNFULL jobs are analyzed and included in the report for Data Protection, and the results now use terabytes (TB) as the unit of measure. 4. Please send the output file as an attachment to the CLA Help alias as instructed in the audit notice. The output file is now standardized for both versions and it will only list the policies /jobs that qualified for the usage charges in the report summary. In addition, the output now presents the usage in Terabyte (TB) units so the user can immediately read the results. This text file can be opened with Excel to allow sorting or filtering of the detailed results for further review. Page 5 CommVault Capacity Licensing Program: Audit Reporting Recommendations

6 III. If you are running a Release 7.0 CommCell then please follow these auditing steps. The 7.0 CommCell environment does not support the qscript framework so direct reporting is not possible within the CLA measurement framework. The recommended reporting approach is to stage a new 9.0 SP-Latest (empty) CommServe instance, upload a recent 7.0 CommCell DR backup instance collected from the customer and use the CommserveDisasterRecoveryGUI.exe tool to import that 7.0 database. The tool usage methods are available on this BOL link ( CommserveDisasterRecoveryGUI Tool ). After that step, the dbupgradeui.exe procedure should be used to upgrade the system to the 9.0 level. The tool usage methods are available on this BOL link ( 9.0 DB_UpgradeUI Tool ). Follow steps 1-4 from the BOL methods. This procedure will produce a staged-9.0 CS using the 7.0 operational data. The user can start the services and run the standard CLA reports using the 9.0 methods listed above. Typically a Virtual Machine (Windows Guest Host) can be used with this method to support the staged-9.0 CS instance. We would recommend 7.0 users contact the Support desk for assistance before they try this procedure the first time. Since many existing customers are evaluating the benefits of a conversion into the CLA licensing program in combination with upgrade plans to 9.0, this 7.0 auditing process may only need to be employed once for the initial sizing /quoting process. The existing 7.0 job summary reports will not provide an accurate answer for CLA quoting. Page 6 CommVault Capacity Licensing Program: Audit Reporting Recommendations

7 IV. Data Usage Reporting Rules Updates to the Data Protection Usage Algorithm The Data Protection usage algorithm now assesses the LAST Full or Synthetic Full backup job per unique policy (vs. prior MAXIMUM/90 day rule). This produces a more accurate measurement of the active Data Protection levels within the environment and allows a user to correct mistakes for example, if a rogue backup job increased 50% in size because users dumped some contraband data onto a file server, the Administrator can adjust the backup policy filters and run a new Full job to skip that data and reset the usage measurement assessed on that policy. The algorithm will now exclude any client or agent policy that has been deconfigured which releases the license and prevents the ability to run new backup or archive jobs. Additionally, the exclusion filter will now apply to any subclient policy which has the backup or archive service disabled. This filter can be used to disqualify older clients or subclients that were configured for a special one-time use or apply to older clients that have been deconfigured. If the backup services are re-enabled or the client/agent is reconfigured for new use then it will be included in the usage calculation. After disabling the policy, you should run the data aging cycle once to see the measurement report reflect the filter. Any existing backup job or archive job associated to those de-activated policies will remain available for restore until that job is normally aged out of the Storage Policy. Use this option to filter out older clients that are obsolete and no longer actively backed up in your Protection schedule. A Release 9.0 CommCell now offers simple and convenient new options to deconfigure a client or agent policy from a right click option. See link: (Deconfiguring / Releasing Licenses with 9.0 CommCells). Page 7 CommVault Capacity Licensing Program: Audit Reporting Recommendations

8 Updates to the Reporting Utility The utility now analyzes both the Data Protection (Backup) and Data Archive usage measurements for the entire CommCell within a single run/report. The reporting procedure no longer requires any specific date ranges or extra arguments. This change simplifies reporting. Reviewing the Output to find Older or Orphaned Policies to Filter The output from the capacity detailed report will provide the line item usage charges which are accumulated and displayed in the dashboard view. The report provides a summary of the categorized usage in the header and each line in the report will detail the unique client/agent/dataset/subclient policy (App ID combination) along with the usage value, the JOB ID and the class attributes. This report is quite useful in identifying older clients that are no longer actively run but remain configured for use and roll-up into aggregate usage charge. The report is designed to allow the administrator to review the Page 8 CommVault Capacity Licensing Program: Audit Reporting Recommendations

9 JOBID listing column to identify JOBID sequence numbers from much earlier operational periods. In many cases, that cans distinguish a client that is no longer run or was created for a one-time need. The Administrator can investigate those client policies and potentially deconfigure the client/agent or disable the action on the subclient to remove them from the usage charges. This affords the administrator with a simple and easy housekeeping method to keep the active policy configuration in check and avoid unnecessary usage charges on migrated or obsoleted clients. Core Backup Size: GB Backup Size: GB Core Archive Size: 6.53 GB Archive Size: GB Job ID Job Type Client Agent Backup Set Subclient Storage Policy Job Size Deduplication Secondary Encryption Backup accord Linux File System defaultbackupset default Bronze Sandbox 1.47 GB Yes No Backup appweb01 Windows File System defaultbackupset default Gold General Data GB Yes No Backup appweb02 Windows File System defaultbackupset default Gold General Data GB Yes No Backup Core archiverex Exchange Mailbox MB group1 Grp1 Silver Compliance 7.89 GB No No Backup Core archiverex Exchange Mailbox MB group2 Grp2 Silver Compliance 3.21 GB No No Backup BXman Linux File System defaultbackupset default Gold General Data 2.06 GB Yes No Backup bes01 SQL Server defaultbackupset default Gold General Data 1.79 GB Yes No Backup bes01 Windows File System defaultbackupset default Gold General Data GB Yes No Backup bes02 Windows File System defaultbackupset default Gold Compliance GB Yes No Backup beuhler Windows bit File System defaultbackupset default Gold Compliance GB Yes No Backup Core billsys Solaris File System defaultbackupset default Silver Compliance GB No No Page 9 CommVault Capacity Licensing Program: Audit Reporting Recommendations

10 V. Capacity Program Reporting Rules Data Protection Usage Rules Data Protection usage is measured based on the amount of active protection policies in the CommCell. The measurement summarizes the size of the last active FULL or SYNTHETIC FULL job for each unique, individual active client/subclient policy within the CommCell. A unique, active client policy is defined as the combination of the Client/BackupSet/Agent/Subclient otherwise referred to as the APP-ID global unique identifier (GUID). The measurement is based on the entire CommCell and it is calculated in Front-End -TB units. Each active backup client/subclient policy is checked within the usage algorithm. Only the Last Full or Synthetic Full backup job applies. If a client is no longer actively used create new backup jobs then it should be deconfigured or marked disabled to avoid usage charges. to The cumulative usage charge is assessed at the whole CommCell level and reported in the Dashboard view. Jobs may be classified under the or Core rules depending on the feature options employed on the policy. All active policies apply there is no time range applied. Page 10 CommVault Capacity Licensing Program: Audit Reporting Recommendations

11 The following table summarizes the core usage measurement rules and filters applied in the Data Protection CLA licensing program. Data Protection Usage What usage do we measure? What makes usage increase? Summary of the Incremental growth in the overall data set Last Full or SFull that the client backup policy protects will job for each increase the size of FULL/SFULL job, unique active increasing the usage figure backup policy Deploying new clients or subclient policies on the entire against new content sources will increase CommCell the usage figure Active backup clients only enabled for backup services What makes usage decrease? If the source data is deleted or archived from a client, then typically the next Full or SFull job size will show a decrease in DP usage. Deactivating/ deconfiguring clients, this will release the client license and all subclient policies under that client will be excluded from the measurement Deleting a subclient policy, yet retaining the backups will also exclude those jobs from the measurement. Deactivating the subclient by disabling the backup service will also drop it from the measurement service, it if it enabled later it will apply to the measurement Deleting the LAST Full or SFULL backup job can reduce the usage slightly if the prior FULL was incrementally smaller. This can be useful if a random FULL spiked in size. What do we exclude in the measurement rules? Multiple instances of same backup job across different copies in the Storage Policy made with AuxCopy; we only measure the LAST FULL or SFULL job, we do not consider any multiple copies In the event that the same subclient policy is repeated over two BackupSets we only analyze the largest (this eliminates double counts when you run redundant Full jobs for compliance reasons) Jobs from deconfigured clients or agents3 (When the license has been released. If the client is reconfigured for new backup operations then it will start counting again.) Jobs from deleted subclient policies; the backup job is retained for restore but the subclient is no longer available for new backups Secondary, deduped SILO Backup Jobs which are part of the CDSO option. In this case the original backup job is charged, we exclude the consolidated /secondary SILO backup jobs. All Legal Hold jobs, these jobs are charged as Data Archive capacity. Content Indexing / Content Director jobs are excluded Imported foreign jobs which reflect jobs that are actively managed in other CommCells (GRC option) or 3rd party jobs from the External Data Collector EDC (these jobs qualify as readonly, deconfigured clients) Combined backup/archive subclients which employ the Archive-Add-in option are classified as archive jobs and will be reported under the DataArchive capacity. 3 A deconfigured client will release the license and exclude its jobs from the CLA measurement process. As long as the actual client is not deleted, those jobs will remain active in the Storage Policy for restore needs. If the client is enabled (reconfigure = license is reinstalled) so it can run new backup jobs then it will automatically count against the CLA measurement. We suggest using this method when a client/dataset is migrated to a new server, deconfigure the original client and reinstall the client on the new server. This will avoid double counts under the CLA methodology. Page 11 CommVault Capacity Licensing Program: Audit Reporting Recommendations

12 Data Archive Usage Rules Data Archive usage is measured based on the amount of active archive policies in the CommCell. The measurement summarizes the cumulative size of the all active archive jobs, legal hold jobs or content store jobs (objects) currently managed within the Storage Policies in the CommCell. Each archive job will be added to the usage figure although this does not consider the number of copies. The measurement is based on the entire CommCell and it is calculated in Front-End -TB units. Each active archive client/subclient policy is checked within the usage algorithm. We add up the size of each Archive job (independent of number of copies). If a client is no longer actively used to create new backup jobs then it should be deconfigured or marked disabled to avoid usage charges. The cumulative usage charge is assessed at the whole CommCell level and reported in the Dashboard view. Jobs may be classified under the or Core rules depending on the feature options employed on the policy. Page 12 CommVault Capacity Licensing Program: Audit Reporting Recommendations

13 The following table summarizes the core usage measurement rules and filters applied in the Data Archive CLA licensing program. Data Archive Usage What usage do we measure? Total size of all active archive jobs on the system All Legal Hold jobs, these jobs are charged as Data Archive capacity All Content Store jobs All Content Archive (Archive- Add-on) clients - last cycle jobs What makes usage increase? Each new archive job will incrementally add to the overall total Data Archive TB usage figure What makes usage decrease? Archive jobs that age off or that are fully deleted are no longer active and are excluded from the measurement. Deleting a subclient policy, yet retaining the archive job will also exclude those jobs from the measurement. Deactivating the subclient by disabling the archive service will also drop it from the measurement service, it if it enabled later it will apply to the measurement What do we exclude in the measurement rules? Multiple instances of same archive job across different copies in the Storage Policy made with AuxCopy Jobs from deconfigured clients (disabled for new Archive services) Secondary, deduped SILO Backup Jobs which are part of the CDSO option. In this case the original archive job is charged, we exclude the consolidated /secondary SILO backup jobs. Imported foreign jobs which reflect jobs that are actively managed in other CommCells (GRC option) or 3rd party jobs from the External Data Collector EDC (these jobs qualify as read-only, deconfigured clients) Content Indexing or Content Director jobs Please note that 9.0 SP2 introduced a change in the Application Size reporting algorithm for jobs that backup/protect file environments with sparse attributes. File System backup jobs run after applying SP2 will now report the reduced or sparse size in the job details. This change is critical in systems that employ backup and archive strategies since archived stub files use the sparse setting. This change ensures that customers can reap the benefits of using an integrated backup and archive strategy to contain the overall usage charges on the backup environment by frequently archiving off older data (reducing the active size of the production store/backup size) to more cost efficient locations. Page 13 CommVault Capacity Licensing Program: Audit Reporting Recommendations