Project

General

Profile

action #44078

Implement proper backups for o3 size:M

Added by okurz over 2 years ago. Updated 15 days ago.

Status:
Workable
Priority:
Low
Assignee:
-
Target version:
Start date:
2018-11-20
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We should find a backup space for o3, e.g. 4TB for test data/assets

Acceptance criteria

  • AC1: Test assets are backed up and can be restored
  • AC2: Test results are backed up and can be restored
  • AC3: Screenshots are backed up and can be restored
  • AC4: /etc is backed up and can be restored
  • AC5: List of installed packages is backed up for reference

Suggestions

  • Use storage.qa.suse.de
  • We already have database backups elsewhere
  • Consider snapshots (if available) or rsync

Related issues

Related to openQA Infrastructure - action #69577: Handle installation of the new "Storage Server"Resolved2020-08-04

Copied to openQA Infrastructure - action #94015: proper backup for osdNew

History

#2 Updated by okurz over 2 years ago

As o3 is in a special network I recommend rsnapshot on backup.qa.suse.de syncing the data from o3.

#3 Updated by okurz over 2 years ago

#4 Updated by okurz over 2 years ago

  • Status changed from New to In Progress
  • Assignee set to okurz

Talked with tbro. 4TB is a problem. Anything in the range of up to 100GB is no problem to have, using space on old netapp, on request. However, I think then we can just as easily go with backup.qa which is easier for us given that we have full control of that machine and can trigger backups from there as suggested in #44078#note-2

#5 Updated by okurz over 2 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)

Unassigning again as preparation for longer absence. I should really not leave tickets assigned to me dangling "In Progress" :)

#7 Updated by okurz over 2 years ago

Automatic backup for the o3 webui host introduced with https://gitlab.suse.de/okurz/backup-server-salt/tree/master/rsnapshot covering so far /etc and the SQL database dumps. As next steps I recommend to save a bit more if feasible from /var/lib/openqa as well as from the workers which are transactional-servers. Maybe as well just /etc plus an autoyast profile.

#8 Updated by okurz about 1 year ago

  • Priority changed from Normal to Low
  • Target version set to Ready

#9 Updated by okurz 9 months ago

  • Related to action #69577: Handle installation of the new "Storage Server" added

#10 Updated by okurz 9 months ago

  • Status changed from Workable to Blocked
  • Assignee set to okurz

waiting for #69577 or #41918 first

#11 Updated by okurz about 1 month ago

#12 Updated by okurz about 1 month ago

  • Status changed from Blocked to New
  • Assignee deleted (okurz)

storage.qa.suse.de in place and usable

#13 Updated by cdywan 15 days ago

  • Subject changed from proper backup for o3 to Implement proper backups for o3 size:M
  • Description updated (diff)
  • Status changed from New to Workable

Also available in: Atom PDF