NimbostratusI upgrade a new hotfix to cure Shellshock and run into an issue on a few devices. The cron job and all shell scripts did not transfer to the new boot partition even I selected "Install Configuration." The other device on the same pair has everything transfer to the new boot partition, so I am not sure what I did wrong?
Employeenot sure that every cron tasks or scripts that are not tmsh based are backuped. could you have change the backup script on some device and not others ?
sol4422: Viewing and modifying the files that are configured for inclusion in a UCS archive
https://support.f5.com/kb/en-us/solutions/public/4000/400/sol4422.html
Adminhi AP, that is expected behavior. Anything you do the system outside of configuration awareness will not be carried forward with a hotfix or upgrade. You can try the process Arnaud is suggesting, but I believe the USC configuration files are not carried forward either so it would likely not work.
What version are you on, and what does your script do that requires cron? In newer versions, three are alternatives with iCall and now built-in functions that used to require system scripts.
NimbostratusWe have a centralized backup location for all Linux devices and that is a standard across the board. My script create a backup to a /var/tmp, then remove it after scp to the backup location. It is a pain to rebuild the cron job, recreate the keygen, and ask the other admin to update the new key every time. I have looked into BIG-IQ as a solutions next year but not sure if it has the ability to move UCS files to the network shared.