SEO

Hi Traveller,

I have not looked at those size yet, but I guess what you see here is an
estimate of the object size, which onbar passes trough the XBSA
interface to the storage manager. So this might not be the real size of
this object. The reason that both sizes are the same might be a bug in
onbar as I remember some problems with that in the past. BTW, I'm
working in Informix support ;-)

Are those size important for you? What are your expectations? I would
consider them as information only. I tried to look for alternative ways
to figure out the real size from the TSM server side, but I wasn't very
successful. Maybe your TSM admin might be helpfull here.

When we do a backup we only backup the used pages from the
dbspaces/chunks which might be much less then your current 3GB.
Additionally TSM might be configured to use compression.

As I said I work in Tech Support therefore I have no real production
dsm.opt and include/exclude file to share. Your inclexcl.def could look
something like this:

include /process_tcp/.../* MC07
include /process_tcp/.../[0-2] MC365

Here you would define a different management class MC07 for your logical
log backup objects and a management class MC365 for all dbspace objects.
Your TSM management classes [which need to be defined in the TSM server]
could then contain a different retention period of 7 days vs. 365 days.
This is just an example how it could work, your figures are purely
depending from your business needs.

There is also a good TSM ressource on the web

http://publib-b.boulder.ibm.com/Redb...4877.html?Open

I hope this gives you some pointers.

Cheers

-- Steffen.


Traveller2003 wrote:
> Hi Steffen ,
>
> The output from the dsmc q b -inactive "/process_tcp/process_tcp/*/*"
> command give me the following output.
>
> Size Backup Date Mgmt Class A/I File
> ---- ----------- ---------- --- ----
> API 177,754 KB 16-08-2004 15:26:36 DEFAULT A
> /process_tcp/process_tcp/datadbs01/0
> API 177,754 KB 16-08-2004 15:25:55 DEFAULT A
> /process_tcp/process_tcp/rootdbs/0
>
>
> What does the size relate to ? The size is the same for both dbspaces
> yet datadbs01 is about 3gig. So I am not quite sure why the sizes are
> the same. I know that onbar backups at the binary level and therefore
> does not backup all the 3gig but I would have expected to see a size
> difference in the rootdbs and datadbs01.
>
> I may be missing the obvious :-)
>
>
> Any ideas any more commands to check this out ? Also do you have a
> sample copy of dsm.opt and include/exclude files. i.e Do you specify
> the dbspaces in the include/exclude files.
>
>
> Thanks for the help.
>
> Cheers
>
> Traveller2003
>
>

sending to informix-list