Skip to main content
Skip table of contents

Fbackup error in Datasafe

This support note applies to:

  • Profiles (AU)
Article ID: 26269

The following errors may appear in your DataSafe backup log, backuip.txt while performing a backup:

  • Fbackup: Cannot copy to database <database backup dir> <file name>
  • Fbackup:rebuild; dbcopy from <database.dir> to <database.backup.dir> failed.

To resolve this error, run the Check Now utility.

All users must exit all MYOB AE modules, and integrity must be shutdown prior to running this routine. Refer to KB 28506: Running Application Finder to help determine whether any users have MYOB AE applications running 

To run the Check Now utility
  1. Follow the menu path: Start > All Programs > MYOB Accountants Enterprise > DataSafe. The DataSafe Utilities screen appears.

    For users on terminal server, ensure the Current Database that displays at the top of the DataSafeUtilities screen is the database that is experiencing the error. 
  2. Click Check Now. The Database Check screen appears.
  3. Select the checkbox Also check and repair the referential integrity of the application schema and click OK. Once complete, the prompt "No errors were found in your database" appears.

    This routine should take no longer than five minutes. If a file is locked on the server, the check now routine appears to hang on that file, for example 000000.css. If check now appears hung, you may need to reboot your server to unlock the file.
  4. Click OK. The Check Database Paths screen appears.
  5. Click Update. The Updating embedded database paths screen appears.  Once complete, the prompt "No errors were found in your database" appears.
  6. Click OK.

If running the Check Now utility does not rectify the issue, contact MYOB Support and quote KB 26269.


If the fbackup error refers to any of the Key Profiles or Timecost databases such as 000000.pms, 000000.wip 000000.deb, you will most likely have to restore data from a current Datasafe backup.

These databases all integrate with each other and cannot be restored individually, or you will risk further database corruption!

In some instances, other databases may be restored individually. Speak to a member of SST for advice in these instances.

There are 4 different restore options within Datasafe:


Restore full database

Restores a complete set of data for your practice, including AE Tax (SQL) data.
Restore full database - except for AE Tax (SQL) data
Restores a complete set of data for your practice, excluding AE Tax (SQL) data.

Restore key database files only (excludes AE Tax (SQL) data)

Restores the five main Business files: PMS, WIP, DEB, TAX and CSS, excluding AE Tax (SQL) data.

Restore AE Tax (SQL) data only.

Restores only AETax (SQL) data.

If the client integrates with AE Tax, you may be able to avoid restoring AE Tax data if there has not been any or many new clients added to the database. In this case, you would use one of 2 options in the restore screen that excludes AETAX (SQL) data from being restored, as listed in KB article above.

In this instance, the client will need to be aware that if there are tax returns in the Tax database for clients added into Contacts after the last successful current backup, then these will need to be noted, and when the restore is complete, these clients will need to be added back into contacts using the same client code and name, in order to link back up with the returns in the AE Tax database.

As a reference, items that will be lost when restoring any of the key Profiles or Timecost databases are:

  • Timesheet entries entered after the date and time of the last good Datasafe backup
  • Bills/Receipts/Credit Notes etc raised after backup as above
  • Comments and notes made on clients and changes on address/phone details etc after backup as above
  • New clients entered after backup as above
  • Changes to client details/attributes etc after backup as above
  • Documents saved with contacts after backup as above

You will need to advise the client having to restore data of the above items, and get them to print out details of any of the above prior to restoring so they can be re-keyed again.



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.