SysAdmin documentation - How to Shrink the Repository ... questions

> Hey,
>
> first - the whole topic is new to me. Therefore I've no real idea, what
> is really needed.
>
> My disc is full and I want to execute 7.6 in the documentation:
>
> -> Step 3 shuts down the stone
> -> my extent is still available and also all my logs
> -> Step 4 removes all my extent files (I just make a backup of)
>    and one copies the original extent file
>
> -> Actually the stone is still down - and therefore I think that I have
> to remove all log files BEFORE I go to step 5. Otherwise the stone can
> not be started as describd in step 5) - but with a special option (-r) ?
>
> Well I removed all my logs and continued with step 5 - but left out step 8.
>
> Marten
>
>

> And the whole procedure failed (:-()
>
> When connecting to the stone via Jade a commit or abort is not possible:
>
>
> a TransactionError occurred (error 2248), Commits are not allowed while
> a restore from backups or transaction logs is in progress.
>
>
> Hmm, very strange ....
>
>
>
> Marten
>
>
>
>
> Am 23.08.2015 um 09:23 schrieb [hidden email] via Glass:
>> Hey,
>>
>> first - the whole topic is new to me. Therefore I've no real idea, what
>> is really needed.
>>
>> My disc is full and I want to execute 7.6 in the documentation:
>>
>> -> Step 3 shuts down the stone
>> -> my extent is still available and also all my logs
>> -> Step 4 removes all my extent files (I just make a backup of)
>>     and one copies the original extent file
>>
>> -> Actually the stone is still down - and therefore I think that I have
>> to remove all log files BEFORE I go to step 5. Otherwise the stone can
>> not be started as describd in step 5) - but with a special option (-r) ?
>>
>> Well I removed all my logs and continued with step 5 - but left out step 8.
>>
>> Marten
>>
>>
>

> Aah, I see ... perhaps you should put "commitRestore" as a single Step
> 9) - it has nothing to do with the restore from logs - but from the
> overall restore process ...
>
> I was not aware of that.
>
> Thanks,
>
> Marten
>
>

> Marten, why Guide are you reading exactly? Because in mine
> (GS64-SysAdminGuide-3.1.pdf) I do have a step 9 which even does the
> #commitRestore.
>
> Step 9. Between the time the full backup was started (Step 3) and the
> time the repository was shut down (Step 4), there may have been
> transactions on your
>
> repository. To ensure that no work is lost, restore from transaction
> logs and commit the restore. For example:
>
> topaz 1> printit
> SystemRepository restoreFromCurrentLogs
> %
> Restore from transaction log(s) succeeded.
>
> topaz> login <details omitted> successful login
>
> topaz 1> printit
> SystemRepository commitRestore
> %
> Restore from transaction log(s) succeeded. commitRestore succeeded
>
>
> Maybe you are using a newer guide that for some reason lost this?
>
> Cheers,
>
>
>
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>

>
>
> On Mon, Aug 24, 2015 at 4:06 PM, [hidden email]
> <mailto:[hidden email]> via Glass
> <[hidden email] <mailto:[hidden email]>>
> wrote:
>
>     3.2 and yes, the documentations differs between 3.1 and 3.2.
>
>     I still want to point to the point, that step (5) in 3.2 or step (6) in
>     3.1 do not work because the tranlogs files are still present.
>
>
> That's true. If you see the bash I shared with you above, you will see I
> start the stone with -R
>
> Cheers,
>
>
>  
>
>     Marten
>
>
>     Am 24.08.2015 um 20:59 schrieb Mariano Martinez Peck via Glass:
>     > Marten, why Guide are you reading exactly? Because in mine
>     > (GS64-SysAdminGuide-3.1.pdf) I do have a step 9 which even does the
>     > #commitRestore.
>     >
>     > Step 9. Between the time the full backup was started (Step 3) and the
>     > time the repository was shut down (Step 4), there may have been
>     > transactions on your
>     >
>     > repository. To ensure that no work is lost, restore from transaction
>     > logs and commit the restore. For example:
>     >
>     > topaz 1> printit
>     > SystemRepository restoreFromCurrentLogs
>     > %
>     > Restore from transaction log(s) succeeded.
>     >
>     > topaz> login <details omitted> successful login
>     >
>     > topaz 1> printit
>     > SystemRepository commitRestore
>     > %
>     > Restore from transaction log(s) succeeded. commitRestore succeeded
>     >
>     >
>     > Maybe you are using a newer guide that for some reason lost this?
>     >
>     > Cheers,
>     >
>     >
>     >
>     > _______________________________________________
>     > Glass mailing list
>     > [hidden email] <mailto:[hidden email]>
>     > http://lists.gemtalksystems.com/mailman/listinfo/glass
>     >
>
>
>     --
>     Marten Feldtmann
>     _______________________________________________
>     Glass mailing list
>     [hidden email] <mailto:[hidden email]>
>     http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com