- $0.99 since Sep 11, '19
- $3.99 for 397 days Aug 10, '18
- $4.99 for 17 days Jul 24, '18
- $0.99 for 4 days Jul 20, '18
- $7.99 for 21 days Jun 29, '18
- $2.99 for 33 days May 27, '18
- $3.99 for 6 days May 21, '18
- $1.99 for 19 days May 02, '18
- $0.99 for 4 days Apr 28, '18
- $2.99 for 6 days Apr 22, '18
- $0.99 for 179 days Oct 25, '17
- $1.99 for 47 days Sep 08, '17
- $0.99 for 10 days Aug 29, '17
- $3.99 for 60 days Jun 30, '17
- $2.99 for 3 days Jun 27, '17
- $0.99 for 3 days Jun 23, '17
- $1.99 for 2 days Jun 22, '17
- $2.99 for 1 day Jun 21, '17
- $3.99 for 277 days Sep 17, '16
- $2.99 for 207 days Feb 23, '16
- $0.99 for 3 days Feb 20, '16
- $3.99 for 43 days Jan 08, '16
- Free for 1 day Jan 07, '16
- $3.99 for 10 days Dec 28, '15
- $4.99 for 4 days Dec 24, '15
- Free for 4 days Dec 19, '15
- $4.99 for 13 days Dec 06, '15
- $2.99 for 171 days Jun 18, '15
- $1.99 for 38 days May 11, '15
- $2.99 for 4 days May 07, '15
- $0.99 for 1 day May 06, '15
- Free for 5 days May 01, '15
- $1.99 for 14 days Apr 17, '15
- Free for 9 days Apr 08, '15
- $1.99 for 239 days Aug 12, '14
- $0.99 for 6 days Aug 07, '14
- $1.99 for 234 days Dec 15, '13
- $0.99 for 16 days Nov 29, '13
- $1.99 for 32 days Oct 28, '13
- $3.99 for 4 days Oct 24, '13
- $1.99 for 46 days Sep 08, '13
- $0.99 for 9 days Aug 30, '13
- $3.99 for 7 days Aug 23, '13
- Free for 2 days Aug 21, '13
- $3.99 for 4 days Aug 17, '13
- $1.99 before Aug 17, '13
You can use IDatabase.backup method inside a Jedox Integrator Groovy Job to execute a backup of databases. Such a job can then be triggered or scheduled to be run on a regular basis to produce database backups without the need to shutdown any of the services. Backup itself runs asynchronously in non-blocking mode, hence regular work should not be impacted provided enough system resources are available. For every database, a separate ZIP archive will be produced containing the database itself plus the System database. Both of these are in a committed state - all journals are processed and no archives are present in a zip file which, when used, speeds up startup times of the database server. Use the zip-backup parameter to influence the compression level used.
Assuming there is a connection of type Jedox called localhost_demo which points to database Demo, a bare minimum Groovy script which backups Demo database to a file Demo.zip inside Data directory could look like this:
IDatabase db = OLAP.getDatabase('localhost_demo');
db.backup('Demo.zip');
A more comprehensive script which backups all the databases for a specific connection and adds timestamp suffix to archive name is included in the Integrator Sample project 'ETLTasks' in the setup, and looks similar to the code below: Privatus 5 1 2 – automated privacy protection systems.
![Idatabase Idatabase](https://www.researchgate.net/publication/318713971/figure/tbl1/AS:631678355636248@1527615264336/Competition-benchmarks-and-test-cases-i-database-setup-preparing-encrypting-and_Q640.jpg)
It relies on at least the JedoxGlobal connection OlapTarget being properly set. By default, if the backupDirPath variable is not set, the backup job will write a ZIP file in the data directory of the Jedox In-Memory DB; otherwise, the directory specified as a value for the backupDirPath variable is used. For this variable, forward slashes must be used as separators between directory names; backslashes are not allowed. The format of the archive name is <DB_NAME>_<DATE_TIME>.zip, e.g. Demo_20160321_1536.zip. Please note that the user running the Jedox In-Memory DB Server service/process must have write access to the target directory to be able to create the output file.
Idatabase 3 33 Sailboat
Updated July 24, 2020