Hi everyone, anyone know what this is? Looks like each export zip contains entities.xml and activeobjects.xml.
IM Renderer Page
-rw-r-----. 1 jira jira 80319061 Jul 23 19:00 2018-Jul-23--1900.zip -rw-r-----. 1 jira jira 80332648 Jul 24 07:00 2018-Jul-24--0700.zip -rw-r-----. 1 jira jira 80371606 Jul 24 19:00 2018-Jul-24--1900.zip -rw-r-----. 1 jira jira 80382916 Jul 25 07:00 2018-Jul-25--0700.zip -rw-r-----. 1 jira jira 80430859 Jul 25 19:01 2018-Jul-25--1900.zip -rw-r-----. 1 jira jira 69890048 Jul 26 07:00 2018-Jul-26--0700.zip -rw-r-----. 1 jira jira 15110144 Jul 26 20:01 2018-Jul-26--1900.zip |
Looks like JIRAs own (internal) backup system exporting to XML.
For production use or large Jira application installations, it is strongly recommendedthat you use native database-specific tools instead of the XML backup service. XML backups are not guaranteed to be consistent, as the database may be updated during the backup process. Inconsistent backups are created successfully without any warnings or error messages, but fail during the restore process. Database-native tools offer a much more consistent and reliable means of storing data.
To turn this of, follow the How-To: Automating Jira application backups
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're most welcome. Welcome to Atlassian Community.
In case you've been successful disabling those backups, please mark this case to be solved. Otherwise we'll be happy to help further :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.