Docker - End of Life Notice

  • 4 March 2021
  • 8 replies
  • 211 views

Userlevel 7
Badge +19

Docker Change

 

On Dec 15th 2020, Commvault released Feature Release 11.22 which represents the third software release to support protection of Docker containers that are managed by Kubernetes. Commvault also announced deprecation of the Docker Virtual Server Agent (VSA)     

 

What changed?

 

Commvault has observed a significant shift from our customers and the containerization market in general towards orchestrated container platforms like Red Hat OpenShift Container Platform (RHOCP) and Kubernetes. As popularity for RHOCP and other Kubernetes distributions has grown, we have observed a reduction in demand for native Docker protection.

 

In line with market trends, Commvault announced Deprecation and End-of-life for the Docker VSA functionality in Feature Release 11.22

Deprecation and End-of-Life

Virtual Server Agent (VSA) Docker Support is Ending
Beginning in Feature Release 11.23, you will not be able to create any VSA Docker clients.  Existing clients will continue to function but will not receive any further software enhancements or bug fixes. Support will be on a 'best effort' basis as this feature is end-of-life.

https://documentation.commvault.com/11.22/essential/1479_announcements.html

What’s the impact?

 

If you are using the Docker VSA to protect an environment today, these is no immediate change. Commvault will not disable or alter your currently configured Docker protection setup.

From 11.23, you will no longer be able to create new Docker clients for protection.

 

Workaround

 

Commvault recommends that you look at migrating your Docker containers to a Kubernetes orchestrated environment which can be protected, included any attached persistent volumes (PV).

Kubernetes

https://documentation.commvault.com/11.22/essential/123634_kubernetes.html

 

Commvault releases

 

Commvault releases the Kubernetes VSA with Feature Release 11.20 and continues to expand its capabilities in accordance with the Kubernetes project and related CNCF projects.

 

Want to learn more?

 

For additional information check out these resources:

Kubernetes - System Requirements

https://documentation.commvault.com/11.22/essential/123634_kubernetes.html

Kubernetes – Backup

https://documentation.commvault.com/11.22/essential/123639_kubernetes_backup.html

Kubernetes – Restore

https://documentation.commvault.com/11.22/essential/123640_kubernetes_restores.html


8 replies

Badge +4

Do you know, is a dedicated VSA required for each K8S endpoint (cluster)? Or, to get this going, can the same node be used to talk to multiple clusters?

thanks

Userlevel 7
Badge +19

Do you know, is a dedicated VSA required for each K8S endpoint (cluster)? Or, to get this going, can the same node be used to talk to multiple clusters?

thanks

Hey @downhill !  Good question.  I’m pretty sure you can use one access node for many clusters (though performance might be an issue).  Let me double check that for you.

Userlevel 3
Badge +2

You absolutely can use a single Access Node (aka VSA) to protect multiple Kubernetes clusters.

Then just scale horizontally as you need more parallelism to meet your backup window

Userlevel 7
Badge +19

The legend himself, thanks @Mathew Ericson !

Badge +4

Cool, that’s sort of what I thought, the BoL could add the comment (or I’ll submit some feedback in there).

thanks guys

Userlevel 7
Badge +19

Cool, that’s sort of what I thought, the BoL could add the comment (or I’ll submit some feedback in there).

thanks guys

I’ll hit up our documentation team (was waiting to get a confirmed answer first :-).

@Seema Ghai , can you get this link modified to clarify that one Access Node can service multiple clusters?

https://documentation.commvault.com/11.22/essential/124720_hardware_specifications_for_access_node_for_kubernetes.html

Badge +2

Hey @downhill; just curious what K8s flavours do you use and how many clusters and applications do you have in your setup?

Badge +4

I believe we are on OpenShift 4.6. 6 clusters running, at least 6 more to go.

As many may know, it is an endless tail chase. The days of staying on a release until the “next” one gets stable are history IMO.

Glad to see Commvault is staying about as bleeding edge as we seem to be.

Reply