Skip to main content

Ftp Site Synchronization with Wget

I have a task for synchronizing a remote ftp folder to a local folder. At the remote site, that day’s folder is placed in the form of year_month_day and the local folder placed in the form of year/month/day .

 I have to copy the current day’s folder everyday because previous days folders are deleted regularly. In the case of a failure for copying files, the script must continue copying where it left off. So i decided to use wget command, wrote a script for that and put it into the crontab. I hope this helps you in such cases.


Remote ftp site synchronization script:
#!/bin/bash
year=$(date +%Y)
month=$(date +%m)
day=$(date +%d)
remote_folder=$year’_'$month’_'$day
local_folder=<ROOT FOLDER>/$year/$month/$day/
user=<USERNAME>
pass=<PASSWORD>
address=<FTP ADDRESS>
log_file=’<LOG FOLDER>’$remote_folder’.log’
touch $log_file
wget --mirror -nH --cut-dirs=1 -P $local_folder -o $log_file 'ftp://'$user':'$pass@$address'/'$remote_folder

Comments

Popular posts from this blog

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter:

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three