Opened 3 years ago

Last modified 2 years ago

#2859 new task

Configure backups

Reported by: dustin Owned by:
Priority: major Milestone: sys - other
Version: Keywords:
Cc: sysadmins

Description (last modified by dustin)

We had discussed using Amanda for this, but I'm not particular.

The key goals are, I think, disaster recovery and backups of data that is not mirrored elsewhere (databases, FTP, etc.)

# Priority List #

  • Trac
  • Mailing List Archives
  • Package repositories (ftp.buildbot.net)

Change History (4)

comment:1 Changed 3 years ago by sa2ajj

  • Cc sysadmins added
  • Version 0.8.9 deleted

I do not think any backups are in place at the moment.

So we probably need to list things in the importance order that need to be taken care of one by one.

comment:2 Changed 3 years ago by dustin

  • Description modified (diff)

comment:3 Changed 3 years ago by dustin

From sysadmin email:

  • backup drive is mounted at service1:/mnt/backup0

---

And from Amar:

I have mounted our remote storage from the RTEMS NAS on service1. It is at /mnt/remote we are free to use whatever we need there. It costs us nothing to backup to our backup drive, boot a copy over there and then burn to bluray.

For backups I would prefer we create a /data/backup on each service host and jail then run local, staggered scripts to backup to this directory with Amanda to squirrel it away.

The reason I like this method is it is easy to do a local recovery in an emergency. We only need max 7 days of backup if we need longer we can go to archives of which we should have at least a months worth on our drive in service1. Barring that we can go to permanent archives or archive1 to grab older archives and then BD as required.

As always these are just what I had planned I'm open to ideas or other ways of doing things..

comment:4 Changed 2 years ago by dustin

  • Milestone changed from sys - on-bb-infra to sys - other
Note: See TracTickets for help on using tickets.