File corruption on F5 Back-Ups

RodNC

I am having a problem downloading configs from our F5 BigIP systems.  The back-up runs okay and pulls the file down to the NCM server but the size is different and when I try to restore that file it does not work.

I suspect that the problem is the "cat" command in the device template.  My thought is that the "cat" command does not move the file as a binary file but rather as a text file and that is what is causing the problem but I don't know how to confirm or fix it.

chris.lapoint

Per this thread, it appears you need to back up the .ucs file via TFTP or SCP to get all the necessary files for a full restore.   I believe the .ucs file is a binary file.  NCM standard config download process only accepts text-based configs to avoid corrupting config compares and config change reporting, so you'll need to back it up using a execute script job.