[DOCS-4832] Document data type changes when restoring data via MMS Created: 17/Feb/15 Updated: 27/Jul/16 Due: 10/May/16 Resolved: 02/May/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Ronan Bohan | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 43 weeks, 1 day ago | ||||
| Epic Link: | docs-restore-data | ||||
| Story Points: | 2 | ||||
| Description |
|
The subtype of a BinData object can change when the database is backed up and restored using MMS. In particular, a source database which contains a BinData object with 'subtype 2' will be converted to a BinData object with 'subtype 0'. While the data is still intact this is a change in format which may not cause some confusion ("why does not restored database not contain the same data as the source database?" - it does at the logical level but not at the physical level) Subtype 2 is deprecated as per the 'BSON spec' but we do not document that the backup and restore process will automatically convert the subtype. |
| Comments |
| Comment by Steve Briskin (Inactive) [ 19/Apr/16 ] |
|
This is still the case, the bug ticket and original customer ticket are linked. |
| Comment by Ian Bentley [ 15/Apr/16 ] |
|
Seems possible. I can't find a matching bug ticket right now. Should be easy to run a test to confirm/deny. |