Creating site backup when syncing local site

I’m syncing my local site to mirror my live site. It’s the first time I’ve tried that after initially setting everything up. The first step was “Creating site backup” which took a long time.

Is that step creating a backup of the local site that I’m trying to replace or remote site that I’m syncing from?

If it’s backing up the local site, I wonder if there is a way to skip that step since it will get replaced anyway and it takes so long?

Hello Ryan :wave:

Yes, the first step “Creating site backup” is indeed creating a backup of the local site on your computer.
If you check the application main.log file (please check this on how to access the main.log file: DevKinsta Error Codes - Kinsta® ) , there you may notice something similar to the following (when DevKinsta processed that 1st step to create a local site’s backup file) :

[2023-01-26 08:44:47.955] [info]  [createSiteBackup] Creating site backup for yoursitename
[2023-01-26 08:44:47.964] [info]  [createSiteBackup] Writing to /tmp/backup/
[2023-01-26 08:44:48.188] [info]  [containerExec] Command 'wp --allow-root --skip-themes --skip-plugins core is-installed --path=/www/kinsta/public/yoursitename' on devkinsta_fpm finished with exit code 0
[2023-01-26 08:44:48.189] [info]  [useWordpressCheck] is a wp site, setting it to WP.
[2023-01-26 08:45:43.256] [info]  [createSiteBackup] yoursitename site successfully archived!
[2023-01-26 08:45:43.256] [info]  [createSiteBackup] yoursitename site successfully backed up at path /tmp/backup/!
[2023-01-26 08:45:43.258] [info]  [dockerUtil/getContainer] Get 'devkinsta_fpm' Docker container
[2023-01-26 08:45:43.304] [info]  [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-01-26 08:45:43.342] [info]  [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-01-26 08:45:43.691] [info]  [createSiteBackup] 331324599 total bytes
[2023-01-26 08:45:43.691] [info]  [createSiteBackup] yoursitename site successfully archived!

The time to process backup this local site may vary (depends on the site’s files and database size, and how fast the computer to compress them into a .zip file ). There’s no option to skip this step unfortunately.


It might be worth considering adding that option. It seems unlikely that someone would want to back up a local site that they’re in the process of trying to replace with the latest remote site. And for large sites creating the back up takes a while.

Thank you for your reply and feedback! :+1:
I will pass it on to our internal devs/team, so they may want to review and see if it’s something that can be considered as an option (to skip that local site backup creation) - though I can’t promise anything about it!