TSM and 3590E Tapes

2001-07-10 Thread Louis Wiesemann

We are running TSM 3.7.3 on OS/390 2.8.  We are getting ready to upgrade our tape 
drives from model B's to model E's.  IBM says that the upgraded drives will read the 
old tapes just fine, but will write them at the new density.  I am unable to determine 
what, if anything, I need to do to configure TSM for this change.  The deviceclasses 
only define 3590 with no model information.  The capacity information for the old 
density tapes will not be correct when it starts writing at the new density.  Is this 
something that TSM will adjust automatically or do I need to reset it somehow?

Are there any problems I'm not thinking of that might bite us with some tapes at the 
old density and some at the new, once TSM starts writing tapes with the upgraded 
drives?  

Anything, else I should be looking at.

Thanks for any advice.



Louis J. Wiesemann 502-852-8952


 

The Daily Word For Reflection is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://www.cin.org:81/guest/RemoteListSummary/dailywordtoday




Re: TSM and 3590E Tapes

2001-07-10 Thread Louis Wiesemann

Thanks.  I just sent an email query for the archives.  I had been trying to seach them 
from the web, but had no luck.  The LSOFT pages show a web archive link at:

vm.marist.edu/htbin/wa

but when I try to link to it I can't get connected.  Is there really a web interface 
for ADSM-L archives?



Louis J. Wiesemann 502-852-8952


 

The Daily Word For Reflection is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://www.cin.org:81/guest/RemoteListSummary/dailywordtoday


 [EMAIL PROTECTED] 07/10/01 10:55AM 
Definitely go thru the archives on this one...there is alot of good
information out there
Also review this email



Re: TSM and 3590E Tapes

2001-07-10 Thread Louis Wiesemann

Thanks.  One thing I'm not clear on is whether I need to set the old B tapes to 
readonly or can I let TSM do it for me.  IBM says that the new drives will not write 
over a non-scratch tape in the old format.  When TSM calls for an output tape and the 
drive detects the old format will it genrate an error that causes TSM to mark the tape 
readonly and then mount a scratch tape?  Or should I set the B tapes to readonly 
before bringing TSM up with the new drives?

Thanks also to those who pointed me to the online archives.



Louis J. Wiesemann 502-852-8952


 

The Daily Word For Reflection is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://www.cin.org:81/guest/RemoteListSummary/dailywordtoday


 John Marquart [EMAIL PROTECTED] 07/10/01 12:24PM 
The archive is at www.adsm.org.   not sure where the vm.marist.edu pages
point.

in case you haven't gotten your answer - there is no problem w/ the
upgrade.  as long as your drivers are current - and you have space in your
library - you should be ok.   

The biggest gotcha is that your old B tapes will all become readonly -
because the E drive can't write the 128 track B format.  All your new
tapes written in E (256 track) format will reflect the proper
capacity.  If you are running mostly backups - and have a constant stream
of migrations / reclamations -  you can probably leave things alone.  if
your data is pretty static once it hits tape - then you might want to do
move datas on those tapes.

-john

 



Re: Unable to init TCP/IP driver in OS390 2.10

2001-05-08 Thread Louis Wiesemann

This sounds like what we saw when converting to 2.8 last year (are just now working on 
2.10).  I think it has to do with the telling TSM which TCPIP you are using, IBM's or 
something else.  There should be an ANRDDDEF member in the SYS1.SAMPLIB for R10.  It 
has comments describing how to setup the job for your environment.  Then I think you 
need to rebuild your DSMSERV module.  There should be some doc on this in the TSM 
section of the upgrade information as well as in the ANRDDDEF.



Louis J. Wiesemann 502-852-8952


 

The Daily Word For Reflection is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 05/07/01 04:13PM 
We just upgraded our development MVS to OS390 2.10. Since then, ADSM
generates this error:
ANR5092E Unable to initialized TCP/IP driver - error creating acceptor
socket.

TCP/IP is up and running, and still under the same name that it's always
had.
We are running ADSM Version 3, Release 1, Level 2.50.
Would this be a release incompatibility issue (we're aware that this release
of ADSM is no longer supported), between ADSM and the new OS390?
Any other ideas on what may cause this error?
Thanks, in advance,

Peter Glass
Distributed Storage Management (DSM)
Wells Fargo Services Company
 * 612-667-0086  * 866-249-8568
 * [EMAIL PROTECTED] 




Re: Can't Get New MGMTCLASS to Work

2001-03-29 Thread Louis Wiesemann

The select output shows that all the files being backed up, even as recently as last 
night, are still using the STANDARD mgmtclass.  Below is the configuration information 
you asked for in your note.

Thanks for any help.
_
 
adsm q node fpserv1 f=d

 Node Name: FPSERV1
  Platform: NetWare
   Client OS Level: 5.0
Client Version: Version 4, Release 1, Level 1.0
Policy Domain Name: IT-LAN
 Last Access Date/Time: 03/29/2001 02:56:03
Days Since Last Access: 1
Password Set Date/Time: 03/26/2001 13:47:38
   Days Since Password Set: 3
 Invalid Sign-on Count: 0
   Locked?: No
   Contact: [EMAIL PROTECTED]
   Compression: Client
   Archive Delete Allowed?: Yes
Backup Delete Allowed?: No
Registration Date/Time: 08/12/1998 18:15:52
 Registering Administrator: DSMPDL
Last Communication Method Used: BPX-Tcp/Ip
   Bytes Received Last Session: 9,164
   Bytes Sent Last Session: 131.83 M
  Duration of Last Session: 6,175.22
   Pct. Idle Wait Last Session: 55.66
  Pct. Comm. Wait Last Session: 0.09
  Pct. Media Wait Last Session: 0.00
 Optionset: UOFLOPT1
   URL:
 Node Type: Client
Password Expiration Period:
 Keep Mount Point?: No
  Maximum Mount Points Allowed: 1

adsm q mgmtclass it-lan active collocate f=d

Policy Domain Name: IT-LAN
   Policy Set Name: ACTIVE
   Mgmt Class Name: COLLOCATE
  Default Mgmt Class ?: No
   Description: Collocate IT-LAN Filespaces Mgmt Class, Primary
 Policy, IT-LAN Domain
Space Management Technique: None
   Auto-Migrate on Non-Use: 0
Migration Requires Backup?: No
 Migration Destination: SPACEMGPOOL
Last Update by (administrator): LJWIES1
 Last Update Date/Time: 03/29/2001 09:03:17
  Managing profile:

adsm q mgmtclass it-lan active standard f=d

Policy Domain Name: IT-LAN
   Policy Set Name: ACTIVE
   Mgmt Class Name: STANDARD
  Default Mgmt Class ?: Yes
   Description: Standard Mgmt Class, Primary Policy, IT-LAN
 Domain
Space Management Technique: None
   Auto-Migrate on Non-Use: 0
Migration Requires Backup?: Yes
 Migration Destination: SPACEMGPOOL
Last Update by (administrator): LJWIES1
 Last Update Date/Time: 03/29/2001 09:03:18
  Managing profile:


*  client options file for Tivoli Novell NetWare client

 
TCPSERVERADDRESS 136.165.1.12
TCPPORT  1500
*  ---

  NODENAME  fpserv1

*  NetWare general excludes
*  -
 EXCLUDE  sys:\system\secaudit.log
 EXCLUDE  sys:\system\events.log
 EXCLUDE  sys:\system\system.log
 EXCLUDE  sys:\system\btrieve.trn
 EXCLUDE  SYS:\system\tsa\err$hst.*
 EXCLUDE  sys:\system\tsa\err$log.*
 EXCLUDE  sys:\system\tsa\skip$log.*
 EXCLUDE  sys:\system\tsa\tsa$temp.*
 EXCLUDE  sys:\system\sys$log.err
 EXCLUDE  sys:\_swap_.mem
 EXCLUDE  sys:\vol$log.err
 EXCLUDE  sys:\tts$log.err
 EXCLUDE  SYS:\system\CSLIB\LOGS\SMLOGS\*
 INCLUDE  USR:*   COLLOCATE

*  NetWare Screen option
*  ---
*  The following option instructs the NetWare client to destroy
*  the TSM screen when quitting the dsmc program.
*
 NWWAIT NO

 PASSWORDAccess  GENERATE

*  UofL options  **
processor 200
subdir yes
___
 [EMAIL PROTECTED] 03/28/01 06:10PM 
Run a "select * from backups where node_name='NODENAME'" from
the TSM administrative prompt.  Find out what management class is
being used.  If the management class is DEFAULT, then either the include
statement doesn't match the objects being backed up, the management class
does not exists in the active policy for the nodes domain.  The management
class may not exist because there was a syntax error in the include
statement, the policy was not activated, or the node does not belong to the
domain where you put the new mgmtclass.

For trouble shooting post the following.
q node NODENAME  (replace nodename with the appropriate value)
q mgmtclass DOMAIN active (replace domain with the domain from q node)
dsm.opt (from the node having the problem)


James Thompson



Can't Get New MGMTCLASS to Work

2001-03-28 Thread Louis Wiesemann

We are running 3.7.3 server on OS/390.  On one of our NetWare servers running client 
level 4.1.1 we wanted to start collocating a filespace we were not collocating before. 
 I defined a new management class and backup copygroup for it.  I pointed the 
copygroup to new storage pools (a disk pool migrating to a tape pool).  I formatted 
and defined volumes for the disk pool.  I activated the policyset with the new 
management class.  I had the NetWare people update the backup to use an include naming 
the new management class.  But when the backup runs it does not use the new management 
class.  Nothing gets written to the new storage pools.  The logs for the backup don't 
show any problems that I can relate to this.  I have reviewed the documentation and 
the list archives but have not found anything additional I need to do.  Am I missing 
something?  Does anyone have suggestions for where to look.

Thanks for any ideas.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Re: ANS1301E Error

2001-03-26 Thread Louis Wiesemann

It did not have a max size set on the pool, but the pool was full enough that it could 
not fit 5G more into it.   This apparently is treated like a file size limit and tries 
to dump the large file directly to tape (at least when the storage pool is not full 
enough to trip the migration limits).

Thanks



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 03/25/01 01:49PM 
Hey Louis,

try doing a Q STGPOOL xx F=D on your disk pool and see what the MAXIMUM
SIZE THRESHOLD is set to. It might be that you disk pool only accepts files
to a maximum of say, 2 GB in size and the Oracle file are trying to backup
looks to be about 5 GB plus.

Rik



ANS1301E Error

2001-03-23 Thread Louis Wiesemann

A client is reporting the error below trying to backup a file.  The ANS1301E error is 
vaguely worded "server detected system error".  I can find no errors in my TSM 3.7.3 
server log or my OS/390 system log during the time of this backup attempt.  Since it 
is an "ANS" message, is this error really trying to tell me that there was an error on 
the clients's system?

Thanks

Normal File-- 5,767,172,096 /scratch/backup/oracle/data/wkudb/wkudb_ts.dbf  ** 
Unsuccessful **
ANS1114I Waiting for mount of offline media.
Retry # 1  Normal File-- 5,767,172,096 
/scratch/backup/oracle/data/wkudb/wkudb_ts.dbf  ** Unsuccessful **
ANS1114I Waiting for mount of offline media.
Retry # 2  Normal File-- 5,767,172,096 
/scratch/backup/oracle/data/wkudb/wkudb_ts.dbf  ** Unsuccessful **
ANS1114I Waiting for mount of offline media.
ANS1228E Sending of object '/scratch/backup/oracle/data/wkudb/wkudb_ts.dbf' failed
ANS1301E Server detected system error

ANS1804E Selective Backup processing of 'wkudb_ts.dbf' finished with failures.





Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Re: ANS1301E Error

2001-03-23 Thread Louis Wiesemann

Thanks for your suggestions.

Yes, I had available drives.  The only other process using a drive was a DB backup.

Yes, the disk pool is shared and was full enough that the 5G would not fit, so that 
explains the tape mount attempt.  But I can still find no reason for the job to fail.  
We do have plenty of scratch tapes available.  There were no errors related to tape 
problems or other problems during the 4 to 5 minutes this backup was trying to run.  I 
have forced migration of the storage pool.  It was only about half full, so had not 
triggered a migration yet.  The backup seems to be running to the storage pool ok.

This pool is not collocated, but we have seen backups wait for a tape being used by 
migration when the storage pool was migrating for a collocated pool.

The last comment in your note 

you allow client backups to tape drives (a setting I believe...)?

does trigger an idea.  We have recently seen a problem with some Novell backups of 
large files that tried to go to tape.  They appeared to fail because the MAXNUMMP 
setting apparently came in with our upgrade to 3.7, but existing nodes got set with 
MAXNUMMP=0 instead of the default of 1.  They failed with ANS1312E error that clearly 
referenced the MAXNUMMP setting.  I'm wondering if this problem is the Unix client 
version.  This client is an existing AIX client that also was left with the MAXNUMMP=0 
after the upgrade.





Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 03/23/01 10:10AM 
Do you have available tape drives at that time (it appears that your
are going straight to tape). IF you are not going straight to tape, the DISK

area that you are trying to backup to can't hold your 5+GB file.
Mind you, that if the DISK pool is shared...it could be some percent full
from other
backups? Another thought..colocation on?...tape in use by another
process (it shouldn't matter...but...)...available scratch tapes?
FYI Thanks Tim
you allow client backups to tape drives (a setting I believe...)?





 



Re: ANS1301E Error

2001-03-23 Thread Louis Wiesemann

Thanks, I had looked at these and reset the Novell nodes, just yesterday, I didn't get 
around to the Unix ones then or might have avoided this problem today.  I did reset 
the MAXNUMMP for this node (and my other old nodes), but as I said, I had already 
migrated the pool.  So, I will have to do a separate test.

On a related question, when I queried some of these and reset some yesterday  I 
noticed some nodes were set to "unlimited", like your example.  I looked at the 
documentation and played around with UPDATE some, but could not figure out how to set 
it to unlimited.  I don't think I need it but I wondered how to set it and why some 
nodes already had it set that way. 

What should they be set to?  I have been setting them to 1 per the default, but know 
that the defaults are not always what is the best. 



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 03/23/01 11:52AM 
Yes, do a q node f=d...for the node in question...max mount points
allowed...

  Maximum Mount Points Allowed: Unlimited




 



Re: I cant delete a backupset . . .

2001-02-12 Thread Louis Wiesemann

For what it is worth, we are at 3.7.3 on an OS/390 server.  The automatic delete of 
the the backupsets when their retention period is exceeded does not happen.  But a 
DELETE BACKUPSET command did work to delete the backupset from the VOLHIST and allow 
the tape to be scratched.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 02/09/01 07:24PM 
There is a known APAR for this;  it's fixed in 3.7.4 (for 3.7),,, don't know
when it's fixed for 4.1.  

Hope this helps.

Don France

Technical Architect - Unix Engineering/P.A.C.E.
San Jose, CA
mailto:[EMAIL PROTECTED] 
PACE - http://www.pacepros.com 
Bus-Ph:   (408) 257-3037



Backing Up Novell Directory Structure

2001-02-06 Thread Louis Wiesemann

I have just been made aware that I should be backing up the directory structure for my 
Novell servers separately and I have few questions.  I have reviewed the documentation 
about the dirmc option.  

Is there some way to calculate the size of the storage pool I should use for this 
management class?  I have no idea how large to make it.  I don't plan to define a next 
pool because I want it to stay on disk.

Also, how is this affected by previous backups that have been run without the dirmc 
option?  Will a new incremental backup with the option backup the entire structure to 
the new storage pool or will some of it still be retained with the previous backups.

Is there somewhere besides the Admin Guide, Admin Reference, and Novell client manuals 
that I can find more documentation on this?

Thanks for any help.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Backup Retention Period

2001-01-11 Thread Louis Wiesemann

We are running TSM 3.7.3 on OS/390 2.8.  I have a request from my boss to temporarily 
extend a retention period for some server backups.  I know where I can reset the 
retention information, but it was not clear to me if this would be retroactive for 
existing backups or just affect new backups.  The intention is to save some backups 
that are about to expire for a little while longer since some customers have reported 
they did not get all of their files back from a large restore we had to do.

Any other suggestions on how to accomplish this?

Thanks



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Backupsets in OS/390 TSM Server

2001-01-08 Thread Louis Wiesemann

I'm just wondering if anyone has any real life experiences to relate about generating 
TSM backupsets under TSM 3.7.3 running on OS/390.  

We recently had a server failure that took us awhile to restore, for various reasons.  
We are looking at possibly generating backupsets on some sort of regular basis for the 
more critical servers.   We hope to reduce the number of tape mounts required for 
these large restores.  So, we are wondering what kind of real life experiences people 
have seen for generating backupsets and/or using them for restores.  We are using tape 
robot with 3590 tapes.

Any experiences with this on other platforms might also be helpful. 

Thanks,



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Moving a Node to Another Domain

2001-01-03 Thread Louis Wiesemann

I am running TSM 3.7.3 on OS/390 2.8.  I have a set of nodes defined that have already 
run some backups, but now I would like to place them in a separate domain.  After 
looking at the documentation, the only way I can see to do this is to EXPORT and then 
IMPORT them back into the new domain.  Am I missing something?

Thanks



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Re: Moving a Node to Another Domain

2001-01-03 Thread Louis Wiesemann

Thanks for the quick responses referencing  the UPDATE NODE command.  I have 
successfully migrated my nodes.





Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Excluding Files on Restore

2000-12-20 Thread Louis Wiesemann

Is there a way to exclude files when restoring?  All of the documentation describes 
excluding on backups, but I could find nothing about excluding on restores.  We're 
trying to restore a volume (NetWare TSM client 3.1.08), but it keeps hitting a certain 
file and ending the restore.  We would like to run the restore excluding this 
directory for now without having to issue restores for each directory individually.  
Thanks for any help.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Re: Excluding Files on Restore

2000-12-20 Thread Louis Wiesemann

Thanks.  Yes, we thought of this, but the long file name that is the problem was 
unable to be created on the NetWare server.  Our NetWare guy played with this for 
awhile.  At this point we're not real sure how the file got backed up but it is still 
causing us a problem.

At this time we are running a restore of the particular directory specifically 
including the files we want restored and leaving out the bad file name. Fortunately, a 
large number of files were restored there before it hit the problem.  Then we hope to 
run an incremental backup against the directory to force TSM  to mark the bad file as 
inactive.  Then we will rerun the general restore which should not try  to restore the 
inactive file again.

For your information, Tivoli did not have any hits on this problem.  They liked our 
idea for restore-backup-restore.  They suggested upgrading the NetWare client as a 
next attempt and if that did not work to trace the problem for them to diagnose 
further. 

Thanks for the suggestions I have received on this problem.

 [EMAIL PROTECTED] 12/20/00 17:43 PM 
I would have to look into that, but for now a quick workaround is to
create a file with the exact name of the file you do not want restored in
the directory where that file lives, and then have TSM clinet not
overwrite existing files.  Durring the prepar phase, this file will be
disqualifed for restore operations, and thus skiped.

Keith Davey


On Wed, 20 Dec 2000, Louis Wiesemann wrote:

 Is there a way to exclude files when restoring?  All of the documentation describes 
excluding on backups, but I could find nothing about excluding on restores.  We're 
trying to restore a volume (NetWare TSM client 3.1.08), but it keeps hitting a 
certain file and ending the restore.  We would like to run the restoe excluding this 
directory for now without having to issue restores for each directory individually.  
Thanks for any help.

 


 Louis J. Wiesemann 502-852-8952

 


 The "Daily Word For Reflection" is a free service and a non-discussion
 list intended primarily to allow personal reflection on the Word of God.

 SUBSCRIBE/UNSUBSCRIBE at:

http://monica.cin.org:81/guest/RemoteListSummary/daily_word
 




No Subject

2000-12-20 Thread Louis Wiesemann

What determines that a restore job will be "restartable"?  I've looked in both the 
server and client manuals but all I have found are instructions for restarting or 
querying restartable restores.  The online help for the client had some information 
about options that would make a restore non-restartable, but we thought we had met the 
requirements and the restores still do not show up as restartable.  I queried the list 
for "restartable" and found some information, but nothing specific.  If you can point 
me to the information about this I would appreciate it.

Thanks



Restore Tape Drive Usage

2000-12-18 Thread Louis Wiesemann

We are running TSM 3.7.3.0 and trying to complete a large restore from over the 
weekend which had to be restarted last night due to a hardware problem.  It  is my 
understanding that restore requests will only use one tape drive for mounting restore 
volumes.  My boss is asking if there is a way to make the restore use more of the 
drives.  I've already suggested breaking up the restore into multiple commands.  I was 
unable to find documentation that each restore session would only use one drive.   Can 
anyone verify this (for my boss) or tell me how to make a restore session use more 
than one drive at a time, if possible.

Thanks for any suggestions.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Restore Throughput

2000-12-18 Thread Louis Wiesemann

I'm just looking for any guesstimates anyone might have for the throughput we might 
"expect" to see restoring a Netware 3.1.08 client with a TSM 3.7.3.0 OS/390 server.  
This is over a 100M ethernet with 3490 tape robot on the server.  We have split the 
restore up over 4 sessions and have disabled any other TSM processing while we run the 
restore.

We are seeing about 1.2G an hour actual data being restored.  Can anyone say whether 
this is about what we should expect?  I have been in contact with Tivoli and tuned the 
client and server options per their instructions.  I was wondering if anyone had any 
idea if this seems a reasonable rate.

Thanks for any input.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Re: Groupwise on Netware

2000-12-08 Thread Louis Wiesemann

This is from our GroupWise people:


Our GW is running on NW5.0 SP5.

Yes, we back up all the GW boxen with agents running. I haven't checked the logs that 
closely but suspect we're not getting open files. We're investigating reimplementing 
St. Bernard OFM product at the moment to overcome that. Other than open files, I don't 
think we have seen any issues.

I just did go and check a few of the logs, and it seems in fact we are getting good 
backups. Since there's not a lot of client activity during backups, the user databases 
are closed, or open for short periods, and get backed up. If open files are retried at 
all, they would probably get caught the next try. There's naturally a lot of both new 
and expired message files in the transaction areas, and I saw no problems there.

Another tidbit. I misspoke slightly earlier, or just mis-assumed. Below is a sample of 
the failures we see. Apparently retries are not attempted on open files.

12/08/2000 02:28:23 ANS1228E Sending of object 'MAIL:/POB1/OFMSG/MSG6.DB' failed
12/08/2000 02:28:23 ANS4037E File 'MAIL:/POB1/OFMSG/MSG6.DB' changed during 
processing.  File skipped.
12/08/2000 02:51:23 ANS1228E Sending of object 'MAIL:/POB1/OFMSG/MSG8.DB' failed
12/08/2000 02:51:23 ANS4037E File 'MAIL:/POB1/OFMSG/MSG8.DB' changed during 
processing.  File skipped.
12/08/2000 03:57:14 ANS1802E Incremental backup of 'MAIL:' finished with 2 failure
_




Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 12/04/00 10:04AM 
I am interested to know if anyone is using TSM to backup Groupwise running
on Novell Netware.  If you are backing up Groupwise, are you using the
standard TSM backup/archive client and are there any issues regarding
recovery if you do the backups while the mail system is up?



Re: The TCP window size-errors after installing TSM 4.11 ?

2000-11-27 Thread Louis Wiesemann

We started getting these on our OS/390 server when issuing commands from our TSO admin 
client after upgrading the server from 3.1.2.50 to 3.7.3.  Support indicated that it 
was not a real problem, just a nuisance message.  They also told us that it was just 
an issue for the TSO client that they had not gotten around to fixing yet, but you 
appear to be getting it in a different environment.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 11/27/00 09:06AM 
Hello

I get a lot of error-messages like:

"11/27/2000 14:11:05 The TCP window size 64K is not supported by your
system. It will be set to the allowed size - 63K."
"11/27/2000 14:16:03 The TCP window size 64K is not supported by your
system. It will be set to the allowed size - 63K."

They have started to appear efter I Upgraded the clients on some NT4
servers from ADSM 3.1.xx to TSM 4.11.

Im sorry to say - but I don't know what it means.
I havn't changed anything I can come to think of and are still using the
same Opt-files as I were before upgrading.

Where do I go on finding the answer to this ?


Best regards

Gunnar




Gunnar Uhr
IT-Service
KAROLINSKA HOSPITAL
171 76  STOCKHOLM  e-mail  [EMAIL PROTECTED] 
SWEDEN



Looping Access Errors

2000-11-15 Thread Louis Wiesemann

We have seen this problem a couple of times now and were wondering if anyone has any 
suggestions for an easy way to deal with it.  We have seen someone who is not a 
registered node on our OS/390 TSM 3.7.3 server attempt to access the server with a 
client.  Of course, they get rejected as an invalid node, but they apparently have a 
poorly designed automated process which repeatedly retries the attempt.  We have had 
to determine who it is based on their IP address and try to contact them about 
stopping their process.

It is similar to what we have seen when a registered NT node gets their password out 
of sync and continues to generate repeated access errors.  We can lock those nodes 
until they correct the problem, but we can't lock a node that is not defined.  Well, I 
assume I can't; I didn't actually try it.

It would be nice to have some way to control these repeated non-registered access 
errors from the server side as well.

Thanks for any ideas.  





Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 




Re: Migrating from ADSM to TSM

2000-10-06 Thread Louis Wiesemann

I am also working on the upgrade to TSM.  Can anyone give more specific information 
about how long I might expect the UPGRADEDB to take?  I only have an 8G database, but 
some other database processes I have used took many many hours.  It would be nice to 
have some idea how long this might take.

Thanks,

p.s. I am cross posting this to ADSM-L but wanted to ask here since there was already 
discussion on IBM-MAIN.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 10/06/00 07:07AM 
P ADSM
add parm='/upgradedb' in proc ADSM
S ADSM
wait for message : (it can be long for 30
gigas)



Re: Audit DB - Duration

2000-08-01 Thread Louis Wiesemann

The last time I tried this (on ADSM v3.1.2.40 with about a 6G DB) it ran for a day and 
a half over a weekend before I canceled it.  This was on a 9672-R51 with 512M memory.



Louis J. Wiesemann 502-852-8952


 

The "Daily Word For Reflection" is a free service and a non-discussion 
list intended primarily to allow personal reflection on the Word of God.

SUBSCRIBE/UNSUBSCRIBE at: 

   http://monica.cin.org:81/guest/RemoteListSummary/daily_word 


 [EMAIL PROTECTED] 08/01/00 02:42PM 
Could anyone have an idea as to how long the 'dsmserv audit DB fix=yes'
takes
to run?  Last I heard was and hour per GB of DB.

The TSM server is V3.7.2 on an AIX SP2 node 9076 (wide) dual processor
200Mhz, 2GB memory.

Thanks,
Jerry Siciliano