What determines how long the backup_export script will take to run?
Article ID: KB0082438
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | v 7.0.0 and higher |
Description
Taking a backup is fundamentally an archiving activity (i.e. it is similar to using the Windows WinZip utility to zip up files). The time that backup_export.sh or backup_export.bat takes to run will depend on:
(1) The amount of metadata to be archived. If you have a lot of resources, it will take longer.
(2) The size of your JVM Heap Memory (as archiving uses a lot of memory). You can view the Heap Memory size by opening Studio and navigating to Administration >> Configuration >> Server >> Memory >> Java Healp >> Total Available Memory (On Server Restart).
Run the backup_export script on the same machine as your TDV server. We do not recommend running the backup_export script on a different machine than the one on which TDV is running, because in that case the data will be transferred over a network connection. Sending data over the network takes longer and it increases the chances of a connection timeout.
(1) The amount of metadata to be archived. If you have a lot of resources, it will take longer.
(2) The size of your JVM Heap Memory (as archiving uses a lot of memory). You can view the Heap Memory size by opening Studio and navigating to Administration >> Configuration >> Server >> Memory >> Java Healp >> Total Available Memory (On Server Restart).
Run the backup_export script on the same machine as your TDV server. We do not recommend running the backup_export script on a different machine than the one on which TDV is running, because in that case the data will be transferred over a network connection. Sending data over the network takes longer and it increases the chances of a connection timeout.
Issue/Introduction
What determines how long the backup_export script will take to run?
Feedback
Yes
No
Powered by
