| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Technical Name |
auto_backup_odoo |
| License | See License tab |
| Website | https://www.linkedin.com/in/hilar-ak/ |
| Versions | 8.0 9.0 10.0 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0 |
BACKUP ODOO DATABASES & FILESTORE
Available Odoo Backup DB/Filestore Modes:
- Local
- Remote Server
- Google Drive
- Dropbox
Module For backup ODOO databases and automating the backup process of ODOO.
- Multiple Backup Modes
- Filestore Backup
- Backup ODOO Databases in specified path
- Detailed Message Log
- Backup Status Information and History
- User can select the format to dump, either custom archive, plain text SQL or tar archive
- Archive Backup Process
- Repeat Missed Backup Process
Features
- Dump ODOO Database in specified format
- Zip filestore in a specified loaction
- Output a custom archive suitable for input into pg_restore. This is the most flexible format in that it allows the reordering of loading data as well as to object definitions. This format is also compressed by default. Here we user gzip ie, test.gz, We also recommend you to select Custom, because Using the custom format you can restore single objects from a backup.
- Output a plain-text SQL script file (the default). The plain text format is useful for very small databases with a minimal number of objects but other than that, it should be avoided.
- Output a tar archive suitable for input into pg_restore. Using this archive format allows reordering and/or exclusion of database objects at the time the database is restored. It is also possible to limit which data is reloaded at restore time. we use tar with gzip
- Backup Filestore
- Multiple backup modes at sametime
Tech
Odoo Auto Backup Module uses
- PYTHON - Models
- XML - Views
- HTML - UI
- Twitter Bootstrap - UI
- backbone.js - Views
- jQuery
- PSQL - DB
External Dependencies
- PYSFTP
pip install pysftp - Dropbox
pip install dropbox - Progress Meter
pip install tqdm
Installation
Install the odoo and Auto Backup module. After installation you can configure backup under general settings. If you are using the google drive mode, then msust enable the google integration under general settings and update the google drive refresh token.
CHANGELOGS
Date: 07/12/2020
- Performance Improvement
- Session Upload Trace For Dropbox Files > 150 mb
- Full Metadata Track In Message Logs
- Fix Dropbox Tar files upload
- Progress Meter In Logs
Todos
- Amazon S3 Backup
Author
Hilar AK
Git Repository
Hilar AK
Installation Guide: Python Packages with pip and Virtual Environments
Installing Python Packages with pip
Python packages can be easily installed using pip, the package installer for Python. Follow the steps below to install packages using pip:
- Open your command-line interface (e.g., Terminal, Command Prompt).
- Check if pip is installed by running the following command: bash
#!/bin/bash $ pip --version
If pip is not installed, you can install it by following the official documentation athttps://pip.pypa.io/en/stable/installing/.
To install a package, use the following command:
$ pip install package\_name
Replace package_name with the name of the package you want to install.
Example: To install the pysftp, dropbox, tqdm, simplejson package, run:
$ pip install pysftp dropbox tqdm simplejson
You can install multiple packages by listing them with spaces:
$ pip install package1 package2 package3
To install a specific version of a package, use the following command:
$ pip install package\_name==version\_number
Replace version_number with the desired version of the package.
Example: To install version 2.2.0 of the numpy package, run:
$ pip install numpy==2.2.0
- If you don’t specify a version, pip will install the latest version available.
Installing Packages within a Virtual Environment
Using a virtual environment is a recommended practice to manage Python packages for specific projects. Follow the steps below to install packages within a virtual environment:
- Create a new virtual environment by running the following command:
$ python -m venv env\_name
Replace env_name with the desired name for your virtual environment.
Activate the virtual environment:
- On Windows:
$ .\env\_name\Scripts\activate
On macOS and Linux:
$ source env_name/bin/activate
Once the virtual environment is activated, use pip to install packages as described in the previous section. The packages will be installed within the virtual environment and won't interfere with other Python installations.
To deactivate the virtual environment, simply run the following command:
$ deactivate
- This will return you to your regular command-line environment.
Using virtual environments helps maintain clean and isolated environments for different projects, ensuring package dependencies are managed effectively.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module