• Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Medium Medium
    • None
    • 2.3.3
    • None
    • Tomcat 5.5.20 java 1.5_09 linux

      During daily backup no disk space left and the length of confluence.cfg.xml became 0. I tried to restore confluence.cfg.xml from a previous backup but it does not contain it although this config file resides in the data directory and cerated by confluence.

            [CONFSERVER-8435] confluence.cfg.xml missing from backup

            I accept your resolution and you can close the issue. On the other hand i think it is misleading that any installation information resides in the data directory of the instance.

            vi

            Verhás István added a comment - I accept your resolution and you can close the issue. On the other hand i think it is misleading that any installation information resides in the data directory of the instance. vi

            An export of Confluence contains only the data in the instance, not the installation information.

            The best way to backup Confluence is to take a file system backup of confluence.home, and a DB backup of your database using your vendor's tool.

            You should do a fresh Confluence installation and then restore your export.

            Please open a support case at http://support.atlassian.com if you need any help with this.

            Tom

            Tom Davies added a comment - An export of Confluence contains only the data in the instance, not the installation information. The best way to backup Confluence is to take a file system backup of confluence.home, and a DB backup of your database using your vendor's tool. You should do a fresh Confluence installation and then restore your export. Please open a support case at http://support.atlassian.com if you need any help with this. Tom

              Unassigned Unassigned
              93aa57d606d0 Verhás István
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: