Menu

#4605 Filesystem Backup - Command to run after backup not running

1.750
closed-fixed
nobody
None
5
2015-09-05
2015-05-27
Sk1llSh0t
No

I have a bash script that i want to run after a filesystem backup is complete. i can run it from a terminal no problem. It does not seem to run when the backup completes. I also have a script that runs before the backup starts and this works fine without problems. Can someone verify if post backup command is working trying to run a bash file?

Discussion

  • Jamie Cameron

    Jamie Cameron - 2015-05-28

    Does your backup complete successfully? If not, the script won't be run ..

     
    • Sk1llSh0t

      Sk1llSh0t - 2015-08-31

      When i run the backup manually, i see a few "file changed as I read it" entries in the output. The files were a few log files. anyway to ignore this and complete successfully?

       
  • Sk1llSh0t

    Sk1llSh0t - 2015-08-31

    I found the setting to ignore file access errors like this one. I checked this and ran the backup again. I still get the file changed as i read it error even when ignore read errors is set to yes.

     

    Last edit: Sk1llSh0t 2015-08-31
  • Sk1llSh0t

    Sk1llSh0t - 2015-08-31

    So the way i corrected the above error is i had to add --warning=no-file-changed --warning=no-file-removed to the extra command line parameters. I still get a failed. the output is below. any help on this would be great.

    Performing backup of / to /VPS_Backup-%Y_%m_%d.tar.gz ..

    tar: Removing leading /' from member names tar: Removing leading/' from hard link targets

    .. backup failed!

     
  • Sk1llSh0t

    Sk1llSh0t - 2015-08-31

    i'm out of ideas. Here is what i have currently and it appears to run without any errors
    Extra Parameters: --warning=no-file-changed --warning=no-file-removed -C /
    Directories to backup: .
    This is my current setup for backing up. i also have ignore read errors checked. I get no errors or warnings and it still says it fails in the end. The backup file is created. Not sure what else to do.

     
  • Jamie Cameron

    Jamie Cameron - 2015-09-01

    Unfortunately those flags cause the tar command to not output any error messages, but still exit with a failure status code when it completes.

     
  • Sk1llSh0t

    Sk1llSh0t - 2015-09-01

    Do you have any suggestions for getting around this? The only workaround i can think of is to setup a cron job that runs my post backup script after the filesystem backup runs. It doesn't appear there is a way to ignore all errors. For whatever reason, the filesystem backup fails everytime and there is no way to bypass it. Thanks for any help you can provide!

     

    Last edit: Sk1llSh0t 2015-09-01
  • Jamie Cameron

    Jamie Cameron - 2015-09-02

    Unfortunately not - the tar command just behaves this way :-(

    Or are you looking for a way to have the post-backup command always run even if the backup appears to fail?

     
  • Sk1llSh0t

    Sk1llSh0t - 2015-09-02

    I'm looking for a way for the post-backup command to run even if tar "fails".

     
  • Jamie Cameron

    Jamie Cameron - 2015-09-03

    Ok, I will add a checkbox for this in the next Webmin release.

     
  • Jamie Cameron

    Jamie Cameron - 2015-09-03
    • status: open --> closed-fixed
     
  • Sk1llSh0t

    Sk1llSh0t - 2015-09-05

    Great! Thanks. I appreciate that

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.