Using SFTP or SCP to back up a Cisco Switch overwrites files instead of incrementing.
Our previous method of Cisco Switch backup using TFTP would increment a file of the same name instead of overwriting it. Below is example of Cisco TFTP commands.
wr\r
\p\p\p\p\p\p\p
copy running-config tftp:\r
\p
127.0.0.1\r
\p
\r
The example of new commands to work with Cerebrus SCP are below.
copy running-config scp://ciscobackup.backup.com/ \r
\r
\r
\r
Neither set of commands explicitly call out increment versus Overwrite
I would be nice if Cerebrus would handle config file incrementation.
-
The behavior you're describing regarding file incrementation or overwriting in the context of Cisco switch backups is typically not determined by the SCP (Secure Copy Protocol) or SFTP (SSH File Transfer Protocol) itself. Instead, it depends on how the remote device (in this case, the Cisco switch) and the SCP/SFTP client handle file transfers. Both SCP and SFTP are designed to overwrite files by default if a file with the same name already exists on the remote server.
To achieve file incrementation when backing up configurations from Cisco switches using SCP or SFTP, you typically need to implement this logic on the switch itself or use a script to handle the file renaming before transferring it to the server. Unfortunately, Cerberus just follows the behavior dictated by the client.
0
Please sign in to leave a comment.
Comments
1 comment