Project

General

Profile

Feature #3085

Feature #3076: migrate to new (2018-03) server "host2.osmocom.org"

where to migrate openmoko-backup?

Added by laforge over 1 year ago. Updated 12 months ago.

Status:
In Progress
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
03/19/2018
Due date:
% Done:

40%

Spec Reference:

Description

This is currently eating up most of our disk consumption. The new server has 500GB RAID-1 SSD but no bulk HDD space.

  • Keep the old machine as backup storage?
  • backup to sysmocom office?
  • alternatives?

Related issues

Related to Osmocom.org Servers - Feature #3303: migrate openmoko.org into "archive mode" and remove dedicated server for itNew05/29/2018

Related to Osmocom.org Servers - Feature #3304: create static archive of openmoko.org web pagesRejected05/29/2018

Related to Osmocom.org Servers - Feature #3305: migrate openmoko.org mail + lists to osmocom.orgClosed05/29/2018

History

#1 Updated by zecke over 1 year ago

Sysmocom off-site or admin.sysmocom.de? For non company data maybe we can periodically put the data somewhere else as well?

#2 Updated by laforge over 1 year ago

  • Subject changed from where to migrate openmok-backup? to where to migrate openmoko-backup?

#3 Updated by laforge about 1 year ago

  • % Done changed from 0 to 40

once openmoko.org moves to serving static pages from an archive, this will mostly solve itself. We can keep one final snapshot on an HDD somewhere in storage.

#4 Updated by laforge about 1 year ago

  • Related to Feature #3303: migrate openmoko.org into "archive mode" and remove dedicated server for it added

#5 Updated by laforge about 1 year ago

  • Related to Feature #3304: create static archive of openmoko.org web pages added

#6 Updated by laforge about 1 year ago

  • Related to Feature #3305: migrate openmoko.org mail + lists to osmocom.org added

#7 Updated by laforge 12 months ago

  • Status changed from New to In Progress
  • I've rsync'ed hydra.openmoko.org:/space/backup (404GB) to a dedicated logical volume on our new berlin off-site backup machine. This contains backups of former agni, bhavani and chandra, i.e. more of an archive than a daily/current backup
  • I discovered that the backup (about which this ticket was created) is failing since March 4, 2017 with the following error:
    BackendException: ssh connection to 2a01:4f8:191:444b::2:6:22 failed: Incompatible ssh peer (no acceptable kex algorithm)
    

So somehow the SSH key exchange algorithms accepted by either of the two sides are no longer in agreement, resulting in no working transfer of the backup files. When manually using the "ssh" command, it works. It appears that duplicity is using paramiko, and we're using an ancient version of it. Trying to work around it to get the backup going before migrating it.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)