Closed Nyholm closed 9 years ago
Hmm weird.. What is your backup config part?
Here is my config.
dizda_cloud_backup:
# such as: hostname_2014-01-01_21-08-39.tar
output_file_prefix: %site_domain%
folders: [ web/uploads ]
processor:
type: tar # Required: tar|zip|7z
cloud_storages:
google_drive:
token_name: 'tobias_gmail'
remote_path: %google_drive_backup_path%
databases:
mysql:
all_databases: true
db_host: %database_host%
db_user: %database_user%
db_password: %database_password%
Are you sure that you have tar and gzip installed? This version is really messy, you should maybe try to migrate to the last version
Yes, tar is installed.
I think I got it now btw. The 2.0 version does not have the --folders
option on the command. Which makes the "copy folders" non-optional. I got GB's of data in my web/uploads. That might be why the tar commands takes forever... I will do some more tests to make sure this is the reason.
Right! I removed it, because it did not make sense to me.
But I understand the utility now.
The default behavior when we start the command should apply all steps defined in the config.yml, right?
Maybe we should rename it to --no-copy
or something like this?
What do you think?
I agree that it did not make any sense. --no-copy
would be a better solution.
_But_, do we want it at all? Is there a use case where I sometimes want to to a "complete backup" and sometimes a "database backup"?
You tell me :)
You mean that you want to make a separate command?
For me, there is no use case. I thought I would like to do that (have 2 different backups) but I've never used it. I suggest to leave it as it is until a feature request comes around.
Agreed! Anyway, thanks for this interesting point.
I don't know why or if it is related to the bundle or my machine.
On prod machine:
On local machine:
I will investigate in this further.