In some cases it might be nesessary to create a backup directly on a remote machine for example if the remaining storage space on the PLC is to little to store the whole backup.
This could be achieved as follows.
On the PLC for local backups:
TAR_Local= tar -cpf ${StoreBackupAt}/backup-${DATE}.tar -C ${DATAPATH} $[DATA}
Adding a remote destination parameter the same backup script could be used even from a remote host.
On a PC connecting to the PLC via SSH:
REMOTE=user@192.168.1.10
TAR_Remote= ssh ${REMOTE} "tar -C ${DATAPATH} -cpf - $[DATA}" | gzip.exe > ${StoreBackupAt}/backup-${DATE}.tar
Another possibility to consider should be RSYNC and GIT to keep an archive of backups remotly continuously.
In some cases it might be nesessary to create a backup directly on a remote machine for example if the remaining storage space on the PLC is to little to store the whole backup.
This could be achieved as follows.${DATAPATH} $ [DATA}
On the PLC for local backups:
TAR_Local= tar -cpf ${StoreBackupAt}/backup-${DATE}.tar -C
Adding a remote destination parameter the same backup script could be used even from a remote host.
On a PC connecting to the PLC via SSH:$[DATA}" | gzip.exe > $ {StoreBackupAt}/backup-${DATE}.tar
REMOTE=user@192.168.1.10
TAR_Remote= ssh ${REMOTE} "tar -C ${DATAPATH} -cpf -
Another possibility to consider should be RSYNC and GIT to keep an archive of backups remotly continuously.