Title: SQL file
Last modified: April 19, 2017

---

# SQL file

 *  Resolved [Karin H Olsson](https://wordpress.org/support/users/kaolss/)
 * (@kaolss)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/sql-file-3/)
 * I have 15 sites backed up and the way db (sql) is saved and named differ between
   them.
 * In some sites I have files named xxx-backup.sql.09b1fc07e7087df852138f3ff41011bebc25b17a-
   wptc-secret and a new file for every backup.
 * In other sites the backup in dropbox is xxx.sql using dropbox version history.
   
   This seems to be the right way.
 * Are there problems with the files in the backup first mentioned?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [WPTimeCapsule](https://wordpress.org/support/users/wptimecapsule/)
 * (@wptimecapsule)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/sql-file-3/#post-9043751)
 * Hey Karin,
 * You are right, your sites will have files named xxx-backup.sql.09b1fc07e7087df852138f3ff41011bebc25b17a-
   wptc-secret, these are files stored locally on your site so that the file name
   is not just xxx-backup.sql which will be easy for hackers to identify.
    When 
   they are uploaded to the cloud they are uploaded as xxx.sql using the dropbox
   version history as you mentioned. Once the sql file is uploaded to the cloud,
   the local copy that has a bigger file name will automatically be deleted.
 * However, coming to your scenario I just checked some test sites of mine and saw
   that some had their names saved as xxx.sql while others had the filename with
   the entire hash. So I tried restoring the site with the revision file name and
   the other site with the hashed file name. Looks like both the restores were successful.
 * So what’s happening here is that the files are getting stored as revisions on
   some scenarios while on some they are getting saved as new copies. Rest assured,
   there will not be any problems with the files in the backup first mentioned.
 * Also to confirm, can you please let me know if the first backup file is a multisite
   install or installed inside a subdomain? We are looking into this and we will
   fix it once we have some more data on the same!
 * Regards,
    Tauseef
    -  This reply was modified 9 years, 1 month ago by [WPTimeCapsule](https://wordpress.org/support/users/wptimecapsule/).
 *  Thread Starter [Karin H Olsson](https://wordpress.org/support/users/kaolss/)
 * (@kaolss)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/sql-file-3/#post-9044159)
 * Thanks for your explanation.
    No one is multisite. I have subdomains with both
   filetypes. And not subdomains with both.
 *  Plugin Author [WPTimeCapsule](https://wordpress.org/support/users/wptimecapsule/)
 * (@wptimecapsule)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/sql-file-3/#post-9044227)
 * Hey Karin,
 * Thanks for sharing, I will have the development team look into this and get it
   fixed at the earliest 🙂
 * Regards,
    Tauseef
 *  Plugin Author [WPTimeCapsule](https://wordpress.org/support/users/wptimecapsule/)
 * (@wptimecapsule)
 * [9 years ago](https://wordpress.org/support/topic/sql-file-3/#post-9108100)
 * Hey Karin,
 * We have fixed this issue in 1.9.1. Thanks a lot for bringing this to our attention.
 * Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘SQL file’ is closed to new replies.

 * ![](https://ps.w.org/wp-time-capsule/assets/icon-256x256.png?rev=1614914)
 * [Backup and Staging by WP Time Capsule](https://wordpress.org/plugins/wp-time-capsule/)
 * [Support Threads](https://wordpress.org/support/plugin/wp-time-capsule/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-time-capsule/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-time-capsule/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-time-capsule/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [WPTimeCapsule](https://wordpress.org/support/users/wptimecapsule/)
 * Last activity: [9 years ago](https://wordpress.org/support/topic/sql-file-3/#post-9108100)
 * Status: resolved