Backup Strategy Not Working (Solved Apparently)

[Graham Watkins]

On 01/08/15 19:49, Graham Watkins wrote:
> On 01/08/15 12:34, Robert Heller wrote:
>
>>
>> This *strongly* suggests that there is a 'quoting hell' issue going on.
>> Because of the way cron works, you might need to quote the spaces
>> *twice*.
>> (This is similar to what happens when you use spaces in file names and
>> then
>> use scp: you have to quote the spaces for the source shell and the remote
>> shell.)
>>
>> The easy solution is to NOT USE SPACES IN FILE NAMES.  If that is not
>> possible
>> for some reason, you can create a script file (whose name does not
>> contain
>> spaces!) and put your command there (spaces, warts, quoting, etc.).
>>
>
> I have taken your advice and renamed Expansion Drive to Expansion_Drive.
> I've brought the time and date of the task forward (14 minutes and
> counting down) and will see what happens.
>
> I will of course, let you all know what happens.
>
> Thanks for all the input.
>
> Cheers,
>
> Graham
>
>
>
>

RESULT!

The task ran according to it's new schedule and I was able to open the 
archive using Engrampa.

I must admit it never occurred to me that spaces might be an issue. I'd 
thought that the "\" in "Expansion\ Drive" would take care of that. 
Evidently not.

Thank you all.

Cheers,

Graham