You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This Page is under Development

Introduction

Backup and Restore is the feature developed in regard to WebUI.

The user can Backup the current user settings to the local PC and Restore the same to device when required.

Backup Settings:

  • Allows the user to save the current settings
  • Settings from database files are backed up in an encrypted format
  • Generates a tar file of the encrypted database files
  • Saves the tar file to Local PC.

Restore Settings:

  • Allows the user to select the backup file with required settings
  • Extracts the tar file and Decrypts the containing database files
  • Loads backed up settings to device
  • Device will be rebooted automatically to apply the settings.

Design Considerations

Backup and Restore functionalities are supported by a set of script files. Following are the mentioned script files:

   →   ConfPhp

   →  download_user_settings.php

   →   upload_user_settings1.php

   →   upload_user_settings2.php

   →   backup_user_settings.php

These script files which are already present in the RDK build, will execute when the Backup and Restore buttons are clicked.

Backup Settings

Scripts backup_user_settings.php, download_user_settings.php performs Encryption and download of the encrypted file.

It encrypts the database files which contains the Current User settings. A tar file is generated with encrypted files together and stored in temporary folder /tmp/. The tar file from temporary folder is downloaded to the Local PC of User.

Restore Settings

Scripts upload_user_settings1.php, upload_user_settings2.php perform the Restore and Status update functions.

The files which are uploaded in WebUI are extracted to get the encrypted files. These encrypted files are decrypted and the database files are saved to temporary folder /var/tmp/. The files are retrieved and replaced with the existing database files in RPi image.

Architecture


  • Layout

           <Architecture Diagram>

  • Communication

          <Describe the communication between the sub-systems. (Diagrams may be used to illustrate communications). >

External Interfaces (Input/Output files or data sets)

< Identify input interfaces, function call protocol, and the nature of the data structures passed across the interface between the sub-modules>

< Identify output interfaces, function call protocol, and the nature of the data structures passed across the interface. >

Data Model

<Provide a description of the data model>

Limitations

             < Describe the cases that are identified as problem but unable to report to it due to various factors. Describe the factors >

Future Enhancements

            < Describe how the current design is suitable for future enhancement without completely modifying existing design . >

  • No labels