backup automation
5 TopicsF5 Auto Backup iApp Error 550 Filename Invalid on FTP
Trying the codeshare iApp here :https://devcentral.f5.com/codeshare/f5-iapp-automated-backup-1114 All works well but then dies at the end with the ftp stor command. Tried some stuff with adding / etc to the path on filezilla but still nothing. (000010)4/9/2019 15:36:11 PM - (not logged in) (10.1.62.42)> 215 UNIX emulated by FileZilla (000010)4/9/2019 15:36:11 PM - (not logged in) (10.1.62.42)> USER labftp (000010)4/9/2019 15:36:11 PM - (not logged in) (10.1.62.42)> 331 Password required for labftp (000010)4/9/2019 15:36:11 PM - (not logged in) (10.1.62.42)> PASS ********** (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> 230 Logged on (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> TYPE I (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> 200 Type set to I (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> PASV (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> 227 Entering Passive Mode (10,1,62,201,219,75) (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> STOR /ftpsrv/20190409_bigip2.akmlab.local.ucs (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> 550 Filename invalid (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> QUIT (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> 221 Goodbye (000010)4/9/2019 15:36:11 PM - labftp (10.1.62.42)> disconnected. (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> Connected on port 21, sending welcome message... (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> 220-FileZilla Server 0.9.60 beta (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org) (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> 220 Please visit https://filezilla-project.org/ (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> SYST (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> 215 UNIX emulated by FileZilla (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> USER labftp (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> 331 Password required for labftp (000011)4/9/2019 15:36:27 PM - (not logged in) (10.1.62.41)> PASS ********** (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> 230 Logged on (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> TYPE I (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> 200 Type set to I (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> PASV (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> 227 Entering Passive Mode (10,1,62,201,244,80) (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> STOR /ftpsrv/20190409_bigip1.akmlab.local.ucs (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> 550 Filename invalid (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> QUIT (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> 221 Goodbye (000011)4/9/2019 15:36:27 PM - labftp (10.1.62.41)> disconnected.Solved685Views0likes2CommentsHelp! - SCP Automated Backup file using Password
Hello Gentlemen, I need to push the automated configuration backup files to a Windows server. I tried this by copying the pub_key on to the destination server where this didn't work as the destination windows server is not supporting key based authentication. The F5 LTM devices are running on TMOS version 11.4.1 I need to authenticate the destination server with password and I'm not sure if the automation script in place is working as expected, request your assistance. Thanks for your help in advance! Please find the code below: ! /bin/bash var1=date rm /automation/backup/* devicename=F5LTM01_`date +%F`.ucs tmsh save /sys ucs /automation/backup/$devicename scp /automation/backup/$devicename F5Backup@XX.XX.XX.XX:/F5Backup echo "Back up File copied to the Back Up Server(XX.XX.XX.XX) successfully to /F5Backup/ directory"387Views0likes1CommentVMWare Backups of active VEs?
We collect nightly UCS files of all of our BIG-IP VEs. If we need to restore from UCS, it requires requesting the build of a new guest before we can apply the latest UCS backup (VMWare is managed by a different team). Most of our other organization VMs have snapshots taken that can be used for quick restoration in the case of failure. We do not have snapshots taken of our VEs because it is not recommended: K000093184: Since the Snapshot 'freezes' or 'pauses' TMM this prevents real-time access to the CPU. Due to this F5 does not support the Snapshot process being used on a BIG-IP. Other than restoring from UCS files, are there any other recommended automated backup procedures of ACTIVE VMWare BIG-IP VEs that full backups can be done from?Solved113Views0likes5CommentsBIG-IP Auto backup configure and send SCP/SFTP using crontab
Prerequisite: Secure Copy Protocol server (SCP) server. BIG-IP CLI Access- recommened root user. Configuration Steps: Step#1: Login BIG-IP cli and generate ssh key pair. #ssh-keygen Step#2: Push the id_rsa.pub key to remote scp server. So that without password we can login. ssh-copy-id scp_user@<remote-scp-ip> #ssh-copy-id -i /root/.ssh/id_rsa.pub scpnet@10.1.1.10 Now you can check ssh public key authentication working by tring ssh login. ssh scpnet@10.1.1.10 Now test that public key authentication working. Simply do ssh on scp server: ssh scp_user@scp_ip If it's login remote scp server without password now good to go next step. Step#3: Make directory where the backup will stored. mkdir /var/ucs Step#4: Set schedule through crontab. crontab -e Step#5: After open cron file click i for insert and paste backup taking command. 0 1 * * * tmsh save /sys ucs /var/ucs/$(/bin/hostname).ucs && scp /var/ucs/$(/bin/hostname).ucs scp_user@<scp_server_ip>:/home/scpnet/F5/DC_F5_Node_02/$(/bin/hostname)-$(date +\%Y-\%m-\%d).ucs For save click ESC :wq Step#6: Now verfiy the crontab by crontab -l Note: This is the simplified 😊 version of below two article. I am tried to simplify and straightforward guide. https://my.f5.com/manage/s/article/K13418 https://my.f5.com/manage/s/article/K1345447Views0likes0CommentsBIG-IQ Archive Error
Hello, We currently have a BIG-IQ that was successfully performing backups to the backup server until the server guys implemented some stricter SSH timeouts. From what I gather, the archive is failing because the BIG-IQ seems to open up the SCP connection before the backup finishes. Once the backup has finished it then proceeds to pass the username but the SSH session has timed out by that time. Does anyone know of a way to change the order in which the BIG-IQ does the backup, so change it from SSH -> Backup -> SSH credentials -> copy file to Backup -> SSH -> SSH credentials -> copy file to Backup?35Views0likes0Comments