Varying frequency file removal about nbackup HOT 1 OPEN

I really like this idea.

I can't see anyway to do this without adding new settings to the .conf files -- with hard-coded defaults in the .sh script for old .conf files that don't have the new settings.

It can get super complex/tricky very fast. For example, you may want specific rules for previous week, and someone may want specific rules for 2 weeks prior.

How are you thinking of handling the logic?

I can think of two options:

• Add command line options/paramaters to nBackup.sh that reads in a delete rule (in some specific syntax). That way, you'd make X # of additional calls to nBackup.sh with rules for what to delete. It could even read multiple delete rules like nBackup.sh -d "delete rule syntax" -d "delete rule syntax" -d "delete rule syntax" ....
• Allow setting X # of delete rules (in some specific syntax) in the .conf file that nBackup.sh iterates over. Something like:

  DELETE_RULE_1=....
  DELETE_RULE_2=....
  DELETE_RULE_A=....
  

  nBackup.sh would just iterate over all of the variables that start with DELETE_RULE.

Coming up with the delete rule syntax is the hard part.

I'm keenly interested to hear your thoughts.

from nbackup.