Forum Discussion

refra_151287's avatar
refra_151287
Icon for Cirrus rankCirrus
Jan 27, 2015

automatic archiving issue

Hi experts, I configured the automatic archiving template as configured [here], (https://devcentral.f5.com/articles/archiving-big-ip-configurations-with-an-iapp-in-v112) "" but i was informed that the archiving is not working (there's no any archives in the repository "/shared/backups/archives"), and also the apllication service related to this template gives an error says "warning source template has changed", and i'm not able anymore to change this application service. actually i don't know why the issue has happened, so i'm not able to detect the issue. so please could anyone face similar issue update me with best way to make it operational again. thanks in advance.

 

application delivery
devops
iApps
LTM
management

3 Replies

  • StephanManthey's avatar
    StephanManthey
    Icon for Nacreous rankNacreous
    Jan 27, 2015

    Hi refra,

     

    how about using a crontab and shell script to create archives per schedule?

     

    Two things to keep in mind:

     

    1. crontab configuration is not stored in archive file (.ucs)

     

    2. SSH keys in known hosts file are not stored in archive (.ucs)

     

    I used to install another script (called by /config/startup) to restore this data automatically.

     

    Please let me know, if this approach would be interesting.

     

    Thanks, Stephan

     

  • THi's avatar
    THi
    Icon for Nimbostratus rankNimbostratus
    Jan 29, 2015

    I tested the https://devcentral.f5.com/articles/f5-automated-backups-the-right-way today in my lab.

     

    First with local storing, then scp copying over to a Linux box. After a bit of struggle with ssh keys (have to be rsa not dsa for this to work) got it working well. When importing the template there is an ltm log warning message, however the import is successful and creating the backup app service with it goes ok. What I miss is logging when backup has been created/copied to target successfully. If the backup script fails, there is an error message in the ltm log.

     

    Implemented it to my customer later today and seems to work fine. Changing backup schedule is very easy with the iAPP.