Strange,
I am seeing a similar message during start of the server (3.1.2.57), but
never saw it during a restore. I always contributed it to a problem
we are known to have in our DB. (I could not afford to run the suggested
DUMP/LOAD/AUDIT DB so far.) And, what a coincidence, we are also using
Hello *SMers,
I am in a situation where I cannot use trial and error, so...
Does anybody know how to define a restore schedule for a single file such
that it is renamed on the target node?
What does the OBJ string need to be? - I dont want to get this wrong and
overwrite the file that is
Larry,
You may need to increase your maxsessions option in the server options
file.
Brian
Lawrence Clark
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
ATE.NY.US cc:
Sent by: "ADSM:
We are experiencing a number of sessions that seen to sit idle and not
complete. This message, not in the message manual, appears:
ANS1351E Session rejected. All server sessions are currently in use.
Larry - The message is in the messages manual, in chapter:
Chapter 7. Client Common
Hi:
We are experiencing a number of sessions that seen to sit idle and not complete. This
message, not in the message manual, appears:
ANS1351E Session rejected. All server sessions are currently in use.
Has anyone seen this one before?
Larry Clark
NYS Thruway Authority
Hi Brenda,
The latest doc for 4.1 does include the infor for RC 41. Also,
you can find the brief description in dsmrc.h, located in
directory ..\TSM\api\include.
RC 41 means DSM_RS_ABORT_EXCEED_MAX_MP, which means that the
client was attempting to use more mountpoints for a backup or
archive
Does anyone know what the following means? This return code is not listed
in the API book.
SQL2025N An I/O error "41" occurred on media "ADSM".
Brenda - SQL messages are from DB2 itself. See IBM message references
like http://magna.cs.ucla.edu/db2doc/db2m0/sql2000.htm
But the
When client compression is turned on, the data is already
arriving to the TSM server in a compressed state. The 3590
may indeed be trying to compress this data again, but
compressed data does not compress very well, so this is why
you see the misleading utilization.
Keep in mind though, that the
Well, yes and no, depending on how much pain you are willing to put up with.
If you are looking to be able to directly MOVE the data for these filesystems,
the answer is NO! That funtionality doesn't exist in TSM, but has been
requested several times. The only way I got done what you're
I look after the companies TSM environment. Approx 700 servers back up an
average of 60-70gb per night. The ADSM server runs on OS/390 with 500 OS/2 and
200 NT clients. I have 2 primary disk pools, one of 45GB for the NT
servers(colocated) and one of 4GB for the OS/2 servers(non colocated). HIMIG
I had a similar situation and support gave me the following work around.
This was for a 3.1.0.7 client so you may need to adjust it for the Tivoli
version. Since it involves 'hacking' the registry, do this at your own
risk. I believe there is an apar open for this problem as well.
James
Hello,
I would do some tests to see how quickly you are able to migrate from the
diskpool with single or multiple migration processes, and also to see how
quickly your diskpools fill up, and take it from there. The only other thing
I would be aware of is the size of the files being backed up -
I finally traced the dragging performance to a NIC card that had been reconfigured to
half-duplex. It should have been full-duplex 100mb.
Thanks,
Larry Clark
NYS Thruway Authority
[EMAIL PROTECTED] 10/24/00 08:02AM
Larry,
Query Status and look at the "Maximum Sessions" and Maximum Scheduled
Hi:
-look at your activity log for stats
-you would normally not do a selective.
-your 1st incremental will back up everything. After that changed files. Doing a
selective would be a lot of overhead to back up ( again) files that haven't changed.
[EMAIL PROTECTED] 10/20/00 04:27PM
Hi ,
Can
Hi:
This showed up on our server after migrateing to TSM 3.7. Looking thru the activity
log it appears to be because of our use of the MS-SQL agent, which I believe
previously did not require a license file on the server.
Larry Clark
NYS Thruway Authority
[EMAIL PROTECTED] 10/20/00 10:07AM
Interestingly enough, I just completed my first config of ADSM for a
cluster. Although the installation is not clearly documented, I found the
Redbook fairly useful. One warning however: the notes for the options
required for the service install aren't as good in the Redbook. I ended up
using
To all:
Environment:NT Server 4.0
TSM server 3.7.3.8
Oracle TDP 3.7.2 (NT)
Oracle 8.1.5 (NT)
TSM client V3.7.2
In the process of Setting up TDP for Oracle Client, can anyone share with me
the Daily backup schedule RMAN scripts
OK, I basically keep a diskpool big enough to contain an entire night's
backups.
Now this is compressed...
Things to remember:
Clients, even though using compression, allocate enough disk space
in the diskpool to hold the file uncompressed, once the transfer is
completed, unused space is
What I have gleaned from *SM studies is that you should have enough disk
cache to hold one day's worth of backups. Most installations will backup AND
migrate important data. But this is an installation's decision. In doing so,
it may be beneficial to backup the disk storage pool before migrating
Sorry if this has been asked before. Is it possible to
do tape copypool reclamation with a single tape drive
? The reclaimpool option isn't allowed for a copypool,
so I can't see how to define file (disk) space to do
it. Since I can do reclaim of primary tape pools using
a reclaimpool on disk, I
I am running TSM 3.7.20.0 on MVS OS390 2.8 mainframe. We are short on tape
drives and we are receiving the following message:
ANR5373I Unable to allocate tape drive with device type TAPE36 for tape
276414. Reply C (cancel), R (retry), or W (wait).
My question is; should I reply W to wait and
We reply R to that Message,
It is done via our automation software.
Jim Doll
CNJ Rm330B 908-236-3492
Fax 908-236-3668
|+---
|| "David |
|| Browne." |
|| dbrowne@HUMA|
|| NA.COM |
|
Hello group,
I hope somebody can help me. We are trying to backup our NDS and are
running into a problem. As the NDS backs up, the amount of memory
'consumed' by SMDR.NLM grows and grows until no more short term memory
can be allocated on the server. Our NDS is relatively large but for the
Copypool reclamation is performed by copying data that is still valid on
the tape that is being reclaimed from the *source* primary stgpool again to
a new copypool tape.
e.g. if files a,b,c are all still unexpired on copypool tape c1 and d is
unexpired on c2, they also still exist in the
Dean,
We are targeting Q1 2001. As usual...no promises.
Thanks,
Del
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
"Amini, Mehdi" [EMAIL PROTECTED]@VM.MARIST.EDU on 09/22/2000
11:44:42 AM
Dean Winger [EMAIL PROTECTED]@VM.MARIST.EDU on
25 matches
Mail list logo
