Hello,
I'm currently trying out Robinhood v3 for a new lustre deployment and
I've been having a bit of trouble figuring out how to use the backup
policies.

I have working lhsm and cleanup policies, so after reading the wiki on
the backup policy I had a go with the config below, however I don't
think I'm setting the 'backend_path' correctly, as when I run
robinhood I get error:

2016/09/11 23:43:04 [7470/1] CheckFS | Error 2 in realpath(/backend):
No such file or directory
2016/09/11 23:43:04 [7470/1] smi_init | Failed to initialize status
manager backup: error=2

My current config (condensed):

%include "includes/backup.inc"

backup_archive_parameters {
  nb_threads = 8;
  # suspend policy run if action error rate > 10% (after 100 errors)
  suspend_error_pct = 10%;
  suspend_error_min = 100;
  action_params {
    backend_path = "/mnt/path/to/backup/location";
  }
}

backup_archive_rules {
  ignore_fileclass = empty_files;
  ignore_fileclass = migration_directory;

  rule backup_archive_directory {
    target_fileclass = archive_directory;
    condition { last_mod >= 30min }
  }
}
backup_archive_trigger {
  trigger_on = periodic;
  check_interval = 5min;
}

backup_remove_parameters {
  nb_threads = 8;
  # suspend policy run if action error rate > 10% (after 100 errors)
  suspend_error_pct = 10%;
  suspend_error_min = 100;
  action_params {
    backend_path = "/mnt/path/to/backup/location";
  }
}
backup_remove_rules {
  # keep deleted files for 6 month before removing from tape
  rule default {
    condition { rm_time > 24w }
  }
}
backup_remove_trigger {
  trigger_on = scheduled;
  check_interval = 1h;
}

I'm sure that the actual path I'm putting in for 'backend_path'
exists, it's on an NFS mount if that makes a difference.

Any hints would be much appreciated!
Cheers,
Matt Raso-Barnett

------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to