Skip to main content

Hello Community,

 

after migrate to V2 VSA for VMware with v2 migration workflow, I observed that certain VM clients are linked with the VSA agent, while other clients do not exhibit this association. though all of clients are part of the VSA backup .

 

In the "Client Properties" section, specifically within the "Virtual Machine Properties" tab, the "Virtualization Client Name" directs to the V2 VSA pseudo client 

 


below screenshot has vm and agent level backup but  VSA agent is not linked to it, the "Virtualization Client Name" refers to the V1 VSA pseudo client.


 

It seems that the V2 VSA agent is exclusively visible in new deployments, correct?

 


 

Yes, your right!!!

Once you have done the V1 to V2 index migration your old Vcenter will be renamed with “_V1” and another Vcenter will be created with the same settings and schedules.

Each VM’s associated under the Vcenter for backups, will be highlighted with the OS icon with Virtual server iDataAgent (In V1 indexing the VM’s will be graded out)

Also, here you can initiate the new backup for the failed VM instead of running it for the entire sub client. 

Hope it helps, thanks.

@Thiyagu Kanthan  thanks

Reply


Terms & ConditionsCookie settings