Storage and Deduplication

Unusual performance drop detected in pruning for following deduplication databases: [GDSP_ALL_<Servername_8]: due to increase in (CommServe Job Records to be Deleted) - Check details in: http://backupserver:80/webconsole/reportsplus/reportViewer.jsp?idstringIf i check the report, it’s grown from 0 to 12399 commserve job records to be deleted from 9’th january to today the 18’th.….However, this media-agent is a media-agent that is spending half it’s life completely offline and shut down, and it has been shut down since the 9’th, and powered on again today, so i assume this is expected behavior, but because i have not seen this message before, i figured i’d check with the hivemind first :-) Software version is: 11.24.78

Oracle Archive Log Backups are backed up to a storage policy.  The primary copy’s retention is configured for 30 days with 0 cycles.  The Data Retention Forecast and Compliance Report shows the Archive log is required by the RMAN Full backup which has been aux copied from a primary copy (Disk Library) to a secondary copy (Tape Library).  The Secondary Copy retention is 7 years. I would like for the Log Backup on Disk to follow the primary copy retention of 30 days and expire once 30 days have been met, however it is not expiring since itis required by the Full backup on tape with the longer retention. I had a similar issue with SQL backups where the log backups were not expiring because the log backups were required for the SQL full that had been aux copy to tape with a long 7 year retention.  The setting to correct this behavior is under Storage → Media Management Configuration → Data Aging → and disabling <Honor SQL Chaining for Full jobs on Selective copy>.Does anyone know if

Tape library is not displayed correctly, only the drives are seen individuallyWhat will be the problem?

Hello,  I have Oracle backups running which are scheduled through RMAN which occasionally fail with the following error code: “Error Code: [82:177] Description: Timeout while waiting for a reply from DeDuplication Database engine for Store Id [X]” Steps that I have taken to troubleshoot the issue: Dedupe engine is active and running Created a one way persistent tunnel from the client to the commserve and Media agentsas suggested by another thread pertaining to the same issue “ERROR CODE [82:172]: Could not connect to the DeDuplication Database process for Store Id [xx]. Source: xxxx, Process: backint_oracle | Community (commvault.com)”Our Q&I times across the board for our media agents are quite high. For this particular engine the times are 6,416 microseconds (307%). I believe the ddb is not running on SSD, but regular disk. Is it possible that this could be causing the above error? If not I’m not sure what else could be the reason for this. 

Due to the fact of changing the backup storage infrastructure, I only want to change the storage policy.Our former strategy was to have a spool copy and to aux copies - one to NAS and one to LTO.This was done due to the fact that we had a performance/backup time issueWe solved this by direct attached SSDs to the backup server.Now I want to set a retention to the primary copy and delete the no longer needed Aux copy to NAS. This points also to the same storage (the local SSDs) and wastes the need space on this.If I want to change the retention on the primary storage policy I get error shown in the screenshot and changes are discarded.I don’t know where to find these settings (Archiver retention rule and “Onepass”) I have never set a archiver (retention rule), we are not using archiving  

There is a related topic regarding my question but I don’t feel it was adequately answered:  Essentially there is a conflict in documentation regarding versioning and how object locking works. Firstly the public cloud architecture guide for AWS states that bucket and object versioning is not supported in Commvault (p. 85 of AWS Cloud Architecture Guide - Feature Release 11.25 (commvault.com))However, when enabling object locking in AWS, versioning is enabled by default on the bucket and objects - it is by design. Under ‘Enabling S3 Object Lock’ section (https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html) it states that versioning is enabled.So if Commvault doesn’t support versioning (and will result in orphaned objects), how can Commvault support object locking, which also enables versioning?We have also tested this in the lab and can confirm when object locking is enabled, we do not see any data prune from the cloud library. We have run the workflow, store

Similar to this article, I'd like to show simple queries to retrieve DDB information from CSDB.Important note: do not modify CSDB data and modules, just use READ operations only.Also pleaseTo keep your activities safe you need to keep uncommitted read from any table as one of the following techniques:use CommServ -- just for convenience-- place the following at the top of any queryset transaction isolation level read uncommitted;-- place with(nolock) statement in each table referenceselect * from APP_Application with(nolock)Most of the DDB information is stored in tables started with Idx, for configuration of DDB is stored mainly the following 3 tables, first one is for DDB information, latter 2 for partitions:select * from IdxSIDBStoreselect * from IdxSIDBSubStoreselect * from IdxAccessPathTo combine this, including which MA is in use for each partition, like the following:select store.SIDBStoreName as 'DDB Name' ,apc.name as 'MediaAgent' ,ap.Path as 'Partition path'from Id

Sharing this information Proactively.Issue:After upgrading to 11.20 or higher, NFS Mount Paths show offline in the Comcell GUI with the error "The mount path is marked offline due to nfs local_lock option set in mount options"CVMA.log on the Media Agent will show:102415 1901f 01/13 19:06:53 ### WORKER [96/0/0 ] :CVMAMagneticWorker.cpp:6992: Marking mount path \[<mount path>] mounted on dir \[/commvault\_fas\-syd\] offline due to mount options [rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=170.65.110.200,mountvers=3,mountport=635,mountproto=tcp,local_lock=all,addr=<IP Address>]Cause:Checking the NFS mount options by running mount -v will reveal the path is not set to "local_lock=none":In earlier releases, it was advised to set local_lock=none as per https://documentation.commvault.com/commvault/v11/article?p=12567.htm. However, 11.20 has enforced the check. This was done due to issues where

The following procedure allows you to safely update Fujitsu Appliance iRMC Password which won't impact operations such as: RHEV-M Hardware failure alerting Important Note - for the HyperScale Appliance\, Commvault leverages the IPMI protocol to monitor the physical hardware by design\, and reports back to Command Center if there is a fault. IPMI - Intelligent Platform Management Interface is a set of computer interface specifications for an autonomous computer subsystem that provides management and monitoring capabilities independently of the host system's CPU, firmware and operating system. The following procedure are applicable for the following use cases: Updating iRMC Password for security purpose Resetting iRMC Password if it is forgotten or lost IPMITool is installed at the Guest OS level (Redhat OS)Updating iRMC Password First, you will need to establish a SSH session onto the Guest OS (HyperScale RedHat 7.#) Then input the following command: # ipmitool user set password