Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.6.0
-
Untriaged
-
1
-
No
Description
Build: 7.0.0-1902
Steps:
Create a bucket with 100 scopes and 1 collection in each scope (including default scope and collection)
Load 1000 items in each named scope (except default scope)
Configure backup with s3
Take backup of the bucket
Restore it to a bucket which has same scope names but with different id
Restore failures are printed twice:
[root@node1-mad-hatter-testing-centos7 bin]# ./cbbackupmgr restore -a /tmp/entbackup -r backup --s3 --s3-bucket aruntestbackups3 --obj-staging-dir /tmp/s3obj -c 10.112.194.102 -u Administrator -p password
(1/1) Restoring backup 2020-05-03T21_12_42.673993609-07_00
Copying at 0B/s (estimating time remaining) 0 items / 0B
default [ ] 100.00%
Error restoring cluster: Scope 38 with name 'my_scope_31' exists with a different name/id on the cluster, a manual remap is required
Restore bucket 'default' failed
(1/1) Restoring backup 2020-05-03T21_12_42.673993609-07_00
Copying at 0B/s (estimating time remaining) 0 items / 0B
default [ ] 100.00%
[root@node1-mad-hatter-testing-centos7 bin]# ./cbbackupmgr restore -a /tmp/entbackup -r backup --s3 --s3-bucket aruntestbackups3 --obj-staging-dir /tmp/s3obj -c 10.112.194.102 -u Administrator -p password --map-data default=default
`--map-data` option only works for the Data service. Will not restore the metadata for any other service
(1/1) Restoring backup 2020-05-03T21_12_42.673993609-07_00
Copying at 0B/s (estimating time remaining) 0 items / 0B
default [ ] 100.00%
Error restoring cluster: no such file or directory
Restore bucket 'default' failed
(1/1) Restoring backup 2020-05-03T21_12_42.673993609-07_00
Copying at 0B/s (estimating time remaining) 0 items / 0B
default [ ] 0.00%
Attachments
Issue Links
- relates to
-
MB-39128 CBM s3 backup progress issues
- Closed