Aldo,
It was a suggerence only, when I said "Repository" I meant
"Bucket" or "Directory".
The Backup scheduler runs every XX Minutes and have a notifier that
can be configured, this makes one configuration for all the directories.
I know status of the whole backup process from "Scheduled Events"
Cristián,
I think you mixed two ideas together here, and it sounds like you're
suggesting to forget about the bug ;)
>> The workarounds have been useful,
>> but maybe its simpler to have different scheduler instances for each
>> repository?
If the second line is a hint of a feature request, ple
Cristian Vasquez wrote:
The workarounds have been useful,
but maybe its simpler to have different scheduler instances for each repository?
No, we need to fix the issue and make an updated document covering this
aspect of our offering :-)
Kingsley
Thanks,
Cristian.
On Wed, Apr 1, 2009 at 1
The workarounds have been useful,
but maybe its simpler to have different scheduler instances for each repository?
Thanks,
Cristian.
On Wed, Apr 1, 2009 at 10:15 PM, Kingsley Idehen wrote:
> Cristian Vasquez wrote:
>>
>> I have some questions regarding the backup mechanism,
>>
>> I configured vi
Cristian Vasquez wrote:
I have some questions regarding the backup mechanism,
I configured virtuoso to do scheduled backups and store files in two
places, a local directory and S3,
it worked fine some days, until it failed with this error:
---
Last backup execution returned:
42000 IB015: dire
I have some questions regarding the backup mechanism,
I configured virtuoso to do scheduled backups and store files in two
places, a local directory and S3,
it worked fine some days, until it failed with this error:
---
Last backup execution returned:
42000 IB015: directory univrz_virtuoso_back
