Project

General

Profile

Actions

action #96269

closed

openQA Project - coordination #103947: [saga][epic] Scale up: Future proof backup of o3+osd

Define what a "complete OSD backup" should or can include

Added by okurz over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2021-07-29
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We want to have a complete OSD backup but for that first we need to understand what can be included in "complete", depending on importance, restorability, expected sizes and available space

Acceptance criteria

  • AC1: We know for which data from OSD we have enough space to save at least one copy on storage.qa.suse.de

Suggestions

  • DONE: Find out currently available space on storage.qa.suse.de -> as of 2021-07-29 we have 11TB free
  • Get an overview of which components of storage and which folders take how much space, e.g. based on
df -h
Filesystem      Size  Used Avail Use% Mounted on
…
/dev/vda1        20G  6.8G   12G  37% /
/dev/vdb        100G   74G   27G  74% /srv
…
/dev/vdc        7.0T  5.9T  1.2T  84% /assets
/dev/vde        5.5T  2.0T  3.6T  37% /space-slow
/dev/vdd        5.5T  4.8T  809G  86% /results
  • Update #88546 with the result of what should/can be included in a complete backup

Related issues 2 (0 open2 closed)

Related to openQA Infrastructure - action #44078: Implement proper backups for o3 size:MResolvedmkittler2018-11-20

Actions
Copied from openQA Infrastructure - action #88546: Make use of the new "Storage Server", e.g. complete OSD backupResolvedokurz

Actions
Actions

Also available in: Atom PDF