Browse Prior Art Database

A method to save multiple copies of configuration file as backup on a TFTP server

IP.com Disclosure Number: IPCOM000015187D
Original Publication Date: 2001-Nov-27
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 54K

Publishing Venue

IBM

Abstract

A method to save multiple copies of configuration file as backup on a TFTP server Disclosed is a method to obtain multiple backup copies of files saved at different times on a TFTP server avoiding to make assumption or development on the TFTP server itself to achieve this. Problem statement :

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

A method to save multiple copies of configuration file as backup on a TFTP

server

Disclosed is a method to obtain multiple backup copies of files saved at different times on a TFTP server avoiding to make assumption or development on the TFTP server itself to achieve this.

Problem statement :

  In a network environment the configuration of the machines (e.g. routers) need to be saved in order to allow a fast and easy backup in case of failure. When the machine fails it is replaced and the saved configuration is installed on the new machine.

   To allow this , many machines provide the capability to save the current configuration on a TFTP server (TFTP = Trivial file Transfer Protocol) . The functionality provided by a TFTP server is very small : only the capability of transferring file from or to the server is given, no file management capability from the client machine is available

  When the configuration is subject to frequent changes, there is a need to save it on a regular time base. Triggering an automatic process that save the file on a TFTP server is a convenient way to do it . But if you do this you will basically save a copy of the configuration that will be overridden by the new copy each time the process is triggered.

  Now there are cases when you want to keep several copies of the configuration, let's say one each day of the last 7 days. If you fear for example that for some reason the configuration might be corrupted of badly changed just before it is (automatically) saved. Therefore you need older copies to make sure you can recover with some minimal effort.

  The way you usually do this in similar situation is that you have your seven last days configuration copies : cfg_day-1, cfg_day-2, ...., cfg_day-7 .

  The next day you do a copy of cfg_day-6 on cfg_day-7 , overriding it , cfg_day-5 on cfg_day-6 etc and finally the current configuration is saved overridin...