Re: Thoughts on really old clients and newer servers...
This is a big problem for us at Oxford and we are pretty cautious in our approach to rolling out new client software. There is a clear case to use the latest client code when there for new platform support. It is much less clear that persuading people who are happy and working well on the old version that life will be better if they use new code. It has been our experience that new is not always better ... An example (I am almost, but not quite ashamed to admit) is that on my Solaris workstation I am using 3.1.0.7. A great vintage and it is working well will TSM 4.1 server. Ian (my nice colleague) has a brand new Solaris workstation and is running a 4.1 flavour - sadly, his scheduler has died several times in the last two weeks with no clues. A recent PMR has highlighted that common code in one of the 4.1 versions (we saw the problem first at AIX) has memory leaks. It is difficult. What we really need to know is why the 3.1 client (or even earlier) is not actually going to work with later server versions? And is this really true for all older platforms? As well, not all our users can afford new kit, new versions of OS and gain a natural opportunity to upgrade to the latest TSM. Another issue I am not very comfortable with is releasing client code which is more in advance than the server code - again, the technical issues relating to this would be appreciated. What policy do others have on this? Regards, Sheelagh -- Sheelagh Treweek Oxford University Computing Services Email: [EMAIL PROTECTED] Phone: +44 (0)1865 273205 Fax:-273275 +-+ | http://tsm-symposium.oucs.ox.ac.uk/ OXFORD 20/21 September 2001 | | REQUIREMENTS http://tsm-symposium.oucs.ox.ac.uk/requirements.html | +-+
3rd copy of dbvol on other Volumegroup
Hi all, Im having 2 dbvolume copies on same VG called tsmvg. Im intrsted in keeping the third copy of the DBvol in rootvg instead in TSMvg . My view in this is to recover latest dbvolume from rootvg incase of TSMvg corruption. Can i keep 3rd copy on rootvg. if so, please let me know the steps involed. Help in this regard is highly appriciated. THanks and regards sreekumar.
SV: TSM Win2K 4.2.0 client scheduler problems
I have the excact same experience - and have found no other solution than to go back to TSM v4.1 lev. 2.19. Then the problem was gone. Server: TSM v4.1 lev 1.0 on OS/390 Client: Windows NT 4.0, SP6 Henrik Bach Gravesen Jyske Bank A/S, Denmark [EMAIL PROTECTED] A user of mine is using the TSM Win2K 4.2.0 client acceptor service to manage the client scheduler. The acceptor service wakes the scheduler every 12 hours and starts the scheduled backup with no problems. All is well except that she is getting the error code 4099 in the application event log every time the scheduler wakes up (every 12 hours). In dsmerrorlog, SessOpen: Error 137 from signon authentication (3 times) Password is set to generate. GUI, command line, and scheduled backups all run fine. The user is not prompted for the password. So there must not be any authenication problems and the password is stored in the registry. Has anyone seen this with their W2K 4.2.0 clients? Is this normal behavior? server - TSM 4.1.3 on AIX 4.3.3 client - Windows 2000 4.2.0 Thanks in advance, Eliza Lau Virginia Tech Computing Center [EMAIL PROTECTED] 540-231-9399
Antwort: Stop/Restart Scheduler on NT Client
Hi, please try the following 1. create a script for all your NT clients Script example: @echo off REM TSM Client Scheduler Restart script REM -- REM File location: C:\tsm\baclient REM File name: schedrestart.cmd REM Location of log file: C:\tsm\baclient REM Log file name: schedrestart.log REM -- echo *** BEGIN TSM Client Scheduler restart *** 1 C:\tsm\baclient\schedrestart.log 21 date /t 1 C:\tsm\baclient\schedrestart.log 21 time /t 1 C:\tsm\baclient\schedrestart.log 21 net stop TSM Client Scheduler 1 C:\tsm\baclient\schedrestart.log 21 net start TSM Client Scheduler 1 C:\tsm\baclient\schedrestart.log 21 echo *** END TSM Client Scheduler restart *** 1 C:\tsm\baclient\schedrestart.log 21 2. copy this script to all your TSM Clients 3. create a client scheduler script with a command and expiration date Scheduler example: def sched domain NT_sched_restart Type=Client desc=NT TSM Client Scheduler Restart action=command objects=C:\tsm\baclient\schedrestart.cmd startd=08/15/01 startt=07:00:00 expiration=08/15/01 4. associate your NT clients with the scheduler def assoc domain NT_sched_restart NTClient1,NTClient2, ... Sincerly Juergen Heinrich Verdi Information Consult GmbH Systemsmanagement Niederlassung Berlin Wittestraße 30K D-13509 Berlin http://www.verdi-ag.de
Re: Recovery Log size / roll forward benefits
I agree with Paul, it is pretty rare - but it can happen. You can't guarantee to prevent software or hardware corruption : you just have to plan the recovery path ... The last corruption I had was on a (pretty large) test DB when trying to see the impact of a problem I had at 3.7 (live) on the 4.1 (test) DB. Well, the 4.1 DB got corrupted, the server crashed and it wouldn't restart - I won't bore you with the details. The point is, I was able to recover the DB using the last FULL, INCRs and recovery log. This level of protection is essential for us. Like Paul, we have also had problems with the recovery log filling up too quickly (as well as the occasional 'pinned' logtail). Recently, we have escaped by the skin of our teeth when the recovery log hit 99% and the triggered INCR could not complete fast enough ( - trigger now lowered and we split expire inventory into a twice weekly run). I too have reservations about the 13GB log (although we certainly intend to use it) and I have been looking at timings for triggered INCRs; 13GB may take rather a long time ... Regards, Sheelagh -- Sheelagh Treweek Oxford University Computing Services Email: [EMAIL PROTECTED] Phone: +44 (0)1865 273205 Fax:-273275 +-+ | http://tsm-symposium.oucs.ox.ac.uk/ OXFORD 20/21 September 2001 | | REQUIREMENTS http://tsm-symposium.oucs.ox.ac.uk/requirements.html | +-+
Re: Missing Message-text
Hello, Check if the fileset tivoli.tsm.msg.en_US.server is as the same level than the fileset tivoli.tsm.server.*. Regards. -Original Message- From: Christoph Pilgram [mailto:[EMAIL PROTECTED]] Sent: vendredi 3 août 2001 14:51 To: [EMAIL PROTECTED] Subject: Missing Message-text Hy all, on our TSM-Server this message appears in the act-log everytime a tape could not be checked in into the library. We have just upgraded to Version 4.14 on an AIX 4.33-Server. Does anybody know, how to get the full-text for this message-number ? Message number 8376 not available for language EN_US Thanks Christoph
Re: Question on Novell Problems
4.11 SP6 or 4.2 original release as per my network folks. -=-Original Message- -= -= -=What Service Pack Level are your NW Servers ? -= -=__ -= -=Regards -= -=Dave Clifford -= -= -= -= [EMAIL PROTECTED] 03/08/01 13:38:42 -=I posted this the other day but I have not seen a response. Here is a -=repost. Can anyone help? -= -=+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ -= -=Hello, I have been experiencing a couple problems with our Novell clients -=that I'm wondering if you experts can help me with. First, my -=environment is -=Server: OS/390 4.1.0.0, Novell v4.2 and Novell Client 4.1.2.13. -= -=Problem number one deals with the schedule log. DSMC SCHED is constantly -=getting locked out of its log file (DSMSCHED.LOG). The file is locked and -=DSMC is unable to write to it. The error received is: -= -=ANS0118C LogSchedMsg: Unable to open schedule log file '(path and name of -=file)' for output. -= -=Quitting the scheduling service then restarting it cures the problem but -=only for a while. Eventually on ALL of our Novell servers the -=schedule log -=file gets locked and the above error is displayed on the console. -= -=The second problem is in reference to DSMC SCHED not releasing -=all resources -=when the NLM is quit. This only occurs when problem #1 above occurs. The -=following error messages are displayed: -= -=Threads-4.11-076 DSMC.NLM filed to close handle 18. -=Contact the supplier of the NLM. -=Threads-4.11-076 DSMC.NLM filed to close handle 19. -=Contact the supplier of the NLM. -= -=08-01-01 9:26.52 am: SERVER-04.11.2715 -= Module did not release 480 resources -= Module: Tivoli Distributed Storage Manager -= Resource: Small Memory Allocations -= Description: Alloc Memory (Bytes) -= -=Can anyone offer any advice on a possible cure for these problems? -= -=Thank you! -=Alan Davenport -=Selective Insurance -=973-948-1306 -=[EMAIL PROTECTED] -=
Re: Server Down
I had this problem first I used dsmfmt to create log and then extended log from dsmserv. PL go to adsm.org and search for log .U will get many mails archives. -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 7:05 AM To: [EMAIL PROTECTED] Subject: Re: Server Down I don't know if this is available to 3.1 or if it came about in 3.7 but DSMSERV EXTEND LOG (Emergency Log Extension) Use this command to extend the size of the recovery log when you need additional log space to restart the server. After the server is running, you can do the following: v Back up the database, which frees the recovery log space. v Adjust the size of the recovery log, the database backup trigger full percentage, or both to allow for successful future database backups. Note: Use the DSMFMT utility to format a new recovery log volume. Syntax DSMSERV EXTEND LOG volume_name megabytes -Original Message- From: Phil Stockton [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 2:16 AM To: [EMAIL PROTECTED] Subject: Server Down Hi, Im running ADSM 3.1.2.90 on AIX 4.3.2 ona RS6000 H70 Overnight the log became full. I ran a dsmfmt to assign another log file and then dsmserv to extend it. When I try to bring up the server it falls over. Bringing it up in single user mode via ./dsmserv I get the following message ANRD logsec.c(498) log space has been overcommited (no empty segment found) base LSN =358650.0.0 Server operation terminated. Anyone got any ideas ? Regards Phil Stockton RS Components *** The contents of this Email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. The views stated herein do not necessarily represent the view of the company. If you are not the intended recipient of this Email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this mail in error please Email the sender. *** RS Components Ltd.
Re: vaulting problem
Yes, you should feel comfortable with your vendor, but don't. The worst time to find out your inventory is off is when you are trying to recover from a disaster. I highly recommend (and this is from experience) that you audit your vault at least twice a year. Even with all the safeguards, problems can happen. Nick Cassimatis [EMAIL PROTECTED] Today is the tomorrow of yesterday.
Re: vaulting problem
We will be assigned a range of slots. We tell them what tapes to put in what slots, so it's under our control -- but we also have to keep track. I suppose it would be possible to write a basic script to manage that. It would have to keep its own database of course (although probably a single flat file would work). Check out Autovault... it may handle that for you (for a price). Speaking of bad vault vendors, the one we had a couple of years ago (who shall remain nameless) when we first started using ADSM, actually placed their own hand-written gummed labels over our barcodes! I mean, how dumb is that? Needless to say, we have taken our business elsewhere... to Vital Records Inc., who I can highly recommend. Robin Sharpe Berlex Laboratories
Re: Server Down
I don't know if this is available to 3.1 or if it came about in 3.7 but DSMSERV EXTEND LOG (Emergency Log Extension) Use this command to extend the size of the recovery log when you need additional log space to restart the server. After the server is running, you can do the following: v Back up the database, which frees the recovery log space. v Adjust the size of the recovery log, the database backup trigger full percentage, or both to allow for successful future database backups. Note: Use the DSMFMT utility to format a new recovery log volume. Syntax DSMSERV EXTEND LOG volume_name megabytes -Original Message- From: Phil Stockton [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 2:16 AM To: [EMAIL PROTECTED] Subject: Server Down Hi, Im running ADSM 3.1.2.90 on AIX 4.3.2 ona RS6000 H70 Overnight the log became full. I ran a dsmfmt to assign another log file and then dsmserv to extend it. When I try to bring up the server it falls over. Bringing it up in single user mode via ./dsmserv I get the following message ANRD logsec.c(498) log space has been overcommited (no empty segment found) base LSN =358650.0.0 Server operation terminated. Anyone got any ideas ? Regards Phil Stockton RS Components *** The contents of this Email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. The views stated herein do not necessarily represent the view of the company. If you are not the intended recipient of this Email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this mail in error please Email the sender. *** RS Components Ltd.
Question on Novell Problems
I posted this the other day but I have not seen a response. Here is a repost. Can anyone help? +_+_+_+_+_+_+_+_+_+_+_+_+_+_+ Hello, I have been experiencing a couple problems with our Novell clients that I'm wondering if you experts can help me with. First, my environment is Server: OS/390 4.1.0.0, Novell v4.2 and Novell Client 4.1.2.13. Problem number one deals with the schedule log. DSMC SCHED is constantly getting locked out of its log file (DSMSCHED.LOG). The file is locked and DSMC is unable to write to it. The error received is: ANS0118C LogSchedMsg: Unable to open schedule log file '(path and name of file)' for output. Quitting the scheduling service then restarting it cures the problem but only for a while. Eventually on ALL of our Novell servers the schedule log file gets locked and the above error is displayed on the console. The second problem is in reference to DSMC SCHED not releasing all resources when the NLM is quit. This only occurs when problem #1 above occurs. The following error messages are displayed: Threads-4.11-076 DSMC.NLM filed to close handle 18. Contact the supplier of the NLM. Threads-4.11-076 DSMC.NLM filed to close handle 19. Contact the supplier of the NLM. 08-01-01 9:26.52 am: SERVER-04.11.2715 Module did not release 480 resources Module: Tivoli Distributed Storage Manager Resource: Small Memory Allocations Description: Alloc Memory (Bytes) Can anyone offer any advice on a possible cure for these problems? Thank you! Alan Davenport Selective Insurance 973-948-1306 [EMAIL PROTECTED]
Missing Message-text
Hy all, on our TSM-Server this message appears in the act-log everytime a tape could not be checked in into the library. We have just upgraded to Version 4.14 on an AIX 4.33-Server. Does anybody know, how to get the full-text for this message-number ? Message number 8376 not available for language EN_US Thanks Christoph
Re: Question on Novell Problems
What Service Pack Level are your NW Servers ? __ Regards Dave Clifford [EMAIL PROTECTED] http://www.carltontv.co.uk Direct Tel: +44 (0)207 615 1852 Mobile Tel: +44 (0)78 011 888 55 Company Fax: +44 (0)7092020624 CONFIDENTIALITY NOTICE This e-mail is intended only for the addressee named above. As this eMail may contain confidential or privileged information if you are not the named addressee or the person responsible for delivering the message to the named addressee please telephone us immediately. The contents should not be disclosed to any other person nor copies taken. * This footnote confirms that this e-mail message has been scanned for the presence of known computer viruses by Norton Antivirus. However, it is still recommended that you use local virus scanning software to monitor for the presence of viruses. * [EMAIL PROTECTED] 03/08/01 13:38:42 I posted this the other day but I have not seen a response. Here is a repost. Can anyone help? +_+_+_+_+_+_+_+_+_+_+_+_+_+_+ Hello, I have been experiencing a couple problems with our Novell clients that I'm wondering if you experts can help me with. First, my environment is Server: OS/390 4.1.0.0, Novell v4.2 and Novell Client 4.1.2.13. Problem number one deals with the schedule log. DSMC SCHED is constantly getting locked out of its log file (DSMSCHED.LOG). The file is locked and DSMC is unable to write to it. The error received is: ANS0118C LogSchedMsg: Unable to open schedule log file '(path and name of file)' for output. Quitting the scheduling service then restarting it cures the problem but only for a while. Eventually on ALL of our Novell servers the schedule log file gets locked and the above error is displayed on the console. The second problem is in reference to DSMC SCHED not releasing all resources when the NLM is quit. This only occurs when problem #1 above occurs. The following error messages are displayed: Threads-4.11-076 DSMC.NLM filed to close handle 18. Contact the supplier of the NLM. Threads-4.11-076 DSMC.NLM filed to close handle 19. Contact the supplier of the NLM. 08-01-01 9:26.52 am: SERVER-04.11.2715 Module did not release 480 resources Module: Tivoli Distributed Storage Manager Resource: Small Memory Allocations Description: Alloc Memory (Bytes) Can anyone offer any advice on a possible cure for these problems? Thank you! Alan Davenport Selective Insurance 973-948-1306 [EMAIL PROTECTED]
Latest LTO firmware levels ?
Hi, does anyone know the latest firmware levels for the 3584 LTO library, and 3580 LTO drives ? My tape drives are at version: 16E0 , and my 3584 is at version: 1450 . Pls adv. Brgds, Othonas Xixis
Re: vaulting problem
Here's a little bit of code to get you started.
Alex
#!/bin/ksh
#
# This is a simple script to process vault slotting for ADSM DR Media
# The slot file has to be generated first, and looks something like
#
# A001 -Empty
# A002 -Empty
#
#
#set -x
function usage {
print
print usage: vault [-r|-v] file1 file2
print usage: vault [-o|-e] file2
print usage: vault [-s] string file2
print
print -- -r return from vault
print -- -v send to vault
print -- -o print contents of slots
print -- -c free slot count
print -- -s search slots for a string
print -- -e edit the slot list
print string search string
print file1 filename of the list of tapes to send or return
print file2 filename of the list of slots
}
function unslot_tapes {
tapes=$1
slots=$2
grep -f $tapes $slots | awk '{print $1 -Empty}' slots.empty
grep -vf $tapes $slots slots.unchanged
cat slots.empty slots.unchanged
awk '{print $1}' slots.empty tmp3.$$
grep -f tmp3.$$ $slots
rm tmp3.$$
sort +0 -1 slots.unchanged $slots
rm slots.unchanged
}
function slot_tapes {
tapes=$1
slots=$2
grep -f $tapes $slots slots.vaulted
awk '{print $2}' slots.vaulted tmp.$$
grep -vf tmp.$$ $tapes tapes.2
grep -vf tmp.$$ $slots tmp2.$$
cat tmp2.$$ $slots
rm tmp2.$$
rm tmp.$$
exec 3 tapes.2
grep \-Empty $slots | awk '{print $1}' | while read slotnum; do
if read -u3 volume; then
print $slotnum $volume `date +%m/%d/%y` slots.vaulted
else
break;
fi
done
awk '{print $1}' slots.vaulted tmp.$$
grep -vf tmp.$$ $slots slots.unchanged
rm tmp.$$
cat slots.vaulted slots.unchanged
sort +0 -1 slots.unchanged $slots
rm tapes.2 slots.unchanged
cat slots.vaulted
}
if [[ ! $# -gt 1 ]]; then
usage
return 1
elif [[ $1 = -c ]]; then
if [[ ! -s $2 ]]; then print unable to open file $2; return 1; fi
grep -c \-Empty $2
elif [[ $1 = -o ]]; then
if [[ ! -s $2 ]]; then print unable to open file $2; return 1; fi
grep -v \-Empty $2 2/dev/null
elif [[ $1 = -e ]]; then
if [[ ! -s $2 ]]; then print unable to open file $2; return 1; fi
vi $2
elif [[ ! $# -eq 3 ]]; then
usage
return 1
elif [[ $1 = -s ]]; then
if [[ ! -s $3 ]]; then print unable to open file $3; return 1; fi
grep $2 $3 2/dev/null
if [[ ! $? -eq 0 ]]; then
print Unable to find pattern
return 1
fi
elif [[ ! ( -s $2 -s $3 ) ]]; then
print one of the files, $2 or $3, doesn\'t exist.
return 1
elif [[ $1 = -r ]]; then
unslot_tapes $2 $3
elif [[ $1 = -v ]]; then
slot_tapes $2 $3
fi
-Original Message-
From: Adam J. Boyer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 02, 2001 2:00 PM
To: [EMAIL PROTECTED]
Subject: Re: vaulting problem
We will be assigned a range of slots. We tell them what tapes to put in
what slots, so it's under our control -- but we also have to keep track.
David Longo
David.Longo@HEALTH-To: [EMAIL PROTECTED]
FIRST.ORG cc:
Sent by: ADSM: DistSubject: Re: vaulting
problem
Stor Manager
[EMAIL PROTECTED]
U
08/02/01 04:52 PM
Please respond to
ADSM: Dist Stor
Manager
BTW: How will you know what slot they have put your tape in??
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.5525
[EMAIL PROTECTED]
WorldSecure Freightliner.com made the following
annotations on 08/03/01 10:30:09
--
[INFO] -- Content Manager:
The information contained in this communication is confidential and intended solely
for the use of the individual to whom it is addressed and others authorized to receive
it. If you are not the intended recipient, any disclosure, copying, distribution or
taking of any action in reliance on the contents of this information is prohibited. If
you have received this communication in error, please immediately notify the sender by
phone if possible or via email message.
==
Re: Latest LTO firmware levels ?
The latest 3584 firmware is 1450. The latest 3580 firmware is 16E0. Rick Pruitt Distributed Storage Management IBM Global Services, KY ``Most human beings have an almost infinite capacity for taking things for granted.'' - Aldous Huxley Othonas Xixis/Raleigh/Contr/IBM@[EMAIL PROTECTED] on 08/03/2001 01:09:59 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Latest LTO firmware levels ? Hi, does anyone know the latest firmware levels for the 3584 LTO library, and 3580 LTO drives ? My tape drives are at version: 16E0 , and my 3584 is at version: 1450 . Pls adv. Brgds, Othonas Xixis
bufpoolsize and AIX
Our bufpool hit ratio has been running in the mid 90% and I would like to increase it's size. Currently, it's set to: dsmserv.opt: BUFPoolsize 1048576 Our tsm server is a hand-me-down with lots of memory - 12GB. I decided to double the bufpoolsize parm to 2048576. When I tried to start tsm it complained that it couldn't acquire this memory and failed to start. I tried to set it to just a few hundred mb more, but had the same result. I finally just put it back to the origional value and got our server up and running. The doc states that the limit on the bufpoolsize parm is the size of your virtual memory. I'm well under that! Any idea what limit I might be hitting? I think I must be hitting an AIX (4.3.3) limit of some kind. Thanks Rick
Re: copypools using tsm server to server
1) well, this is why I set up a domain just for remote servers, they have no backup copy group and their archive copy group has a default of never expiring archives. (I'm big on covering my a$$) 2) IT is always nice to easily see just what in the heck is going on utilization wise with a remote server, by sticking it into an isolated storage pool, it is real easy to look at things. additional question answer... to delete a filespace of a source server over on the target server you can't get away with just del file other_server_node you are forced to use del file other_server_node TYPE=SERVER it is just a CYA in TSM... (which I like ! ) If that is part of a def that you still are having problems with... I've found it is possible to clean up everything on either end no matter what order things were deleted/removed You just have to get the specific commands right with the specific options... more along the lines of having to specify type=server with a del file, that sort of stuff but I've had some pretty UGLY situations and I've been able to clear them all up... also remember there are volumereusedelays you might have to wait on once you purge data from tapes the such... Oh, and I'm at TSM Srv 3.7 currently. hope this helps later, Dwight -Original Message- From: Steve Bennett [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 1:22 PM To: [EMAIL PROTECTED] Subject: copypools using tsm server to server Fellow *SMers, I have two TSM 4.1.3 servers in different cities and would like to use themn each for offsite storage for the other. Bandwidth considerations aside I have some other questions based upon things I have read in the server to server redbook. This can get a bit convoluted so get ready to wade through my verbage. 1) The book indicates that the virtual vols on the target server are only deleted at the request of the source server and at no time will the archive retention of the target server management class cause the virtual vol archive to be deleted. Have any of you verified this? 2) I would like to have server-1 backup it's primary stgpools to target server-2 and vice versa. Given that all primary pools for server-1 reside on server-1 is there any reason I shouldn't let the copypool data from source server-1 comingle with the data in the primary stgpools on target server-2? One additional question that might be related to #1 is that at one time I had some server to server virtual vols defined for primary pool migration. That has since been abandoned and some of the server to server and node defs deleted. However there are some parts of the defs that I cannot delete because it says there are still inventory references, in particular the other server def. I suspect that because part of the defs were already deleted there is no way for the source server to tell the target server to delete the archives and when I try to do it manually it slaps my hand. Is there any way to delete those inventory references so I can delete the other server def? TIA -- Steve Bennett, (907) 465-5783 State of Alaska, Information Technology Group, Technical Services Section
Help please, how to format log and db with adsm 3.1 under OS/390
Hello, under OS/390, I have to format 1 log data set and 10 db data sets. The total length of all these names is more than 100 caracters. How can I give such a long string of caracters on the EXEC card, the OS/390 refuses it when exceeding 100 car.? FORMAT 1 ADSM.RCVRYLO1 10 ADSM.DB1 ADSM.DB2 . ADSM.DB10' Is it possible to extend this limit or use a DD card ? Thanks for any help René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential.
Re: Transfer Rate
No, you have to turn it on. Run a Q STATUS command; one of the lines show ACCOUNTING either ON or OFF. To turn it on, just enter: SET ACCOUNTING ON It will stay on across any server restarts, until you turn it off. We have a script that runs every month that copies the dsmaccnt.log file elsewhere (or you could archive it) then clears it. You will want to do something similar so the file won't grow forever. The dsmaccnt.log file is a simple comma-delimited format; the fields are described in the admin guide. -Original Message- From: Francisco Reyes [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 5:13 PM To: [EMAIL PROTECTED] Subject: Re: Transfer Rate On Thu, 2 Aug 2001, Lindsay Morris wrote: If you really want to speed up your backups, you need to look at the accounting log records (.../server/bin/dsmaccnt.log - see admin guide for layout) to see which of your clients suffer most from idle wait, media wait, or comm wait. Is this accounting file created by default? I don't see one in my bin directory.
Re: Help please, how to format log and db with adsm 3.1 under OS/ 390
exactly what I needed ! thanks a lot René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. -Original Message- From: Bill Colwell [SMTP:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 11:12 PM To: [EMAIL PROTECTED] Subject: Re: Help please, how to format log and db with adsm 3.1 under OS/390 Rene, Use the indirect list-of-names method as in the sample below. Hope this help, -- -- Bill Colwell C. S. Draper Lab Cambridge, Ma. [EMAIL PROTECTED] -- --- begin sample --- // --- job card -- //*- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //* //* FORMAT THE LOG PRIOR TO A LOADDB JOB. //* //*- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //SERVER EXEC PGM=ANRSERV, // PARM='/FORMAT 1 FILE:DD:LN 16 FILE:DD:DN', // DYNAMNBR=300 //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //* FOR TSM 3.7.40 //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //STEPLIB DD DSN=ADSM.V3R7M40.LINKLIB,DISP=SHR //IMAGES DD DSN=ADSM.V3R7M40.SANRIMG(ADSMSERV),DISP=SHR //DSMAMENG DD DSN=ADSM.V3R7M40.SANRMSG(ANRMENU),DISP=SHR //HLPAMENG DD DSN=ADSM.V3R7M40.SANRHLP(ANRHENU),DISP=SHR //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //* PERMANENT FILES //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //OPT DD DSN=ADSM.V3R7.PROD.OLDSERVR.OPTIONS,DISP=SHR,FREE=CLOSE //DSK DD DSN=ADSM.PRODGA.DISKLOG3,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* //LN DD * ADSM.PROD.RLA.AL100F //DN DD * ADSM.PROD.DB.AD101F ADSM.PROD.DB.AD102F ADSM.PROD.DB.AD103F ADSM.PROD.DB.AD104F ADSM.PROD.DB.AD105F ADSM.PROD.DB.AD106F ADSM.PROD.DB.AD107F ADSM.PROD.DB.AD108F ADSM.PROD.DB.AD121F ADSM.PROD.DB.AD122F ADSM.PROD.DB.AD123F ADSM.PROD.DB.AD124F ADSM.PROD.DB.AD125F ADSM.PROD.DB.AD126F ADSM.PROD.DB.AD127F ADSM.PROD.DB.AD128F --- end sample --- In [EMAIL PROTECTED], on 08/03/01 at 05:11 PM, Lambelet,Rene,VEVEY,GL-IS/CIS [EMAIL PROTECTED] said: Hello, under OS/390, I have to format 1 log data set and 10 db data sets. The total length of all these names is more than 100 caracters. How can I give such a long string of caracters on the EXEC card, the OS/390 refuses it when exceeding 100 car.? FORMAT 1 ADSM.RCVRYLO1 10 ADSM.DB1 ADSM.DB2 . ADSM.DB10' Is it possible to extend this limit or use a DD card ? Thanks for any help René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential.
TSm and Frame Relay Network?
Any body out there doing some backups over Frame Relay that would be willing to answer a few questions? We have a customer that is planning to do it with some NT clients and is a little nervous. Are you doing it? Approx. how many clients? About how much data per day? Any major problems other than the obvious issue that speed is slower than for local backups?
Re: Help please, how to format log and db with adsm 3.1 under OS/390
Hi René, Use pgm=DSMFMT instead - one step per dataset: example: //* pre-format ADSM.DB6 //FMTDB6 EXEC PGM=DSMFMT,DYNAMNBR=300, // PARM='/SYS3.ADSM.DB6' //DSMAMENG DD DSN=SYS1.SANRMSG(ANRMENU),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* best regards John Svendsen DMdata a/s Lambelet,Rene,VEVEY, GL-IS/CIS To: [EMAIL PROTECTED] Rene.Lambelet@NESTLEcc: .COMSubject: Help please, how to format log and Sent by: ADSM: Dist db with adsm 3.1 under OS/390 Stor Manager [EMAIL PROTECTED] 03-08-01 22:44 Please respond to ADSM: Dist Stor Manager Hello, under OS/390, I have to format 1 log data set and 10 db data sets. The total length of all these names is more than 100 caracters. How can I give such a long string of caracters on the EXEC card, the OS/390 refuses it when exceeding 100 car.? FORMAT 1 ADSM.RCVRYLO1 10 ADSM.DB1 ADSM.DB2 . ADSM.DB10' Is it possible to extend this limit or use a DD card ? Thanks for any help René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential.
copypools using tsm server to server
Fellow *SMers, I have two TSM 4.1.3 servers in different cities and would like to use themn each for offsite storage for the other. Bandwidth considerations aside I have some other questions based upon things I have read in the server to server redbook. This can get a bit convoluted so get ready to wade through my verbage. 1) The book indicates that the virtual vols on the target server are only deleted at the request of the source server and at no time will the archive retention of the target server management class cause the virtual vol archive to be deleted. Have any of you verified this? 2) I would like to have server-1 backup it's primary stgpools to target server-2 and vice versa. Given that all primary pools for server-1 reside on server-1 is there any reason I shouldn't let the copypool data from source server-1 comingle with the data in the primary stgpools on target server-2? One additional question that might be related to #1 is that at one time I had some server to server virtual vols defined for primary pool migration. That has since been abandoned and some of the server to server and node defs deleted. However there are some parts of the defs that I cannot delete because it says there are still inventory references, in particular the other server def. I suspect that because part of the defs were already deleted there is no way for the source server to tell the target server to delete the archives and when I try to do it manually it slaps my hand. Is there any way to delete those inventory references so I can delete the other server def? TIA -- Steve Bennett, (907) 465-5783 State of Alaska, Information Technology Group, Technical Services Section
Moving vol
Hello TSM'ers I need to move some volumes from one devclass to another and then delete the devclass. I can't seem to find the right order of commands to accomplish this.What's the easiest way?? Patrick
Re: Moving vol
The device classes probably are not compatible ??? right ??? like 8mm tape DLT tape or 3590 tape ??? you would have to do move data old_vol_ser stg=stg_pool_using_some_other_devclass like move data AAA001 stg=diskpool hope this helps later, Dwight -Original Message- From: Patrick Sheehan [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 1:46 PM To: [EMAIL PROTECTED] Subject: Moving vol Hello TSM'ers I need to move some volumes from one devclass to another and then delete the devclass. I can't seem to find the right order of commands to accomplish this.What's the easiest way?? Patrick
Re: copypools using tsm server to server
Steve, For #2, no, you don't want to do that, as you'd be making copies of this data back to the original server - making copies of you copy pool data. You'd never finish updating the copy pools, as you'd always be creating more data in the primary pool. It's a circular path for the data, and it would keep going around and around and around and around... You definitely want to make a second storage pool for the remote servers data storage. Nick Cassimatis [EMAIL PROTECTED] Today is the tomorrow of yesterday.
Re: bufpoolsize and AIX
Our tsm server is a hand-me-down with lots of memory - 12GB. I decided to double the bufpoolsize parm to 2048576. When I tried to start tsm it complained that it couldn't acquire this memory and failed to start. I tried to set it to just a few hundred mb more, but had the same result. I finally just put it back to the origional value and got our server up and running. Any idea what limit I might be hitting? I think I must be hitting an AIX (4.3.3) limit of some kind. Rick - Good intuition. Your prevailing Unix Resource Limits are probably your hindrance. Do 'ulimit -a' to check. See the ulimit man page as a lead-in to information. Also look into those pesky AIX Segments. Here are some notes I have: If a Unix system, check Unix Limits values. Assure that the system is not running out of virtual storage. If AIX, you may be in need of more than the single memory segment that AIX allows by default, which you can go beyond via Large Program Support conventions. The scoop: The amount of memory that the process needs may exceed the size of one data segment (256 MB), which is the default number of segments a process may use. The process is in this case killed by the system. The work-around for this is to enable the program to be able to use more than one data segment by enabling Large Program Support, using the following commands: cp -p Pgm_Name Pgm_Name.orig cd /usr/lpp/adsm/bin /usr/bin/echo '\0200\0\0\0' | dd of=Pgm_Name bs=4 count=1 seek=19 conv=notrunc which causes the XCOFF o_maxdata field (see aouthdr.h) to be updated. This allows the program to use the maximum of 8 data segments (2 GB). Choose the string to use for a given number of data segments from the following table: # segmentsvm size string 8 2 GB '\0200\0\0\0' 6 1.5 GB'\0140\0\0\0' 4 1 GB '\0100\0\0\0' 2 512 MB'\040\0\0\0' Richard Sims, BU
Re: Help please, how to format log and db with adsm 3.1 under OS/ 390
ONLY DO A SINGLE LOG A SINGLE DB ! I ran into the same thing... I exceeded the max continuation of a EXEC card ! Just to the single log single db vol then do formats of the other db vols like normal and go into the running tsm that you started with the single log single db vol and add in the additional db vols hope this helps later, Dwight -Original Message- From: Lambelet,Rene,VEVEY,GL-IS/CIS [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 3:45 PM To: [EMAIL PROTECTED] Subject: Help please, how to format log and db with adsm 3.1 under OS/390 Hello, under OS/390, I have to format 1 log data set and 10 db data sets. The total length of all these names is more than 100 caracters. How can I give such a long string of caracters on the EXEC card, the OS/390 refuses it when exceeding 100 car.? FORMAT 1 ADSM.RCVRYLO1 10 ADSM.DB1 ADSM.DB2 . ADSM.DB10' Is it possible to extend this limit or use a DD card ? Thanks for any help René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential.
Re: Help please, how to format log and db with adsm 3.1 under OS/390
Rene, Use the indirect list-of-names method as in the sample below. Hope this help, -- -- Bill Colwell C. S. Draper Lab Cambridge, Ma. [EMAIL PROTECTED] -- --- begin sample --- // --- job card -- //*- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //* //* FORMAT THE LOG PRIOR TO A LOADDB JOB. //* //*- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //SERVER EXEC PGM=ANRSERV, // PARM='/FORMAT 1 FILE:DD:LN 16 FILE:DD:DN', // DYNAMNBR=300 //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //* FOR TSM 3.7.40 //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //STEPLIB DD DSN=ADSM.V3R7M40.LINKLIB,DISP=SHR //IMAGES DD DSN=ADSM.V3R7M40.SANRIMG(ADSMSERV),DISP=SHR //DSMAMENG DD DSN=ADSM.V3R7M40.SANRMSG(ANRMENU),DISP=SHR //HLPAMENG DD DSN=ADSM.V3R7M40.SANRHLP(ANRHENU),DISP=SHR //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //* PERMANENT FILES //* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - //OPT DD DSN=ADSM.V3R7.PROD.OLDSERVR.OPTIONS,DISP=SHR,FREE=CLOSE //DSK DD DSN=ADSM.PRODGA.DISKLOG3,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* //LN DD * ADSM.PROD.RLA.AL100F //DN DD * ADSM.PROD.DB.AD101F ADSM.PROD.DB.AD102F ADSM.PROD.DB.AD103F ADSM.PROD.DB.AD104F ADSM.PROD.DB.AD105F ADSM.PROD.DB.AD106F ADSM.PROD.DB.AD107F ADSM.PROD.DB.AD108F ADSM.PROD.DB.AD121F ADSM.PROD.DB.AD122F ADSM.PROD.DB.AD123F ADSM.PROD.DB.AD124F ADSM.PROD.DB.AD125F ADSM.PROD.DB.AD126F ADSM.PROD.DB.AD127F ADSM.PROD.DB.AD128F --- end sample --- In [EMAIL PROTECTED], on 08/03/01 at 05:11 PM, Lambelet,Rene,VEVEY,GL-IS/CIS [EMAIL PROTECTED] said: Hello, under OS/390, I have to format 1 log data set and 10 db data sets. The total length of all these names is more than 100 caracters. How can I give such a long string of caracters on the EXEC card, the OS/390 refuses it when exceeding 100 car.? FORMAT 1 ADSM.RCVRYLO1 10 ADSM.DB1 ADSM.DB2 . ADSM.DB10' Is it possible to extend this limit or use a DD card ? Thanks for any help René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential.
Re: Transfer Rate
On Thu, 2 Aug 2001, Lindsay Morris wrote: If you really want to speed up your backups, you need to look at the accounting log records (.../server/bin/dsmaccnt.log - see admin guide for layout) to see which of your clients suffer most from idle wait, media wait, or comm wait. Is this accounting file created by default? I don't see one in my bin directory.
Re: Moving vol
You can't change the device class of a volume that already exists. Define your new device class. Define a new storage pool that uses the device class. MOVE DATA volname stgpool=newstgpool ONce the volumes are empty, they will be delete (go back to scratch) automatically. Then you can delete the old stgpool. Then you can delete the old device class. -Original Message- From: Patrick Sheehan [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 2:46 PM To: [EMAIL PROTECTED] Subject: Moving vol Hello TSM'ers I need to move some volumes from one devclass to another and then delete the devclass. I can't seem to find the right order of commands to accomplish this.What's the easiest way?? Patrick
