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, please elaborate on it and provide basic use cases. I assume you mean "graphs". In that case, I believe that one of the blessings of working with Virtuoso is that you can keep everything within one environment and one database. Different backups for different graphs can become a PITA because they are usually inter-related. Thanks, A On Thu, Apr 2, 2009 at 7:28 AM, Kingsley Idehen <kide...@openlinksw.com> wrote: > 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 10:15 PM, Kingsley Idehen <kide...@openlinksw.com> >> wrote: >> >>> 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: directory univrz_virtuoso_backup contains backup file >>>> bckp_33.bp, backup aborted >>>> --- >>>> >>>> With a S3 bucket with less files (from bckp_1.bp to bckp_32.bp). >>>> >>>> I don't know yet why it failed to write on S3 once, but the backup >>>> process stopped on the two places. >>>> >>>> Is there any built in mechanism to do some sort of sync of the backup >>>> directory and S3 bucket? >>>> Is there any way to configure the scheduler to continue the backup >>>> process other directories if an 42000 IB015 error arises? >>>> >>>> Thanks! >>>> >>>> Cristian >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> Virtuoso-users mailing list >>>> Virtuoso-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >>>> >>>> >>>> >>> If you are using our ec2_exts.vad package, then feel free to delete >>> "bckup_33.bp" and simply re-run the backup attempt. Re. S3 (when using >>> ec2_exts.vad) you can also empty your bucket and resync from your local >>> backup collection to a new bucket. >>> >>> The is a subtle index bug in the backup routing that periodically leads to >>> this anomaly. The issue is known and it will soon be resolved. But for now, >>> the workarounds I've suggested will take care of the problem. >>> >>> >>> -- >>> >>> >>> Regards, >>> >>> Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen >>> President & CEO OpenLink Software Web: http://www.openlinksw.com >>> >>> >>> >>> >>> >>> >> >> > > > -- > > > Regards, > > Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen > President & CEO > OpenLink Software Web: http://www.openlinksw.com > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > -- Aldo Bucchi U N I V R Z Office: +56 2 795 4532 Mobile:+56 9 7623 8653 skype:aldo.bucchi http://www.univrz.com/ http://aldobucchi.com/ PRIVILEGED AND CONFIDENTIAL INFORMATION This message is only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, please do not distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail. INFORMACIÓN PRIVILEGIADA Y CONFIDENCIAL Este mensaje está destinado sólo a la persona u organización al cual está dirigido y podría contener información privilegiada y confidencial. Si usted no es el destinatario, por favor no distribuya ni copie esta comunicación, por email o por otra vía. Por el contrario, por favor notifíquenos inmediatamente vía e-mail.
