Solved

I want to to fetch a list of clients which has file system agent installed in it using Commvault DB query and the output of the same will be used as an input to display all FS clients to run backups only for file system agents.

We are planning to deploy some Media Agents for extra copies.As the primaries are RedHat machines we prefer Windows for the copy where the current preferred version is Windows 2022 Core.Allhough I’m confident it will work based on the documentation here: https://documentation.commvault.com/2023/expert/3011_windows_file_system_system_requirements.htmlI know it’s about a File Agent, but it states that non-GUI / push installs will work fine on a CORE edition. The only packages to my knowledge that require a GUI installation are CS & WebServer.SInce we want to be fully supported we do try to follow the specific supported OS’s for a Media Agent here: https://documentation.commvault.com/2023e/expert/2822_mediaagent_system_requirements_01.htmlThere you can see that ‘Microsoft Windows Server 2022 Standard Editions’ is supported, but it’s not mentioning specifically Windows 2022 Core (which it does for Windows 2019 Core).Some time ago Commvault support mentioned that a documention update wa

I have a webserver we are no longer using (webserver is now hosted by commserve), and this webserver was also tagged/installed/configured as a media agent.  However: it performed no media agent functions, just the webserver.  My beliefs in “how to retire a media agent” are: Right click on media agent, choose “Delete media Agent”. A warning pop-up appears: says to view ‘media Agent impact Deletion report’ (and follow impact/remediation steps from there) and then when ready to actually delete the media agent, type in a long phrase to confirm deletion. Perform any remediation steps in the report so the report is ‘empty (and mine is, as it was never really used as a media agent). Put media agent into maintenance mode? Using the Commvault services UI/tool: Shut down the CommVault services on the media agent, set them to “not restart services”, and power off server/OS. Delicense the client associated with the media agent (i.e. it has the same name).  I chose to use the “retire server workflo

Hi everyone, We’ve got a customer who intends to implement a storage replication, main storage is connected to a MediaAgent in which backed up data is written to it, customer has acquired same storage hardware and wants to implement a replication (A feature available on the storage system) between the main one and the newly bought one. We already know that we can implement this using AUX/DASH copies, but customer insist on implementing it through storage side. My question here is, how does commvault can manage this type of architecture ? Does the MediaAgent connected to the main storage system needs to also be mapped to the new one ? Is there any configuration needed from Commvault side to let it know about the new storage (Maybe configure it as a replication storage ...). In this case, the MEdiaAgent will automatically redirect it’s I/Os to the new Storage in case of a failure of the main one. Regards.

I deployed a FREL OVA machine and was using it for Commserve 1. Now the commserve1 is not in use and I would like to use the same FREL machine for a new Commserve. Can I use the same machine or I need to deploy a fresh OVA?

We are in the process of hyperscale refresh, Creating aux copy and once the data fully copied promoting new copy as primary is the method we are following,There is a dash copy which is copying data from old primary copy,there are many job to be copied, If we change the primary to new primary wethere these pending jobs get copied from new primary copy? Or do we need to wait unitl it completes fylly 

I am trying to estimate the capacity I am going to need when changing the retention time on my Global Deduplication policy - Primary copy from 30 days to one year.If I look at the capacity of the storage policy now, w/ the 30-day retention period, would multiplying that by 12 give me an accurate estimate on capacity I will need to keep that primary copy for one year?  Ex - Primary copy w/30-day retention period = 300GB - changing to 365-day retention period = 3.6TB ? 

Hello,We have migrated Commserve on new hardware. Now simpana version is 11.28.68 .It seems to be ok.When I open Commcell Console I see “Login with Command Center” What does mean?I do not know is this related with Commvault Cloudhttps://cloud.commvault.com/home/   I´m already member….Best regards,Elizabeta

Dear Team,We have five data center and each DC deployed one media agent and taking backup through disk library. Out of five data center one is the main and another four are the branches. Now we are planning to deploy tape library for only secondary copy. Which is the best option to take tape backup? Taking secondary copy in the same data center. So, need to deploy tape library for each dc or will move all secondary copy to main dc in one of the disk library and then moving to tape copy. Need your support to implement the solution in Commvault.

Active directory object restore fails with below error. While trying to restore a deleted OU, USERS etc.  Backup is successfull and I am able to browse the objects.  Error Code: [72:106]Description: Failed to restore "OU=,OU=,OU=,DC=,DC=,DC=local". Error:32Source: , Process: adRestore logs I see AdRestore::OnBufferPlFsHdr() - Error retrieving current set of attributes for the    DN OU=Users,OU=Site,OU=AM,DC=asdf,DC=fdsa,DC=local

Hello, Has anyone heard anything from Commvault regarding support of vCloud director 10.5?It was released sometime a month ago i guess and customers are already starting to push us for the upgrade.With the 10.4 release in mind and the deprecated API’s for backup in that release I googled and I see that on the green competitor’s forum that if you do the upgrade to 10.5 now, backup will just stop as it did when 10.4 was not supported by Commvault or other backup providers.

Hello community, I would like to ask you for an advice. Lately I`ve found the failure when I did check readiness on media agent (windows 2016, CV version 2022E/11.28.56). Error:Communication failure between MediaAgent 172.xx.xx.23 and the client “mediaagent1”. Error returned is:Services on destination are down.  Communication failure between MediaAgent 172.xx.xx.23 and the DDB MediaAgent “mediaagent1” Error returned is: Error returned is:Services on destination are down.When I checked services on both media agents, all are up and running. both are in same vlan, so no FW is in place. Both servers were rebooted in last days. DDBs on both MA`s are either online.if it is a normal FS client, I would push “repair software” option on the media agent. Thanks a lot for any advice. 

Hi, In my environment 2 data center and centralized commcell, commserver data replication is happening every 15mints, yesterday network team done switch level upgradation in dc2, because of the  network activity,  DC2 disks library are  fluctuating,  and we are facing issue  Index restore jobs running more 12 hours. still index restore running, looking for suggestions.    

 Hi everyone, We are in the progress of testing how to setup Gridstor with shared library which mount paths are assigned to each Media Agent locally (no NAS available).  Assuming we have Disk Library configured with MA01 and MA02, mount paths are shared to each other (read access only) configured as below: Disk Library MA01 MA02 Mount Path A Mount Path C Mount Path B Mount Path D \\Mount Path C (Read Only) \\Mount Path A (Read Only) \\Mount Path D (Read Only) \\Mount Path B (Read Only)   However, if MA01 down, with Gridstor backup would continue to run on MA02. But when comes to restore (coincidently), MA02 would not be able to access shared mount path on MA01. We being told that we could re-zone/mount the Mount Path A and Mount Path A to MA02, configure mount path as part of MA02 then we could perform data restoration. Example as illustrated below: Disk Library MA01 MA02 Mount Path A Mount Path C Mount

I have a number of VSA psuedoclients that need to renamed but the option simply isn't there.Am I missing something simple? I can’t imagine this is a real issue.

Hello,Is there a way to exclude DDB + Index server backups from a Synchronous secondary copy ?Some Additional setting that will do the job ? Thanks

HiDoes anyone know if there are any restrictions in the workflow engine regarding the use of temporary tables in the CommservDBQuery activity? In the SSMS the query works fine.  When I run the above SQL query in the debug mode, I don’t get any output: I also tried to use a table as variable, which did not work either.The workflow engine runs on a dedicated server. Could this cause the issue? Thanks for your inputsMichael

when the backup initiated what’s happen scan phase, backup phase, Archive phase and index phase, what will happen if once failed. 

Hi,We are currently running Commvault in a VM 11.20.168 on Windows Server 2019, and also using a FREL.As the title states, I would like to upgrade the Commvault release from 11.20.168 to the latest version 11.32, and also the Windows Server version. We have 4 instances that I maintain, and it is a closed network (I have to download the update files and transfer them over).This VM was previously running Windows Server 2012R2 but I upgraded our instances to Windows 2019. I could just do an in place upgrade again to 2022, but maybe it is best to make a new VMs. Please share your thoughts and recommendations.

Hello!Problem description:SAP for Oracle agent has following subclients:1) Online - For Online Database backups2) Offline - For Offline Database backups3) Logs - For log backupBackups for Online and Logs subclients happening regularly. Offline subclient is used for special cases, only one job for this “Offline” subclient exists and it is marked for 5 years retention.Problem: Jobs of “Logs” subclient not aging, with reason LOG RULE and with “Required By Jobs” mark, where required job is job of “Offline” subclient, which we want to keep for 5 years.How to resolve problem with Log aging and keep job, which is blocking aging?

I would like to know if there is a report on backed up VMs and Filesystem divided into quantity by operating system.Similar to VM Backup Health and Fileserver Backup Health but with both reports together.I don't know if I explained it correctly

We have a media agent with low disk space alerts going off (on the OS disk), all the usual suspects only returned a few GB of free space.After analyzing the media agent’s OS disk, the JobResults folder is 192GB (55.2GB on disk), one of the largest offenders.Can this folder safely be relocated to give it some more breathing room?This seems to mention clients however at the same time does not mention media agents.If I move the JobResults location, will it potentially nuke the media agent and all jobs/indexes too?https://documentation.commvault.com/11.21/expert/6588_changing_path_of_job_results_directory.htmlThanks everyone!

Dumb Question, but  I don't want to have to have my systems team argle bargle. Media Agents have to be physical servers, correct? I am assuming there shouldn't be a reason why it cannot be a virtual machine, but before I put my foot in my mouth (tasty btw) I want to see what the community best practice is. 

Hi,for about a week we have a problem with our O365 Exchange backup. It runs instead of about 4 Minutes without error now over 3 hours with errors.We get the following error messages:Failed to process mailbox [Mailbox does not exist]Failed to process mailbox [Too many concurrent connections opened, Cannot open mailbox. Server = BEZP281M…...]According to the joblog will be Exchange only setup detected with no public folder association.The Access-Node is a Windows Server 2019 with PowerShell 5.1use modern authentication is enabled5 Azure Apps configured10 max streams configuredCommvault Version 11.28.80Does anyone have any idea how i can solve the problem?RegardsFranz

Some of our sites are failing during backup with the following errors “http://oursite/whatever FAILED There is not enough space on the disk.”  I am not sure what disk they are talking about that is out of space.  I checked the server our sharepoint sits on and it seems like we have more than enough space on the Disk.  Anyone seen this issue before?  I wanted to ask here before i opened up a ticket.  Also our Sharepoint is inhouse we are not on 365 yet.  Thanks for any pointers.