[MGNLBACKUP-125] Provide ability to exclude some workspaces from backup Created: 06/Feb/19  Updated: 05/May/22  Resolved: 05/May/22

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Federico Grilli Assignee: Roman Kovařík
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLPER-72 Make Find Bar result ranking user spe... 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)
Date of First Response:
Epic Link: Periscope improvements
Team: Nucleus

 Description   

The module doesn't seem to have the ability to choose which workspaces to include/exclude from backup. Apart from some basic workspaces which should probably always be included (e.g. config, pages, users, userroles etc), there are cases when it could be useful to be able to exclude some.

For instance, with the introduction of AI search rankings per user (MGNLPER-72) a new rankings workspace would be automatically added. Such workspace may easily end up holding GBs of non critical data which could be easily recreated at runtime. 



 Comments   
Comment by Richard Gange [ 25/Aug/21 ]

I think the best way to go about doing this is separate repositories. If you divide things up then you have some control.

Although it could work to exclude workspaces. I don't see a problem with that. But you would have to customize some JR Code for it. Repository copier is not offering the option to specify a list of workspaces. It works at the repo level so it seems repository splitting is the cleanest option.

The real problem with trying to exclude (or specifically include) workspaces is the shared resources. How can you ever be sure the datastore will be managed correctly. The nodetypes file as well. Versions. It could get tedious.

Comment by Dominik Maslanka [ 01/Mar/22 ]

check with aichimescu / ilgun  if issue still relevant 

Comment by Roman Kovařík [ 05/May/22 ]

Closing due to the amount of other high priority tickets. Please reopen if needed.

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