Allocate a new/additional recovery log file...
Find some file space and lay down a file with the dsmfmt command... like
Unix dsmfmt -m -log /opt/IBMadsm-C/newlog 16
then do a
Unix DSMSERV EXTEND LOG /opt/IBMadsm-C/newlog 16
After that you should be good to go, just start the dsmserv again...
Ok, maybe my environments are odd balls but I don't see where you are
allowed to use the "vollist=file:x" option with checkout libvol.
and I never do it that way... I just do a bunch of normal checkouts in the
form of a macro
Dwight
--
From: Shekhar Dhotre[SMTP:[EMAIL
The HSM client (if you have HSM licensed on your tsm server) will take files
from your unix client and replace the actual file with a stub file to reduce
the amount of space occupied by files on your client box. A space
management tool.
Dwight
that was the short-n-sweet condensed version
full : end of volume has been reached... %util is low because files have
expired... must run reclamation to get back
pending : check your "reusedelay" setting... tape has gone empty but
reusedelay is preventing it from rolling scratch again (for x number of
days)
Dwight
Uh try admin guide
just break down the tape volser list into 5 differnet files the perform from
aix
nohup dsmlabel -library=/dev/lmcp# -drive=/dev/rmt1 -keep filewith1st5th
nohup dsmlabel -library=/dev/lmcp# -drive=/dev/rmt2 -keep filewith2nd5th
nohup dsmlabel -library=/dev/lmcp# -drive=/dev/rmt3 -keep
lto:[EMAIL PROTECTED]]On Behalf Of
Cook, Dwight E
Sent: Wednesday, August 16, 2000 9:40 AM
To: [EMAIL PROTECTED]
Subject: Re: multiple label libvols?
just break down the tape volser list into 5 differnet files the perform
from
aix
nohup dsmlabel -library=/dev/lmcp# -drive=/dev/
tsm server Server Version 3, Release 7, Level 2.0
Client Version: Version 3, Release 1, Level 0.8 Platform: SUN SOLARIS
Client OS Level: 5.6
well, I see what part of my problem might be now...
but anyway if you query the file systems of the client from an admin session
on the server you see
And yes, sometimes the values might seem WAY out of line but here is what
I've had to set mine at to get things to work. But remember the idletimeout
has more to do with the brain-child client node rather than anything to do
with the tsm server. I've had to set the 240 minute idletimeout because
Long, check the availability of your db log files from your operating
system...
looks like you probably had a volume group go unavailable...
also you might have to add to and extend your log to get back up...
DSMSERV EXTEND LOG (Emergency Log Extension)
Use this command to extend the size of the
for an archive this shows up when you query the archived file
for backups, it all depends on how many versions you keep, how often the
file changes, and how little the file changes... there is some of the
"stuff" logged in the server's activity log but I tend to avoid even going
there and it
Are the devices available at the library? that is under service pull down
menues
Does a "q drive" show them ?
Do you see them in a "show libr" list ?
maybe something like...
Library TTC3494LIB2 (type 349X):
refs=0, online=1, borrows=0, create=0, update=0
driveListBusy=0
You may also just update the node and change its domain...
upd node x domain=y
--
From: Shekhar Dhotre[SMTP:[EMAIL PROTECTED]]
Reply To: ADSM: Dist Stor Manager
Sent: Thursday, August 03, 2000 8:30 AM
To: [EMAIL PROTECTED]
Subject:
ie :-)) )
Or am totaly out in the blue here??
Henrik Hansson
Nomafa AB
Web; www.nomafa.com
Mail; [EMAIL PROTECTED]
"Cook, Dwight
E" To: [EMAIL PROTECTED]
[EMAIL PROTECTED]cc:
I'm sure TSM 4.1 is a "for a price" upgrade and you'll probably need the CD
to do the base code install...
I haven't looked into 4.1 yet though...
Dwight
--
From: Shekhar Dhotre[SMTP:[EMAIL PROTECTED]]
Reply To: ADSM: Dist Stor Manager
Sent: Tuesday, August 01,
I'm doing that...
Lots of different situations...
If they say the data is REALLY REALLY REALLY important I leave it in the tsm
server, have it in an isolated storage pool with a copypool copy of it AND I
export the node, twice, and give the end user one of the copies.
If it is REALLY important
Now on a different subnet I'm guessing...
a different interface to the same subnet won't get you much 'cause TSM can
flood the network !
so say you have a client with interfaces
1.2.3.6
and
1.2.4.6
and a tsm server with interface 1.2.4.8
just make sure your tcp/ip is configured to route .4
Now from what I remember (and I haven't double checked the 3.7 docs) is that
if you don't own a file, you CAN NOT back it up because backups
(incremental/selective) actually causes data to go away (rolling off
inactive versions).
I'm surprised that 3.2 let you... when I tested things, you
OUCH !... that is really what the include/exclude list is all about... (and
domain statements and the dsm.sys and/or dsm.opt file(s)) to set what you
want to process, then any backup is as easy as
inc
OK, besides that... you have to remember to backup a file you HAVE TO BE THE
OWNER OF
1st try a
q stg tapepool f=d
and look for the reuse delay... see if it is greater than zero, that would
explain the empty state without rolling back scratch
Ok, you checked in the libvols to the library using device stk9710 as
scratch, correct ?
For each storage pool (such as tapepool)
401 - 419 of 419 matches
Mail list logo