Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2292

[Backup] cbbackupmgr 6.6.2 doesn't support backup from non 6.6 clusters

    XMLWordPrintable

Details

    • 1

    Description

      Backup Image in CND 2.2.0 GA is based on cbbackupmgr 6.6.2

      Our docs suggest that with this image in 2.2.0, we can take backup of Couchbase Cluster from 5.5-6.6

      https://docs.couchbase.com/operator/current/prerequisite-and-setup.html#couchbase-backup-and-restore-compatibility

      This is not valid as cbbackupmgr 6.6.2 doesn't support backup from non 6.6 cluster.

      https://issues.couchbase.com/browse/DOC-6711 

      This was confirmed by running a backup test with Operator 2.2 running 5.5.0 CB cluster and the test case failed : http://qa.sc.couchbase.com/view/Cloud/job/k8s-cbop-gke-pipeline-2.2.x/50/console  (Operator framework 2.2.x doesn't support server versions pre 6.5.0) 

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Had a quick chat with Patrick Varley on slack. He confirmed that cbbackupmgr 6.6.2 tool doesn't support non 6.6.x clusters.

            prateek.kumar Prateek Kumar (Inactive) added a comment - Had a quick chat with Patrick Varley  on slack. He confirmed that cbbackupmgr 6.6.2 tool doesn't support non 6.6.x clusters.
            patrick.stephens Patrick Stephens (Inactive) added a comment - We probably should link to the docs here: https://docs.couchbase.com/server/current/backup-restore/enterprise-backup-restore.html#additional-65-options  

            Current understanding is: “CAO 2.2 supports running operator backup image (1.1.0) on clusters running server image versions 6.6.2 & 6.5.2, i.e. backup and restore jobs for those clusters. This image uses a base image including cbbackupmgr 6.6.2 so will restore backups made by server versions 5.5+ to 6.6.2." We should reference the tools docs as the ultimate arbiter for truth as well.

            The question is if our QE testing for the CAO 2.2 release of server version 6.5.2 is sufficient to say we support it? Do we say we only support 6.6.2 for backup/restore on CAO 2.2 (which might be too restrictive) or take the chance on 6.5.2 testing being adequate that no issues will come up that we missed?

            patrick.stephens Patrick Stephens (Inactive) added a comment - Current understanding is: “CAO 2.2 supports running operator backup image (1.1.0) on clusters running server image versions 6.6.2 & 6.5.2, i.e. backup and restore jobs for those clusters. This image uses a base image including cbbackupmgr 6.6.2 so will restore backups made by server versions 5.5+ to 6.6.2." We should reference the tools docs as the ultimate arbiter for truth as well. The question is if our QE testing for the CAO 2.2 release of server version 6.5.2 is sufficient to say we support it? Do we say we only support 6.6.2 for backup/restore on CAO 2.2 (which might be too restrictive) or take the chance on 6.5.2 testing being adequate that no issues will come up that we missed?

            Docs changes in place to attempt to clarify the matrix shown.

            Separately we need to consider the issue of support for server image 6.5.2.

            patrick.stephens Patrick Stephens (Inactive) added a comment - Docs changes in place to attempt to clarify the matrix shown. Separately we need to consider the issue of support for server image 6.5.2.
            prateek.kumar Prateek Kumar (Inactive) added a comment - - edited

            Backup Image 1.1.0 was tested with 2.2.0 against combinations of following versions apart from current supported versions in 2.2.0 GA :

            1. Server Versions: 6.6.0, 6.6.1
            2. K8s Versions: 1.18, 1.19
            3. OCP Versions: 4.5, 4.6

            No issues found.

            prateek.kumar Prateek Kumar (Inactive) added a comment - - edited Backup Image 1.1.0 was tested with 2.2.0 against combinations of following versions apart from current supported versions in 2.2.0 GA : Server Versions: 6.6.0, 6.6.1 K8s Versions: 1.18, 1.19 OCP Versions: 4.5, 4.6 No issues found.

            Discussed with Patrick Varley to confirm there should be no inherent problem with it on 6.5.2, it is more there were no resources to formally QE it for backwards compatibility. There are even some customers using it in this manner apparently.

            As part of CAO 2.2 QE, we have tested it with 6.5.2 within the scope of the needs for CAO.

            QE has confirmed that backup works for CAO 2.2 across these versions so, whilst the more general use of the tool is not covered by backwards compatibility testing, we are indicating it is supported for CAO 2.2.

            patrick.stephens Patrick Stephens (Inactive) added a comment - - edited Discussed with Patrick Varley  to confirm there should be no inherent problem with it on 6.5.2, it is more there were no resources to formally QE it for backwards compatibility. There are even some customers using it in this manner apparently. As part of CAO 2.2 QE, we have tested it with 6.5.2 within the scope of the needs for CAO. QE has confirmed that backup works for CAO 2.2 across these versions so, whilst the more general use of the tool is not covered by backwards compatibility testing, we are indicating it is supported for CAO 2.2.

            Tools QE ran a subset of backup tests with 6.6.2 cbbackupmgr tool against a CB cluster running 6.5.2 , the tests pass. This supports the assertion made by Patrick above.

            prateek.kumar Prateek Kumar (Inactive) added a comment - Tools QE ran a subset of backup tests with 6.6.2 cbbackupmgr tool against a CB cluster running 6.5.2 , the tests pass. This supports the assertion made by Patrick above.

            After some further review, the confusion seems to be that the server docs weren't updated after 6.6.1. Since it's tested/working and is what the engineering teams discussed, I've opened a doc bug in MB-47243. I'll close this accordingly.

            ingenthr Matt Ingenthron added a comment - After some further review, the confusion seems to be that the server docs weren't updated after 6.6.1. Since it's tested/working and is what the engineering teams discussed, I've opened a doc bug in MB-47243 . I'll close this accordingly.

            People

              ingenthr Matt Ingenthron
              prateek.kumar Prateek Kumar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty