Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-34338

Backward compatibility of 6.5 cbbackupmgr.

    XMLWordPrintable

Details

    • High

    Description

      cbbackupmgr 6.5 should be compatible with older versions of cluster (5.5.x,6.0.x)
      https://docs.google.com/document/d/12CtplPjnc8ZWsLyGufJSvY9DQa-yl4e9LMW7SrEOZH4/edit?usp=sharing

      Attachments

        Issue Links

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

          Activity

            Patrick Varley Arunkumar Senthilnathan isn't 6.5cbbackupmg tested with older version for compatibility?

            anil Anil Kumar (Inactive) added a comment - Patrick Varley Arunkumar Senthilnathan isn't 6.5cbbackupmg tested with older version for compatibility?

            This is tested by dev team, although couldn't get this officially done by QE. I would still push for this post Mad Hatter in 6.5.x.

            chaitra.ramarao Chaitra Ramarao (Inactive) added a comment - This is tested by dev team, although couldn't get this officially done by QE. I would still push for this post Mad Hatter in 6.5.x.
            thuan Thuan Nguyen added a comment - - edited

            Manually verified using cbbackupmgr from 6.5.1-6155 to run backup and restore on 6.0.1 and 6.0.4 cluster.
            Case 1 (cbbackupmgr 6.5.1 run on 2 clusters: 6.0.1 and 6.0.4):

            • Create 2 nodes cluster with travel-sample bucket.
            • Create backup repo
            • Run backup
            • Run backup
            • Add 1 doc to travel sample and create gamesim-sample
            • Run backup
            • Run backup
            • Create default bucket and load 10K docs
            • Run backup
            • Flush all 3 buckets
            • Run restore data back to bucket. => Passed
            • Merge backup from 4 to 5 => passed
            • Flush all 3 buckets
            • Run restore data back to buckets. => Passed
            • Delete all 3 buckets
            • Run restore data with --auto-create-buckets => passed
            • Merge backup from 1 to 4 => passed
            • Delete all 3 buckets
            • Create 3 buckets
            • Run restore data back to buckets. => Passed

            Case 2:

            • Start with cbbackupmgr from a node of 6.0.1
              • Create 2 nodes cluster with travel-sample bucket.
              • Create backup repo
              • Run backup
              • Run backup
              • Add 1 doc to travel sample and create gamesim-sample
              • Run backup
            • Uninstall node 6.0.1 (the one use cbbackupmgr) and clean install 6.5.1 to use cbbackupmgr from 6.5.1 version on backup repo of 6.0.1
              • Run backup (from now, backup and restore will run with cbbackupmgr from 6.5.1 version)
              • Create default bucket and load 10K docs
              • Run backup
              • Flush all 3 buckets
              • Run restore data back to bucket. => Passed
              • Merge backup from 4 to 5 => passed
              • Flush all 3 buckets
              • Run restore data back to buckets. => Passed
              • Delete all 3 buckets
              • Run restore data with --auto-create-buckets => passed
              • Merge backup from 1 to 4 => passed
              • Delete all 3 buckets
              • Create 3 buckets
              • Run restore data back to buckets. => Passed
                Verified data, views and indexes backup in repo and restore back to cluster.
            thuan Thuan Nguyen added a comment - - edited Manually verified using cbbackupmgr from 6.5.1-6155 to run backup and restore on 6.0.1 and 6.0.4 cluster. Case 1 (cbbackupmgr 6.5.1 run on 2 clusters: 6.0.1 and 6.0.4): Create 2 nodes cluster with travel-sample bucket. Create backup repo Run backup Run backup Add 1 doc to travel sample and create gamesim-sample Run backup Run backup Create default bucket and load 10K docs Run backup Flush all 3 buckets Run restore data back to bucket. => Passed Merge backup from 4 to 5 => passed Flush all 3 buckets Run restore data back to buckets. => Passed Delete all 3 buckets Run restore data with --auto-create-buckets => passed Merge backup from 1 to 4 => passed Delete all 3 buckets Create 3 buckets Run restore data back to buckets. => Passed Case 2: Start with cbbackupmgr from a node of 6.0.1 Create 2 nodes cluster with travel-sample bucket. Create backup repo Run backup Run backup Add 1 doc to travel sample and create gamesim-sample Run backup Uninstall node 6.0.1 (the one use cbbackupmgr) and clean install 6.5.1 to use cbbackupmgr from 6.5.1 version on backup repo of 6.0.1 Run backup (from now, backup and restore will run with cbbackupmgr from 6.5.1 version) Create default bucket and load 10K docs Run backup Flush all 3 buckets Run restore data back to bucket. => Passed Merge backup from 4 to 5 => passed Flush all 3 buckets Run restore data back to buckets. => Passed Delete all 3 buckets Run restore data with --auto-create-buckets => passed Merge backup from 1 to 4 => passed Delete all 3 buckets Create 3 buckets Run restore data back to buckets. => Passed Verified data, views and indexes backup in repo and restore back to cluster.

            Manual testing for customer scenarios and P0s done - ETA for automation 03/03

            arunkumar Arunkumar Senthilnathan added a comment - Manual testing for customer scenarios and P0s done - ETA for automation 03/03
            thuan Thuan Nguyen added a comment - - edited

            Manually verified using cbbackupmgr from 6.5.1-6200 to run backup and restore on 5.5.0 cluster.
            Start with cbbackupmgr from a node of 5.5.0

            • Create 2 nodes cluster with travel-sample bucket.
            • Create backup repo
            • Run backup
            • Run backup
            • Add 1 doc to travel sample and create gamesim-sample
            • Run backup
            • Uninstall node 5.5.0 (the one use cbbackupmgr) and clean install 6.5.1-6200 to use cbbackupmgr from 6.5.1 version on backup repo of 5.5.0
            • Run backup (from now, backup and restore will run with cbbackupmgr from 6.5.1 version)
            • Create default bucket and load 10K docs
            • Run backup
            • Flush all 3 buckets
            • Run restore data back to bucket. => Passed
            • Merge backup from 4 to 5 => passed
            • Flush all 3 buckets
            • Run restore data back to buckets. => Passed
            • Delete all 3 buckets
            • Run restore data with --auto-create-buckets => passed
            • Merge backup from 1 to 4 => passed
            • Delete all 3 buckets
            • Create 3 buckets
            • Run restore data back to buckets. => Passed

            Verified data, views and indexes backup in repo and restore back to cluster.

            thuan Thuan Nguyen added a comment - - edited Manually verified using cbbackupmgr from 6.5.1-6200 to run backup and restore on 5.5.0 cluster. Start with cbbackupmgr from a node of 5.5.0 Create 2 nodes cluster with travel-sample bucket. Create backup repo Run backup Run backup Add 1 doc to travel sample and create gamesim-sample Run backup Uninstall node 5.5.0 (the one use cbbackupmgr) and clean install 6.5.1-6200 to use cbbackupmgr from 6.5.1 version on backup repo of 5.5.0 Run backup (from now, backup and restore will run with cbbackupmgr from 6.5.1 version) Create default bucket and load 10K docs Run backup Flush all 3 buckets Run restore data back to bucket. => Passed Merge backup from 4 to 5 => passed Flush all 3 buckets Run restore data back to buckets. => Passed Delete all 3 buckets Run restore data with --auto-create-buckets => passed Merge backup from 1 to 4 => passed Delete all 3 buckets Create 3 buckets Run restore data back to buckets. => Passed Verified data, views and indexes backup in repo and restore back to cluster.
            ritam.sharma Ritam Sharma added a comment -

            Thuan Nguyen - I believe you have verified the improvement. Can you please close on the ticket.

            ritam.sharma Ritam Sharma added a comment - Thuan Nguyen - I believe you have verified the improvement. Can you please close on the ticket.

            People

              thuan Thuan Nguyen
              chaitra.ramarao Chaitra Ramarao (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty