Hi @ManiD Final question, multiple storage policies aux copy like FS, DB, VM will write single Media ( Week1 - 00001L5 ) right. If you are using Global Secondary copies, yes. Though I’m not sure what limitations you may meet when combining all of the above to meet your requirements. Is there any kb article or documents please provide. Thanks This is not a common solution or requirement, so you’ll not find any documentation or KB to architect this for you. Most environments will have Weekly tapes and allow Commvault to manage the media fully (Meaning, we will use tapes as we need, and recall them when ready, no unique barcode is required). Cheers,Jase
Hi @ManiD As you mentioned ‘Mark media full’ on weekly Aux copy schedule level. So, The Aux copy job completed for Week1 the media will mark as full and then week2 aux copy will pick another media automatically? Correct, lets say you have 5 days labaled 000001L5, 000002L5, 000003L5, 000004L5, 000005L5.On week one, the Aux Copy runs and moved data to 000001L5. On Completion, it marks it full.On week two, we cannot use 000001L5, however we can use any of the 4 remaining tapes so we may write to 000004L5. At the end of the copy, the media is marked full.On week three we will choose from 000002L5, 000003L5 and 000005L5. We cannot dictate that Week 1 uses Tape 1, and Week 2 uses tape 2 etc, but we can ensure data from week to week are not mixed together on a single tape.If you create separate selective copies with separate scratch pools for each week, with a separate selective criteria, you may be able to have each week write to a specific tape, but to achieve this you would need:5
@Mani Devaraj @ManiD , What you are asking for cannot be achieved with a single Secondary Copy. Hi Support Team, We are running backups daily, weekly and monthly to disk library. Now we are going to take secondary copy in to tape with three tape drives. So, The requirement is Weekly Full Backup for Database Servers and Monthly Backup for File server and application servers. Weekly backups need to take tape like First Week backup for week-1 Tape, Second Week backup for week-2 tape, Third week backup for week-3 tape, Fourth week backup for week-4 tape and Fifth week backup for week-5 Tape. Monthly backups need to take dedicated Monthly tape. Also Two tape drive for dedicated to backup and another one for restore purpose. Could you please help us how to achieve and its possible. Thanks Regards, ManiD For the Weekly Full Backup for Database Servers and Monthly Backup for File server and application servers, you would need separate selective copies;Primary Weekly DB Fulls o
Hi @Junior Vega, If this is for a Backup Copy or an Auxiliary Copy? Thanks,Jason
Hi @TheCVNoob Thanks for your modesty, but great work getting here! I’ll start at the top;- The throughput is calculated using Application Size and Run Time (600GB over 60hrs). - Read is where 98% of the time is being spent. So its currently the bottleneck.- You can increase the number of readers at the subclient level, the application layer will not become overloaded, but the limit will be defined by the next Bottleneck (Hardware (CPU,Memory), network write, disk write, deduplication performance etc). There is no rule here on whats best, but fine tuning is often required. You could start by increasing the number of readers by 10 if the hardware isnt breaking a sweat yet. Or you could go more conservatively at increments of 5.The automatic option, appears to be predefined based on IDA and may not ‘scale’ up based on your hardware availability:https://documentation.commvault.com/2023e/expert/10979_setting_data_readers_for_file_system_agents.htmlYou’ll need to let the job run for a good
Hi @tsmtmiller @RC23 , It sounds as though you are both performing NAS backups leveraging a Windows Proxy to protect these shares as CIFS. Can you let me know when creating the schedule, if selecting Agent Type ‘Windows File System’ behaves differently? Cheers, Jason Thanks for the response. If I change the Agent Type to Windows File System it fails right away saying no eligable subclients found. This WAS working on ONTAP 9.6. Thanks @tsmtmiller Can you help confirm;Is your backup a NFS/CIFS backup of the NetApp array or are you performing it via the NDMP Agent? Have you configured the Cluster within Array Management? Does the Vserver we trigger the backup from have a tunnel into the Cluster? Can you provide output of the “vserver snapdiff-rpc-server show -vserver <vserver>” output?My understanding is, we’re leveraging SnapDiff to perform the indexing process, however with the changes to SnapDiff V1, V2 and V3, licensing from NetApp tightened up some of the f
Hi @tsmtmiller @RC23 , It sounds as though you are both performing NAS backups leveraging a Windows Proxy to protect these shares as CIFS.Can you let me know when creating the schedule, if selecting Agent Type ‘Windows File System’ behaves differently? Cheers,Jason
Hi @Knorr-Bremse I suspect you may have enabled at a subclient level, Object level retention:https://documentation.commvault.com/2022e/expert/61633_subclient_properties_retention.html This may be impacting you’re ability to reduce to remove retention at the Storage Policy level.In any case, its always best to have an engineer review before changing retention or deleting data. I’d recommend reaching out to support to log a case and have one of our retention experts take a look and advise. CheersJason
Hi @sowjanya There shouldnt be any issue with setting up multiple storage pools to leverage the same Library (cloud, disk or tape). Cheers,Jase
Hi @Melissa Adams I’ve had a look at the screenshots you shared to the incident and from a quick glance, theres no deduplication on these backups. Most commonly this is due to Deduplication being disabled at a Client/Subclient level, this option will overwrite the storage policy deduplication settings. If not this, than the source data may be encrypted resulting in 0% dedupe savings. Also worth checking if Windows Dedupe is enabled:https://documentation.commvault.com/11.24/expert/11716_troubleshooting.html Synthetic Full Backup Size Greater Than the Size of Data on DiskSynthetic full backup size may be greater than the size of the original data on disk in Windows Server 2012 and Windows Server 2016 computers.Windows Server 2012 and Windows Server 2016 have a deduplication feature that can be enabled. When this feature is enabled, data from deduplicated volumes are backed up in their original, uncompressed state. Therefore, the size of synthetic full backups can be greater than the size
Hi @Melissa Adams There’s a load of things you can do, as Mike’s mentioned.The first thing is to check if the destination has ‘baselined’ the source yet. That is, if the Source DDB is 100TB of data on disk, then when the destination reaches this also, we’ll see an increase in throughput as theres less unique data to send. As well, if the baseline has been written you can revert the DDB Option to ‘Disk Optimized’ as we are sending much less data now.If the Baseline has not been written yet, than ensure ‘Network Optimized’ is selected atleast until the baseline is committed.https://documentation.commvault.com/11.24/expert/93891_online_help.html#b59046_deduplication_advancedOr as mentioned, Seeding the destination copy where the network is a huge bottleneck is a great option. If the data is being backed up using File System agent, you can increase the number of readers to increase the number of streams. You don’t necessarily need to break it into multiple subclients, though this is not a
Hi @Kavya You’ll need to give us some more detail around the design of the environment and how / what you’re using to implement this.You’ve already said the storage is internal disk, how are you replicating the storage between the two physical nodes? If you’re using Microsoft Server Clusters and implementing Storage Replication, than presumably this would mean that the Physical Server at Site A is identical in every way, besides the hostname, to the physical server in Site B.NB: i have very little understanding on how Microsoft Clustering and Storage Replication works, so someone else or perhaps Microsoft might be able to provide better feedback hereBeing a Windows Cluster, the Media Agent is configured to leverage a psuedo name, which points to to the active node (managed by Microsoft clustering). Seeing as the storage and the servers are replicas, during a failover, Commvault won’t know any better that the server has changed homes and continue to run as normal. There would likely be
Hey @Alexzy Can you see the LTO5 Drive from Device Manager of the Media Agent you’re performing the detect from?When you attempt the ‘detect’, there will be a log output on the screen of what was detected. Do you see any devices in this list that match the LTO5 device? Cheers,Jase
Hey @Mauro You can seal the DDB and this should address the alerts, as we don’t protect a sealed DDB.However if you want to retire the Storage Policy and Media Agent / Library, than you’re steps are spot on. A couple of important notes:Ensure all data in the Storage Policy is Aged and Pruned. Ensure the Media Agent is not responsible for any other roles (Indexing Server, Content Indexing Node, Proxy MA etc) Ensure the library is not used for any other backups/deduplication databases before attempting to delete.One note, you don’t require the XML to seal the DDB. You can do this from the GUI by righ clicking the DDB Policy > All Tasks > Seal Deduplication Database. Cheers,Jase
Hi @Kavya If you’re using a Physical MA with internal disk, if the server goes offline, than the storage goes offline with it. I’m not sure how you maintain HA with internal disk storage?If you’re using Deduplication, than thats catastrophic to your failover plan, as backups will be unavailable while the DDBs offline, and reconstruction will fail as the storage is unavailable for reading.If you’re not using deduplication, than backups can continue to run to the ServerB Storage, however restores of the previous backups will be unavailable. If the storage is accessible from both ServerA and ServerB, than this will be okay, with limited CONs outside of complexity and management (You’ll need to run updates on 2 servers at all maintenance intervals).The DDB folder structure will need to be recreated on ServerB and the reconstruction job run, however this will run as the storage is accessible for reads, and once completed backups will continue without any loss to continuity.Generally, i don’
Hi @Garima Unless im mistaken, CIMC is just console access to the Server essentially giving you the same access as if you were physically standing infront of it with a keyboard, mouse and monitor?If yes, than you can do everything from CIMC and won’t need any RDP or Putty access to the OS directly. From network requirements, its fairly flexible and theres no hard or fast rule, however a few things to consider are;splitting up your Data and Production network This is to prevent saturation of your Production Network This also helps to limit performance impact to your Data Network (data network being the network between the storage and the Media Agent). You may also consider VLANing the networks your Media Agents are on to split traffic for inter-MediaAgent communication. This will help to manage Aux Copy and Deduplication traffic on the network and prevent your ‘Admin’ tasks performed within Commvault from impacting any production network. If i were deploying an MA I’d aim to have 4 VL
Hi @G.lee Default chunk sizes are covered below:https://documentation.commvault.com/11.24/expert/8588_increasing_chunk_size.htmlThese are designed for a balance between performance during write and recoverability.For Cloud storage, theres no need to modify block size to storage. The writes are wrapped up in HTTP Calls as Puts and Gets so block size does not carry across.However we do recommend Deduplication Block size of 512kb for cloud UNLESS the source is a deduplicated copy, in which case we recommend matching the deduplication block size of the source (by default disk is 128kb). Cheers,Jase
Hey @Theja Please see Documentation for Dedupe Q&A:https://documentation.commvault.com/11.25/expert/12643_deduplication_faq.htmlWe recommend not to use other hardware or software deduplication applications with Commvault Deduplication. This is because using a secondary software or hardware deduplication application on top of Commvault deduplication can incur unneeded performance and resource utilization on systems and provides no further benefit to the already deduplicated data. For Compression, though Commvault performs Compression before Deduplication, you may see a reduced Deduplication rate if compression is performed by the client.This may need to test Compression on the Filer vs Compression on Commvault determine what works best for your environment. Cheers,Jase
Hey @AlfredMJ Take a look at the documentation link below, this will work you through ‘moving media between scratch pools’.Once media is assigned to a scratch pool, the media will return there after its contents age out.https://documentation.commvault.com/11.25/expert/10237_media_operations_configuration.html#b10241_move_media_from_one_scratch_pool_to_another Cheers,Jase
Hi @BackupOK I provided a pretty exhaustive response here to the options and some others came in with feedback on their preferences: Its not exactly directed to you’re question, however covers with a bit of detail on what you’re trying to do. Cheers,Jase
Hi @Simon R Smith Have confirmed with engineering team that documentation will be updated to reflect Mino as ‘Compatible’, however not as certified.This is because we know it works based on a few observations:Many cusotmers are already using it. The five major hardware vendors are already supporting MinIO in their S3 object storage solution Nutanix Buckets, Qumulo, VMware K8 Pods, Seagate LyveCloud are using MinIO underneath, and we certified these. I can see that the draft documentation update has been updated and expect that the public facing documentation will be updated within the next few weeks. Cheers,Jase
Hi @Alpha Assuming you just want to keep copies of backups on Primary AND Secondary, you can leverage Auxiliary Copy to move data between locations.Depending on the hardware used to take these images, you could leverage mirroring between source and destination filers OR at the filer level, set up a ‘Mirror’ copy and have Commvault write to primary and leave a read only path from ‘secondary’ for DR situations.https://documentation.commvault.com/11.24/expert/11490_additional_copies_of_backup_data.html However if you want the images to be available for restore in the Secondary Commserve and vice versa, you would need to ‘CCM’ (Commcell Merge) the jobs to the Secondary location. Not really something you’d want to be doing often if this is an ongoing job/task.This is because each Commcell is its own independent environment, Primary being unaware of whats going on at Secondary and vice versa.Jobs written in one, won’t exist in the other even though data may be copied over there. Cheers Jas
Hi @VincentM Looks as though Nutanix is supported for CIFS and NFS:https://documentation.commvault.com/snap/#/storage_checkAnd if you’re wanting to backup virtual environment:https://documentation.commvault.com/11.24/expert/37169_supported_hardware_storage_arrays.html Cheers,Jase
Hi @Kamil I had a look at the incident and will clarify for you to ensure there’s no confusion.Firstly, since early version 10 days, all backups are performed in this order ‘Compression > Deduplication > Encryption’. However, in more recent years we found with Database backups, as compression can cause very high rates of change to the dataset, we find better performance performing deduplication first (Deduplication > Compresssion > Encryption).When we perform Dash Copy, we assume again that we are doing Compression > deduplication > Encryption and so when reading from Primary (regardless of IDA), we remove encryption and then perform signature generation. With that, for this to explain your findings, you’d need to check that you’re doing a good amount of Database backups. If so, than this certainly explains it as the other key areas match up (size on disk and number of jobs).If you still want to try and remove those discrepancies, you can look to make the two copies
Hi @virgil The media group is the scratch pool the media was/is assigned to.When the jobs on this tape age out, the media will return back to the ‘MENSUELLE’ group for the next jobs to reserve. If you check from the Storage Policy, you should see that the Copy that reserved and wrote to this tape is setup using that same Scratch Pool for tape media. Now i need to find a way to work ‘Mensuele’ into a conversation with my partner to show off my new french words :) Cheers,Jase
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
