Hi guys
I have a MXE III controller running MCD 7 SP1 PR1 and when I try and make a backup it instantly fails. The log files indicate the following error: "Backup failed due to a prior database audit failure"
I have done a database audit and ht result was: "Database audit succeeded"
Unfortunately it has made no difference with the backup.
I have come across the following note in the help file but was hoping there is another way or workaround as I will lose a lot of config changes if I have to restore a previous back.
Aufit Failure:
"Indicates a system backup failure(s) on the local node. Details are stored in the /db/spyLog/alarms/backupAlarm file, which is renamed and can still be viewed after the alarm is cleared. The directory is removed only during an upgrade or full install.
The most common reasons for a backup failure are:
An Audit Failure alarm already exists.
Database verification fails during the backup.
There is not enough disk space.
Failure to copy files during the backup.
Failure to create a .tar file during the backup.
Only one alarm (always Major) is generated for any number of backup failures. The alarm persists after a system reboot; it clears only after a system restore OR once the Audit Failure alarm (if present) and other issues are cleared and the backup process completes successfully."
I have a MXE III controller running MCD 7 SP1 PR1 and when I try and make a backup it instantly fails. The log files indicate the following error: "Backup failed due to a prior database audit failure"
I have done a database audit and ht result was: "Database audit succeeded"
Unfortunately it has made no difference with the backup.
I have come across the following note in the help file but was hoping there is another way or workaround as I will lose a lot of config changes if I have to restore a previous back.
Aufit Failure:
"Indicates a system backup failure(s) on the local node. Details are stored in the /db/spyLog/alarms/backupAlarm file, which is renamed and can still be viewed after the alarm is cleared. The directory is removed only during an upgrade or full install.
The most common reasons for a backup failure are:
An Audit Failure alarm already exists.
Database verification fails during the backup.
There is not enough disk space.
Failure to copy files during the backup.
Failure to create a .tar file during the backup.
Only one alarm (always Major) is generated for any number of backup failures. The alarm persists after a system reboot; it clears only after a system restore OR once the Audit Failure alarm (if present) and other issues are cleared and the backup process completes successfully."