Is it Ok to abort database backup while upgrading to 1.0.2 ?
I tried using the Thirty Bees updater v1.2.2 to update to TB 1.0.2.
I had the option checked to back up my files and database.
I started the update and realized the backup was going to take a long time. When the file count got to zero, it started all over again with a new file countdown.
I aborted the backup by exiting the module.
Is this going to cause any problems? Is there an orphan record somewhere that I need to delete?
If you have your own backup it is no problem. I abort every time to save time
@Havouza Did the older versions of the Updater module not have the option to turn off backups?
I think it had, I dont remember
All the versions have had the option to not backup the database.
I, as havouza, uncheck this option because it takes a long time to finish. Obviously this is recommended as long as you have another option to backup your server.