Forum Discussion

Josh_44053's avatar
Josh_44053
Icon for Nimbostratus rankNimbostratus
Oct 08, 2012

Persisting scripts and crontab entries

I recently experienced the pain of losing a few scripts and crontab entries after an upgrade/hotfix. The scripts were stored in /root/scripts. I reproduced them with some effort, but it left me wondering.

 

 

Am I doing something improperly that is causing this?

 

5 Replies

  • What version are you running (and did you upgrade from). Did you not have an UCS files backed up off the device? Did you upgrade a volume other than the one with your scripts on (which you would of had), if so, you're files are probably still on the other volume. I think if you put these files in the /home/admin directory they get moved across in an upgrade and stored in UCS files.
  • I'm pretty sure crontab entries get moved too as long as you use crontab -e. Just don't put the files in the cron directories.

     

  • We upgraded to 10.2.4. After booting into HD1.2 and using the software management tool in the GUI, I booted back into HD1.1 (where we usually run). After switching back, /root/scripts (directory I created) had taken a hike and the rsa keys in /root/.ssh/ also said adios.

     

     

    Like you, I expected at least the files to get carried through in the ucs file. I'm currently investigating to see if perhaps the backup that was used after the upgrade didn't include these files in the first place.
  • i do not think /root/script is included in ucs by default.

    sol4422: Viewing and modifying the files that are configured for inclusion in a UCS archive

    http://support.f5.com/kb/en-us/solutions/public/4000/400/sol4422.html

    [root@ve10:Active] config  ls -l /root/scripts/
    total 2
    -rw------- 1 root root 5 Oct  9 13:52 test.sh
    
    [root@ve10:Active] config  b config save foo.ucs
    Saving active configuration...
    
    [root@ve10:Active] config  tar tzvf /var/local/ucs/foo.ucs |grep -i test.sh
    [root@ve10:Active] config 
    
  • As an aside, if you create your scripts as external monitors, pointing to "phantom" pools, you can create scheduled processes without dealing with crontab, and anything you put in /config/monitors is backed up in the UCS process.