Storage and Deduplication

Hi,Is there any statistic, maybe in logs, what amount of data is send from storage to media agent during restore? In backup we have “Data transferred on network” but what about restore?I mean - let’s say I’m restoring something from Disk Library or Azure - data in library is deduplicated and compressed. I know that dedupliaction doesn’t matter here, but what about comporession? I believe media agent get compressed data from storage, uncompress it and then send to the client? So size of application will be not the same as the data size taken from storage? How to check it? Regards

My customer just testing Storage accelerator in his environment and has some questions.Scenario 11.36 : Client installed with file agent. SA in place and does its work for weeks. Now the connection to the S3 library failed for some reason.We observed that backups still running but without SA (fall back) over a MA.We also observed that backups do not come automatically back to SA if network connection to S3 lib is repaired.We found some keys in registry which may steer the behavior, but we do not completely understand how the software decided to use the Storage accelerator feature or not.  If we have no connection to cloudlib the two keys are created.The StorageacceleratorAutodisabledUntil key seems to renew all 24 hoursThe StorageacceleratorConsecutiveFailureCount seems to be increased after timestamp StorageacceleratorAutodisabledUntil was reached if “S3 network connection” is down.Max value is 8 . After this count value SA does not try again to use a direct connection to the S3 libra

Is anyone else getting this error message every time their SynFulls run?  11.36.46 I want to say this stuff started happening when we moved from Server 2012 to 2022, but I don’t think that’s my problem.  Windows Server 2022 - CS, MAs, VSA Proxies Every time the SynFulls run, most of them sit there in a Waiting status, yet there is always a single stream that shows Active (some over 24 hours) and always throw this error message, which was supposedly fixed a few MRs ago:Error Code: [19:1926] Description: Some jobs were skipped due to read errors. Will retry after some time. Source: bccmvcs01, Process: JobManager I’m not doing anything special with them.  They are Continuous and do a SynFull every 7 days.  Any help would be greatly appreciated.  I remember when SynFulls would just run, and very quickly I might add, but now they just queue up and eventually finish after a looooong time.  We have 4 MAs - each with a piece of the DDB partition.  Not sure what other details you may need, but

We are evaluating ways to strengthen our backup infrastructure against ransomware and improve immutability. Below is our current environment setup:Infrastructure Setup CommServe + Media Agent  Backup Targets: Primary: Dell EMC Data Domain ( No dedup) Secondary: Auxiliary copy to Azure Blob (Cool ) (De-Dup) Policies: Policy A: 35 days basic retention Policy B: 35 days basic retention + extended retention (Monthly – 365 days, Yearly – 15 months) Exploring Areas for Ransomware ProtectionOn Data Domain to enable immutability.  Compliance lock on storage policy copies Within Commvault   Has anyone implemented Commvault compliance lock along with DD Retention Lock. if yes what are the recommendations. Appreciate your insights, especially around practical challenges

Hi everyone,I have several commcells. On one of them there are “No data available” on the Comcells, Agents, and Client Groups tiles. All other tiles seems ok. Anybody know why and how to fix it?Also, on my other comcells there seem to be no data from january to july for the same three tiles. I guess there is no way to generate the missing data again, but do anybody know if it is a known bug? RegardsGunnar

 Hi Team, We are getting the below error very frequently while running aux jobs. It tells that all device streams exhausted and job will be in pending state until streams become available. Please advise me how to allocate devices streams to avoid this issue.  I have increased Parallel data transfer streams on the Media agent level and Device streams on the Storage policy settings- it does not seems to be helping. Please advise me how to define stream values and what are the things we should consider when increasing or decreasing the streams. How it works?  

Hi Team,After upgrading to Commvault Platform Release 11.40.13, we observed an issue in the Backup Job Summary Report. The report now shows an additional status – “Completed without Backup.”On review, most of the jobs under this status belong to SQL servers with databases configured in Simple Recovery Model, where TLOG backups are skipped. Although the jobs complete successfully, they are being flagged under this new status, which is impacting the SLA completion percentage in reporting.We would like your guidance on the best approach to handle this: Exclude “Completed without Backup” jobs from the Backup Job Summary report so they don’t affect SLA metrics. Alternatively, create separate schedules for databases configured with Simple Recovery Model (without TLOG backups). Kindly suggest which approach would be recommended or if there is a Commvault-supported configuration change to address this reporting issue. 

Hello guys!we have 5 XL Linux Media agents, and all of them have 2 DDB Partitions in the size of 5.9 TB. both of the DDB partitions are configured in RAID 1  when trying to configure storage pool from these media agents, we only can configure up to 6 DDB Partitons, and we need all 10 partitions to be available within the storage pool  is there any chance of it?

Hello Community,Thanks for all answers.I am having same issues with CIFS shares using VSan Dell storage.How do I increase the SMB credits to 256?  In media agent Windows registry key?Thanks Error occurred in Disk Media, PathCV_MAGNETIC\V_1508600] [The parameter used for the current operation is not supported by the Operating System, OS Drivers or the underlying Hardware.]. For more help, please call your vendor's support hotline.

I have a NDMP NAS SP (shares / subclients)I want to copy the data to a DR facility.My DASH copy is running very slow. 25GB/hr but the data to be copied is several TBs.Is there anything I can do to improve the performance?. How I can add more streams? 

Hi all,I have a simple deployment with 2 Media Agent in GRID using SAN disk; deduplication is enabled on Media Agent.I wanted to segregate back-end storage for different platform (VMware, AIX, etc...) or customer. Is there any option to achieve that? Should I create many storage pool for each platform/client or is there any way to associate multiple libraries to the primary storage pool? Thank a lot for support.

Evening folks,I am after some advise/best practice info if possible (happy to be linked to any documentation!)What is best practice when using multiple cloud libraries (AWS S3) - is it better to an individual cloud library per S3 bucket (which also means multiple DDBs!!) or is it best to have a single cloud library with multiple mount paths to each S3 bucket within said library (which I believe will leave you with a single DDB?)Many thanks in advance!

What is the actual difference between micro pruning and macro pruning in reference to DDB and data aging ? In which scenario micro vs macro pruning is enabled and where i can check it in console or command center? 

Hello to the entire CommVault community,I am in the process of migrating our CommVault v11.40 environment to an Azure cloud infrastructure, and I would like to gather your experiences and advice on several technical aspects, particularly the integration of Azure Lifecycle Management with CommVault's native archiving features. I am not an absolute expert in CommVault or Azure, so I will explain my context in detail to make it clear. Feel free to correct me or share similar experiences!Context of Our MigrationWe are transitioning from an on-premise deployment to a self-hosted setup in Azure. Specifically: Our CommServe is installed on a Windows Server 2019 VM. We have a Media Agent on another Windows Server 2019 VM, configured to use an Azure Blob storage account of type Cool (to optimize costs for infrequently accessed data). Backups are stored in this Cool Blob Storage, with varied retentions from our current configuration (extracted via an Excel report). For example, we have short

Good morning, I have a library with two drives, and I need the copy to use only one drive, leaving another drive free for another copy. As of today, when a copy is launched, it uses all available drives, and the second copy is put on hold. I saw that the copy is configured with 100 streams. Should I lower that to 1? Could you guide me so that each copy launched to tape uses only one available drive.

We have quite a few VMware VMs being backed up via VSA streaming backups that have multiple scsi disks defined. We would like to be able to specify only the system disk (SCSI 1:0) and exclude any other disks. However, the default VM Disk filter in the subclient only allows for excluding disks. We’d like to be able to just specify which disk to include rather than which disks to exclude. Is this possible to do somehow? Thanks!

I am using Commvault 11.36 and have a storage policy with a retention of 7 days, 1 cycle. I recently ran the Data Aging Job and generated the Data Retention Forecast and Compliance reports, but I think some aged data may not have been pruned.Could someone guide me on how to verify if the aged data has actually been removed? Are there specific reports, job logs, or steps I should check to confirm this?Disk Library is Full. Is there any solution for now?

my setup is like this file server → Production CommVault --   (auxiliary copy) DR Media Agent  + DR CV → File ServerIn this setup file server backups data to production CV system. I want the auxiliary copy to be pulled by DR Media agent and we are using NFS to put this data to DR CV and from DR CV we are restoring the file server dataHow can i configure a pull mechanism from DR Media Agent? is this possible? my environment - RHEL based infrastructure with command center no java console

About 3 weeks ago we upgraded from 11.28 to 11.36.   Since then our VMware SAN mode (Fiber Channel) backups on average are 25% slower.    Has anyone else run into this?   I can see the slow down in the job run times and throughput, as well a looking at my Fiber Channel SAN ports.  Here is a screen shot of the SAN port performance for the last year.  The ports in the chart are only used to pull the VMware backups from our ESX environment.   The spikes are the full backups each weekend.   We can see the last 3 weekends have been much slower than the trend was before that.   Was there changes to the VDDK or some other related piece of the backup? 

Hello, hope this finds you all well! A few days ago I configured backups for an Oracle RAC client and I’ve been noticing a very strange behavior… Every incremental backup gets switched to a full backup and there always this error being displayed: “UpdateIndex failed on MediaAgent [media agent name] - Index files are missing. Job could have earlier run on a different MediaAgent possibly due to a failover.Source: media agent name, Process: UpdateIndex”.It is true that we have a pool of 4 media agents and it can use any of them but we don’t notice this error on any other of our hundreds of backups and they also jump media agents between jobs. A lot of them being other Oracle RACs…What is even stranger is that this error happened even during its first full backup. Could this be happening because this DB is a duplicate of one configured with other Storage Policy that uses other media agents? Even though they use different DDBs? Can it be that this is somehow creating some confusion?Events f

We are frequently encountering a problem where data chunks are missing, and this is impacting our ability to restore multiple VMs. Initially, we suspected an issue with the cloud storage provider and requested the support team to investigate. However, upon further analysis, we discovered that a delete command was issued by Commvault, which led to the deletion of the data from cloud storage.As a result, multiple storage policies have been affected, and we are currently unable to restore the data for several virtual machines. Analysis: According to DataCore logs:The SFILE delete request was received at 08:08:49 The Compact File delete request was received at 08:07:55Commvault is expected to send a delete request for the Compact File only after a successful remote copy of the Compact File to recreate the SFILE. If this process is followed correctly, the SFILE should have already been deleted before the Compact File is removed.However, this sequence appears to be reversed, and DataCore has

Based on our current Commvault infrastructure: We have one CommServe and a Media Agent at the DC location. A Standby CommServe has recently been configured in Azure, and we successfully tested a planned failover. During the test, we were able to run backup and restore jobs using the Standby host while the Production CommServe (services) was down. Now, we would like to extend our testing to include the Media Agent as well, specifically for a scenario where both the Production CommServe and the Media Agent at DC are unavailable.From the planned failover test, we have confirmed that the Standby CommServe can take over. However, in the event of a complete DC outage (CommServe and Media Agent down together), we need clarity on how to proceed.Our current policy setup is: Primary copies → Local storage (without DDB). Secondary copies → Cloud storage (with Commvault DDB). We would like guidance on how to best configure a Media Agent in Azure so that it can act as a standby. The goal is to

Hello, TeamWe have Unity Storage With Multiple LUNs, acting as mount paths attached to 6 Media agents with about 2.6TB datasize in total. There are multiple disks failure on the Unity storage end and we need to move the active data into another Newly purchased storage. The plan is to have all mount pats or data written to that storage with their  dependencies.The plan is to use commvault for this migration and here are my queries below:Should we use the Move Mount Path option? if yes, can restore happen while the mount paths are being moved? Each LUN is about 10-20TB each and we have multiple of them. Should we use the Storage policy create new copy or auxillary copy to move the data and promote the destination storage to primary.Also, considering data size, how could it take the data to complete migration?When the migration is completed. We would love to see that the data has left the Unity storage. The source storage and destination storage are like 50KM apart on an uncapped network

Hi,according to BOL Deduplication Building Block Guide,a Media Agent can host up to two (2) DDBs (from on LUNs of different RaidGroup) ALL DDBs of all Storage Pools on a Media Agent should share the same volume / paths (e.g. D:\DDB)My question is now, does this require to create a streched / expanded Volume accross multiple (2) LUNs / Disks ?otherwise I don’t get, how one single directory or volume can be used to place the data to mutiple LUNsand should this be a striped or a concatinated volume layout ?In the past I used D:\DDB and E:\DDB as paths (different volumes on different LUNs).This doesn’t seem to be best practice anymore, if I understand the BOL entry correct.I could understand, if this restriction is valid for all (3 horizontal scaling) DDBs belonging to the same Pool. But the article states, that all pools should use the same volume or path.rgdsKlaus

Hi,I have a question regarding move mount path. The one and only possible MA is Linux.Source is a nfs share which supports sparse files. Target is a CIFS share which does NOT support sparse files.“move mount path” is a tool in Commvault.What happens with the files if using move mount path?wikipedia wrote:Sparse files can cause problems when copying: When copying to another file system that does not support sparse files, the target file cannot be created in compact form. Therefore, the undefined areas of the source file are written as null characters in the target file. This results in a significantly larger target file. The target file system must have sufficient capacity. In addition, both the copy or backup program and the target operating system must support sparse files and be able to recognize them as such.How does Commvault handle these files between the different file locations? SW is not too old 11.32 or 11.36Thanks in advanceJoerg