should installTode allowed to specify whether to snapshot or not?

Dale, 

I found out that the `upgradeStone` ends up creating a extent backup before installing tODE. 

In the case of the `upgradeStone` is VERY much likely we have already made a backup before starting the process. And extent snapshots are very expensive on disk. Wouldn't it be nice if the `upgradeStone` would allow a parameter whether to backup or not and pass that to `installTode` ?

Thanks in advance, 

--

Mariano
http://marianopeck.wordpress.com

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Mariano,

Since you say that "extent snapshots are very expensive on disk", I assume that you never really want installTode to do extent backups....

If that is true, then you can customize the script that does the extent backup by copying the file $GS_HOME/sys/default/client/tode-scripts/installServerTode2 to $GS_HOME/sys/local/client/tode-scripts and then remove the backups and or snapshots as you'd like.

BTW, the extent backup is made AFTER tode is installed, because before tODE is installed there is no tODE to do the command...

Any, here is the default installServerTode2:

  script --script=setUpSys      # set up the in-image tODE /sys structure
  bu backup --commit tode.dbf   # backup of initial tODE install with /sys structures in place
  bu snapshot --commit tode.dbf # make a snapshot of initial tODE install with /sys structures in place

And you can remove both or one of the backups made ... the setUpSys is the important bit...

Dale

On 10/25/15 1:46 PM, Mariano Martinez Peck via Glass wrote:

Dale, 

I found out that the `upgradeStone` ends up creating a extent backup before installing tODE. 

In the case of the `upgradeStone` is VERY much likely we have already made a backup before starting the process. And extent snapshots are very expensive on disk. Wouldn't it be nice if the `upgradeStone` would allow a parameter whether to backup or not and pass that to `installTode` ?

Thanks in advance, 

--

Mariano
http://marianopeck.wordpress.com

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

On Sun, Oct 25, 2015 at 6:25 PM, Dale Henrichs via Glass <[hidden email]> wrote:

Mariano,

Since you say that "extent snapshots are very expensive on disk", I assume that you never really want installTode to do extent backups....

If that is true, then you can customize the script that does the extent backup by copying the file $GS_HOME/sys/default/client/tode-scripts/installServerTode2 to $GS_HOME/sys/local/client/tode-scripts and then remove the backups and or snapshots as you'd like.

BTW, the extent backup is made AFTER tode is installed, because before tODE is installed there is no tODE to do the command...

Any, here is the default installServerTode2:

  script --script=setUpSys      # set up the in-image tODE /sys structure
  bu backup --commit tode.dbf   # backup of initial tODE install with /sys structures in place
  bu snapshot --commit tode.dbf # make a snapshot of initial tODE install with /sys structures in place

And you can remove both or one of the backups made ... the setUpSys is the important bit...

OK, thanks Dale. I guess that at least for the upgrade process I can change these files. Or..maybe I will remove the snapshots for sure (maybe I let backups, I will see).

 

On Sun, Oct 25, 2015 at 6:33 PM, Dale Henrichs via Glass <[hidden email]> wrote:

BTW, there are other script in the tode-scripts directory that do `bu snapshot` so you'd probably want to customize them all while you are at it ...

mmm I have seen one named preUpdate.dbf.gz. But neither a grep nor a find string give me an answer. Do you know where that one is done?

Cheers,