[MGNLBACKUP-98] Datastore not restored properly Created: 06/Apr/16  Updated: 29/Mar/22  Resolved: 07/May/16

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: 1.6.1
Fix Version/s: 2.0, 2.1

Type: Bug Priority: Critical
Reporter: Richard Gange Assignee: Ilgun Ilgun
Resolution: Obsolete Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 4.75d
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLBACKUP-97 Restore doesn't respect Datastore con... Closed
supersession
is superseded by MGNLBACKUP-99 Refactor backup module to use Reposit... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Sprint: Basel 42
Story Points: 13
Team: Nucleus

 Description   

To reproduce this issue:

  • Take a backup of a system that is known to have items in the datastore
  • Restore that backup to a new target environment.
  • Observe the datastore has no items

The instance will still work. All large binaries seem to be in the system. It appears that the restore process is not respecting the threshold set in the repo config and putting the binaries into the db.

You can also see a difference in the size of the db and repo. After the restore the db is larger and the repo is smaller.



 Comments   
Comment by Ilgun Ilgun [ 29/Apr/16 ]

Blocked due to MGNLBACKUP-99

Comment by Vivian Steller [ 17/Nov/16 ]

Why is this ticket obsolete?

Generated at Sun Feb 11 23:25:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.