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 <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 > > > > >
