Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.6.0
-
Untriaged
-
Unknown
Description
version: 7.0.0-1611
Steps:
1) create bucket testBucket
2) create custom scope my_scope
3) create custom collections collection1 and collection2 in my_scope
4) load data in collections default, collection1 and collection2
5) take backup
6) load more data in collections collection1 and collection2
7 ) take backup
8) drop collection collection1
9) take backup
10) create bucket with same scope and collections in destination cluster
11) restore from backup 1 to 1 to destination cluster with --include-data testBucket.my_scope.collection1
expected: only data in collection1 in backup to be restored
current behavior: 0 items restored
[root@node1-mad-hatter-testing-centos7 bin]# ./cbbackupmgr restore -c 10.112.194.102 -a /tmp/entbackup -r backup -u Administrator -p password -start 1 --end 1 --include-data testBucket.my_scope.collection1
|
|
(1/1) Restoring backup 2020-03-19T19_45_57.816700088-07_00
|
Copied all data in 1.001289205s (Avg. 0B/Sec) 0 items / 0B
|
|
Restore completed successfully
|
same behavior with _default and collection2 as well:
[root@node1-mad-hatter-testing-centos7 bin]# ./cbbackupmgr restore -c 10.112.194.102 -a /tmp/entbackup -r backup -u Administrator -p password -start 1 --end 1 --include-data testBucket.my_scope.collection2
|
|
(1/1) Restoring backup 2020-03-19T19_45_57.816700088-07_00
|
Copied all data in 1.000308832s (Avg. 0B/Sec) 0 items / 0B
|
|
Restore completed successfully
|
exclude-data works well as expected
Attachments
Issue Links
- relates to
-
MB-38623 cbbackupmgr backup is backing up zero documents for single collection in CC build 7.0.0-1569
- Closed
For Gerrit Dashboard: MB-38366 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
124036,3 | MB-38366 Fixed a bug causing '--include-data' to behave incorrectly | master | backup | Status: MERGED | +2 | +1 |