User stories: BackupUserStories
Milestone 1: Backup of @lab user's home directories.

Date 11/04/2008

Mounting disks ton a backup client machine

• From the disk machine do

  exportfs -i -o ro,async,no_root_squash 10.0.0.10:/export/disk/users/
  

• On backup client machine create a directory for mount point.

  mkdir /backup
  cd backup
  mkdir disk2 disk3 disk4
  

• Mount directory

  mount -o ro disk2:/export/disk/users disk2
  mount -o ro disk3:/export/disk/users disk3
  mount -o ro disk4:/export/disk/users disk4
  

Backups using Amanda

• Took backups of random data from user's home directories.
• Problem in restoring the backups - index list of backups was not seen. Problem resolved - error in documentation.
• Successful restoration.

Setting up mazurka

• Installed CentOS 5.0 on mazurka

Date 11/05/2008

Backups using Bacula

• Took backups of random data from user's home directories.
• Successful restoration.

Upgraded CentOS on mazurka to 5.2 version

• Installed amanda server on mazurka

Note:

• I was trying to create a test backup using mazurka server. However, when I tried to label virtual tapes as

  for ((i=1; $i<=9;i++)); do amlabel test test-0$i slot $i; done
  for ((i=10; $i<=25;i++)); do amlabel test test-$i slot $i; done
  

I received message as,

reading label test-01, tape is active

• Amanda does not label any tapes further. Also, after trying to reset tape to first slot, the message was 'loaded slot 25'.

  amtape test reset
  

Date 12/10/2008

I started from scratch last week and was able to run a successful backup and restore job for users on disk2. I couldn't debug the error regarding vtapes labeling, but possible reason could be misconfigured disk changer script.

I was unable to run amcheck command for users on disk3 with the error message as permission denied. However, backup and restore for the same users was successful. Related wiki post on amanda: Why does amcheck fail while amdump succeeds?

Bacula running successfully: Able to run successful backup and restore jobs using bacula. No failure issues so far.

Date 12/11/2008

• Bacula maintains directory structure.
• Explore different backup levels such as full, differential, and incremental for the same directory being backed up at the same storage location/directory.

Approx. data size of all @lab desktops: 320 GB Approx. max disk space available for backup on mazurka: 180 GB