Storage and Deduplication

We want to migrate jobs from one S3 cloud library to another S3 library without DDB, avoiding the use of auxiliary copies or data path moves. We aim to use an internal bucket-to-bucket copying mechanism to avoid standard data egress and ingress—thereby reducing egress costs, even though the transfer itself will still incur a charge. Once the data has been copied, we will import the metadata to ensure the backup chain remains consistent for future restores.

Hello all!In our environment, we have created a temporary copies within our few storage policies - (call them copy 6 and 7). Those were tape copies. We have keep some backup there for 2 months, but it is no longed needed. We do not need those copies within those storage policies any more. But for now, even if they are no longer any backup retained on this 6-7 copy, we do have a lot of “Big Data Apps” jobs retained on those copies.We would like to delete those copies because it interferes with our “workflow” which picks jobs for copies and it's keeping to mark them to copy for 6-7 copy. (even if copy is disabled) So my question is - what exactly this Big Data Apps is? It is some kind of Index, am I correct? If those “Big Data Apps” are stored on copies 6-7 are there any dependencies for other copies, other jobs keep in other/same storage policies?Can we just delete copy 6-7 from our storage policies even if they are still those Big Data Apps stored on it, and it won't affect the rest of

How can Commvault be configured to write backups to tape media? (Note: I have already added the tape and can see the drives and media; I have two drives and three tapes, as well as two backup plans. However, while one plan always succeeds, the second consistently results in errors [32:690] and [32:193].) 

how make the commvault write backup on tape media (note: actually i added the tape and i can see the drives and tape media and i have 2 drives and 3 tape media and i have 2 plans but one plan only that always is success job and the plan number 2 give me error [32:690] , [32:193] ) 

Hello,I would like to ask a  question about cleaning the local on-prem S3 storage (Netapp AFF C30).We have two buckets created (two mount path’s). Both have micro-pruning enabled from the beggining.On Mount path “General” informations I can see that:bucket1: Size on Disk: 90,68TB / Estimated Media Size: 68,06TBbucket2: Size on Disk: 86,86TB / Estimated Media Size: 65,77TB I had similar values in the past on Commvault (MCSS/MRR/AGP) cloud storage - and after running Space Reclamation - we were able to free up a lot of space.Should I run a space reclamation here on this S3 storage? Is micro pruning sufficient way for cleaning on-prem S3 storage in commvault? or maybe we should run this space reclamation from time to time?It would be great to hear what best practices are.Thanks in advance.Regards,Matt

Hello, guys  I want to perform a secondary copy to tape, and be able to write the data to tow tapes at once, Same data must be written to tow different tapes that belong to two different pools (main pool and copy pool). The idea is to be able to have mirroed data on tapes that will be stored on different sites (customer policy). Data must be read once from primary store (source) and write at same time to diferent tapes.Customer has a library with 3 drives. Any idea?Regards.  

Hello everyone,For the past few days, I’ve been working with a Commvault engineer to disable the compliance lock on the Storage Policy. There was some obsolete data that wasn't expiring—possibly because we didn't have secondary copies, or because some items were linked to other data that hadn't yet completed its lifecycle. Anyway, the data was deleted, but the change wasn't reflected in the storage yet. To be certain, is it best to validate this via the library or the Storage Pool? Could you please advise?

NetApp is currently selling the successor to the ASA (SAN Only), the ASAr2, at an attractive price. Basically, it is a system from the ONTAP family, like the FAS or AFF systems. Unfortunately, the API has changed considerably, and Commvault does not yet support the ASAr2 API. I’ve heard that integration is being worked on. Is there a timeline for this?We have a few projects where Commvault (new customer) and NetApp would be a good combination.

I have a customer running 11.40 and Commvault now has the combo tiers for cloud storage configured by default. My question resides in which tier the bucket should be created. The customer had previously created a bucket in AWS (this may come into play later) that was used to create a Cloud Library in Commvault using the AWS Glacier Deep Archive tier. When examining the data in the bucket, we can see the CHUNK data is written to Glacier Deep Archive however, the index metadata is showing under Glacier Instant Retrieval. This seems wrong to me.I have read that Commvault will apply an Amazon storage class header to every upload API call and then writes the data to the bucket, which is part of what is allowing the CHUNK data to be written to one tier with the index metadata to another tier. I’m starting to believe that the storage class header only is being applied to the CHUNK data and the metadata is using whichever storage tier the AWS S3 bucket was created with. Documentation doesn’t m

Hi all,just wondering if anyone can help me. I’ve noticed on our Hyper-V hosts then when a backup is triggered in CommVault the system event log on the hosts are flooded with Disk and partmgr warnings for specific disks.I’m just wondering if this is normal behaviour or something we need to look in to? For context, these hosts are running Windows Server 2019, are MediaAgents for all our VMs and we are running CommVault version 11.36.102.The disks presented to the cluster are CSVs and are presented via iSCSI from our NetApp.I cant see that its causing any hard to the backups as they are completing successfully. The Vms and hosts also appear to be fine - but not sure what could be causing these warning or how to remediate them. 

I was teaching a CV Engineer trainingsome time ago, using a lab setup for demos that I upgraded from 11.32 to 11.40. I created a disk storage pool to demo things. When I started to configure dedupe, I only got the possibility to choose the MA for the DDB, not the location (vloume / folder), so the DDB ended on the C: drive. Is this because the upgrade went wrong, or is this by design? If it's by design, why???

EnvironmentCommvault Version: 11.40.51 Windows Server CommServe and MediaAgent installed on the same server Primary Storage: Disk Library (Deduplication Enabled) Secondary Copy (Copy-2): Remote Disk Library (Deduplication Enabled) Copy-2 uses its own Global Deduplication PolicyDisaster Recovery Test ScenarioConfigure a Primary Deduplicated Disk Library. Configure an Auxiliary Copy (Copy-2) to a remote deduplicated Disk Library. Run backups successfully. Run Auxiliary Copy successfully. Create a CommServe Disaster Recovery Backup. Simulate a complete disaster: Original CommServe is lost. Original MediaAgent is lost. Original DDB files are completely lost. The remote Copy-2 Disk Library (Chunk Store) remains intact. Install Commvault 11.40.51 on a new Windows server. Restore the CommServe using the DR Backup. Reconnect the existing remote Disk Library.Current StatusAfter DR recovery:CommServe recovery completed successfully. Storage Policies were restored. Disk Library was restored an

Dear Community,Perhaps anyone can answer me the following question. My customer use storage accelerator (SA)  for backups and Aux copies to cloud. Now he asked:How can I easy see that SA was used or not?We are at 11.36.55. First, I asked Arlie but answer seems only partly correct. I am still at the beginning to check all points Arlie told me. Java GUI is not useful in this case. It shows allegedly only results if SA is used. To make a clear statement, I always must check the log file.In the command center, I must differentiate between backup jobs and Aux copy jobs.Backup jobs indeed have a line: storage accelerator yes/no which is the expected behavior.According to Arlie, there should also be a line for Aux copy jobs that clearly indicates the use of SA.I am not able to find. Can you help?My customer needs a clear indication on user level that shows if an aux copy uses the SA or not.We currently analyze logs or the network traffic to get clear results which is not useful. Thanks in adv

Hi everyone,I'm looking for some advice regarding a tape backup issue in Commvault.Environment:    Commvault Web Console v11.40.42    HPE Ultrium LTO-6 standalone tape driveThis tape drive was previously used in another backup solution. Before using it with Commvault, I:    Stamped the tape media.    Used the Delete and Reuse option to erase the existing contents.    Set the tape as Primary media.    Started a backup job.The first backup completes successfully and writes about 1.16 TB of data. However, after the backup finishes, the tape media is usually marked as Unavailable, and sometimes it is marked as Full.From my understanding, an LTO-6 tape should have a native capacity of around 2.5 TB, so I'm not sure why Commvault considers the tape full after only about 1.16 TB of backup data.When I start another backup job, Commvault prompts me to insert a new tape instead of continuing to write to the current tape.I also noticed the following:    If I power cycle the tape drive, the tape a

Commvault Backup & Recovery 11.40 (Command Center - browser-based) when backing up a Windows file server to an HPE tape drive.Environment:Commvault Backup & Recovery 11.40 Browser-based Command Center Backup target: HPE tape drive/library Workload: File Server backup to tapeIssue:During or after the backup job, the HPE tape is automatically ejected. This does not happen every time, but it occurs frequently enough to interrupt our backup operations. 

Good day to you all,I am experiencing with our Dell EMC PowerScale NDMP IntelliSnap backups across our two CommCell environments.Context: We have two CommCell environments configured to back up Dell EMC PowerScale shares to a HyperScale target. Currently, the shares are split between the two CommCells.The Issue: While the snapshot backups for both CommCells complete successfully, the Backup Copy job for CommCell 1 is consistently failing.Upon investigation, we identified that for CommCell 1, the data movement from the PowerScale server to the MediaAgent is defaulting to a higher-end port/interface instead of the expected 10000 port. Interestingly, CommCell 2 is configured similarly and is performing its backup copies without any issues. Kindly advise on this. Robert.R

We recently migrated our Commserve to a new physical server and now several weeks post migration we are getting errors on about 90% of our synthetic fulls when they reach the end of the job, they will continously run at 99% but looking at the synth full logs we see alot of this:30236 5280 06/05 12:34:18 13071395 SdtDecryption::ProcessBuffer:218 Cannot decrypt data for afid [28434509]. cur_afid [28725857], orig_afid [28434509]30236 574c 06/05 12:34:18 13071395 SdtDecryption::ProcessBuffer:218 Cannot decrypt data for afid [28434509]. cur_afid [28725857], orig_afid [28434509] The event viewer gives the generic Unable to communicate with Media Agent or Pipeline error. Opened a high priority ticket about a month ago and we’re being told we need to seal every DDB store in our environment and re-base. We have several thousands of VMs with some over 60TB in size. I feel like re-basing is going to take weeks, and we may not even have enough storage to do it. Any other thoughts or ideas would be

Hi,How may I know if my Aix environment is supported with DataDomain DDBoost over fiber?  Commvault Version: 11.40 release 22Commvault Media Agent SO: AIX 7.1/7.2 We have a large Oracle DB with 50Tb that we would like to protect.

Hi all, I’m planning on replacing our MA server, and I just needed a sanity check on the Replace Media Agent App and Move Mount Point processes. The old MA has a Disk Library with 7 mounth paths, most of which are iSCSI LUNs from a couple different arrays. The new MA will have much more direct attached storage, so I’m plannin on just 2 mount points. If I run the Replace Meda Agent App process, and let it run the Move Mount Point process, am I able to consolidate the old mount paths down to 2 during this process, and specify the destination of each of the source MP’s?  I assumed that I can because the Move Mount Path function in the Commcell console offers me the option to move it to an existing device, however the documentation says: The move mount path operation overwrites the destination mount path. Therefore, ensure that the destination mount path is an empty folder.  Can anyone offer any clafification?Thanks!

Can Commvault store full backups and incremental backups in separate buckets, with immutability enabled only for the full backup bucket, to optimize costs? If feasible, what are the pros, cons, and key considerations of this design?

The topic generally covers a few points.We have an “older” backup system, running Windows Server with “suitable” hardware specs, containing >50 TB of storage. No cloud stuff etc. but an LTO-9 library attached.Why is the fragmentation so high at all. I’ve configured allocation of writeblocks to 1024 MB. But it seems to clearly not do - or keep - that. I hoped to find help in:  But the recommendation to use “space reclamaition” instead of defragmenting sounds like someone has no clue about the topic. If my library is “full”, I can’t reclaim anything and by that it does not help the fragmentation-status the tiniest bit. For DR-use, we not only save the dr-backups (config etc.) but also have a scheduled job running, that backs up (copies) all library-files from storage to our tape library (also enabling us to airgap data frequently - good for ransomware attacks). But due to the fragmentation, our backup process is limited by the RAID containing the library. It’s still “spinning rust”

Hello community, we used a deduplicated WORM cloud storage pool  for a while but needed to start fresh because of unexpected growth.In the process of aging the data of the old pool we noticed an issue because of the default 1 cycle retention which required a workaround to bypass the cycle retention.Therefore we would like to enable zero cycle retention on the new WORM pool like described here: Configuring WORM Storage LockWhen preparing the pool and assigning the first storage policy to it I noticed that the cycle retention got increased to 1 after enabling WORM despite running the command from the documentation beforehand.So my question is: Is there more to do than described in the documentation to enable the zero cycle retention on WORM pools or is the GUI just “showing” 1 cycle but using 0 in the background?

What fields/tables  are used to decide the copy type of an StoragePlicyCopy : “snap primary”,”primary”, “selective”,”synchronous”,… 

We have a client sitting in a DMZ that can successfully connect to media agent 01. However, media agent 01 does not have a DDB. In the job logs we can see the scan phase for the job complete on MA01 but then it fails on the backup phase. We noticed in the logs an attempt to connect to the CVD service on media agent 02 which houses the DDB. The client does not have a path to MA02. In this situation, does commvault require the client to have comms to the DDB media agent MA02? I thought that MA01 would handle connecting to MA02 not the client. How does Commvault handle the data flow in this setup?  Thanks!

Hi all, I would like to enable client-side deduplication on a Windows VSA proxy so that only unique data is sent directly from the VSA to the MediaAgent DDB/backup library, instead of sending all read data from the VSA and deduplicating only on the MediaAgent side.We are looking to this approach because the VSA proxy will be a VM inside an AVS environment, while the MediaAgent will be outside of AVS (as Azure VM).  Could you please help with:Required packages on Windows VSA proxy: What Commvault packages are needed on the Windows server acting as VSA proxy to support client-side deduplication (e.g., Virtual Server, File System Core, File System, or any additional components)?How to enable client-side deduplication for VSA backups: What are the step-by-step configuration steps (storage policy, subclient properties, etc.) to enable source-side/client dedup specifically for VSA workloads?How to verify client-side dedup is working: What are the step-by-step checks (job details fields, repo