Hi,


-------------------------------------------------------------------------------------------------------------------------
Dept. A153,  STG/ISC EMEA AIS Strategy and Architecture
Development Leader Stonehenge
IBM intranet ---> http://w3.ais.mainz.de.ibm.com/stonehenge/
internet ---> http://www-5.ibm.com/services/de/storage/stonehenge.html
Phone (+49)-6131-84-3151
Fax      (+49)-6131-84-6708
Mobil   (+49)-171-970-6664
E-Mail : [EMAIL PROTECTED]


[EMAIL PROTECTED] wrote on 21/02/2005 18:02:07:

> --On Monday, February 21, 2005 09:42:38 -0500 Steve Simmons <[EMAIL PROTECTED]>
> wrote:
>
> > # 01:
> > "extend the vos examine command with the parameters -server
> > -partition  to do a bulk vos examine for a server or for a server
> > specific partition ."
> >
> > "bulk" means here multiple volume listing (textual).
>
> 'vos listvol -long' already does this, for the most part. It doesn't print
> the vldb information, but the vldb information isn't really interesting
> when you are listing an entire partition.
> See also the -format option if you want machine readable output.

but the VLDB output is the output i would be most interested in .. especially if you like to export this data to use it in excel or other tools ..

>
> >#02
> > "an additional "flag" inside VLDB where we update a counter each time a
> > file within a specific volume was updated (needed to query volumes which
> > are worth to backup) which can be explored with vos examine and can be
> > reseted to zero with the vos setfield command (and over the api)"
> This is a reasonable idea, but is there any reason that you cannot use the
> volume's update timestamp to decide if the volume should be backed up? Are
> you actually trying to prioritize backups based on activity or do you just
> want to exclude those volumes that have not been changed?
>

the timestamp shows only if you have done an update , but to prioritize backups, you may skip a backup for a 10G Volume, if just 1 file changed .
an additional "feature" would be to query a changed file list with the path started from the volume root.
this would speed up file based backup dramatically . this File Log should be enabled/disabled with a vos setfield flag ...


Sven

Reply via email to