I would try openfile support in 5.2 . First tests look quite good.
Regards Stefan Holzwarth
-Ursprüngliche Nachricht-
Von: Gordon Woodward [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 29. Juli 2003 04:01
An: [EMAIL PROTECTED]
Betreff: Lotus Notes Non-TDP backups
We currently have over
Hello TSM experts,
I've got a TSM server 4.1.4.1 running on Windows NT SP6a. In the weekend a full export
is taken with the command:
export server filedata=backupactive devclass=DLTCLASS1 scratch=no
volumenames=000375,000383,09
This has been running fine for quiet a period (a few years),
Hi,
copy the notes.ini and the notes server id to the restore server, edit the
PATH'S in the notes ini for the TL's and Notesdat directory to reflect your
restore servers environment.
Do as you did, edit the TDP to use the real server node name and point it to
the notes.ini.
Now try it again.
Dynamic management class will stop the retries.
Y ou are probably getting the retries because your users are not logging off
their notes
accounts, and the backups should be ok for restore in that case. But with all
potential
fuzzy backups scenarios which is the risk with dynamic, you really need
Hi fellows
Some time, when I request the status report of the scheduled events ,
one or more clients showing
status value = (?) ,
what does it mean and why ?
here is an example :-
Scheduled Start Actual Start Schedule Name Node Name
Status
Stefan, Gordon,
Urrgh - no!
As soon as you try to restore any of these files which will have changed during the
backup, even with open file support, you'll more than likely get a corrupt .nsf
database! Notes .nsf files are pretty sensitive and any change somewhere in one part
of the db will
Hi Zosi!
Please supply the complete server level (like 5.1.7.0).
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Zosimo Noriega [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 26, 2003 08:49
To: [EMAIL PROTECTED]
Subject: Re: Error in deleting filespace
Remco,
I missed the discussion, but this is what the output you gave said:
tsm: BASKETq vol stat=empty f=d
Volume Status: Empty
Access: Read/Write
Pct. Reclaimable Space: 0.0
-- Scratch Volume?: Yes--
In
On Tue, 29 Jul 2003 12:31:51 +0200
Rick Harderwijk [EMAIL PROTECTED] wrote:
Remco,
I missed the discussion, but this is what the output you gave said:
tsm: BASKETq vol stat=empty f=d
Volume Status: Empty
Access: Read/Write
Pct.
Remco,
Hmm... indeed, I missed that one. Does the tape ever get release or reused?
Regards,
Rick
-Oorspronkelijk bericht-
Van: Remco Post [mailto:[EMAIL PROTECTED]
Verzonden: 29 juli 2003 12:32
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Empty volume does not return to scratch?
On Tue, 29
STATE does not translate to MEDIA_STATE, since it already existed in the previous
version. I guess what I am looking for is some doc on how the new table translates
from the old one. A kind of key or something. I am aware of the changes to the
schema, but cannot find any doc to show what is
Hi Zosi!
This looks like APAR PQ71660 which is fixed in 5.1.7.0. So my advice is:
upgrade.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 12:28
To: [EMAIL PROTECTED]
Subject: RE:
Hi,
Looking a problem myself at the moment.. I'm getting some errors on drives,
but it might be a tape that's not OK. I decided to remove the volume from
the library and set the volume to destroyed (ofcourse, I first moved the
data to another tape...). However, when I try to destroy the tape, I
Looking closer at the SESSION table I think the MEDIA_STATE is spread over
multiple columns, being
MOUNT_POINT_WAITINPUT_MOUNT_WAITINPUT_VOL_WAIT
INPUT_VOL_ACCESSOUTPUT_MOUNT_WAIT OUTPUT_VOL_WAIT
OUTPUT_VOL_ACCESS
Regard,
Karel
-Oorspronkelijk bericht-
...
ANRD asvol.c(1734): ThreadId55 Unknown result code (166) while
deleting a volume.
Anyone can shed some light on this?
Why the resistance to simply looking up the condition in the IBM database?
Just go to www.ibm.com, enter key text like while deleting a volume,
and you will find the
...
07/26/2003 05:18:11 ANRD xibf.c(664): Return code 87 encountered in
writing object 0.9041218 to export stream.
...
Kurt - Interesting problem. There may be a size issue with that object.
I would use SHow INVObject and SHow BFObject to try to identify
the
Usually I prefer to test using a large precompressed (zip/tar.gz) file and
not to disable compression. This is closer to the reality eliminating
possible (with low chance) problems due to different settings. It also
helps to reveal the expand after compression issues.
Pipe the output of tar+gzip
Hi David,
as i understood the openfile feature a snapshot is made for the whole
filesystem. Therefore there should be no problem with db-consistency between
db-files if they live all on the same volume. Since in my company our lotus
db files have proofen some kind of robustness (we only have a
Hi everyone!
I was wondering if anyone has had an issue when upgrading a windows client
from 5.1.5 to 5.1.6.0 with the point in time restore? Apparently we aren't
seing all of the files that should be there. The TSM server is on os/390
5.1.6.2. Any ideas? Thanks!
Joni Moyer
Systems
Hi Richard!
Indeed you're right! When the administrator logs on and drills down to the
directories in error he also receives an access denied message. So it
doesn't seem to be a TSM issue.
Thanks for your reply!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
There are two *guaranteed* ways to get a consistent
Domino database backup.
1.) Shut down the Domino server and back up the files.
(For example, use the BA client.)
2.) Use Data Protection for Domino, which uses the
Domino backup and restore APIs.
This can be done while the Domino
HI all
Last week we got page mismatch errors during database backups on our
production tsm server. In the end we restored from a previous good database
backup on the understanding that a dsmserv audit db would take too long.
However me being curious, I copied across the database dsm files when
Erik,
I'm on 4.2.1.12 (W2K) - and indeed it looks like APAR IC33841 sigh
Regards,
Rick
-Oorspronkelijk bericht-
Van: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]
Verzonden: 29 juli 2003 13:14
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Ehm.. what's that??
Hi Rick!
This looks like
Hi All
I have a strange problem. Today one of the servers we back up went down
(Win NT TSM Client 4.2.2.8). The NT guys have been busy at work fixing it
and part of this required that some files (including the TSM client on that
machine), needed to be installed again. Now, when we go to start the
All,
I am trying to run a 'dsmserv restore db volume=030265
devclass=359CLASS1' command and when I run it I get the following error:
ANR0200I Recovery Log assigned capacity is 3600 megabytes.
ANR0201I Database assigned capacity is 12004 megabytes.
Message number 8476 not available for language
try reactivating the policy set
Pauline
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Farren Minns
Sent: 29 July 2003 15:33
To: [EMAIL PROTECTED]
Subject: Win NT 4.2.2.8 Client Problem
Hi All
I have a strange problem. Today one of the servers we
I am trying to run a 'dsmserv restore db volume=030265
devclass=359CLASS1' command and when I run it I get the following error:
ANR0200I Recovery Log assigned capacity is 3600 megabytes.
ANR0201I Database assigned capacity is 12004 megabytes.
Message number 8476 not available for language AMENG
Hi TSM'ers
Has anybody out there gone from 3 years of nocollocation and then
changed to collocation for better restores. We are currently at 2-3+ TB of
info on 540 tapes (this is all in our 1 TAPEPOOL). We have about 410
scratch tapes and the uppers are worried about making the global
Thanks to all who responded. We will try testing with this process also to
see difference it shows in our performance tests.
Brenda
|-+
| | Zlatko Krastev |
| | [EMAIL PROTECTED]|
| | ET |
Remember that tar cmd writes only 10k bytes and dd cmd you gave 256k. So, tar cmd can
give the impression of poor performance. Also, FC address could be another factor when
used as sigle with mig from disk to tape. My 2 cents...
Gus
[EMAIL PROTECTED] 07/22/03 02:41PM
The test to move data
I did that about 2 years ago. Not quit as big as you at the time...
I did not move everybody at once. Moved AIX nodes then my Novell then my
NT/2000 then Oracle MS SQL nodes because that is the way I broke out my
storage pools.
Depending on what version of TSM you are on should be easier (if
How was your scratch tapes. Did you loose tapes to inefficiency? since
collocation will not be tape effecient. Also, did you create a new tape
pool (collocated) as you were migrating your backups? How bout timewise,
what kind of time line am I looking at?
Thank You,
Bill Rosette
Data
Stefan
Fair enough, and if you've made proven progress in your company of using the openfile
snapshot feature (which I personally have not yet played with) then good stuff!
My only experience (using the below configuration) was in an AIX Notes server
environment which was a) pretty large and
Has anybody out there gone from 3 years of nocollocation and then
changed to collocation for better restores. We are currently at 2-3+ TB of
info on 540 tapes (this is all in our 1 TAPEPOOL). We have about 410
scratch tapes and the uppers are worried about making the global switch to
Has anybody out there gone from 3 years of nocollocation and then
changed to collocation for better restores. We are currently at 2-3+ TB of
info on 540 tapes (this is all in our 1 TAPEPOOL). We have about 410
scratch tapes and the uppers are worried about making the global switch to
collocate
You can put a line in the dsm.opt that forces dsmc to give up some
processor time for something else. The line is processor (without the
quotes) with a number. My dsm.opt shows processor 2. This forces dsmc to
give up processor time for 10 sec. at a time. Even though you may not
see your
Yes I created new tape pools. It took me about 6 months? I let some happen
on its on through reclamation expiration. When I had some time I would
move data manually. Yes I lost some tapes because of small nodes but I
think it is definitely worth it. Especially during restores.
When did this
We are running V 4.2 on a NT platform and clients V 4.2 on NT and 2000 .
We have policies in place for never to expire down to 1 month . We have
info for the last 4 years . The server keeps on Dr Watson at night , may
it be that my databases is to big or not . ( Database sits at 150 GB and
Log at
Bill,
I made this change a while back without any real problems. I just enabled
collocation. It took some time but eventually my tapepool became
collocated. Also, TSM shouldn't crash because it ran out of scratch tapes.
Remember, if TSM runs out of scratch tapes it will find the least used tape
I agree, except that it's not necessarily one tape mount for each node.
If you have more clients than tape slots, you can still use collocation by
setting MAXSCRATCH on your storage pool to the number of tapes you want to
be used.
For example, if you have 200 clients, and set MAXSCRATCH to 100,
We just got TSM 5.1.6.5 running on Windows 2K server. Server configured
and started a couple of weeks ago and it has been running great. I've been
backing up clients, getting all the data on the server, so far so good,
until an hour ago.
I was backing up 3-4 clients at a time, when all of a
You need to go to the back of the Reference Guide and look at how to add log
space to the server. There is a procedure for recovering the server due to
overcommited log space.
I don't know the answer for the shadow device, but it really isn't the problem
here I believe.
Once the log is extended
Yes, that did it. Server is running again. The exact commands I had to do
were:
dsmfmt -log tempreclog 1000
dsmserv extend log tempreclog 1000
Thanks for the help,
Alex
--- ---
Alex Lazarevich | Systems Administrator | Imaging
Bill,
1. I think 1 tape pool is a bad idea. Not every machine needs a fast recovery and big
database backups won't benefit much from it. Split your nodes into different domains
and don't collocate the tape stgpool of one of them.
2. Insert your new collocated tape pool between disk and the
Looks like it may be a 3494 librar, in which case you'll have t edit the
devconfig file and make it libt=manual and mount the tape in the flashing
drive. For some reason the 3494 isn't supported at some/most levels of the
server for restore db processing. Found out the hard way at a disaster
Gordon,
Check to see if full-text indexing is running against those databases.
That's what tripped us up when we tried to do file-based backups of the
databases. Before the TSM client could finish sending the database, the
indexer would run and update the date/time stamp causing TSM to see that
46 matches
Mail list logo
