Re: Question on defeating TSM strengths: due to budget constraints << solved

[DFrance]

Yep... it worked in our case since the environment was (a) stable (all policy 
decisions had been settled, so there was not a big risk of changing one po-set and 
forgetting to change the other, in lock-step), (b) enabled the most current full 
backups to stay in the single silo (the main exposure was getting the full backups 
done over the course of a weekend, being available for help if problem arose during 
that weekend, once a month).

TWO of the sites I referenced were going to stay with single-drive solution; the net 
result was, to keep it "lights out", I convinced them to keep primary pool data on 
disk, sending two copy-pools to tape -- one for onsite, one for offsite storage.  In 
this instance, the customer was able to live with the limits of the disk array we 
installed for primary storage pool data... whew!  

Now, with serial ATA drives on the scene, there's much discussion of various ways to 
exploit larger pools of cheap disk, maybe as secondary in the storage hierarchy (maybe 
as FILE volumes, with the SANergy enhancements in v5.1), so as to enable much larger, 
online/nearline primary pool storage.

I agree, the "correct" answer lies with the specific customer situation; in general, 
we gotta "sell" the customer on the need for HW investment (ie, at least TWO, prefer 
odd number of drives for data center solutions).  When that is not "in the cards" (for 
a short or long while), then ya gotta get creative to keep the customer whole, and 
"keep the faith", eh!?!

Regards,
Don


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: Steven Pemberton [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 22, 2003 7:43 PM
To: ADSM: Dist Stor Manager; DFrance
Subject: Re: Question on defeating TSM strengths: due to budget
constraints << solved


On Friday 23 May 2003 11:08, DFrance wrote:
> With all due respect, I supported an international account exactly this
> way; as an interim solution (while they ordered up a second tape drive) at
> 3 of their 12 sites, using policyset swap to re-drive the full-backups (ie,
> change copygroup to "absolute", from "modified") was just what we needed,
> so they could run (almost) lights-out for a month at a time, using
> incrementals after each monthly full.

As with most of TSM, there is no one "right way". Just lots of flexibility. :)

Yes, swapping policy sets will work, but you run the risk of someone updating 
one of the "twin" policy sets and not the other. Then when the policy sets 
are swapped, your data may be rebound (if a MC doesn't exist) or retained (or 
not) for an unexpected period.

If you were going to do this I'd prefer to copy the "active" set to a 
temporary name, change the copygroup to/from absolute/modified, and then copy 
it back to the "active" set.

But I'm still hesitant about swapping policy sets because it's not "obvious".

> If you've got the bandwidth to run the full-backup over a weekend, this
> fits the bill;  if not (due to multiple nodes), then you'll need to work
> harder and support multiple node-names per client machine... one for daily
> INCR, one for weekly INCR --- Hmmm, maybe that's a better scenario for your
> situation, eh?  (My customer's scenario worked best because it allowed us
> to do en-mass swap of scratch tapes for old backup tapes... which
> facilitated remote restore from the help desk, transparently to the
> help-desk folks!)

Also, if you use two node names for the "daily incr" and "weekly full" 
backups, they can use two separate management classes, with different 
retention periods.

So, when your management decides they want to keep the full backups for a 
month/year, and the incremental backups for only a week/month, you can.

Alternatively, have you considered keeping *all* the primary backups on disk 
(, lots of disk :) and only sending the copy pool versions to tape for 
offsite storage? Or maybe only sending backup set versions to tape (which can 
be retained and restored separately from the TSM server?

But, of course, the "correct" answer is to but another tape drive.

Regards,
Steven P.

-- 
Steven Pemberton  Mobile: +61 4 1833 5136
Innovative Business Knowledge   Office: +61 3 9820 5811
Senior Enterprise Management ConsultantFax: +61 3 9820 9907

Re: HSM IN WIndows Environment

[DFrance]

Ed,  Go check out OTG's Disk eXtender, now owned by Legato... it does the HSM for NT, 
is not as spiffy as the native Unix version from IBM, but, that's what is out there, 
at this time.  Get the doc from their web site, after you register, you can get the 
full doc. & eval. software.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Edgardo Moso
Sent: Friday, March 28, 2003 5:21 AM
To: [EMAIL PROTECTED]
Subject: HSM IN WIndows Environment


I'm trying to research on HSM for windows but I couldn't any related
document.  Does IBM supoort HSM client for windows?

Any input is very much appreciated.

Thanks,

Ed Moso

Re: select statement

[DFrance]

Sadly, the events info (via "q events") is a consolidation of several tables, 
including internal info not externalized; I understand that IBM is working to resolve 
this so we can "select" query such info.  

For now, you must use the "q ev" command (with modifiers) to easily get this info;  in 
your example, "q ev * * HM*" (HMCH* and HMPG* using two commands).

One way of pulling out a simpler time expression...
time(date_time)>'16:00:00'
so, maybe(?), 
time(scheduled_start)>'16:00:00' 
(else, play with other SQL modifiers -- see Paul's presentation from SHARE -- and post 
your examples).  

HTH!


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Joni Moyer
Sent: Wednesday, March 19, 2003 7:09 AM
To: [EMAIL PROTECTED]
Subject: select statement


Hello,

I am trying to do a select statement that queries events for only the
client backup schedules.  I received the following command from a fellow
user:

select node_name , scheduled_start , schedule_name , status from events

I tried to customize this command and I am receiving no output when I know
that there is.  Is there any suggestions?

Here is what I am trying to do:

I want to select all nodes that begin with HMCH* and HMPG* for the past
day.  I tried the following command and received no results.  Is my syntax
wrong?  Thanks!!!

select node_name, scheduled_start, schedule_name, status from events where
node_name like 'HMCH%,HMPG%' and scheduled_start > current_timestamp - 1
day order by node_name

Also, is there any way to shorten the current_timestamp to get rid of the
ss?  Thanks again!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: Dual copy of files

[DFrance]

Regardless of what script/TDP/etc. is used, sending (two copies of)
archive logs to two separate tapes is done using TWO storage pools.  

One way to do this is via "copypool", which depends on timely execution of
an admin command;  another way (most dba's prefer) is to use 
"-archmc=ARCH1" (and ARCH2, respectively), sending two copies across the
network.  Large business customers liked this approach -- UNTIL the new v5
feature arrived! The new v5.1 feature -- send the primary & copypool once,
have TSM write that single instance to primary & (1 or more) copy pools at
that time.

As always, there are several ways to accomplish, just not the one that
Joni's customer tried to do -- need collaboration of dba & TSMadmin.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Rupp Thomas
Sent: Wednesday, March 19, 2003 4:31 AM
To: [EMAIL PROTECTED]
Subject: AW: Dual copy of files


Hi,

if they use "Tivoli Data Protection for Oracle" then you can assign
a different management class (= different storagepool) for every copy
of the archive logs and therefore send them to different tapes.

HTH
Kind regards
Thomas Rupp
Vorarlberger Illwerke AG


-Ursprüngliche Nachricht-
Von: Joni Moyer [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 19. März 2003 13:19
An: [EMAIL PROTECTED]
Betreff: Dual copy of files


Hello!

I have a user that wants 2 copies of their database logs on 2 different
tapes (the onsite tape storage pool is collocated).  They thought that by
archiving the file twice several days apart that it would be on different
tapes (just in case a tape went bad or it never made an offsite copy due
to
a tape problem).  Is there a parameter or a certain file configuration
that
would allow the user to have 2 copies of the same logs on different tapes?
As of now the only way I can think to do this is to create another onsite
tape storage pool and have them archive their data to both pools.  Is
there
a better way?  Thanks!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: Prompted mode backups did not start

[DFrance]

Hi David,

Haven't seen this on v5.1.1.6 -- would sure like to know how it gets resolved... have 
a customer running 5.1.6.2 since last week, and wants to start using server-prompted 
mode (for more precise scheduling).  Keep us posted, eh?!!

Thanks,
Don


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
David E Ehresman
Sent: Wednesday, March 19, 2003 7:32 AM
To: [EMAIL PROTECTED]
Subject: Prompted mode backups did not start


We've been running prompted mode backups for a few months and have been
running the AIX TSM Server 5.1.6.2 for about a month and life has been
good.  Last night, NONE of our prompted mode backups started.  There
were no server side "ANR2561I Schedule prompter contacting VHOST3
(session 23462) to start a scheduled operation." messages that we
normally get at the start of the backup window.  Other than backups not
being started, the server appears to be responding normally and complete
the daily administrative tasks without error.   There are no entries in
the client dsmsched or dsmerror logs for the clients that did not run.
Our lone polling mode backup did run normally.

Any ideas what might have caused this or things to look for?  I've sent
logs to TSM support and if no one comes up with things to check, we'll
restart the server before tonights backups and hope that clears things.

David Ehresman

Re: Client login with admin id and password

[DFrance]

Some customers mitigate this security issue by eliminating the DSMCAD service, as a 
matter of policy;  that's probably okay for some businesses -- not likely okay for 
help-desk when supporting desktop users.

A number of requirements are being considered (thru SHARE) along the lines of better 
security and/or security-audit;  with Windows, the TSM admin can do restores (via 
machine login) using his NT-network ID which is part of the backup operators group -- 
without the need for DSMCAD.  Using DSMCAD (ie, remote-web-client) is where there is 
no auditability to indicate who accessed what data... and, this is ALSO the most 
convenient interface for remote/help-desk/TSMadmin restore assistance.

We need to better articulate the requirement for the level of audit needed -- and 
where it applies -- such as, must there be audit file that shows every file/directory 
restored and/or even viewed using alternate/admin ID?  

The simplest (and minimal) solution might be to include the admin's ID in the activity 
log, at session start time, reflecting "session started for Node xxx (using admin-ID 
yyy)".  But this only says who, and when, not what was accessed/downloaded.  (And, of 
course, the ENCRYPT option, as Andy suggests.)

Can you help?


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Gerhard Rentschler
Sent: Tuesday, March 18, 2003 7:11 AM
To: [EMAIL PROTECTED]
Subject: Re: Client login with admin id and password


Hello,
> IMHO, the TSM server really needs to leave better tracks for this type of
> activity.
>
> ..Paul>
that's what I would like to have. In Germany we have a law which requires
that access to data which is related to individuals must be restricted and
logged. That means that on request it should be possible to tell who
accessed the data. With TSM this is not possible. Is it possible to open a
pmr on this ground?
Best regards
Gerhard
---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany

Re: Dirdisk stgpool volume deleted

[DFrance]

Also, you might try running a backup using -dirsonly option?  This, at least, would 
re-establish the directory info -- you can then restore the data/file-tree structures, 
but you'd likely have trouble using point-in-time parameters for a restore that 
includes the lost (older) directory objects.

For the future, I'd advise your Dirdisk be copy-pooled TWO (or even THREEE) times -- 
one to it's own storage pool (that stays in the silo), then once to the same copypool 
as the primary data.  I assume you've already configured sequential (FILE) primary 
pool for migration from the primary (DISK) pool -- to mitigate reclamation performance 
for copypool volumes marked "offsite".

HTH!

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Zlatko Krastev/ACIT
Sent: Sunday, March 16, 2003 5:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Dirdisk stgpool volume deleted


If *all* your storage pools have reuse delay and this reuse delay has not
passed since you started the show there is still a chance: restore again
the DB, restore only the dirdisk stgpool, perform regular incrementals.

If reuse delay have passed (it is if equals to 0) and after reclamation
some volumes are overwritten: you still can restore the DB, mark them as
destroyed and restore them from copypool.

But if you have made some backups/archives which TSM must not lose there
is no good answer - old backups/archives are inconsistent due to lack of
directories info; TSM DB restore cannot be made because it would forget
that important backups/archives.
Now which backups are "must-not-lose" is up to you. And archives with
deletion definitely fall in the category. Now you have the hard task to
evaluate the damages - for 300+ servers it would take lot of time.

Zlatko Krastev
IT Consultant






Brenda Collins <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
13.03.2003 18:59
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Dirdisk stgpool volume deleted


We have a dilemma!

We made changes to our disk a few weeks back and unfortunately the
diskpools for the database and dirdisk were reformatted along with the
rest of the
work being done.  As a result, we had to restore the database.  Due to the
fact that the dirdisk volume was reformatted, it was assumed the data was
no good anyways and then started the deletion process of getting rid of
the data.  This was stopped in the middle because we then determined we
would
lose the copy of the data also.

To correct the situation, we put the volume offline to TSM and thought if
we went through a night's backup, it would pick up all the missing
directories.  No such luck!  When trying to restore some clients, we
determined that we were still missing a lot of directory data.  At this
time, we
figured it was because there was data still on the offline volume and
regardless of being offline, TSM still knew it.

Next step, we deleted all the data on that old dirdisk volume and then ran
through backups again.

Now we are trying to restore clients and getting very inconsistent
results.  It appears that the directories are not in sync with the data
needed to
restore.  If we restore directories only and then files only, we seem to
get around it is some cases.  We have had a couple servers so far where
this
does not work either and it is making people very nervous.

If we would have thought of it immediately, the best answer would have
been to restore the stgpool.  Unfortunately, expiration and reclamation
have
run so that is not an answer.

Any ideas on how to get out of this condition?  It appears that even
though all the directories should be backed up again, they are not
necessarily in
sync with the old data that is there.  I have an open pmr on this but no
answers yet.  Do we have to run a full backup on every server?  (300+)

Thanks,

Brenda Collins
ING
612-342-3839
[EMAIL PROTECTED]

Re: Creating two tape copies offsite with each has Different Retention

[DFrance]

Ed,

You are right on both counts;  backup objects have one set of retention parameters, 
from the MC in the backup copygroup;  backupset is one way to achieve different 
retention (for all the active objects at the point-in-time it's created); another 
method is to use more than one nodename, and/or play with export/import -- not really 
the intended backup/restore scenario TSM was designed to handle the only way to 
achieve different retention (in TSM) for any given set of files is to use archive, and 
vary the management class (which maps to specific retention).

In v5, backupset performance has been improved -- especially, client-side restore.

BTW, this idea runs counter to the TSM-copypool & backup philosophy...
1.  if it's worth backing up, it's worth duplicating,,, or,
2.  Never trust your backup data to a single piece of tape!
3.  This scenario seems to ignore the possibility that a media failure (ie, either 
congenital defect or "the operator dropped the cartridge")

HTH.



Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Edgardo Moso
Sent: Wednesday, March 12, 2003 1:20 PM
To: [EMAIL PROTECTED]
Subject: Creating two tape copies offsite with each has Different
Retention


Hello Fellow TSMERs,

This is quite a wild idea but I just would like to solicit your opinions if
how could I satisfy the the requiremetn asked by manager. He wants in one
backup instance to create two copies for the two copy storage pools one for
onsite and one for OFFSITE.  I know this can be done in TSM 5.1.  Aside
from this he added that each of this shoudl have different retentions.
Say, onsite is 15 days retention and offsite  is only 7 days.   I tried
reading the technical manual of TSM 5.1 but I think it's impossible to do
this unless I will apply the concept of backup set.I don't think the
new features of TSM 5.1 inlcudes this. What do you think, gurus?

If I used the backupset, does anybody of you have experience on this?  How
does the backupset performance behaves in the new TSM 5.1?

Any ideas are greatly appreciated.

Thanks,

Edgardo Moso

Re: progressive backup vs. full + incremental

[DFrance]

To (briefly?) summarize... (the first two bullets address your original query):

- With TSM, all the active AND inactive versions are (a) always in the silo, (b) only 
sent across the network ONCE (if you use the progressive-incremental the way it was 
intended)... extra copies of the same "version" are created via copy pools and/or 
backupsets and/or image backups.  

- TSM's database is used to retrieve *only* the versions of files being requested, 
automatically taking into account all the modifiers used (eg, point-in-time, 
replace=y/n, etc.). TSM is designed as a "lights-out" application -- no need to attend 
to the daily/weekly/monthly tape rotations; more simply, use MOVE DRMedia (at the 
operator's convenience, notwithstanding your site's offsite-vaulting policy for extra 
copies) to control tapes moving to offsite vault and back (to scratch).

- the old G-F-S (grandfather-father-son) of mainframe days involved periodic FULL 
backups, typically every weekend; this technique consumes huge amounts of both (a) 
band-width (every new FULL goes across the network), and (b) tapes, just for primary 
copies (most sites have no time left to create a 2nd copy, so they're totally exposed 
to restore failure if that only volume fails for any reason!)

- FULL+Incremental mentality of Legato & Veritas is, unremarkably, similar to G-F-S -- 
its main benefit is that it's easy to understand and implement (if you are NOT the 
operator trying to track down the tapes!);  to recover any given file-system requires 
(a) retrieve the latest FULL, then (b) retrieve all subsequent INCRementals --- that 
can be alot of extra traffic, not to mention the tricks needed to avoid "losing" any 
files created and deleted within the same week AND you must know where the tapes are 
and get them loaded.  BTW, if any tape in the series goes bad, the data on that tape 
could be lost forever -- unless the file's age is such that some previous FULL or 
INCRemental captured it!

HTH!

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Joni Moyer
Sent: Wednesday, March 05, 2003 6:21 AM
To: [EMAIL PROTECTED]
Subject: progressive backup vs. full + incremental


Hello everyone!

I was wondering why the full + incremental would result in a longer restore
time than the progressive backup methodology?  From several co-workers
point of view they thought that it would be quicker on the full +
incremental because you wouldn't have to go back to the beginning backups
of the file and restore all of the incrementals, you would just go back to
the most recent full backup and apply the incrementals after that point.
When I went to explain the reasoning behind this, I had some problems
understanding the concept myself, so I was hoping someone could explain
both methods and why they differ in restore time and why progressive is
better than the full + incremental.  Thank you so much for any help you can
lend on this matter!



Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: archive retention - quick question!!

[DFrance]

Retention of 65 days means "after" 65 days -- so that would be tomorrow; but, even 
then, only AFTER you run EXPIRATION will they be deleted from the db.  To 
prevent/defer that action, just avoid running EXPIRATION.  

Unfortunately, there is not a supported (ie, externalized) mechanism to re-establish 
the expiration of these archived objects... you must either re-run the archive job 
(ugh!), or maybe use EXPORT Node to re-save the data.  See the Richard Sims *AND* Josh 
Bassi responses to this thread, as well -- they are BOTH correct.

There is a pending SHARE requirement to change this, so we can "update" the retention 
for an existing archive package... don't know the prospects for delivery.



Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Joni Moyer
Sent: Thursday, March 06, 2003 4:27 AM
To: [EMAIL PROTECTED]
Subject: archive retention - quick question!!


Hi everyone!

I just wanted to make sure I understood the archive retention period
correctly so that some of the users at my company don't lose data they
wanted to restore from 12/31/2002.  Apparently they archived the data on
12/31/2002 and it has a retention period of 65 days.  Today is the 65th
day.  Will the files expire today or will they expire tomorrow?  Also, is
there anyway to prevent them from expiring (give them a longer retention
period)  before restoring the file?  Thanks for your help!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: progressive backup vs. full + incremental

[DFrance]

A)  The speed of new tape drives (eg, 9840 & 3590) with their mid-point load mostly 
mitigates the restore speed issue;  even IBM's LTO or STK's 9940 seem to be 
sufficiently fast, they're more like the speed of disk of just a few years ago;

B) TSM further mitigates restore speed by consolidating the tape mounts for a given 
restore -- provided you properly implement DIRMC for your NT file [EMAIL PROTECTED]

If you cannot tolerate collocation, consider smaller storage pools, organized by 
mission-critical vs. production vs. non-prod/desktops... personally, I've found that 
when a customer takes the time to properly identify his mission-critical servers (from 
a file-system recovery perspective), collocation is needed for less than 20% of the 
"farm"!  And, for the business-critical servers (if that different than 
"mission-critical for file-system recovery), it's more appropriate to use HACMP 
solution (possibly, in concert with collocation).

Hope this helps!


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
William Rosette
Sent: Wednesday, March 05, 2003 7:22 AM
To: [EMAIL PROTECTED]
Subject: Re: progressive backup vs. full + incremental


This progressive incremental confuses me.  This is what I thought was going
on:

1. Differential is all changes from last FULL backup.
2. Incremental is all changes from last ANY backup
3. Full is all files not matter change on backup.

We used to do Differential with Weekend Fulls.  During a restore we would
restore Full if file had not changed, and then the last differential for
the other files that changed.  We never restored more than necessary.  It
depended on the restore.  Restore 1 file was the same on Differential as
Incremental (most current or before corruption).  The problem comes when
you are restoring directories or a whole system as in DR.  In the
Differential Weekend Full world you would restore Full and lay on top the
last Differential and your done.  Always 2 restores was all and restores
flew since data was all together.

Now the TSM world has its own database with its own reclamation,
expiration, migration, collocation, and the works. Come restoring 1 file it
is the same as above.  Come restoring directories or whole systems it will
depend where all the data is.  Our case, if the restore is not far back we
have a quick restore, but the further back we go in date the slower the
restore because of the no-collocation and the data is spread over 100's of
tapes.  This seems to be the same as an Incremental that the TSM database
keeps track of every file from every tape.

Thus, the reason we did not use Incrementals before was 1. Restores were
long, 2. No database to keep track of all Incremental tapes, 3.
Differential & Full used less tapes, and 4. money.  I am still dealing with
the progressive incremental that progressively eats resources/money.  My
suggestion would be for reclamations to reclaim to a collocate status or
somehow keeping the data together as it gets older.  Right now I am
probably going to run FULLs just to keep my restores to a minimum since the
tape issue will hurt us if we collocate

If I am off, I would appreciate anyone that can straighten out my
backups/restores.

Thank You,
Bill Rosette
Data Center/IS/Papa Johns International
WWJD



  Gianluca Mariani1
 cc:
  Sent by: "ADSM:   Subject:  Re: progressive backup vs. 
full + incremental
  Dist Stor Manager"
  <[EMAIL PROTECTED]
  EDU>


  03/05/2003 09:47
  AM
  Please respond to
  "ADSM: Dist Stor
  Manager"






Progressive incremental backs up only new or changed files.  during the
initial backup the client  backs up all eligible files of course(full
backup). Subsequently, files are backed up again only if they are new or
have changed since the last backup. In TSMs case, a pointer to each version
of every file for every client is kept  in the database , so there is no
need for another full backup.
When  you  need to restore, you can choose the specific version of the file
or  point-in-time  to  restore,  and TSM will restore only  that particular
file or files. The approach used for full + incremental backups (NetBackup)
requires  an  initial  full  backup,  followed  by  regular  incremental or
differential  backups (usually once a day), with the complete cycle needing
a  full  backup  to  be  repeated on a regular (usually weekly) basis. This
backup  method  results in redundant weekly full backups of files that have
no

Re: incremental restore

[DFrance]

This "problem" sounds impossible,,, kinda like an "Ann Landers" test(?).

If you want to restore file that changed AFTER the latest backup, by definition, it 
has not been backed up, yet!  I suspect, like other respondents, that you are really 
looking for point-in-time restore... 

I worked with a customer situation where a drive failure occurred "slowly", such that 
the admin's failed to prevent normal-daily-incr from running after hundreds of 
thousands of files got vaporized, though the drive was still operating;  the net was 
to research the logs for the last successful (and full/good) daily incremental, 
selecting the date-time of completion for the PIT parameters.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Xavier Merlin
Sent: Thursday, February 20, 2003 4:41 AM
To: [EMAIL PROTECTED]
Subject: incremental restore


Hello,

Someone wants to restore only the files which have changed after the latest
backup.
The opposite of the -ifnewer option on the restore command, in other words
doing an "incremental restore".

There are possible ways of doing this, like for instance for a unix client:

 touch -t some_time_stamp some_ref_file
 find -newer some_ref_file > files_to_restore
 for each if the files in files_to_restore dsmc restore .

Are there any other possibilities, preferrably using standard TSM
mechanisms ?

Xavier Merlin




DISCLAIMER

This e-mail and any attached files are confidential and may be legally privileged. If 
you are not the addressee, any disclosure, reproduction, copying, distribution, or 
other dissemination or use of this communication is strictly prohibited. If you have 
received this transmission in error please notify KBC immediately and then delete this 
e-mail.
KBC does not accept liability for the correct and complete transmission of the 
information, nor for any delay or interruption of the transmission, nor for damages 
arising from the use of or reliance on the information.
All e-mail messages addressed to, received or sent by KBC or KBC employees are deemed 
to be professional in nature. Accordingly, the sender or recipient of these messages 
agrees that they may be read by other KBC employees than the official recipient or 
sender in order to ensure the continuity of work-related activities and allow 
supervision thereof.

Re: Semote storage pool

[DFrance]

Sorry to say, you might have had a version with a big HOLE in it; both FILE and DISK 
storage pool volumes must be "local" devices to Win2K... using 4.2.1.0.  This may be a 
problem with my 4.2.1 system -- as I recall, SANergy is designed to help this type 
situation using SAN-based disk pools; it failed on LAN connection with:
ANR8366E DEFINE DEVCLASS: Invalid value for DIRECTORY parameter.

Separately, with TSM's virtual volumes, a TSM server on the Linux box could be used to 
store data from the Win2K server, using DISK storage pool, archive objects, etc.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jozef Zatko
Sent: Tuesday, February 18, 2003 3:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Semote storage pool


Hi Etienne,
it is easy. I suppose you have a server with disk capacity, which you want
use for TSM to store data. I do not know if that remote machine is Windows
or Unix system. It is possible to use both of them (I actually worked only
with Windows system but with NFS in Unix it should be also possible).

On Windows system you create shared directory, which TSM server will use
for file volumes. You must assign access proper rights to this share for
user, under which TSM server is running, so that TSM server can access this
directory  and create and delete files.
Let say for example that your remote machine is named "server1" and shared
directory is named "data".
If TSM server have proper access rights, you can create storage pool on
this shared directory like this:

define devclass remotefile devt=file maxcap=200M directory=\\server1\data

define stg filestg remotefile maxscr=100

You have to be carefull about setting maxscr parameter. This parameter
depends on maxcap parameter from device class. If you multiply this two
number, the result should not be greater than storage capacity you have
available on remote server (in my example I assume you have 20 GB).

If you have Unix machine, you can do the same steps except that in devclass
definition for directory parameter you use your NFS mount directory.

And that is all.

Hope this helps

Ing. Jozef Zatko
Login a.s.
Dlha 2, Stupava
tel.: (421) (2) 60252618


   

"Chandrasekha  

r, C.R"  To: [EMAIL PROTECTED]  

 Subject: Re: Semote storage pool  

Sent by:   

"ADSM: Dist

Stor Manager"  

<[EMAIL PROTECTED]  

RIST.EDU>  

   

   

18.02.2003 

11:27  

Please 

respond to 

"ADSM: Dist

Stor Manager"  

   

   





Ing. Jozef Zatko,

Can you share the steps to achieve this remote storage pool.

Thanks,

chandrasekhar


-Original Message-
From: Jozef Zatko [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 3:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Semote storage pool


Hi Etienne,

Re: Missing files

[DFrance]

The successful backups do NOT say all files were sent during backup;  following 
thoughts may help you discover the true reason for the missing files:

- C$ on WinNT (esp. Win2K) has lots of system-protected files that get skipped;  they 
are rolled into the system state "blob", so could be all is a-okay.

- if you were using the scheduler, your dsmsched.log file contains a line for every 
file processed; search that log for the signs the files were (ever) sent... to learn 
the date and full-path to the source.

- if a drive failure occurs, even if just files/dirs trashed, followed by INCR backup, 
your retention policy for deleted files may be too short.

- with the client installed, query inclexcl might reveal the files were excluded?!?

- scan the activity log (and dsmerror.log) for messages re. the files in question; 
maybe the files were skipped (or inactivated) due to copy-mode or open-file contention.

I agree that the user's data might have really been on a network share, not the 
locally-failing drive, in which case, they might still be there;  alternatively, the 
possibility of slowly-dying drive causing a huge bunch of files to "disappear" is not 
very likely to go undetected more than a day or 3... but, if that did really happen, 
you'd better "fix" the RetainOnly value (to protect for this situation).

Hope this helps.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Fred Johanson
Sent: Tuesday, February 11, 2003 5:30 PM
To: [EMAIL PROTECTED]
Subject: Missing files


I have a client with a missing files problem.

Around midnight Jan 25/26, TSM did an incremental on a WinNT box.  All three
file systems show as completed in "q fi  f=d".  Some time thereafter, but
before 1/28, the harddrive went south.  On 1/29 directories from c$ were
restored on a new machine.  "Thousands" of ifles are missing.

Where did they go?  "Select" on ll_name for the appropriate hl_name and
node_name from backups finds nothing.  "Select" on hl_name for the appropriate
ll_name and node_name from backups finds nothing.  Combine these queries with
the completed backup from 1/26 and what can we believe but that the files were
not there to backup.  Moreover, the sysadmin says there were file-shares on
another machine(s), which have yet to be identified.

However, the owner says the missing files were on his harddrive before and
after the last sucessful backup.  As he is adamant that the missing files
cannot be on a share somewhere, I have suggested that his hardware problem
crept up on him, making the directory gradually and increasingly unreliable
during backup.  I know this is clutching at straws, but in almost a decade,
this is the first instance of "missing files".

Can anyone suggest a better explanation, or ste of possible explanations, than
I have offered?


Fred Johanson

Re: Tape question

[DFrance]

You will probably need the nested form of the query, something like...
select a.volume_name from volumeusage where blah blah blah and -
a.volumn_name in (select b.volume_name from volumes where -
last_write_date>current date - 60 day)

We are requesting an enhancement for "restore/retrieve -preview" option, thru the 
SHARE requirements process; so far, no official response from development.

Also, I am working with some folks to capture tape vol list via server trace, for 
backup data; don't yet know if this technique would work for archive data.

Finally, I previously worked with a client that did a retrieve like this; as I recall, 
tapes outside the silo were marked "unavailable" or "offsite" (don't recall which 
one), and the retrieve was run repeatedly (3 or 4 times) until completion.  The 
"unavailable" state triggered messages in the activity log for skipped volumes -- they 
re-ran the retrieve after loading up the missing tapes, all was okay after about three 
cycles thru that process.  (For restore, classic restore previously would run to 
completion, skipping over unavailable/offsite vols, listing the tapes in ActLog;  no 
query restore dies on the first missing tape --- have not checked this technique on v4 
or v5, so a caveat emptor).

Hope some of this helps!


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Remeta, Mark
Sent: Tuesday, February 11, 2003 9:47 AM
To: [EMAIL PROTECTED]
Subject: Re: Tape question


This works good however I only want the tapes from the last archive I ran
which was the first of January. This query gives me all the volumes from the
beginning of time that have that nodes filespace in it.. clear as mud?

Re: Is there a stable TSM 5.1.5.x version?

[DFrance]

The short answer is "not yet"...
I liked 4.2.2.10 (and .12);  also, 5.1.1.6 is a good one.

Earlier today, someone pointed out, patch-level 5.1.5.3 was withdrawn, etc.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Rainer Tammer
Sent: Tuesday, December 03, 2002 1:33 AM
To: [EMAIL PROTECTED]
Subject: Is there a stable TSM 5.1.5.x version?


Hello,
I have to install a new TSM server in one of our subsidiaries next week .

I have the choice of the following versions:

1. TSM 5.1.5.3
2. TSM 4.2.3.1
3. TSM 4.2.1.15

The server is a AIX 3.3.3 ML10 box with an IBM LTO library.

Our main servers are running on TSM 4.2.1.15 but if I install a new server
it would be nice to go directly to 5.1.5.3.

Do you have any bad experience with 5.1.5.3


Bye
  Rainer Tammer

Re: AIXASYNCIO

[DFrance]

Hi Dave,

There seems to be some contradicting info -- DIRECTIO in Tech. Guide says
what you say applies to ASYNCIO; yet, in the Admin. Ref., it states no such
limitations.  Then, for ASYNCIO, there's alot of verbiage about how to
configure, and no such stated limitations in either the Tech. Guide or Admin
Ref... Also, DIRECTIO is enabled, by default (I can vouch for that, at least
if you can believe the message on the server console at TSM startup time).

Can you please confirm which limits apply to which new option?!?


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Dave Canan
Sent: Tuesday, December 03, 2002 12:31 AM
To: [EMAIL PROTECTED]
Subject: Re: AIXASYNCIO


A few additional comments I would like to add:

 1. AIXASYNCIO only works with JFS filespaces with ITSM.

 2. It only works with storage pool volumes (not the database and
recovery log).

 3. It only works with storage pool volumes that are < 2GB in size,
and have not been created with large file enabled.

I would also be interested in any performance numbers you generate through
your testing - could you please share them with the rest of the listserv
group?


At 09:28 PM 12/2/2002 -0600, you wrote:
>Edgardo Moso wrote:
>
>>Any input about this server option ASYNCIO?
>>
>>Thanks,
>>
>>Ed Moso
>>
>Ed,
>
>This allows ITSM to take advantage of AIX's Asyncronous I/O(AIO)
>capabilities.  I have not used this in an ITSM setting as of yet.
>However, I have used AIO in other places.  There are several things
>required in order to use this.  You must first configure and enable AIO.
>You can do this thru "smitty aio".  There are only a few attributes to
>set.  Here are some good starting points (remember your mileage may
>vary) set minservers=<# of CPUs in the box>, maxservers=<5 to 10 times #
>of CPUs>, maxrequests=<4096x# CPUs>, do not change server priority
>(kprocprio), state at restart to available, leave fast path enabled.
>Once that is done you will need to reboot in order for it to take
>effect.  AIO requires that the application be written to use it,
>apparently ITSM server code has been updated to do so when the
>"AIXASYNCIO YES" is set in dsmserv.opt file of course the server will
>need to be restarted to pick up that change.
>
>Then make some measurements and see if things are running better.  Of
>course this assumes you have some measurements prior to this to compare
>them.  This has the potential for substantial I/O performance increases.
>I would be very interested in your results.  In fact, I would be
>willing to help you do some before and after measurements as well as
>doing some of the data analysis to determine some additional tuning.
>And when we are done we could post on this list for others to consider.
>If you are interested please write me off the list and we can work it out.
>
>Whatever you decide (with or without my help) please let us know how
>this turns out.  I think there are several people on this list who would
>be very interested.
>
>--
>Regards,
>Mark D. Rodriguez
>President MDR Consulting, Inc.
>
>===

>MDR Consulting
>The very best in Technical Training and Consulting.
>IBM Advanced Business Partner
>SAIR Linux and GNU Authorized Center for Education
>IBM Certified Advanced Technical Expert, CATE
>AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
>Red Hat Certified Engineer, RHCE
>===


Dave Canan
IBM Advanced Technical Support
[EMAIL PROTECTED]

Re: Which cartridge must to be monted whith a retreive

[DFrance]

Try doing a sample retrieve for the desired package-description and
filespec; it should skip tapes marked "unavailable", logging messages to the
activity log... those messages will tell you which tapes you need...

ANR1420W Read access denied for volume volume name - volume access mode =
"unavailable".

Explanation: An attempt to access the named volume for reading fails because
the volume status is unavailable.

System Action: The volume is not used for read access.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Eric LANGUILLE
Sent: Wednesday, November 27, 2002 11:40 PM
To: [EMAIL PROTECTED]
Subject: Which cartridge must to be monted whith a retreive


I would like to execute a simulate with a retreive to know which cartridges
will be demanded.
We have in pool offsite some cartridges (near 200). If we have a demand for
retreived some files, we can't mount cartridge after cartridge in the
library IBM 3494.
The Operators want to have a list before. So, if we have a list, it's easy
to get all the cartridges, and after chekin on them, the final customer can
execute the real retreive.

Do you have an experience on this subject?
___
Ce message est strictement confidentiel. Son intigriti n'est pas assurie
sur Internet. Le contenu de ce message ne peut engager la responsabiliti
d'Atos Origin. Si vous n'jtes pas destinataire du message, merci d'en
avertir immidiatement l'expiditeur et de le ditruire.
This e-mail is privileged and may contain confidential information intended
only for the person(s) named above. If you receive this e-mail in error,
please notify the sender immediately by telephone or return e-mail.=

Re: TSM 5.1 Monitor into TSM Management Console

[DFrance]

Before proceeding, upgrade to 5.1.1.6 (or later);  there were problems in
the 5.1 base, GUI-console (and web-admin) are not installed for proper
operation.  Upgrade to 5.1.1.0, from ftp site, then add patch level that you
like (I would advise 6 or higher, imho).

HTH!

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Luciano Ariceto
Sent: Thursday, November 28, 2002 5:13 AM
To: [EMAIL PROTECTED]
Subject: TSM 5.1 Monitor into TSM Management Console


Hi

I installed  TSM server 5.1.0 and now  I4m try to start the Monitor into
TSM Management Console and the following message appear :

11/28/2002 08:30:10 Monitor Started on server TSM
Server1 on IPBR33
11/28/2002 08:30:10  ANS1035S   Options file 'dsm.opt' not found
11/28/2002 08:30:10  ANS8002I   Highest return code was 406.

I found the dsm.opt in

c:\tivoli\tsm\server\baclient\
c:\tivoli\tsm\server\console\
c:\tivoli\tsm\server\server
c:\tsm\tsmshare


I would like to know where I should keep this file ?


TIA

Luciano Ariceto

Re: TSM and AIX Links

[DFrance]

Read the Unix client "user's guide" about -Archsymlinkasfile option... you
might (likely) want to change your use to the non-default behavior, "No".

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Michael Cleary
Sent: Tuesday, November 26, 2002 2:28 PM
To: [EMAIL PROTECTED]
Subject: TSM and AIX Links


Greetings,

I am somewhat new to AIX and TSM and I have a question about TSM and
AIX Links.

I have a file that is a link that points to the directory that it
resides in.  It looks like this:

root:/udb/prod/sqllib> ls -l

lrwxrwxrwx 1 udbprod udbsadm 1 Oct 11 11:01 .ftok -> .

When I run an AIX find command, it finds one .ftok file.  However,
when I run a TSM archive, it appears to be backing up the directory
in question, following the link to the same directory and backing it
up again.  The archive did this many times, but at some point, it
exited this loop and finished with no errors.

Questions:

1)  Is TSM functioning as designed or should it be smart enough to
figure out that it is following a circular link?

2)  If this is normal TSM logic, why did it finally get out of this
loop?

TIA,

Michael





__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: How to tell which tapes a restore requires?

[DFrance]

Another way to (possibly) "cheat" the system on this is to
(a) run the select from volumeusage to determine list of tapes,
(b) mark volumes outside the silo "unavailable", then
(c) use "classic" restore --- get what you can *and* the unavailable vols!

Unless they "closed" this loophole, it used to be that no-query-restore
would stop if it encountered an "unavailable" tape, while classic restore
would do all that it could (issuing messages to the activity log for volumes
it could not access).  You'll need to test it for your vintage of client.
(To force classic restore, use filespec with a trailing /?* or \?*, the
important part being question-mark then asterisk.)

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gerald Wichmann
Sent: Tuesday, November 26, 2002 2:00 PM
To: [EMAIL PROTECTED]
Subject: How to tell which tapes a restore requires?


Let me ask my question a different way. If I do a restore, the server
requests certain tapes to be mounted if they are offline and not physically
in the library. Is there any way to determine ahead of time what those tapes
are and put them in the library via a preview or something or do I always
have to run the restore and wait to see what tapes it wants?


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.

Re: Querying which volumes have a particular file or node

[DFrance]

Gerald,

This is a known requirement, is being submitted to the developers thru
SHARE;  a preview=yes option for restore/retrieve, which runs thru the
database as if the restore is being processed --- specifically, to obtain
the list of volumes that will be required.

So far, their response was (a) multi-thread restore feature (in 5.1) will
make this more complicated, so (b) they may not list vols in the actual
sequence (due to new parallelism) -- my answer was "the customer does not
care, they just need the list" (at least, for now), as it's the reality that
customers occasionally over-commit their silo capacity, need to do a restore
while awaiting new hardware to match their (new) capacity requirements.

You could construct a SELECT to do this, but it would take much longer than
the actual restore code to rummage thru the related tables; doing select for
a pseudo-join between backups and volumes -- backups using node and "active"
status, correlating to contents... gotta be a painful way to do it, but the
only precise way to do it.

My favorite, less-precise way (that I use for any real customer situation)
is just select from volumeusage based on node and storage pool name -- that
gets you all the vols occupied, so it's distorted abit (due to versions),
but, hey --- they should realize they need a silo large enough to hold ALL
their backup data, else it's never gonna be lights-out (as intended) and you
gotta go thru this pain!  See Karel's reply for an example of this query...
and watch for the new release info, for IBM's response.

select distinct volume_name -
from volumeusage where node_name='XYZ', -
and filespace_name='ABC', -
and stgpool_name = 'DEF'

HTH!

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gerald Wichmann
Sent: Tuesday, November 26, 2002 9:03 AM
To: [EMAIL PROTECTED]
Subject: Re: Querying which volumes have a particular file or node


Not exactly the answer I was looking for..

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)

-Original Message-
From: Raghu S [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 25, 2002 9:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Querying which volumes have a particular file or node

in Tivoli Storage Resource Manager all these are addressed

raghu.



Gerald
Wichmann To: [EMAIL PROTECTED]
 Subject: Querying which volumes
have a
Sent by: particular file or node
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


11/26/2002
03:25 AM
Please
respond to
"ADSM: Dist
Stor Manager"





Given a file with some filenames in it, does someone have a macro/command I
can run against the filenames in that file to determine what volumes those
files are on? I.e. so I can identify which offline volumes I need to put in
my library for a restore before actually running the restore command.

Similarly, given a node, how do I determine what volumes the node has data
backed up to.

I believe both these questions involve a select statement and have been
discussed before so someone should have them handy.

Thanks,
Gerald


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employ

Re: Migration from AIX to Solaris

[DFrance]

FYI, v5.1 supports server-2-server export-import in a single step;  you no
longer need to run the intermediate data thru virtual volumes --- it works
abit like CMS-pipelines, once you get it setup on both sides, data flows
from server-a (node-data-on-tape input) to server-b
(new-node-data-on-new-tape).  It's still a pain, but only half as much as
pre-5.1 days.

Also, there was an earlier post, sometime in the last year, where someone
successfully transferred their TSM db from one Unix flavor to another...
don't recall who (or how), but they reported success!@!

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED] (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Prather, Wanda
Sent: Friday, November 22, 2002 12:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Migration from AIX to Solaris


You can do server to server export/import of the data now, with a DRM
license, using server-to-server virtual volumes.

It's just a pain to set up, and takes QUITE some time:  You have to read the
data on your source system (EXPORT), transmit it to the new server via
TCP/IP, which writes it out on your target server; then you reimport it to
the target server, which reads it again and writes it out to the target
storage pool.


-Original Message-
From: Allen Barth [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 11:50 AM
To: [EMAIL PROTECTED]
Subject: Re: Migration from AIX to Solaris


Wanda,

I agree with what you've stated, and will admit I hadn't thought it
through to the tapes.   But as you say even if it did work, it would be
unsupported.

I thought I read something somewhere about a 'no tape server to server
export/import' feature.   That would aid moving the data and rebuilding
the db, but it would still take some time to finish.

Regards,
Al Barth




"Prather, Wanda" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/22/02 10:37 AM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Migration from AIX to Solaris


Al,

As far as anything I have ever read here and in the manuals, moving the DB
across OS's is NOT supported.
What you describe will work going from AIX to AIX, but if it works going
from AIX to Solaris, it's an unsupported accident.

The other issue is the data that exists on tape.  If you were able to NFS
mount the DB to Solaris and use it, then what happens when you try to do a
RESTORE?   You are using a TSM-on-Solaris tape driver to read data that
was
written with TSM-on-AIX tape drivers.  I don't know if that is feasible
and
again, it isn't supported if a problem does occur.

I've heard that somewhere in 5.2 or higher Tivoli is planning something to
help moving a server across platforms, but we aren't there yet.



-Original Message-
From: Allen Barth [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 11:22 AM
To: [EMAIL PROTECTED]
Subject: Re: Migration from AIX to Solaris


Are you saying that the internal format of the db changes between OS's?

If not, I wonder if this would work:

Install ITSM on Solaris
Export filesystems on AIX containing db and log areas
NFS mount those filesystems to Solaris
Update dsmserv.dsk on Solaris to point to NFS db and log areas

Insights, ideas, gotcha's  all welcome.

Al Barth




"Prather, Wanda" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/22/02 09:41 AM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Migration from AIX to Solaris


The big obstacle here is no, you can't move a TSM DB across platforms.

You can EXPORT the definitions, like policies, mgmt classes, schedules,
admins, etc. and reimport them to the new server; you can EXPORT and
IMPORT
the client data as well, but this is really rebuilding the DB on the new
server as the IMPORTS occur; and it's obviously time-consuming.

There are two ways to approach the move:  some people just start backups
on
the new server, leave the old one around for a while until the data ages
enough to be useless, then shut it down.   Other people try to do the
EXPORT/IMPORT thing.  Your decision will depend on your circumstances, how
much time you have, and how much backup & archive data.

To do the EXPORT/IMPORT, you either have to have compatible media, or use
server-to-server virtual volumes to transmit the data from one TSM server
to
the other.   (This requires a DRM license, I think for the target server.)

As far as using the same library, the answer is "probably".I don't
know
if you can share the 3583 with TSM library sharing, if so that would be
ideal as it would let you use the drives as needed.  The other alternative
is 

Re: Retaining Activity Logs (was Re: Tape History....)

[DFrance]

Yes... this is an excellent idea;  it's so good, that IBM made it even
easier on AIX -- search for "dsmulog" in the admin. guide... it creates the
flat-file in real-time, can be setup to automatically roll-over to a new
file every night at midnight, so I usually advise 30-day retention on act.
log, and setup a mgmt class for the rolled-over files so we can go back a
year (or more, if desired).  Kinda like using generation data groups for the
old syslog files.

With this program, a monitoring program can "watch" the tail of the
flat-file in real-time, sending/recording alerts for significant issues that
arise.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Shannon Bach
Sent: Wednesday, November 13, 2002 9:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Retaining Activity Logs (was Re: Tape History)


When you pull out data from your Activity Log do you pull everything in the
log?  Or just certain information.  What a good idea, I had never thought
of doing this before!  I am setting up a macro to start tonight.  Thanks
for the tip!

Shannon Bach
Madison Gas & Electric Co.
Operations Analyst - Data Center Services
Office 608-252-7260
Fax 608-252-7098
e-mail [EMAIL PROTECTED]

Windows IMAGE backups on NAS or Network drives (was RE: Journaling)

[DFrance]

So... does this same constraint apply to the new Windows IMAGE backup?!?

In particular, I have a customer with Celera NAS,,, wondering if they could
do an image backup (offline or online) of a NAS share from external Win2K
box.

We already know NDMP is "coming real soon", early next year -- not soon
enough;  their immediate problem is (a) EDM is not working well, (b) they
have two servers with very large file spaces -- one's 710 GB (6 million
directory-objects, 12 hi-level directories, for department-level
separation), the other is about 400 GB (user home directories).  I advise
them to get their drive-letters under 1 million files/dirs, under 200 GB,
and they're doing that, but it will take another 6 months to get there!

TIA.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Pete Tanenhaus
Sent: Thursday, November 07, 2002 3:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Journaling


By nonlocal I did mean network drives.

To be more precise, drives that NT considers to be network drives.

To perfectly honest, I'm not all that familiar with SAN and haven't tried
to journal a SAN attached device.

Journal Based Backup relies on the Win32 api ReadDirectoryChangesW to
monitor file system change activity.

If this api will work with a SAN attached device (it doesn't with mapped
drives),
Journal Based Backup will work, if it doesn't it won't.

It hasn't been tested so I can neither confirm nor deny that it will/won't
work, and of course the official
position will be that if it hasn't been tested we don't support it.

If you are in a position to try it please post your results on the list,
I'd be interested.

Implementing Jbb on any type of NAS device would be difficult as  NAS boxes
only implement (actually
simulate might be a better term) a portion of the NT file system and any
type of journaling solution
would have to work in the context of the file system api support the
particular NAS vendor provides,
and I seriously doubt (but don't know for sure) that any type change
monitor support would be available, and
even if were it would probably be specific to the particular NAS box
meaning that we potentially would
have to implement a different solution each specific NAS filer.


Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: [EMAIL PROTECTED]
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"

-- Forwarded by Pete Tanenhaus/San Jose/IBM on
11/07/2002 03:56 PM ---

"Whitlow, Don" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/07/2002 03:19:47
PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: Journaling



Pete,
Thanks for the reply. However, I'm still trying to wrap my head around why
this should not work. When you say a non-local filesystem, are you by any
chance meaning anything mounted via a connection to a share on another
Win32
box? Or maybe via NFS?

I'm not trying to be difficult, I'm just having a hard time seeing how the
OS sees the distinction between a disk connected via a SCSI HBA vs. a disk
on a SAN connected via an FC HBA. An I/O request to either should be
exactly
the same as far as the O/S and anything else at the application layer is
concerned. I'm wondering if maybe we just have a misunderstanding over
semantics?

Again, appreciate the feedback. I'm just trying to clarify the situation as
we have a box or two that would probably benefit from journaling, but the
disk on those servers are SAN-Attached.

Sincerely,
Don Whitlow
Quad/Graphics, Inc.
Manager - Enterprise Computing
[EMAIL PROTECTED]


-Original Message-
From: Pete Tanenhaus [mailto:tanenhau@;US.IBM.COM]
Sent: Thursday, November 07, 2002 1:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Journaling


Unfortunately this is beyond our (development's) control.

The Microsoft Win32 api used to monitor file system changes does not
support non-local file systems.

It might be possible to write some sort of file system extension (filter)
to implement this type of support but
it would be a major development undertaking and would involve a
considerable investment of time and
resource which I'm not sure management would be willing to consider.


Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: [EMAIL PROTECTED]
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"

-- Forwarded by Pete Tanenhaus/San Jose/IBM on
11/07/2002 02:52 PM ---

"Whitlow, Don" <[EMAIL

Re: Question about dirmc

[DFrance]

Ooops, I mis-spoke... It's the output from "Q OCC " (from dsmadmc
prompt) that would confirm whether you are storing data into the DIRMC
storage pool.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: DFrance [mailto:DFrance-TSM@;att.net]
Sent: Sunday, November 10, 2002 4:40 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: Question about dirmc


Nope... all the versions of the directories should be rebound (as indicated
by the messages in the dsmsched.log -- presume you use client scheduler to
run the daily backups).

BTW, did you verify that this helps you for your Netware environment (by
query the filespace to see if any data is getting sent to DIRMC storage
pool)???  I don't recall for sure, but I thought the ACL's for Netware were
not that large, so might (mostly) not exceed the space reserved for that
info in the TSM db.

Regards,
Don

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Robert Ouzen
Sent: Sunday, November 10, 2002 7:59 AM
To: [EMAIL PROTECTED]
Subject: Question about dirmc


Hi to all

I implant a dirmc management class for the directories of my Netware clients
on disk. My question is did the next incremental backup will rebound all the
directories to new management class or I need to do a full backup ???

T.I.A Regards
Ouzen Robert
E-Mail: [EMAIL PROTECTED] <mailto:rouzen@;univ.haifa.ac.il>

Re: Comments on Server Graph or other like utilities

[DFrance]

Everything you say you are looking for, and more, can be found in this
product;  I've used it and continue to work with its developers as an
advisor on future developments... like any product, you must judge its
usefulness for your specific environment.

I suggest you obtain a copy of the User Guide, then download and obtain an
eval license;  I usually advise the install be done on a machine with
reliable network access to the TSM server(s) you want to monitor, like a
development or QA box that allows you to install with minimal bureaucracy.

I know there are several, large TSM sites using this tool that are on this
list; perhaps they, too, will respond.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Curtis Stewart
Sent: Saturday, November 09, 2002 10:42 PM
To: [EMAIL PROTECTED]
Subject: Comments on Server Graph or other like utilities


Hello List:

I administer a rather large TSM system in the financial industry. We are
considering the implementation of Server Graph for monitoring our
multiple TSM servers located all over the country (USA). I'm interested
in any experiences the members of this list may have with this product,
good and bad. Also, are there any other competing products that, in your
experience, work better?

We are looking for a tool that we can use from a central server that
provides TSM monitoring / Alerting, as well as reporting, and analysis
information. Ultimately, we'd like to be able to turn over the day to
day TSM stuff (restores, restarting / troubleshooting hung backups and
other basic tasks) to our 24x7 operations team so we can concentrate on
new TSM implementations, performance tuning etc... We'd like a tool that
will allow us to do both. Essentially we want to automate notification
of our operations team when something goes wrong, as well as use the
tool for in depth reporting and analysis of our site. We understand we
could accomplish this will a bunch of shell or Perl scripts, but we are
looking for something that's already put together and just works. We
don't have the time to reinvent the wheel here.

Our company uses OpenView and we will need to tie into this system as
tightly as possible. I understand that Server Graph claims to integrate
easily with OpenView. Do any of you have any experience with this
application? If so, will you please share your experiences?

Curtis Stewart
TSM Administrator

Re: Question about dirmc

[DFrance]

Nope... all the versions of the directories should be rebound (as indicated
by the messages in the dsmsched.log -- presume you use client scheduler to
run the daily backups).

BTW, did you verify that this helps you for your Netware environment (by
query the filespace to see if any data is getting sent to DIRMC storage
pool)???  I don't recall for sure, but I thought the ACL's for Netware were
not that large, so might (mostly) not exceed the space reserved for that
info in the TSM db.

Regards,
Don

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Robert Ouzen
Sent: Sunday, November 10, 2002 7:59 AM
To: [EMAIL PROTECTED]
Subject: Question about dirmc


Hi to all

I implant a dirmc management class for the directories of my Netware clients
on disk. My question is did the next incremental backup will rebound all the
directories to new management class or I need to do a full backup ???

T.I.A Regards
Ouzen Robert
E-Mail: [EMAIL PROTECTED] 

Re: Journaling

[DFrance]

Nice response, Zlatko --- I was about to say some of the same!

I agree, and would like for Geoff to reply about what he sees, relative to
the GUI window (one clear indicator).  Do his SAN drives appear under the
"Local" branch or "Network"?  (I noticed at my old 4.2 level, my
locally-defined shares were listed under "Network" --- \\server\uploads was
there, it even had the local path in parenthesis, on the c$ drive.)

For myself, I am most interested in learning if one of the SANergy solutions
will be supported by JBB -- the config. where the MDC is on Win2K, owns the
network shares, etc.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Zlatko Krastev/ACIT
Sent: Saturday, November 09, 2002 8:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Journaling


So if we divide the drives in separate categories:
1. Locally attached IDE/SCSI disks - direct-attached-storage (DAS)
2. Direct FC-attached to single system (I am avoiding to use non-shared
term here) - again DAS but using FC
3. SAN-attached disks/subsystems used by single server -
SAN-attached-storage (SAS)
4. SAN-attached disks/subsystems used by several servers but no concurrent
acces to same LUN (again I will not call them SAN-shared to avoid
confusion) - SAS
5. SAN-attached disks/subsystems used by several servers with concurrent
acces to same LUN (in our case MSCS) - SAS
6. LANMAN shares mounted on the TSM client - network-attached-storage
(NAS)

which one ought to be able to use journaling???
IMO categories 1,2,3,4&5 ought to be assumed "local" from Windows point of
view (they are accessed through HBAs not by LAN). So they ought to be
detected by TSM client's "all-local" domain except #5. The latter is not
an exception in attachment but is specifically treated in a MSCS
environment (and *is* supported since v5.1)

Bottom line: DAS & SAS ought to be supported for journaling while NAS
would be normal to expect is not supported.
Back to Geoff's problem - if I understood it correct his configuration is
in 3-rd or 4-th category. In both cases it *should* work.
I guess the support person was confused by somewhere used word "shared"
and categorized the case in #6 (and the requirement should be not for
product enhancement but for support staff education)

Zlatko Krastev
IT Consultant






Pete Tanenhaus <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07.11.2002 23:10
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Journaling


By nonlocal I did mean network drives.

To be more precise, drives that NT considers to be network drives.

To perfectly honest, I'm not all that familiar with SAN and haven't tried
to journal a SAN attached device.

Journal Based Backup relies on the Win32 api ReadDirectoryChangesW to
monitor file system change activity.

If this api will work with a SAN attached device (it doesn't with mapped
drives),
Journal Based Backup will work, if it doesn't it won't.

It hasn't been tested so I can neither confirm nor deny that it will/won't
work, and of course the official
position will be that if it hasn't been tested we don't support it.

If you are in a position to try it please post your results on the list,
I'd be interested.

Implementing Jbb on any type of NAS device would be difficult as  NAS
boxes
only implement (actually
simulate might be a better term) a portion of the NT file system and any
type of journaling solution
would have to work in the context of the file system api support the
particular NAS vendor provides,
and I seriously doubt (but don't know for sure) that any type change
monitor support would be available, and
even if were it would probably be specific to the particular NAS box
meaning that we potentially would
have to implement a different solution each specific NAS filer.


Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: [EMAIL PROTECTED]
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"

-- Forwarded by Pete Tanenhaus/San Jose/IBM on
11/07/2002 03:56 PM ---

"Whitlow, Don" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/07/2002 03:19:47
PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: Journaling



Pete,
Thanks for the reply. However, I'm still trying to wrap my head around why
this should not work. When you say a non-local filesystem, are you by any
chance meaning anything mounted via a connection to a share on another
Win32
box? Or maybe via NFS?

I'm

Re: Daylight saving Disaster

[DFrance]

Andy,

Thanks for researching this; boy, I forgot how many versions got hit with
this... I might be abit foggy, myself, but I was supporting two accounts at
the time (Oct, 2000, again in April, 2001) -- one gottit (big time, several
TB) with the issue on 3.1.0.7 f2, the other was on 3.7.2 (but had just
deployed their Win2K environment, so was something less than 1 TB),,,
something i won't soon forget!

Regards,
Don

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Andrew Raibeck
Sent: Monday, November 04, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: Daylight saving Disaster


Don,

The DST code for Windows has not been broken again. Also, I do not recall
it happening in TSM 3.1.0.6 or 3.1.0.7, though my memory may be wrong in
this regard.

The following link is to a post I made a year ago that discusses which
client versions have the problem.

   http://msgs.adsm.org/cgi-bin/get/adsm0110/473.html

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

Re: Troubleshooting performance issues

[DFrance]

I like all what you two said;  simply turn on the "perform" client trace
opt, specify output file, post the results --- it's a small file of output,
less than 50 lines --- then we can really discuss the issue. (BTW, "perform"
will include client_instr_detail along with time-stamps and client options
in force.)

Simply add the following two lines to the dsm.opt file (for a couple backup
cycles on a couple of the problem nodes):
tracefileperf-trc.out
traceflagperform

I cannot find the old "Prob. Determ. Guide" that has much detail on how to
interpret this client trace, but the line-item categories are clear enough
to tell the difference between client, network and server.

Learn more about tuning from the book at the following link -- the
long-awaited and longed-for (updated to 4.2) version of the original
classic... this is WAY cool (TomH, thanks for the off-list copy you sent, as
well!)

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TSMC/sm42tune
/en_US/HTML/TSMV4.2TuningGuide.html

also, at this location...

http://www.tivoli.com/products/solutions/storage/docs/tsm-tuning.html


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Gianluca Mariani1
Sent: Wednesday, November 06, 2002 4:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Troubleshooting performance issues


try also:


BufPoolSize 81920 --> set to 10% of RAM
UseLargeBuffers Yes ---> set to NO
MoveBatchSize 256 ---> set to 1000

for the rest Zlatko said it all, especially about the tapes. maybe you can
run an instr_client_detail trace to take a look at where the bottleneck
might be.
what about client options?

Cordiali saluti
Gianluca Mariani
Tivoli TSM Global Response Team, Roma
Via Sciangai 53, Roma
 phones : +39(0)659664598
   +393351270554 (mobile)
[EMAIL PROTECTED]



"The people of Krikkit,are, well, you know, they're just a bunch of real
sweet guys, you know, who just happen to want to kill everybody. Hell, I
feel the same way some mornings..."



 Zlatko
 Krastev/ACIT
   [EMAIL PROTECTED]
 Sent by: "ADSM:cc
 Dist Stor
 Manager"  bcc
 <[EMAIL PROTECTED]
 ST.EDU>   Subject
Re: Troubleshooting performance issues

 06/11/2002
 11.20


 Please respond
 to "ADSM: Dist
  Stor Manager"






---> TCPWindowsize 64512

TSM Reference Manual:
"TCPWINDOWSIZE
Specifies, in kilobytes, the amount of receive data that can be buffered
at one time on a TCP/IP connection.
...
3. A window size larger than the buffer space on the network adapter might
degrade throughput due to resending packets that were lost on the adapter.
"
Try "tcpwindowsize 256" instead

---> 3 IDE drives

Is the DB on separate drive? How many volumes ?!?! What is the drive and
what is the DB cache hit ratio?
IDE drives perform terrible if you issue more than one operation against
them - commands are queued in the device driver or controller but the
drive is executing them one-by-one. If you have master+slave drive on same
IDE channel - one drive have to wait until the other finishes its
operation and frees the IDE bus.
Do yourself a favour - buy one or two SCSI drives. It is a server on the
end.

---> 3 drives.  OS - DB - LOG

Your network is 100 Mb/s (~= 10 MB/s). The drives in 3583 are LTO, right
(15MB/s). You wrote 3 drives (and small diskpool or no at all) - so you
are attempting to backup direct to tape? Thus your network is unable to
feed the beast quickly enough and LTO has to stop-rewind back-start.
Usually under such circumstances you not only are wearing out to drive but
also are getting 1-3 MB/s (or less) tape-write rate.

---> Network data transfer rate:  570.67 KB/sec

It might be worth to check the network (preferably after paying attention
to above remarks). The TSM server is 100+Full+NoAuto but what about the
client nodes, switch(es)?

Zlatko Krastev
IT Consultant






Etienne Brodeur <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
05.11.2002 16:44
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Troubleshooting performance issues


I have some major performance issues during archive operations.  I also
have bad performance durning backups, but the backup window is larg

Re: BRMS question (sorry)

[DFrance]

Check out the PASE announcement;  I just attended a web-conf on the PASE for
OS/400 announcement, as it relates to TSM.

There's info on the BRMS web site and (only basic) info in the announcement
letter for v5.1 of TSM server (April 12, 2002).

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Del Hoobler
Sent: Friday, August 30, 2002 10:00 AM
To: [EMAIL PROTECTED]
Subject: Re: BRMS question (sorry)


>> There is an upgraded TSM API for OS/400,
>> but there are no current plans for a TSM BA client for OS/400.

> That's interesting. The presentation sent to our company by IBM early
this
> year told of the coming of both an OS/400 client and a Linux86 server
> "sometime in 2002".

Mark,

Please follow-up with the source of that presentation.
Have them research where they obtained that info.
Maybe the slide was supposed to be referring to
the TSM "API" client for OS/400 - not the client itself.
There isn't a TSM "BA" client on OS/400 in current plans.

Thanks,

Del



Del Hoobler
IBM Corporation
[EMAIL PROTECTED]

- Never cut what can be untied.
- Commit yourself to constant improvement.

Re: ACSLS Lock error

[DFrance]

As of 9/22...
Yep... this is a problem -- which we have, also, recently experienced!

It appears to be related to a level-sensitive ssi (daemon) that runs on the
TSM server, arbitrating communication with the ACSLS server -- according to
Stephen, after discussing this with him (and researching thru many
trial-and-error cycles of testing last week).

Won't know for sure until we upgrade to 5.1; in the meantime have a Sev. 2
PMR open, and developed a work-around that involves clearing the locks and
restarting the rc.acs_ssi before restarting TSM server.  I understand
numerous STK customers accept this as "normal operating procedure", but I
disagree,,, and hope to determine that it is a maint. level issue, as it was
for you.

STATUS_LOCKID_NOT_FOUND is another symptom of the problem;  main issue is
"ANR8851 Initialization failed for library 9310LIB..." -- also, AUDIT
LIBRARY fails, even after clearing the locks so we can use the drives!

Typical message sequence upon starting TSM:
ANR8860W Volume D0 is already locked by .
ANR8852E Initialization failed for ACSLS library 9310LIB.

PVR & MMS trace sent to Tivoli Level 2 support on Monday; will await their
response, probably in another week.

TSM -- 4.2.2.10
ACSLS - 6.1
SN6k -- 2.01

Fast-forward to October --- STK solved a separate problem with ACSLS-6.1
that "fixes" this problem; seems the code didn't properly maintain the
owning server's identity (ie, ACSACCESSID?), so at TSM restart init failed
due to mismatch with the server that owned the existing volume locks... we
are sss happy, now!

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Firmes, Stephen
Sent: Monday, September 09, 2002 11:02 AM
To: [EMAIL PROTECTED]
Subject: ACSLS Lock error


When I start the TSM server the library does not get initialized due to the
following error:

09/09/2002 10:58:27  ANR8855E ACSAPI(acs_lock_volume) response with
  unsuccessful status, status=STATUS_LOCK_FAILED.
09/09/2002 10:58:27  ANR8851E Initialization failed for ACSLS library
LIBRARY1
  will retry in 2 minute(s).

I have recyled the TSM server and the ACSLS daemon,  the ACSLS app and
server, and I even rebooted both boxes.  Still no luck.

Any ideas?

TSM 5.1.1.1
Solaris 8
ACSLS 6.0.1

Thanks for any help.

Stephen Firmes
TSM Engineer
Tivoli Certified TSM Consultant
StorageNetworks, Inc
Work:  781-622-6287
http://www.storagenetworks.com

Re: More on Repeat Backups...

[DFrance]

Tim,

Can you explain how this works? As I recall, when we tested DS restore mode,
we did not have network capability; what that meant to our procedure was...
1 - use the temp. install instance of Win2K, restore system/boot drive from
TSM;
2 - reboot restored-NT-instance into DS restore mode, run NTbackup for the
system objects (from the file restored by TSM, xxx.bkf),
3 - run NTDSutil to assert "authoritative" on desired items.

Also, can you go back further than most recent backup -- using TSM 5.1 for
point-in-time recovery of a piece of the AD or registry?

Thanks,
Don


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Rushforth, Tim
Sent: Wednesday, October 30, 2002 9:22 AM
To: [EMAIL PROTECTED]
Subject: Re: More on Repeat Backups...


That should have read:
1. Boot into DS restore mode and restore the system object using NTbackup or
TSM.
2. Use NTDSUTIL to perform the authoritative restore.

-Original Message-
From: Rushforth, Tim
Sent: October 30, 2002 9:17 AM
To: 'ADSM: Dist Stor Manager'
Subject: RE: More on Repeat Backups...

You can still do authoritative restores from a TSM backup.  You do this the
same as you do with NT backup.
1. Restore the system object using NT backup or TSM
2. Perform the authoritative restore by booting into DS restore mode and
running ntdsutil.

-Original Message-
From: DFrance [mailto:DFrance-TSM@;ATT.NET]
Sent: October 30, 2002 1:18 AM
To: [EMAIL PROTECTED]
Subject: Re: More on Repeat Backups...


Actually, my personal favorite, is to use the NT backup tool (maybe as a
preschedcmd) for making the System Object backup (to a file that gets picked
up by normal, daily incremental);  in the cmd file that runs NTbackup,
determine the daily or weekly logic of your choice, so only re-write the
SysObj.bkf as often as you like... possibly, every Tuesday & Saturday,
whatever.  So, with the 5.1 client, exclude system object backups -- relying
entirely on recovery of the ntbackup file to recover the system, which gives
the nice side-effect of providing a point-in-time recovery point and (also)
allows authoritative restore (of selected pieces of the registry, using
directory services restore mode).  This "side effect" becomes important if
ever you want to use the "authoritative restore" feature introduced by
Win2K;  the current method of backups provided by TSM only permits
non-authoritative restores.

Re: Renaming tsm winxx clients

[DFrance]

It wasn't a problem before (unicode client support); I've done exactly that
with WinNT, Win2K and Unix clients in prior versions.  (In the old days the
vol-label on WinNT needed to be the same.)

As long as you didn't change the TSM client-level from non-unicode to
unicode, you should get what you wanted -- resumption of previous
incremental... report to IBM if you got a "full" by only making the change
you described.  What level of client you did you run?

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Tim Brown
Sent: Tuesday, November 05, 2002 11:20 AM
To: [EMAIL PROTECTED]
Subject: Renaming tsm winxx clients


when a server ex. server01 with drives c: and d: are initially backed up
with tsm
2 file spaces besides the systemobject are are created  \\server01\c$ and
\\server01\d$

i can then rename the server to server99 and rename the filespaces to
\\server99\c$ and \\server99\d$

my next incremental backup seems to be a full backup
is this normal in a situation where you rename a server

Tim Brown
Systems Specialist
Central Hudson Gas & Electric
284 South Avenue
Poughkeepsie, NY 12601

Phone: 845-486-5643
Fax: 845-486-5921
Pager: 845-455-6985

[EMAIL PROTECTED]

Re: Tape drive recomendations

[DFrance]

So... thru most of this thread, the upshot is to consider:
1. Avoid cache=yes, rather use large disk pool with migdelay=1 *and* avoid
offsite  reclamation -- maybe defer the offsite reclamation to weekends,
after clearing out the disk pools.
2. Use not one, but TWO tape technologies -- 3590 (J or K) or 9940A's for
onsite;  then LTO or 9940B's for offsite ?!?  (I don't see many customers
going for that -- two different types of tapes, where most just want to
simplify, K.I.S.S. it for the sake of operator procedures!)
3. Larger arrays of ATA-drives, 1 TB for under $10K -- holy cow, we gotta
find a way to deal with that... how's about large FILE libraries on disk
(with or without SANergy), so disk pools migrate to FILE on disk, recently
expanded to allow more than 100 volumes for SANergy support,,, so, exploit
it as onsite, primary sequential pool.
4. If we truly want to configure (random) disk pool sufficiently large to
hold two days worth of data, for fast restore, then we must avoid
reclamation during that period... ah-ha, with this large array of ATA drives
configured for FILE (sequential) pool as nextstg, that would seem to relieve
the offsite-reclamation *and* the tape contention for primary pools.

All the earlier posts of advice still leaves us with slow DR recovery (due
to my server's data spread across many more tapes than would be with
collocation -- but wait, the truly mission-critical stuff usually comes in 3
flavors: the dbf's for the data base, the logs to recover up to most recent
sweep of redo-logs, and the binaries & config files (the OS flat files); the
dbf's are full backups daily, so it's really just tracking down the
collocated logs & dbf's, and non-collocated OS backups. What's a person to
do?  Collocation is not a good answer; I suspect grouping nodes into
app-based pools (not critical vs. prod. vs. dev/qa) so the critical data
gets spread among enough tapes so that restores of multiple, critical nodes
don't experience tape contention (due to non-critical nodes' data separating
them out).

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Rushforth, Tim
Sent: Thursday, October 31, 2002 8:04 AM
To: [EMAIL PROTECTED]
Subject: Re: Tape drive recomendations


And the issue is still there if you don't use CACHE=YES but don't completely
clear your backup pool.

We have more disk in our storagepool than is required for one night's
incremental - so we thought keeping some backups on disk was a good thing
(why migrate to tape if you don't need the space).


Tim Rushforth
City of Winnipeg

-Original Message-
From: Bill Boyer [mailto:bill.boyer@;VERIZON.NET]
Sent: October 31, 2002 9:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Tape drive recomendations

Be careful of your copypool reclamations with the disk cache turned on!!
There is a BIG performance hit on reclamation when the primary copy of the
file is on a DISK direct access storage pool. Then the MOVESIZETHRESH and
MOVEBATCHSIZE values are thrown out the window and the files are processed
one at a time.

What I've done to relieve the restore times is to not MIGRATE the disk pools
until the end of the day. That way restoring from last night is quick. I had
a client where they wanted CACHE=YES on a 60GB disk pool. The offsite
copypool reclamation ran for 2-days! Changed it so that migration started at
5:00pm and nobody complained about restore times.

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Steve Schaub
Sent: Thursday, October 31, 2002 5:59 AM
To: [EMAIL PROTECTED]
Subject: Re: Tape drive recomendations


This is one reason I am looking into some of the new, cheaper ATA-based
disk arrays.  98% of restores come from the last few versions, so if you
can size the diskpool large enough (and turn caching on) that you rarely
need to go to tape, restores scream.  Some of the initial prices I am
seeing are < $10k per TB.  It's not SSA, but for a diskpool it might be
fast enough.

-Original Message-
From: [EMAIL PROTECTED]
Sent: Wednesday, October 30, 2002 10:15 PM
To: UFL.EDU.asr; VM.MARIST.EDU;.ADSM-L
Subject: Re: Tape drive recomendations
2

=> On Wed, 30 Oct 2002 16:42:14 -0600, "Coats, Jack"
<[EMAIL PROTECTED]> said:

> From my fox hole, LTO works great, but in some ways it is 'to big'.
> The spin time on the tapes is measured as about 3 minutes to rewind
> and unmount a tape.  Meaning if you have to scan down a tape to
> restore a file it can be a while.  Very fast tapes tend to be small,
> so it is a real tradeoff.

> Speed of restore is starting to be a factor here and I have seen
> several posts where that is becoming more of an issue at many sites.
> But 

Re: YAPC.

[DFrance]

So, Allen -- what is it you do that accomplishes the "(virtual) filespace"
configuration... on NT/Win2K?

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 11:11 AM
To: [EMAIL PROTECTED]
Subject: Re: YAPC.


=> On Thu, 31 Oct 2002 07:01:33 -0600, [EMAIL PROTECTED] said:

> I'm still relatively new to the *sm world, so I'm not sure how to go on
the
> storage pool issue.  It was actually suggested to me that the best way to
go
> is just have one storage pool with collocation turned on.  That kind of
> makes sense to me when you think about restore times and such...  We're
> using several storage pools here, too.  I've been thinking about combining
> ours into one and doing the collocation thing.


I am colocating some of the pools, and not others; For instance, my
workstations usually have far, far less than one tape.  Noncolocated.  Many
of
my central servers nearly occupy a tape.  At least one, I've colocated by
(virtual) filespace, to split up a 350GB server into nice bite-size pieces.

- Allen S. Rout

Re: Daylight saving Disaster

[DFrance]

Yep... just see the README;  the usual conditions for upgrade on either the
server or the client is (a) once you upgrade the client, you *can* use the
new client features (ie, the ones specific to client operations), and you
*cannot* go back (this is a more recent caveat, in that new levels add new
objects to the database); (b) upgrade the server, at your convenience, just
realize you cannot exploit new server features (even if supported by the
client), until the proper, supporting server level is installed.

Muddy as heck?  Read the README for the server or the client; the README
file contains the full details you need to know... but, in general, using
the same features you've already been using does not require both server and
client be at the same level.  A 3.1 client can talk to a 4.1 server, and
(also) a 4.2 or even 5.1 client can talk to 4.1 server (just cannot use any
new, 4.2 features that would require cooperation from the server).  The
developers have gone to great lengths to ensure client and server upgrades
are not locked into each other... review the README for your specific
situation.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Bill Dourado
Sent: Sunday, November 03, 2002 6:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Daylight saving Disaster


Don,

What  I need to know in the short term, (if anybody has experience) ,   is
it   OK having  4.2.3.1 clients
running on TSM Server  4.1.1.4 ?

Bill Dourado

Ext 5134





    DFrance
 cc:
Sent by: Subject: Re: Daylight saving
Disaster
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>


02/11/02
22:00
Please
respond to
"ADSM: Dist
Stor Manager"






It was the client code that was previously fixed, more than once, in the
3.1
and 3.7 timeframe --- sounds like the DST code for Windows got broken,
again.  4.1.x is downlevel, for support contract purposes -- unless things
are different for you.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a, for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Bill Dourado
Sent: Saturday, November 02, 2002 7:03 AM
To: [EMAIL PROTECTED]
Subject: Daylight saving Disaster
Importance: High


Hi there

I am in big trouble after daylight saving when  clocks went backup one
hour.

All the clients(50)  are attempting to do full backups !

My TSM Server version is 4.1.4.1

The clients(Windows 2000 & NT) are mostly 4.1.1.0 , a few are 3.1.07 &
3.1.0.6.

I have temporarily suspended all backup schedules  except for the business
critical clients.

I have upgraded one of clients to  4.2.3.1 and intend to upgrade the rest
of the clients.

Will I run into any  problems bearing in mind my TSM Server version is
4.1.4.1 ?

T.I.A

Bill Dourado

Re: TSM and Performance

[DFrance]

To really know if you need a second server, you need to know what your
current server is doing.  An M80 with 5GB of RAM and 2 drawers of SSA drives
should easily handle 1.5 to 2.5 TB/day;  the wide variance is a function of
the number of db-inserts that occur. Do you know your current backup load?

I am nervous about 5.1.5.1;  I will avoid it, for now -- especially since
seeing your earlier posts (and Gretchen's) about some issues.  Regardless of
my concern, you gotta measure your network, CPU and I/O performance on the
TSM serve box, along with the current backup traffic -- see summary table
and/or dsmaccnt.log for that number.

Fastest way for tracking TSM load would be "ServerGraph"; alternatively, you
gotta run your own statistics using VMSTAT, IOSTAT, dsmaccnt.log, and
summary table select's to quantify what you're currently doing.

Hope this helps!


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Gill, Geoffrey L.
Sent: Sunday, November 03, 2002 7:28 PM
To: [EMAIL PROTECTED]
Subject: TSM and Performance


I'd like to hear from anyone who has dealt with performance issues and TSM
that might be able to tell me if the environment I have is at its limits or
some upgrades might help. What I have is an RS/6000 M80 on AIX 4.3.3 running
TSM, that's all it does.

My TSM environment is such that there are about 160 nodes that back up 6
days a week. The one day, Saturday, is set aside for a monthly is there are
any. There are 2 SAP nodes that each back up 200GB a day. The rest is a
mixture of environments, mostly Win2K, with SQL and Domino and a lot of, you
might say, junk. Co-location is turned on, the DB is 43GB, 47%used.

The library is a 3494 with 10 direct attached fiber 3590's. The computer has
5GB of memory, 2 CPU's, is on a GIG but also has 2 other 10/100/1000 cards
not doing anything at the moment. The local disk, 2 drawers, are spread
across 2 SSA adapters. The TSM DB and log are TSM mirrored, one on each SSA.

The TSM support people made a comment to me over the phone I'm not sure I
agree with. In any case I'd like to get some "real life" feedback from
everyone who has this type of environment and tell me if there is something
I need to do now, or very soon. I have outstanding requests to add nodes but
would like to hold off till I find out if I need additional, CPU's, memory
or just environment changes in TSM to beef this up. With all of the issues I
see with 5.1.5.1 I don't know if it's us or the software at this point.
Didn't seem to see this on 4.2.1.9.

Thanks for the help.
Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Re: Daylight saving Disaster

[DFrance]

It was the client code that was previously fixed, more than once, in the 3.1
and 3.7 timeframe --- sounds like the DST code for Windows got broken,
again.  4.1.x is downlevel, for support contract purposes -- unless things
are different for you.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a, for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Bill Dourado
Sent: Saturday, November 02, 2002 7:03 AM
To: [EMAIL PROTECTED]
Subject: Daylight saving Disaster
Importance: High


Hi there

I am in big trouble after daylight saving when  clocks went backup one
hour.

All the clients(50)  are attempting to do full backups !

My TSM Server version is 4.1.4.1

The clients(Windows 2000 & NT) are mostly 4.1.1.0 , a few are 3.1.07 &
3.1.0.6.

I have temporarily suspended all backup schedules  except for the business
critical clients.

I have upgraded one of clients to  4.2.3.1 and intend to upgrade the rest
of the clients.

Will I run into any  problems bearing in mind my TSM Server version is
4.1.4.1 ?

T.I.A

Bill Dourado

Re: TSM reliability

[DFrance]

>From all the posts I've been reading, 4.2.anything is NOT where you want to
be -- the sunset date for 4.2 support is April 15, 2003 -- less than six
months away.

I am working with a  customer who's on 4.2.2.12, we plan to upgrade to
5.1.1.6 -- which (currently) seems to be the cleanest 5.1 release out there;
5.1.5.x is still getting lots of "flack" for regressing things that got
fixed back in 4.2.2.x.

I'd rather step up to 5.1.something, and fight thru the bugs -- there are
some nice features I'd like to exploit (like MOVE NODEDATA); if 5.2
(whatever it gets called) comes in April, or somewhere close, that still
gives them a year to contemplate the next step-up level to maintain currency
(for support purposes).

FYI,
4.2.2.13 = 9/25/02;
5.1.5.1 = 10/11/02;
5.1.1.6 = 9/13/02...
No (public) server patches since these three;  and, the "skinny" on 5.1.5.0
was to forget about running that level, get 5.1.5.1 patch level if you need
5.1.5.  And we've seen the posts about troubles with 5.1.5.1.  Given the
history of recent point-releases, 4.2.3.0 should be better than most (though
it did regress some items shipped in the patch levels for 4.2.2)... caveat
emptor, still!

That's my 2-cents worth.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Paul Miller
Sent: Friday, November 01, 2002 1:48 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM reliability


So far, I haven't had any major issues with 4.2.3.0 on Win2k.  Over the
next couple weeks, I'll be putting other platforms (AIX, HP-UX) to the
same version.  I'll let you know how it goes.

-Original Message-
From: [EMAIL PROTECTED] [mailto:msimpson@;UKY.EDU]
Sent: Friday, November 01, 2002 15:40
To: [EMAIL PROTECTED]
Subject: Re: TSM reliability


At 13:08 -0600 11/1/02, Tab Trepagnier wrote:
>I understand what you're saying and largely agree.  But in TSM's case
that
>would be the x.x.0.0 release.  And history has shown those to be pretty
>much uniformly bad.
>
>It's the reported poor quality of the maintenance releases intended to
fix
>THOSE problems - the x.x.x.0 releases - that are the real shame.

I guess the solution is to avoid any release with a dot in it.

Ten days ago, we asked IBM for a recommendation on which release we
should upgrade to, since it seems to be universally agreed that our
4.2.2.0 is not a good place to be. So far, they haven't been able to
recommend a good release.
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506

mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge
obsolete
profits for their obsolete shareholders.  And this year's run twice as
fast
as last year's.

Re: Slow Offsite Reclamation (Was Tape drive recomendations)

[DFrance]

So,,, the upshot is, for good performance of OFFSITE reclamation:
- empty the DISK (ie, RANDOM) storage pool(s) that feed any
offsite/copy-pool before running reclamation.

This, loosely translates to "only run reclamation for offsite storage-pools
on weekends" -- since we sized the DISK pools to be 2.25 x the daily load,
and set migdelay=1 to allow restores (of most recent backup data) to work
from disk, rather than incur tape mounts.

Thusly, we end up with more tapes in offsite storage (since their
reclamation only occurs once a week);  best to set the rec=60 (as
distasteful as that might seem), when starting reclamation at 2pm on
Saturday, after doing disk-to-tape migration (with migdelay=0) to empty out
the disk pools.

And, for those folks contemplating HUGE primary pools on disk, with no
migration to tape --- you'd better plan on periodic migration to sequential
pools on disk, else your offsite, copy-pool reclamation will take days, not
hours, to complete.  Remember, this product is optimized for (a) disk
(random-access) pools for initial destination (to maximize concurrency with
minimal tape contention for backups), and (b) sequential pools for the
long-term destination of all data, both primary and copy-pool data.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change ayett to att for replies)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Rushforth, Tim
Sent: Friday, November 01, 2002 7:26 AM
To: [EMAIL PROTECTED]
Subject: Re: Slow Offsite Reclamation (Was Tape drive recomendations)


Yes! An old APAR cover's this issue, see below.  When you are running
offsite reclamation watch the throughput when it is reading from disk as
opposed to reading from tape.  It just crawls.

Apar IC15925:

ERROR DESCRIPTION
During an offsite reclamation process; where files are being transfered from
disk to tape.  ADSM fails to group the files together into transaction
groups.  Instead the files are processed sequentially.  Hence a file will be
reclaimed and committed before the next file will be process. ADSM needs to
honor the movebatchsize and movesizethresh options in the server options
file, so that the files will be grouped together properly for reclimation.
As a note, this problem will only be seen where off-site reclamation is
occuring from disk to tape.
COMMENTS:
After taking a very close look at the solution for this APAR, it was
determined that the code needed for this performance enhancement is
significant because it requires a restructure in the offsite reclamation
transaction processing.  A requirement can be taken to include this
performance improvement in the next release or version.


Tim Rushforth
City of Winnipeg

-Original Message-
From: Steve Schaub [mailto:Steve.Schaub@;HAWORTH.COM]
Sent: October 31, 2002 11:15 AM
To: [EMAIL PROTECTED]
Subject: Re: Tape drive recomendations

If I'm reading this correctly, only migrating my diskpool down to 10% is
hurting my DRM reclamation?
Are you saying that putting in a 10TB diskpool that never goes to
primary tape (only dr copies) would give me monstrously bad
reclamations?  Our current main diskpool is 100gb on SSA and has caching
on.  I haven't had a terrible problem with DR reclamation, though the
storage pool backup to DRM only has a throughput of about 5mb/sec.

-Original Message-
From: [EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 11:03 AM
To: CITY.WINNIPEG.MB.CA.TRushfor; VM.MARIST.EDU;.ADSM-L
Subject: Re: Tape drive recomendations


And the issue is still there if you don't use CACHE=YES but don't
completely clear your backup pool.

We have more disk in our storagepool than is required for one night's
incremental - so we thought keeping some backups on disk was a good
thing (why migrate to tape if you don't need the space).


Tim Rushforth
City of Winnipeg

-Original Message-
From: Bill Boyer [mailto:bill.boyer@;VERIZON.NET]
Sent: October 31, 2002 9:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Tape drive recomendations

Be careful of your copypool reclamations with the disk cache turned on!!
There is a BIG performance hit on reclamation when the primary copy of
the file is on a DISK direct access storage pool. Then the
MOVESIZETHRESH and MOVEBATCHSIZE values are thrown out the window and
the files are processed one at a time.

What I've done to relieve the restore times is to not MIGRATE the disk
pools until the end of the day. That way restoring from last night is
quick. I had a client where they wanted CACHE=YES on a 60GB disk pool.
The offsite copypool reclamation ran for 2-days! Changed it so that
migration started at 5:00pm and nob

Re: Expire backups for retired node

[DFrance]

You could delete the node, but first you'll be required to delete the
filespaces in backup storage... "del fi nodename *" should do it -- after
you reply to the prompt asking "are you sure you want to do this?"... when
you're finished with that, then just "rem nod nodename" to delete the node.
(See "help del fi" and "he rem nod" for details.)

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Braich, Raminder
Sent: Thursday, October 31, 2002 1:41 PM
To: [EMAIL PROTECTED]
Subject: Expire backups for retired node


Hi,
  How can I expire all the backups and versions of a particular node which
is going to be retired shortly. We do not need to keep any of the backed up
data. I still have not deleted the node from TSM server.

Thanks
Raminder Braich
SAP/ORACLE Administrator
The Davey Tree Expert Company
Kent, OH
330-673-9515 Ext 270

Re: tape missing under q libv (HELP)

[DFrance]

Nope... "q libv" command will list all tapes in defined libraries; you can
wild-card the library name and/or the volume number.  Seems to me that when
you do bulk-loading the library (ie, you open the door and load slots), then
run TSM "audit libr", there's a missing step or 2 -- make sure no drives are
mounted when you do this, and let the library complete its barcode audit
before asking TSM to do anything.

Other libraries, (eg IBM 3575, Dell 130T) want to do a barcode audit every
time the door is opened; the 3575 prompts the operator (on its external
control screen) to do it, the 130T just does it. Doing more than onsey-twosy
loads is more practical, but you must be careful to ensure the library and
drives are not busy; if you do this while a tape is in a drive, you must
make sure you don't populate its slot, else library (and TSM) will become
unhappy, and you may ultimately need to restart TSM (after clearing things
up with the library inventory and drive status).

(Why didn't you use "checkl=b"?  With ACSLS, that's not allowed, but with
SCSI libraries supported by TSM, that's the way to go, imo.)

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Chetan H. Ravnikar
Sent: Tuesday, October 29, 2002 6:15 PM
To: [EMAIL PROTECTED]
Subject: Re: tape missing under q libv (HELP)


On Tue, 29 Oct 2002, Seay, Paul wrote:
> 4.2.2.0 is a really bad release to be running but I do not think it is
your
> problem.  4.2.2.12 or 4.2.2.13 are pretty good.
we are thinking of moving to 5.1.51 and we have been testing

>
> When you issue the q libvolume command you must specify the library and
the
> volume otherwise you will always get not found.  If you just specify q
> libvolume it will show all volumes.
do I need to specify the lib, even when we have only one lib defined.
q libv  still did not show the vol required.

I can q vol  and it does come back saying it is part of onsite
storage pool! Not sure how it went out of sync!


> When you do the checkin command what does the log say?  Is it really being
> checked in or is the checkin failing.
the checkin come back un-succesful in the beginnning, we had weird
combination of errors. TSM  lost element information on the LIB, a lib
audit failed. After reseating the QIPs the lbtest came back fine.

Now we moved the tape out to the E/E port (manually)and re-checked in the
tape as private, with the below comand which failed to see the tape again
as there were some I/O errors.

CHECKIN  libv gator64k l05232 search=n stat=pri checkl=n

10/29/02 12:03:16 ANR8306I 003: Insert 8MM volume L05232 R/W into the
slot  with element number 0 of library GATOR64K within 60  minutes; issue
'REPLY' along with the request ID  when ready.

apparently on a SpectraLogics gator 64k using TSM, the limitation is that
the E/E port is configured for exports only for TSM. There is no way one
can have tapes in the E/E port and do a BULK checkin via TSM.

We BULK load tapes via the lib console and then do a TSM audit.

Now here is how it worked. we put in the tape back in the E/E/ port and
then ran this comand

CHECKIN libv gator64k search=y stat=pri

ANR8430I Volume L05232 has been checked into library GATOR64K



> What kind of library do you have?
anybody using TSM with Spectra Logics libs and how are they working with
the sequence numbers going out of sync. This happens when we do a BULK
load via the lib-console and say at the same time there is a tape which is
currently being read/written to (basicaly mounted), the lib could just go
load the tape to a slot which had a VALID tsm volume in it and when TSM
returns back with the volume, it freeks out!

it makes me wonder if spectra logics is really really compatible with
TSM!

Not sure how other libs work with TSM on this issue

Many thanks for your time Paul



> Paul D. Seay, Jr.
> Technical Specialist
> Naptheon Inc.
> 757-688-8180
>
>
> -Original Message-
> From: Chetan H. Ravnikar [mailto:Chetan.Ravnikar@;SYNOPSYS.COM]
> Sent: Tuesday, October 29, 2002 11:28 AM
> To: [EMAIL PROTECTED]
> Subject: tape missing under q libv (HELP)
>
>
> Hello
> I have a strange situation, when doing a restore. The process keeps
waiting
> for a media unavialable and bails out.
>
> The volume it is looking for is in the on-site tapepool, but doesn't show
> under q libv. I had re-checked in the volume as private, also I can *q
cont*
> on this vol but for some reason it does not show under q libv.
>
> I have even audit'd the lib, but no success.. any pointers/advice is a
great
> help. I have a customer waiting on this restore
>
> we are on TSM server 4.2.20 on sol-2.8
>
> thanks
> Chetan

Re: ACSLS/TSM on Unix

[DFrance]

There are logs in ACSLS that your friendly STK folks should show you;  also,
there is a two-inch thick book User Guide, that has many things of interest.
If you audit the library (using the ACSLS console) it may take a very long
time, but it's worth it to ensure things are in sync... if that's what you
suspect.

When you replaced the robot's "hand" did you shutdown TSM, and stop ACSLS
(and the acs_ssi daemon that runs in the TSM server)?!?  You might need to
clear the locks, if the ACS audit fails to resolve the issue.

When you do the ACSLS audit, you should prevent TSM from interacting with
the ACSLS server;  upon completion, restart the acs_ssi, typically using
rc.acs_ssi (to re-establish communication between TSM and ACSLS).

If the preceding steps fail to clear this problem, get instructions to
access the ACSLS console, login as ACSSA, and run "cmd_proc" to enter the
console mode interface, and clear the locks (ensure TSM is down during this
process)...
- q lock vol all
- set lock 
- unlock vol all
- repeat the sequence until all volume locks are cleared
- (Note: this simplified sequence assumes a single ACSLS, library and TSM
server!!)

After restart of the TSM, initialization should complete, and "audit libr"
should be run, to totally sync up TSM inventory with ACSLS.  You might also
want to review all the tapes known to ACSLS ("q vol all") and probably run
checkin for the vol-range of tapes not yet checked in to TSM, but known to
ACSLS.

Good luck!


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Peppers, Holly
Sent: Tuesday, October 29, 2002 4:25 PM
To: [EMAIL PROTECTED]
Subject: ACSLS/TSM on Unix


Hello All!!

I need some assistence please.  :-)
Currently we have TSM running on AIX, connected to ACSLS to Wolfcreek
library.  This afternoon, a tape got stuck in the hand of the silo, and the
hand was replace.  However, now when I try to run an audit of the library
within TSM, I am receving tht following error mesage:

10/29/2002 17:21:54  ANR8855E ACSAPI(acs_lock_volume) response with
  unsuccessful status, status=STATUS_LOCK_FAILED.
10/29/2002 17:21:55  ANR8460E AUDIT LIBRARY process for library ACSLIB
failed.
10/29/2002 17:21:55  ANR0985I Process 2 for AUDIT LIBRARY running in the
  BACKGROUND completed with completion state FAILURE
at
  17:21:55.

Is anyone familiar with this?  Please respond.  :-)
Thanks.


Holly L. Peppers
BCBSFL
Technical Services




Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.

Re: More on Repeat Backups...

[DFrance]

Well... actually, if you really want to do it (I would consider it), you can
exclude System Object (or, better, use a "special" management class which
maps to a copygroup that has FREQuency=5, so INCRemental backups only occur
every 5 days).

Clearly, the 200-400MB blob called System Objects, Microsoft wants the whole
set (or none) in the event of system recovery; that's why you always get all
the system files & DLLs, etc.  If you use the 5.1 client, test to make sure
you get the desired results; exclude or avoid backup for System Object on a
daily basis is reasonable -- you must weigh the value of not having it
backed up as often as you did for NT... many shops make system level
recovery images daily, others do it weekly (some even bi-weekly or
monthly) -- which makes you vulnerable to corruption with restore data
that's more than a day (or week) old, so you may lose some config changes
that didn't get backed up.

Actually, my personal favorite, is to use the NT backup tool (maybe as a
preschedcmd) for making the System Object backup (to a file that gets picked
up by normal, daily incremental);  in the cmd file that runs NTbackup,
determine the daily or weekly logic of your choice, so only re-write the
SysObj.bkf as often as you like... possibly, every Tuesday & Saturday,
whatever.  So, with the 5.1 client, exclude system object backups -- relying
entirely on recovery of the ntbackup file to recover the system, which gives
the nice side-effect of providing a point-in-time recovery point and (also)
allows authoritative restore (of selected pieces of the registry, using
directory services restore mode).  This "side effect" becomes important if
ever you want to use the "authoritative restore" feature introduced by
Win2K;  the current method of backups provided by TSM only permits
non-authoritative restores.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to a to reply)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Lawson, Jerry W (ETSD, IT)
Sent: Wednesday, October 16, 2002 6:48 AM
To: [EMAIL PROTECTED]
Subject: More on Repeat Backups...


Date:   October 16, 2002Time: 7:31 AM
From:   Jerry Lawson
The Hartford Insurance Group
860 547-2960[EMAIL PROTECTED]

-
First - let me thank you all for the responses to my original question.
Your answers have gotten me thinking some - I say some, because at my age,
it's hard to get everything going again, and I suffer from "senior moments"
too often.

Most of the answers revolved around the suggestion that I could exclude
something - either the files themselves, or the System Object itself if I
get the newest client.  This seems to me to be treating the symptom, rather
than the problem - if I exclude them, obviously, I can never restore them
(DUH!).  If these do get corrupted or deleted, it would appear that I could
be in for another bout with my desktop support folks - they just had my
Laptop for 3 weeks - I'm not eager to deal with them again.  Now I will be
the first to admit that I'm not MS Certified on any OS, and so the idea of
excluding the whole System Object is scary as well - doesn't that include a
big portion of registry information if I need to do a complete restore?  Or
is the idea of a Bare Metal restore with TSM one that has died?

In my (sometimes overly simplistic) mind, I remember the ADSM class I
attended where the instructor identified how a file was determined to have
changed - either the date, the time, or the size has changed.  Has TSM
changed this philosophy?  After all, I look at the files in question, and
nothing has changed that I can see externally.  Shouldn't there be a better
approach than to say "well, they're a part of the system object, and
therefore you need to exclude them."  Shouldn't the software be smart enough
to figure this out?


-
 Jerry (still tilting at
windmills)



This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all
copies.

Re: Monthly backup

[DFrance]

You must either (a) use TWO node names for this client (in order to have TWO
management policies), or (b) use the archive command (and -archmc=xxx) for
the carefully specified, long-term retention stuff, or (c) create a monthly
backupset for the filesystem in question.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Yahya Ilyas
Sent: Monday, October 14, 2002 6:19 PM
To: [EMAIL PROTECTED]
Subject: Monthly backup


On one of TSM client I am using two management classes/ copy groups.  In
include_exclude file I have added new management class name in front of the
file system's name and the rest of includes use default management class.
Default management group has vere, verd, rete and reto parameters set to 35
days, and that one file system has different management with 365 for all of
these options so I can keep data for one year.

Now I need to change backup for this filesystem to become daily with default
management class for 35 days,  and do  monthly backups to keep for one year.
I will appreciate any suggestions.
Thanks

Yahya



>   -
>   Yahya Ilyas
>   Systems Programmer Sr
>   Systems Integration & Management
>   Information Technology
>   Arizona State University, Tempe, AZ 85287-0101
>
>   [EMAIL PROTECTED]
>   Phone: (480) 965-4467
>
>

Re: reclaims erroring out

[DFrance]

ANR0486W Session session number for node node name (client platform)
terminated - internal error detected.
Explanation: The specified client session is ended by the server because an
internal processing error has been
detected on the server. A programming error may have occurred in the server
program.
System Action: The session is ended and server operation continues.
User Response: Contact your service representative.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Lawrence Clark
Sent: Tuesday, October 29, 2002 10:37 AM
To: [EMAIL PROTECTED]
Subject: reclaims erroring out


For some undetermined reason our reclamations have been erroring out.
Drives are available, and source files in the primary pool are in the
tape library. Here is the error code, which is not in my old copy of the
messages manual:

10/29/2002 11:27:45 ANR0986I

Anyone know what this code means?

Re: continue a restartable session

[DFrance]

When a restartable restore is currently running, it displays the session
number "-1"... only possible when NQR is invoked.

Once that number becomes positive (you have stopped the active restore),
then you can (from dsmc on the client) run "restart restore" (see the using
clients book).  If you continue to restart from the beginning, you will
incur the total restore time all over again -- and, with NQR, you can even
see the data coming down from the server (by watching the network activity).

OTOH, I indicated (in a previous post) how you could trigger classic restore
(rather than NQR), which would still incur think-time, but the server would
do the "thinking" as it determines the list of files eligible to send, then
sorts the tape mounts, and starts sending the data... my experience in
restoring 20 GB filesystem, depends on # of dir-objects, should complete in
less than 4 hours -- although that could be more (ROT is between 2 and 7 GB
per hour for extremely large number of files).

Regards,
Don


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Alexander Lazarevich
Sent: Tuesday, October 29, 2002 8:33 AM
To: [EMAIL PROTECTED]
Subject: continue a restartable session


we've got ADSM 3.1 on an AIX 4.3.3 machine, with a 3575 tape library.

we had a major hardware failure, and i'm restoring the last filesystem
right now. i'm trying to retore a filesystem on an aix system, let's
say its called /home/dude. its a 20GB filesystem. 7GB has already been
restored a few days ago, but the session died because of a missing tape
 which we do not have anymore (data not available to server) (don't ask
why we dont have the tape anymore). but now i must restore the rest of
that filesystem. there was a restartable session for this restore, which i
canceled yesterday.

since the restartable seesion is canceled. im just trying to restart a
brand new restore for that filesystem. i go to the aix client, type dsm,
then choose to restore /home/dude, then it starts working, and at some
point it asks me if i want to overwrite, i say NO, then it hangs. its been
sitting there for 90 minutes??!?!?:

1,380 Tcp/Ip RecvW  1.5 H  826.4 K   5.2 K Node  AIXHERA.ITG.UIUC.EDU

also, when i do a q rest i get this:

  SessRestoreElapsedNode Name  Filespace
NumberState  Minutes   Name
---------
---
-1Restartable 88HERA.ITG.UIUC.EDU  /home/mac/dude

but the sessions should show up as ACTIVE, not Restartable.

so how do i finish restoring this filesystem? i looked in the
administrator guide, page 204, and it does NOT say how to start a
restartable session. it only says how to cancel it.

any ideas? should i just start over? i hate to do that if im just gonna
have to wait another 90 minutes for it to start restoring.

thanks in advance,

alex
------
   Alex Lazarevich | Systems | Imaging Technology Group
   [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu
------

Re: monthly backup

[DFrance]

Yep... most data center customers I've worked with prefer to do online full
backups during the week, then weekly and monthly offline/cold backups...
using "dsmc archive /Ora_instanceX/* -archmc=xyz -su=y".  Using archive
makes it very easy to do just what the customer wants:  weekly (and/or
monthly) cold-snapshot of the db, retained just for the desired amount of
time (as specified in the MC)... archive simply runs the list of files
specified -- no comparing of last-change attributes, etc.  The one
difference you should note is that an archive client schedule will be marked
as "failed" if any files must be skipped; whereas backup is not.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Mark Stapleton
Sent: Tuesday, October 29, 2002 10:19 AM
To: [EMAIL PROTECTED]
Subject: Re: monthly backup


From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
> a client of ours wishes to have a monthly full-backup of their databases.
> My question is , is archiving a good altenative? and how do i set it up?
> (never used archiving options before)

Are you using the regular backup/archive client? If so, yes, that is the
preferred method for you're after. The command is

dsmc arch //*.dbf -subdir=yes

Read up in the backup client documentation on proper setup.

If you're using a TDP agent, you can't archive with that software.

--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
Certified AIX system engineer
MCSE

Re: Directories written in the wrong pool, although using dirmc option

[DFrance]

Hi Andy,

Thanks, for the excellent responses (below and to Mark's message) ... and
know the community continues to appreciate your participation (here and
elsewhere)!

I am relieved to learn DIRMC is still relevant, and will continue to
advocate its use with customers supporting Win2K, Netware and AIX servers.
And, I appreciate your expansion of the question about point-in-time
considerations... that's more ammunition in our arsenal for helping
configure for speedy restores.

Best regards,
Don

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;ayett.net (change aye to reply)

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Andrew Raibeck
Sent: Monday, October 28, 2002 3:32 PM
To: [EMAIL PROTECTED]
Subject: Re: Directories written in the wrong pool, although using dirmc
option


Hi Don,

>>
I share Mark's sentiments... on TWO points:

- if this was resolved, for both users in the discussion, let's share the
results;
<<

It's not a question of sharing results (of course results should be
shared), but in the back-and-forth involved in gathering enough
information to diagnose the problem. I see no point in cluttering up the
list server with traces and other attachments that, by themselves, are
almost certainly of no interest to the majority of users (not to mention
that I don't always get attachments from ADSM-L posts), and some of which
might ultimately not be pertinent to the issue.

Arnaud has already communicated to me that (a) he can not recreate the
problem reliably, and (b) as he mentioned in his last ADSM-L post on this
subject, he created a new policy domain that does for him what he wants.
So the root cause of his trouble is unknowable.

>>
- if DIRMC is no longer relevant, I'd sure like to know why!  Win2K is
becoming ever more prevalent, and most data center customers go wild with
lots of permission groups (causing the ACL's to grow too large to be
contained in the TSM db -- I used to think!)
<<

Yes, DIRMC is still relevant.

>>
The question that's left is whether a given restore will be just as fast
(NQR or classic) since dir's are now more readily backed up -- and, if
that's true, what about point-it-time restores that would get a mix of
dir's restored, to match the state of a time further back than the most
recent backup?!?
<<

Restoring directories whose backup versions exist in storage pools is much
like restoring small files in terms of the performance overhead. So yes,
it will almost certainly take longer to restore 100,000 directories from
storage pools than it would to restore 100,000 directories that reside
strictly in the TSM database. So putting directories in a disk pool (and
not allowing them to migrate) saves time on restore, as opposed to
restoring them from tape. In the same manner, putting very small files in
a disk pool could also save on restore time.

As for point-in-time restores, this has been discussed several times in
the past. Instead of thinking in terms of how many versions to keep,
consider thinking in terms of how far back you wish to be able to recover
your data. For example, if you want to guarantee restorability up to 31
days ago, then set your VEREXISTS to NOLIMIT and RETEXTRA to 31 (and
VERDELETED and RETONLY depending on how you want to service deleted date).
Also make sure that the management class your directories will be bound to
has similar settings. This way, regardless of the number of times a
directory is changed, you can still restore it up to 31 days ago, with the
granularity being the frequency of TSM backups.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




DFrance <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/26/2002 14:27
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Directories written in the wrong pool, although
using dirmc option



I share Mark's sentiments... on TWO points:
- if this was resolved, for both users in the discussion, let's share the
results;
- if DIRMC is no longer relevant, I'd sure like to know why!  Win2K is
becoming ever more prevalent, and most data center customers go wild with
lots of permission groups (causing the ACL's to grow too large to be
contained in the TSM db -- I used to think!)

As far as I can tell, DIRMC is still a very signi

Re: TSM 5.1.5 Media

[DFrance]

Tim,

Just use your keys from 5.1.0.0 media -- see the 5150 or 5151 readme files;
the only folks needing new media (at 515 level) would be for the new Linux
server, its material is in rpm format.

For all other servers, 5.1.5.0 and 5.1.5.1 are both available at the IBM ftp
site.  BTW, if you decide to use 515, be sure to get the patch-level
5.1.5.1 -- else, "caveat emptor" may really "bite" you.

- from the file: TSMSRVAIX5150.README.SRV...
"License certificates and license enablement remains at the 5.1.0.0 level. "

This is Tivoli Storage Manager Server for AIX service level 5.1.5.0
for the following filesets:

tivoli.tsm.devices.acsls
tivoli.tsm.devices.aix43.rte
tivoli.tsm.devices.aix5.rte
tivoli.tsm.msg.en_US.devices
tivoli.tsm.msg.en_US.server
tivoli.tsm.msg.en_US.webhelp
tivoli.tsm.server.aix5.rte64
tivoli.tsm.server.com
tivoli.tsm.server.rte
tivoli.tsm.server.webadmin

For ftp convenience these packages have been tar'd and gzip'd into the file
TSMSRVAIX5150.tar.gz




Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
HEMPSTEAD, Tim
Sent: Monday, October 28, 2002 3:56 AM
To: [EMAIL PROTECTED]
Subject: TSM 5.1.5 Media


Hi,

For the people who are already trying out TSM 5.1.5 ... do you have install
media for 5.1.5 or are you patching onto 5.1.0? ... I ask because we are
building a new TSM server at (hopefully) 5.1.5 but IBM have sent us 5.1.0
media ...

Regards

Tim

--
Tim Hempstead, [EMAIL PROTECTED]
Unix Technical Specialist
SchlumbergerSema


_
This email is confidential and intended solely for the use of the
individual to whom it is addressed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of
SchlumbergerSema.
If you are not the intended recipient, be advised that you have received
this email in error and that any use, dissemination, forwarding, printing,
or copying of this email is strictly prohibited.

If you have received this email in error please notify the
SchlumbergerSema Helpdesk by telephone on +44 (0) 121 627 5600.
_

Re: restore without missing tape

[DFrance]

Alex,

If the tape is truly "bad", first audit that tape (audit vol xxx fix=yes);
if you just want to skip past that tape, one "trick" I've used is to force
classic restore -- nqr won't skip "unavailable" tapes, classic will (or it
used to in the v 3.1 timeframe)...

To force "classic" restore, specify the filespec with a trailing /?* (or
\?*);  you can verify classic restore is running by *not* getting the
message "waiting for files from the server..." (See the Tech. Guide for v
3.1, or Admin Guide, for other parameters that force classic restore
method).

BTW, another advantage to classic restore is it will minimize tape mounts on
the TSM server -- it sorts the eligible restore files/dirs by their needed
tape mounts before sending any data (and only sends data that meets the
restore spec's -- so there is much more "think time" before any data starts
to flow.)

If all this fails (to help), read the Admin Guide topic -- "Correcting
Damaged Files" (it's two pages long); if a file was marked "damaged", and
the data had been copy pool'ed, the (offsite?) copy pool tapes will be
requested; again, since they're unavailable, classic restore will list the
vol's being skipped (in the act-log) but still process data from the
"available" tapes.

Need more help?  Copy-and-paste the error msg you are receiving, include any
relevant context (and added messages that immediately precede or follow).



Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Alexander Lazarevich
Sent: Sunday, October 27, 2002 2:25 PM
To: [EMAIL PROTECTED]
Subject: restore without missing tape


we've got adsm server 3.1 on an aix 4.3.3 machine. tape library is 3575.

if ive donw a restore of an entire filesystem, but the restore stopped due
to a tape error, and that tape is just totally dead (cant migrate anything
off of it), how do i continue the restore of other good data that isnt on
that bad tape.

i ask because im doing a restore of a 23GB filesystem, and it stopped at
7GB complaining about a bad tape. fine, but if i continue the process,
will it go on to other good tapes? or will it sit there and keep
complaining about that bad tape. how do i restore all the other good data
and avoid that bad tape?

thanks in advance!

alex
------
   Alex Lazarevich | Systems | Imaging Technology Group
   [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu
------

Re: restore hangs

[DFrance]

I assume you mean the "dsmc sched" process on the (Unix) client;  that is
the daemon used for running scheduled commands... unless you are defining
schedule on the server for doing the restore, it's not relevant (right?!).

OTOH, it sounds like maybe you *are* running the restore using a client
schedule;  for restartable (and most any other total-filesystem) restores, I
would advise running command-line client from interactive connection to the
client machine -- redirect output for logging purposes, if desired, but do
keep the session from an interactive terminal connection.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Alexander Lazarevich
Sent: Sunday, October 27, 2002 12:20 PM
To: [EMAIL PROTECTED]
Subject: Re: restore hangs


totally cool, thaks don. the restartable process is there!

one question though. the dsm client stoped and i killed that process on
the client. do i need to restart dsm on the clinet before i restart the
process on the server? i praobably do, im just asking in case.

alex

On Sun, 27 Oct 2002, DFrance wrote:

> Tapes marked unavailable usually just need to be marked available (and
> possibly checked back into the library).  I suggest setting it to
readonly,
> for now.
>
> If the msg you got is "waiting for files from the server..." that just
> indicates no-query-restore is invoked, the client will be receiving all
the
> data and is responsible to filter out data it already has, based on your
> specifications.  You probably have a restartable restore in the queue;  do
a
> "q rest" to see; if so, just run the restartable restore -- use the cmd
> "restart restore" to resume where you left off.  (This was new in 3.1, and
> it worked fine after the first PTF was installed.)
>
> Tapes can be marked unavailable if they are out of the library when the
> system needs them, and the operator fails to respond to the reply-request
to
> check-in the tape;  also, sometimes a tape mount error can cause it to get
> marked unavailable -- prevents it from being written.
>
> Don France
> Technical Architect -- Tivoli Certified Consultant
> Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
> San Jose, Ca
> (408) 257-3037
> mailto:don_france@;att.net
>
> Professional Association of Contract Employees
> (P.A.C.E. -- www.pacepros.com)
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
> Alexander Lazarevich
> Sent: Sunday, October 27, 2002 9:37 AM
> To: [EMAIL PROTECTED]
> Subject: restore hangs
>
>
> we are in major trouble.
>
> one of our fileservers is an AIX 4.3.3 running on a f50, with external
> 80-pin SCSI drives in a tower attached to a SCSI card in the f50.
>
> last friday, the SCSI card for that tower failed, and all of the
> filesystems on that tower are screwed! im so pissed. i can't mount any of
> the filesystems, it just says I/O error, and i run an fsck, but that
> doesnt fix it. i think the whole super block is totally lost.
>
> so, im trying to restore all those drives from tape. we have a 3575 tape
> library and run adsmserv 3.1 on that same AIX machine. there are 8
> filesystems that i need to restore. i started with one last night, it was
> going fine, but when i woke up this morning, it had stopped about 1/2 way
> through and complained about data unavailable to server. it only restored
> about 7GB when i know there is about 18GB on that filesystem.
>
> i tried running the dsm client again, and chose not to overwrite any data,
> but as soon as i start it, it just hangs there, doing nothing. maybe its
> still comparing all the 7GB of data that is already restored, but it
> doesnt say anything about that, it just says transfering...
>
> is this normal, or is something not working?
>
> also, i looked at the tapes in the library, and there are 2 marked as
> unavailable. those tapes were not unavailable 2 days ago!! what happened?
>
> any ideas?
>
> man, if i cant restore this data, we are so screwed.
>
> alex
> ------
>Alex Lazarevich | Systems | Imaging Technology Group
>[EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu
> ------
>

Re: restore hangs

[DFrance]

Tapes marked unavailable usually just need to be marked available (and
possibly checked back into the library).  I suggest setting it to readonly,
for now.

If the msg you got is "waiting for files from the server..." that just
indicates no-query-restore is invoked, the client will be receiving all the
data and is responsible to filter out data it already has, based on your
specifications.  You probably have a restartable restore in the queue;  do a
"q rest" to see; if so, just run the restartable restore -- use the cmd
"restart restore" to resume where you left off.  (This was new in 3.1, and
it worked fine after the first PTF was installed.)

Tapes can be marked unavailable if they are out of the library when the
system needs them, and the operator fails to respond to the reply-request to
check-in the tape;  also, sometimes a tape mount error can cause it to get
marked unavailable -- prevents it from being written.

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Alexander Lazarevich
Sent: Sunday, October 27, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: restore hangs


we are in major trouble.

one of our fileservers is an AIX 4.3.3 running on a f50, with external
80-pin SCSI drives in a tower attached to a SCSI card in the f50.

last friday, the SCSI card for that tower failed, and all of the
filesystems on that tower are screwed! im so pissed. i can't mount any of
the filesystems, it just says I/O error, and i run an fsck, but that
doesnt fix it. i think the whole super block is totally lost.

so, im trying to restore all those drives from tape. we have a 3575 tape
library and run adsmserv 3.1 on that same AIX machine. there are 8
filesystems that i need to restore. i started with one last night, it was
going fine, but when i woke up this morning, it had stopped about 1/2 way
through and complained about data unavailable to server. it only restored
about 7GB when i know there is about 18GB on that filesystem.

i tried running the dsm client again, and chose not to overwrite any data,
but as soon as i start it, it just hangs there, doing nothing. maybe its
still comparing all the 7GB of data that is already restored, but it
doesnt say anything about that, it just says transfering...

is this normal, or is something not working?

also, i looked at the tapes in the library, and there are 2 marked as
unavailable. those tapes were not unavailable 2 days ago!! what happened?

any ideas?

man, if i cant restore this data, we are so screwed.

alex
------
   Alex Lazarevich | Systems | Imaging Technology Group
   [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu
------

Re: TSM NT 4.0 Client 5.1.5.0 restore problem

[DFrance]

I'd heard that 5.1.5 vanilla release was flawed (big surprise!?!)  Maybe you
can try the first PTF (5.1.5.1), or patch level, for your situation...

Version 5 Release 1, Level 5.2  PTF
IP22546_02
(this one just released... 10/17)

There's been a long history indicating that running the base 5.1.5.0 (or
pretty much any other release level, like 4.2.2.0) has some problems -- see
the IBM sites for bulletins, wait for reports on this site, or (best) trial
certify for your site.  Ultimately, you gotta go for support, PMR.


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
David Longo
Sent: Tuesday, October 22, 2002 3:14 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM NT 4.0 Client 5.1.5.0 restore problem


No compression used on clients.

David Longo

>>> [EMAIL PROTECTED] 10/22/02 03:49PM >>>
Was the data backed up using compression?  If so, the q ses shows
compressed
data.

-Original Message-
From: David Longo [mailto:David.Longo@;HEALTH-FIRST.ORG]
Sent: October 22, 2002 1:57 PM
To: [EMAIL PROTECTED]
Subject: TSM NT 4.0 Client 5.1.5.0 restore problem

I have an NT 4.0 SP6 client with a C drive as NTFS.  4GB disk 92%
full.
I had a restore problem with this machine when I had 4.2.2.0 client,
which was APAR IC33683 that was fixed with new 5.1.5.0.  I rebuilt
the machine with NT and installed 5.1.5.0 client.  It bombed out with
restore being out of disk space.  Per the "q ses" on the 4.2.2.10
server
I had only restored about 2.7GB.

Output from dsmerror.log below.  (I was wondering if the fact that I
install
a 5.1.5.0 client and then try a full restore of unit that includes a
4.2.2.0
client is part of the problem??)Just log files that are about 20MB in
size
from an application.
---
10/17/2002 17:36:15 ANS4009E Error processing
'\\hfscmhl7mpd\c$\SCMLogs\Backload_logs\0921-2_HL7MGR_PROD-2.log':
disk
full condition
10/17/2002 17:41:41 ANS4009E Error processing
'\\hfscmhl7mpd\c$\SCMLogs\Backload_logs\0921-2_HL7MGR_PROD-2.log':
disk
full condition
10/17/2002 17:44:05 ANS4009E Error processing
'\\hfscmhl7mpd\c$\SCMLogs\Backload_logs\0922-1_HL7MGR_PROD-1.log':
disk
full condition
10/17/2002 17:46:09 ANS1005E TCP/IP read error on socket = 304, errno
=
10054, reason : 'Unknown error'.
10/17/2002 17:46:09 ANS1301E Server detected system error
--

Thanks,


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


"MMS " made the following
 annotations on 10/22/2002 02:58:28 PM

--
This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.
If
you receive this message in error, please immediately delete it and
all
copies of it from your system, destroy any hard copies of it, and
notify the
sender.  You must not, directly or indirectly, use, disclose,
distribute,
print, or copy any part of this message if you are not the intended
recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed
in
this message are solely those of the individual sender, except (1)
where the
message states such views or opinions are on behalf of a particular
entity;
and (2) the sender is authorized by the entity to give such views or
opinions.


==


"MMS " made the following
 annotations on 10/22/2002 04:15:13 PM

--
This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify the
sender.  You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient.  Health First reserves the right to monitor all e-mail
communications through its networks.  Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where the
message states such views or opinions are on behalf of a particular entity;
and (2) the sender is authorized by the entity to give such views or
opinions.

Re: TSM 5.1.5.1

[DFrance]

Geoff,

Yep... there have been several other reports about 5.1.5.1 -- looks like the
oven was still not hot enough for this one... it's still not quite fully
cooked.  We knew base 5.1.5.0 was flawed from IBM bulletins;  didn't know
the full extent of the issue, though.

Last I checked, 5.1.1.6 was the lowest level (of 5.1) that was ready for
production; looks like it is also the highest level.

Sorry to learn of your difficulty; please keep us posted on your progress!
(I am working with a customer and we still plan to upgrade 4.2.2.12 to
5.1.1.6, in a couple weeks!)


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Gill, Geoffrey L.
Sent: Saturday, October 26, 2002 7:32 PM
To: [EMAIL PROTECTED]
Subject: TSM 5.1.5.1


After upgrading to 5.1.5.1 on AIX 4.3.3 I've been having a ton of misses and
failed reports, not to mention some as In-Progress that are not and
completed. Has anyone else seen this phenomenon on their system? Last night
I had 15 failed 25 missed and 6 still show In-Progress.

On the ones reporting failed I see this error on the client log yet the
backup did complete.

10/26/2002 00:07:37 ANS1301E Server detected system error

10/26/2002 00:07:37 --- SCHEDULEREC OBJECT END CLIENT_M-F 10/25/2002
21:00:00
10/26/2002 00:07:37 ANS1512E Scheduled event 'CLIENT_M-F' failed.  Return
code = 4.


On the ones that are missed, they are just missed, but did complete the
previous day, and show in the client log the next scheduled backup. So this
doesn't make any sense either. The server log shows this on one of the
nodes. Looks like it contacted it then just ended up reporting missed. This
schedule starts at 9PM and runs for 2 hours.

10/25/02 22:59:59 ANR2561I Schedule prompter contacting CP-ITS-TAX01

   (session 6587) to start a scheduled operation.

10/25/02 23:00:00 ANR0406I Session 6588 started for node CP-ITS-TAX01

   (WinNT) (Tcp/Ip 139.121.18.204(1089)).

10/25/02 23:00:05 ANR2578W Schedule CLIENT_M-F in domain NT_DOM for node

   CP-ITS-TAX01 has missed its scheduled start up
window.
Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154

Re: Directories written in the wrong pool, although using dirmc option

[DFrance]

I share Mark's sentiments... on TWO points:
- if this was resolved, for both users in the discussion, let's share the
results;
- if DIRMC is no longer relevant, I'd sure like to know why!  Win2K is
becoming ever more prevalent, and most data center customers go wild with
lots of permission groups (causing the ACL's to grow too large to be
contained in the TSM db -- I used to think!)

As far as I can tell, DIRMC is still a very significant issue, most notably
with Win2K servers using typical data center permissions definitions.  If
you create the disk pool and management class, and see it get populated with
any data -- that seems pretty conclusive, to me.

The question that's left is whether a given restore will be just as fast
(NQR or classic) since dir's are now more readily backed up -- and, if
that's true, what about point-it-time restores that would get a mix of dir's
restored, to match the state of a time further back than the most recent
backup?!?


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Mark D. Rodriguez
Sent: Saturday, October 26, 2002 12:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Directories written in the wrong pool, although using dirmc
option


Andrew Raibeck wrote:

>Responded to offline.
>
>Andy Raibeck
>IBM Software Group
>Tivoli Storage Manager Client Development
>Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
>Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
>
>The only dumb question is the one that goes unasked.
>The command line is your friend.
>"Good enough" is the enemy of excellence.
>
>
>
Andy,

I certainly appreciate you being on this list and I look at all of your
posts.  I am not sure why you decided to take a couple of these off-line
 I was interested in following this discussion, but it is certainly upto
you to decide.

Anyway on another note, the IBM/Tivoli education material has been
stating for sometime now that the DIRMC attribute is effectively
obsolete.  The material states that all directory information is kept in
the DB now.  The only reason I used DIRMC in the past was to store my
directories on a disk based storage pool to improve restore performance.
 I have now real way of verifying this information.  I guess I just
beleived the material, as such I no longer bother with this attribute
and I have not had any noticable problem.  Can you please clarify this
for us?

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.


===
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE

===

Re: adsm.org unusable

[DFrance]

Fantastic... this is excellent resolution -- the old screen is still there,
just gotta know its new address!

Thanks,
Don

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Nelson, Doug
Sent: Thursday, October 24, 2002 7:15 PM
To: [EMAIL PROTECTED]
Subject: Re: adsm.org unusable


Try http://search.adsm.org/   it works for me. I agree about the home page
(adsm.org).

Douglas C. Nelson
Distributed Computing Consultant
Alltel Information Services
Chittenden Data Center
2 Burlington Square
Burlington, Vt. 05401
802-660-2336



-Original Message-
From: Kai Hintze [mailto:kai.hintze@;ALBERTSONS.COM]
Sent: Thursday, October 24, 2002 7:16 PM
To: [EMAIL PROTECTED]
Subject: adsm.org unusable


What happened to adsm.org? I tried to go and look for something in the
archives but they weren't there! Instead the site was some funky discussion
board with several columns.

The meat of the board was the middle column. But the column was too narrow
so I couldn't see an entire message without scrolling left and right, but
the scroll bar was two screens below the message so I couldn't ever read an
entire message.

The right hand column was a poll that didn't let me participate.

The left hand column invited me to log in, and had numerous resource
lists--one of which was the archives, but I STILL CAN'T READ THEM BECAUSE
THE COLUMN IS TOO NARROW! And I DON'T want yet another place to log in.

Please, _please_, PLEASE give me back the archives.

- Kai

Re: adsm.org unusable

[DFrance]

Halleluiah!!!  I have ALL these same complaints, too;  I hope our friend in
Virginia sees and responds to this!  It's a great service he does, but it
needs to be made usable, again.,,, nice experiment, now let's fix it,
please?!?


Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france@;att.net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Kai Hintze
Sent: Thursday, October 24, 2002 6:16 PM
To: [EMAIL PROTECTED]
Subject: adsm.org unusable


What happened to adsm.org? I tried to go and look for something in the
archives but they weren't there! Instead the site was some funky discussion
board with several columns.

The meat of the board was the middle column. But the column was too narrow
so I couldn't see an entire message without scrolling left and right, but
the scroll bar was two screens below the message so I couldn't ever read an
entire message.

The right hand column was a poll that didn't let me participate.

The left hand column invited me to log in, and had numerous resource
lists--one of which was the archives, but I STILL CAN'T READ THEM BECAUSE
THE COLUMN IS TOO NARROW! And I DON'T want yet another place to log in.

Please, _please_, PLEASE give me back the archives.

- Kai