Question

Make backup/restore functions via WebUI user friendly for customers.

  • 26 March 2021
  • 7 replies
  • 67 views

Userlevel 1
Badge +4

Hi, 

We are currently in the process of making the Commvault environment more usable for customers. 
The administration of the individual systems in Commvault is to be managed via Active Directory. 
We include the AD groups in Commvault and create in Client Computer Groups per AD group a group with the name of the AD group. 
All systems from the VSA data backup pools are linked into the group. 
The main portal for the clients will be the WebUI. 
Now I have linked a VM from the VSA subclient to the group of an AD for this project and it looks like it could work. But currently I can only restore the last backup of a VM. For backups a few days ago, the "Restore" button is grayed out.

Has anyone here already made experiences or perhaps a better suggestion, how this could be better implemented?

Regards

Thomas

 


7 replies

Userlevel 6
Badge +14

@thomas.S , would you mind posting screenshots of each of the items above?  Are you in Command Center or the Console?

Do you know for sure that the vm was backed up on those days?  or that the job hasn’t aged?

Thanks!!

Userlevel 1
Badge +4

Hi @Mike Struening , 

I have made a few screenshots here where you can see the permission settings and the backups. 
I can restore the VM via the restore button. But not if I want to select a backup from 1 or 2 days ago.

 

 

Userlevel 6
Badge +14

Appreciate the details!

Can you confirm if dmdev01 is the name of the VSA proxy, or is that the name of the VM?

One thing that stands out is the time and size of the jobs.  The one you CAN restore from is nearly 10 times the size of the other jobs which leads me to think the vm you are looking for was not protected within those jobs (maybe they are Incrementals and the vm was off/unchanged during that time)?

If that’s not the case, we may need an incident here.

Userlevel 6
Badge +14

Hey @thomas.S !  Following up to see if you were able to narrow down the issue here based on our observations.

Thanks!

Userlevel 1
Badge +4

Hi @Mike Struening
 

dmdev01 is the name of the VM. This is backed up in the EWS-60-AKQ subclient with many other VMs. For this reason the sizes are also so different.
The VM dmdev01 is backed up with about 20 other VMs. 
I have linked the one VM only with a separate group to prevent that only the VM which also belongs to the customer can be seen and not also the remaining VMs in the subclient EWS-60-AKQ.
Sorry that I am always so late in answering, but there is a lot going on at the moment.

 

Userlevel 6
Badge +14

@thomas.S no need to apologize!  We’re here for you at your convenience!

At this point, it might be best to open a support case and we can then bring the resolution back here.

I suspect that the vm itself wasn’t backed up in all of those jobs (or not successfully), but without having someone looking at it live, I can’t say for sure.

Can you share back the case number?  You can pm me the details if you’d rather do it that way.

Userlevel 6
Badge +14

@thomas.S following up on this issue.  Were you able to get a case created?  If so, can you share the case number with me?

Thanks!

Reply