Re: Lotus Notes Non-TDP backups
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 as a new database. Now we use TDP/Domino, but we're in the process of rethinking our entire Notes architecture, in part due to backup/restore considerations. Tab Trepagnier TSM Administrator Laitram, LLC "We currently have over 160Gb of Notes mail databases that need to be backed up nightly. Due to incompatabilities with the Notes TDP, our version of TSM (v4.2.2.5) and the way compaction runs on our Notes servers, we have to use the normal Tivoli backup client to backup the mailboxes. It takes about 12 hours for all the databases to get backed up each night but the vast amount of this time seems to be spend trying and then retrying to send mailboxes to the TSM server."
Re: ANR9999D admabbk.c on restore DB
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 recovery test with a client. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Clarence Beukes Sent: Tuesday, July 29, 2003 11:28 AM To: [EMAIL PROTECTED] Subject: Re: ANRD admabbk.c on restore DB If your libtype is set to manual in your devconfig file, check that SHARED=NO is not part of the DEFINE LIBR statement.. Clarence Beukes Advisory IT Specialist - Tivoli Certified Consultant Geomar SSO Mid Range and Application Support Discipline Location: IBM Park Sandton, IA2G Tel: +27 (0) 11 302-6622 Cell: +27 (0) 82 573 5665 E-mail: [EMAIL PROTECTED]
Re: Collocation from nocollocation
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 current tapepool. Use maxscr as others have indicated. In the unlikely event that you ever completely fill up the collocated pool it wil automatically flow into the non-collocated one and no data will be lost. HTH Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 30/07/2003 1:22:53 >>> 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 switch to collocate will cause TSM to crash due to no scratch tapes. Also if there are any other gotcha's I would be greatly appreciated. Maybe even send you, some of our greatest pizza haha. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipients(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipients(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. ***
Re: Page Shadow File not valid
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 Technology Group Beckman Institute - University of Illinois [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu --- --- On Tue, 29 Jul 2003, Bob Booth - UIUC wrote: > 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 and you figure out what pinned the log and fix the > problem, you can get rid of the extra space you created. More than likely > the clients pinned the log and a database backup was not able to clear enough > space. You might need more recovery log space in the future. > > bob > > On Tue, Jul 29, 2003 at 02:31:12PM -0500, Alexander Lazarevich wrote: > > 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 sudden the client > > displayed a message: "Not enough space in the recovery log". I went to the > > server and it was hung. I tried to restart the server and I get the > > following errors: > > > > ANR0990I Server restart-recovery in progress. > > ANR0200I Recovery log assigned capacity is 8000 megabytes. > > ANR0201I Database assigned capacity is 4000 megabytes. > > ANR0306I Recovery log volume mount in progress. > > ANR0287W Contents of the page shadow file dbpgshdw.bdt are not valid. > > ANR0285I Database page shadowing started using file dbpgshdw.bdt. > > ANR0353I Recovery log analysis pass in progress. > > ANR0354I Recovery log redo pass in progress. > > ANR0355I Recovery log undo pass in progress. > > ANR0352I Transaction recovery complete. > > ANRD adminit.c(1269): ThreadId<0> Insufficient log space to update > > table Administrative.Attributes. > > > > So it seems the server can't read the dbpgshdw.bdt, yet it starts using it > > anyway, and then the server crashes due to insufficient log space. >
Re: Page Shadow File not valid
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 and you figure out what pinned the log and fix the problem, you can get rid of the extra space you created. More than likely the clients pinned the log and a database backup was not able to clear enough space. You might need more recovery log space in the future. bob On Tue, Jul 29, 2003 at 02:31:12PM -0500, Alexander Lazarevich wrote: > 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 sudden the client > displayed a message: "Not enough space in the recovery log". I went to the > server and it was hung. I tried to restart the server and I get the > following errors: > > ANR0990I Server restart-recovery in progress. > ANR0200I Recovery log assigned capacity is 8000 megabytes. > ANR0201I Database assigned capacity is 4000 megabytes. > ANR0306I Recovery log volume mount in progress. > ANR0287W Contents of the page shadow file dbpgshdw.bdt are not valid. > ANR0285I Database page shadowing started using file dbpgshdw.bdt. > ANR0353I Recovery log analysis pass in progress. > ANR0354I Recovery log redo pass in progress. > ANR0355I Recovery log undo pass in progress. > ANR0352I Transaction recovery complete. > ANRD adminit.c(1269): ThreadId<0> Insufficient log space to update > table Administrative.Attributes. > > So it seems the server can't read the dbpgshdw.bdt, yet it starts using it > anyway, and then the server crashes due to insufficient log space.
Page Shadow File not valid
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 sudden the client displayed a message: "Not enough space in the recovery log". I went to the server and it was hung. I tried to restart the server and I get the following errors: ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 8000 megabytes. ANR0201I Database assigned capacity is 4000 megabytes. ANR0306I Recovery log volume mount in progress. ANR0287W Contents of the page shadow file dbpgshdw.bdt are not valid. ANR0285I Database page shadowing started using file dbpgshdw.bdt. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANRD adminit.c(1269): ThreadId<0> Insufficient log space to update table Administrative.Attributes. So it seems the server can't read the dbpgshdw.bdt, yet it starts using it anyway, and then the server crashes due to insufficient log space. I've looked in the messages guide and it doesn't give any good instructions on what to do next, it just says: dbpg file is not valid, it happened because of blah blah, whatever. So, first thing I need to do is fix the server. How do I do that, as there are no instructions in the messages book? Then I need to find out why this happened, and prevent it from happening again. If I've lost the entire database that's okay, because everything is still backed up on our old server. But I can't have this happen in the future once the old server is offline. The server is installed on a mirrored system partition. Could it be that the logs don't want to exist on a mirror. If the mirror is trying to sync, would that corrupt the logs? Any help would be greatly appreciated. I'm now going to search google and check back here soon. Alex --- --- Alex Lazarevich | Systems Administrator | Imaging Technology Group Beckman Institute - University of Illinois [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu --- ---
Re: Collocation from nocollocation
Other collocation considerations: number of nodes in a storage pool mater and number of tape drives matter - migration takes longer because you mount more tapes if copy pool is not also collocated, reclaim take longer because more onsite tapes have to be mounted to reclaim a given tape if copy pool is collocated and nightly backups do not mostly fill a tape per node, you will daily offsite reclaim as many tapes as you send offsite collocation make a TREMENDOUS difference in restore times of servers (as opposed to individual files) DR can be a real D if data is not collocated
Re: Collocation from nocollocation
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, TSM will politely stack 2 clients per tape, so you would get 100 tape mounts during migration, not 200. If there are 2 clients on a tape, during a restore of clientA, it costs a trival amount of time to skip over clientB's data (after all, you will be skipping over some of clientA's inactive data anyway). The point of collocation is to save you TAPE MOUNTS on restores. By using MAXSCRATCH, you still get most of the benefits of collocation, without blowing the capacity of your tape library or requiring a zillion extra scratch tapes. You just have to keep an eye on the number of tapes in the pool and adjust MAXSCRATCH over time (as you add more data to your network) so that you always have a sufficient number of tapes in FILLING status to benefit from collocation. I have never seen any "gotchas" from turning collocation on whenever you want, as long as you keep an eye on MAXSCRATCH. All collocation does really is change the rules for the order in which tapes get filled: If collocation is off, and TSM has data to write (migration or reclamation), it looks for the least full FILLING tape. If it doesn't have a FILLING tape, it calls for a scratch tape, up to MAXSCRATCH. If MAXSCRATCH has already been reached, the process fails. If collocation is on, and TSM has data to write (migration or reclamation), it looks for the least full FILLING tape where there is ALREADY data stored for the client. If there is no FILLING tape with existing data for the client, it calls for a scratch tape, unless MAXSCRATCH has already been reached. If MAXSCRATCH has already been reached, it takes the least full FILLING tape available. If MAXSCRATCH has already been reached and there is no FILLING tape available, the process fails. That's all there is to it. And in an automated library, I have never seen any benefit to have MOUNT RETENTION set higher than 0. Wanda Prather Johns Hopkins University Applied Physics Laboratory 443-778-8769 "Intelligence has much less practical application than you'd think" - Dilbert/Scott Adams -Original Message- From: Rick Saylor [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 1:09 PM To: [EMAIL PROTECTED] Subject: Re: Collocation from nocollocation 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 and write on it. You loose collocation on that tape but TSM continues on. I can think of only two situations that running out of scratch tapes would be a major problem, 1-when a database backup is needed and 2-every tape in the storage pool has become full. With a little planning and monitoring you should be able to detect and take corrective action before TSM dies. Also, if your drive mount retention is set to high you'll have a bunch of idle tape drives. Remember, collocation will force a mount of at least one tape for each node. So, make sure that you don't use the default of 60 minutes. Cut it back to say 5 minutes so that the drives will be freed up quickly. Rick Saylor Austin Community College At 11:22 AM 7/29/2003 -0400, you wrote >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 switch to >collocate will cause TSM to crash due to no scratch tapes. Also if there >are any other gotcha's I would be greatly appreciated. Maybe even send >you, some of our greatest pizza haha. > >Thank You, >Bill Rosette >Data Center/IS/Papa Johns International >WWJD -- Rick SaylorAustin Community College Voice: (512)223-1182 Senior Systems Programmer 9101 Tuscany Way Fax: (512)223-1211 Information Services Austin, Texas 78754
Re: scheduled events status report
I don't know the official answer. But the ones I have seen, the client has started a backup, but never finished, and never reported the correct status back to the server. Check the client dsmsched.log to be sure. -Original Message- From: Hussein Hasan [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 5:02 AM To: [EMAIL PROTECTED] Subject: scheduled events status report 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 - - - 28-07-2003 19:10:00 28-07-2003 20:54:08 STOS1 STO_CR_AMNH Completed 28-07-2003 19:10:00 28-07-2003 20:37:02 WEBS1 WEB_IT_CPLX Completed 28-07-2003 19:10:01 29-07-2003 01:18:45 PERS1 PER_HQ_CNTR (?) 28-07-2003 19:10:08 28-07-2003 23:14:01 SIGS1 SIG_IT_CPLX Completed 28-07-2003 19:10:31 28-07-2003 21:48:06 ARCHQS1 ARC_HQ_CNTR Completed Thanks alot in advance This e-mail Message is Intended for the named Recipient Only. It May be Privileged and/or Confidential. If you are NOT the Intended Recipient of this e-mail then you Should NOT Copy it or Use it for any Purpose, Nor Disclose its Contents to any Person. You Should Contact The Housing Bank For Trade and Finance as Shown above So that we can Take Appropriate Action
Re: export TSM server 4.1.4.1 fails
This may not be your problem, but I have seen cases with EXPORT where where a relatively simple problem will result in the (totally unhelpful) "error encountered accessing data storage" message. Try the obvious - make sure the drives in DLTCLASS1 are online; make sure those tape volumes are checked into the tape library. If I were you I would try starting the export again, to a scratch volume. Try another function like a DB incremental backup to DLTCLASS1, just to make sure that those drives are accessible. Also try starting an EXPORT NODE of a single client's filedata to see if you get the same error. And if DLTCLASS1 happens to really be a server-to-server class, rather than physical tape, check for drive availability on the target server. Some of those things may help you find the problem. If not, sorry... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 2:10 AM To: [EMAIL PROTECTED] Subject: export TSM server 4.1.4.1 fails 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), but now the export fails with following messages in the activity log: 07/26/2003 05:18:11 ANRD xibf.c(664): Return code 87 encountered in writing object 0.9041218 to export stream. 07/26/2003 05:18:11 ANR0661E EXPORT SERVER: Internal error encountered in accessing data storage. 07/26/2003 05:18:24 ANR0794E EXPORT SERVER: Processing terminated abnormally - error accessing data storage. 07/26/2003 05:18:24 ANR0620I EXPORT SERVER: Copied 9 domain(s). 07/26/2003 05:18:24 ANR0621I EXPORT SERVER: Copied 18 policy sets. 07/26/2003 05:18:24 ANR0622I EXPORT SERVER: Copied 60 management classes. 07/26/2003 05:18:24 ANR0623I EXPORT SERVER: Copied 64 copy groups. 07/26/2003 05:18:24 ANR0624I EXPORT SERVER: Copied 110 schedules. 07/26/2003 05:18:24 ANR0625I EXPORT SERVER: Copied 14 administrators. 07/26/2003 05:18:24 ANR0626I EXPORT SERVER: Copied 28 node definitions. 07/26/2003 05:18:24 ANR0627I EXPORT SERVER: Copied 85 file space 0 archive files, 344120 backup files, and 0 space managed files. 07/26/2003 05:18:24 ANR0656W EXPORT SERVER: Skipped 0 archive files, 1 backup files, and 0 space managed files. 07/26/2003 05:18:24 ANR0630I EXPORT SERVER: Copied 27726403 kilobytes of data. 07/26/2003 05:18:24 ANR0611I EXPORT SERVER started by ADMIN as process 76 has ended. 07/26/2003 05:18:24 ANR0986I Process 76 for EXPORT SERVER running in the BACKGROUND processed 344508 items for a total of 28,391,836,844 bytes with a completion state of FAILURE at 05:18:24. Does anybody have an idea what is going wrong here? What is the mentioned return code 87? Is this a known APAR fixed in a later release of TSM (the client didn't want an upgrade yet). Thanks for any hints, guidelines how to solve this problem! regards, Kurt Beyers
Re: Collocation from nocollocation
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 and write on it. You loose collocation on that tape but TSM continues on. I can think of only two situations that running out of scratch tapes would be a major problem, 1-when a database backup is needed and 2-every tape in the storage pool has become full. With a little planning and monitoring you should be able to detect and take corrective action before TSM dies. Also, if your drive mount retention is set to high you'll have a bunch of idle tape drives. Remember, collocation will force a mount of at least one tape for each node. So, make sure that you don't use the default of 60 minutes. Cut it back to say 5 minutes so that the drives will be freed up quickly. Rick Saylor Austin Community College At 11:22 AM 7/29/2003 -0400, you wrote 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 switch to collocate will cause TSM to crash due to no scratch tapes. Also if there are any other gotcha's I would be greatly appreciated. Maybe even send you, some of our greatest pizza haha. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD -- Rick SaylorAustin Community College Voice: (512)223-1182 Senior Systems Programmer 9101 Tuscany Way Fax: (512)223-1211 Information Services Austin, Texas 78754
Need info on the TSM database
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 10GB ) . We also backup SQL TransLogs every 30min's and one full database backup at night . May it be that we need to start with a new backup server or what may we do to fix this . ALL HELP and INFO will HELP Hugo Badenhorst [EMAIL PROTECTED] 011 285 5587 This email message and the content are subject to the disclaimer displayed at the following link. http://www.hollard.co.za/legal/disclaimer.htm
Re: Collocation from nocollocation
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 I think I started with about half the number of scratch tapes as I had in my tape pool. Then as time went on I added tapes as needed. I never documented how tapes I started with & ended with -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 --- -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 11:53 AM To: [EMAIL PROTECTED] 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 Center/IS/Papa Johns International WWJD "Kamp, Bruce" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: cc: Dist StorSubject: Re: Collocation from nocollocation Manager" <[EMAIL PROTECTED] .EDU> 07/29/2003 11:38 AM Please respond to "ADSM: Dist Stor Manager" 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 you are high enough to have move nodedata command). It was no fun because the tapes that had more then 1 node on it I had to move it to a temporary disk pool then the final tape pool. One thing you will gain is all your new tapes will be nice & compacted! Hope this helps! -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 --- -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 11:23 AM To: [EMAIL PROTECTED] 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 switch to collocate will cause TSM to crash due to no scratch tapes. Also if there are any other gotcha's I would be greatly appreciated. Maybe even send you, some of our greatest pizza haha. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD
Re: High Utilization on Netware Server
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 utilization go down, you can look at the highest processor threads and watch dsmc go down in the list, letting other applications have some time. I am also looking into finding some way that I can lower the priority of dsmc. With regards, Dave Marsh Scottsdale Healthcare Information Services 480.675.4395 -Original Message- From: Anwer Adil [mailto:[EMAIL PROTECTED] Sent: Sunday, July 27, 2003 3:22 AM To: [EMAIL PROTECTED] Subject: High Utilization on Netware Server I recently upgraded a couple of my servers to Netware 6. During backup, the processor utilization pegs at 100%. The tsm client version on the servers is Version 5 Release 1, Level 0. Compression on all the volumes is off therefore I have the following settings in the dsm.opt file: COMPRESSION YES COMPRESSALWAYS NO Please help.
Re: Collocation from nocollocation
> 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 will cause TSM to crash due to no scratch tapes. Bill, I made this move last year myself. The main thing I had to consider was how many scratch tapes I had, and extra library slots available, compared to the number of nodes that were now going to now grab tapes. I don't know the inner working of TSM related but I can say I planned for the worst. I may have had any number of tapes in filling status but I went on the assumption that none were going to be used once co-location was turned on. For me that meant 180 tapes off the top. I also assumed that over time reclamation would clean things up and free up tapes, which it did. For us that was ok because I also had around 400 blank tapes to work from. Something I've had to keep an eye out for since then though is tapes going unavailable/read-only. If that happens then the affected node will automatically grab a new tape. In cases like that I always move the data to free up that extra tape. The bottom line is it went off without a hitch. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Collocation from nocollocation
> 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 will cause TSM to crash due to no scratch tapes. Also if there >are any other gotcha's I would be greatly appreciated. Maybe even send >you, some of our greatest pizza haha. It's no sweat if you simply turn it on and let collocation happen with just new data, as that's gradual and you can casually watch the effects on your tape supply. In any case, it's well worth doing for the primary stgpool. Got calzones? Richard Sims, BU
FW: Lotus Notes Non-TDP backups
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 b) pretty active. In the amount of time taken for the ba client to have piped a 100MB or larger (sometimes well into GB for some users) .nsf mailfile or database to its TSM server it would the majority of the time have gotten written to and caused an inconsistency, which for a user's mailfile backup just wasn't worth the risk. Nor could we afford downtime on the live service. Admittedly, it certainly wasn't a cheap solution, requiring lots of extra hardware and support, but our guys looked into using TDP for Domino and it just wasn't even slightly feasible in the size of our environment at the time (using 3494/3590 and local SSA disk as we were), with projections for simple restores taking *so* many tape mounts and *so* much time. So, in summary - whatever works for your scale of environment is good, but just ensure that *plenty* of testing is carried out and carries on being carried out to ensure that your restores are good ones. After all how many times have we said to our customers, "Oh yes, the backups are running fine!" and then muttered under our breath, "it's the restores that are going to be the problem..." ;o) All the best, David (now using Outlook instead of Notes!) McClelland Global Management Systems Reuters Ltd -Original Message- From: Stefan Holzwarth [mailto:[EMAIL PROTECTED] Sent: 29 July 2003 13:49 To: [EMAIL PROTECTED] Subject: AW: Lotus Notes Non-TDP backups 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 small domino environment) i can not total agree with your absolute no to this topic. Domino uses an underlaying simple database that has to maintain some robustnes towards sudden failures like power off, lost connectivity to the db on a networkshare or some bluescreens. From the other side if an openfile agent waits (configurable) for seconds for inactivity there should not occur a cut through a write operation. I'm sure there are better and more saver ways doing backups of Domino, but most need more efforts or resources. Kind regards, Stefan Holzwarth -Ursprüngliche Nachricht- Von: David McClelland [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. Juli 2003 10:44 An: [EMAIL PROTECTED] Betreff: Re: Lotus Notes Non-TDP backups 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 have repercussions elsewhere in the db and before you know it you won't be able to open up the .nsf at all, and will get 'b-tree structure invalid' or similar complaints from Notes. You need to have the Notes server process 'down' in order to quiece the databases and prevent them from being written to before backing them up. The *usual* way of handling Notes backups without using TDP is to use a 'backup' server - the concept works like this: You have a separate Notes server (i.e. a 'backup Notes server) which contains replicas of the databases on the live Notes servers. Using Notes replication, all changes to the live databases are replicated to the replicas on the backup server. At a time controlled by you, you take the Notes server process down on the backup server (as no users connect directly to the backup Notes server, there will be no outage) and then perform the backups of the now quiesced .nsf files using the normal TSM BA client. Once the backup is complete, bring up the Notes server on the backup server and begin replication with the live servers to the backup .nsf's up to date again. Depending upon hardware, you can have many live Notes server's worth of .nsf's contained on a single backup Notes server - just ensure you have enough time to replicate the data from live to backup server. In terms of recoveries, as the backup Notes server is down during backups, you might want to have an additional Notes partition somewhere on a backup server which you can use as a 'recovery server' - a Notes server which is *always* up, regardless of whether a backup is taking place. Users can connect to this directly and pull back any recovered .nsf databases, or even just documents from a .nsf. Hope this helps :o) David McClelland Global Management Systems Reuters Ltd -Original Message- From: Stefan Holzwarth [mailto:[EMAIL PROTECTED] Sent: 29 July 2003 07:06
Re: Collocation from nocollocation
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 Center/IS/Papa Johns International WWJD "Kamp, Bruce" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: cc: Dist StorSubject: Re: Collocation from nocollocation Manager" <[EMAIL PROTECTED] .EDU> 07/29/2003 11:38 AM Please respond to "ADSM: Dist Stor Manager" 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 you are high enough to have move nodedata command). It was no fun because the tapes that had more then 1 node on it I had to move it to a temporary disk pool then the final tape pool. One thing you will gain is all your new tapes will be nice & compacted! Hope this helps! -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 --- -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 11:23 AM To: [EMAIL PROTECTED] 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 switch to collocate will cause TSM to crash due to no scratch tapes. Also if there are any other gotcha's I would be greatly appreciated. Maybe even send you, some of our greatest pizza haha. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD
Re: Collocation from nocollocation
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 you are high enough to have move nodedata command). It was no fun because the tapes that had more then 1 node on it I had to move it to a temporary disk pool then the final tape pool. One thing you will gain is all your new tapes will be nice & compacted! Hope this helps! -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 --- -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 11:23 AM To: [EMAIL PROTECTED] 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 switch to collocate will cause TSM to crash due to no scratch tapes. Also if there are any other gotcha's I would be greatly appreciated. Maybe even send you, some of our greatest pizza haha. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD
Re: Tape performance
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 from the operating system was just a 10GB file, although it was all zero's. The tape performance on TSM was achieved by doing a disk to tape. We took the ratings from doing a backup storagepool to tape. We tried it with storagepools that had filesystems and databases, the results are fairly close to the same. Our disk is on the SAN so we do not go through the network. Here are results from some new tests we just performed today. (Our drives are 9840B) DD Test with CBN and RMT drivers # mt -f /dev/rmt/6cbn status StorageTek 9840B tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 file no= 0 block no= 0 # time dd if=/dev/zero of=/dev/rmt/6cbn bs=256k count=4 4+0 records in 4+0 records out RESULT: 38.78 MB/Sec real4m24.29s user0m0.17s sys 1m13.05s # time dd if=/dev/zero of=/dev/rmt/15mt bs=256k count=4 4+0 records in 4+0 records out real5m15.57s user0m0.19s sys 1m50.37s # RESULT: 32.5 MB/Sec Here is a core file used to test performance, with 453 MBytes, it take average of 2.2 minutes... # time tar -cvf /dev/rmt/14mt core a core 453736K real2m22.37s user0m0.44s sys 0m28.28s # time tar -cvf /dev/rmt/14mt core a core 453736K real2m19.16s user0m0.25s sys 0m28.79s |-+> | | Richard Sims | | | <[EMAIL PROTECTED]> | | || | | 07/22/2003 12:23 | | | PM | | | Please respond to| | | "ADSM: Dist Stor | | | Manager" | | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Tape performance | >--| >I am wondering if there is something in TSM that throttles the tape >performance we should be getting. I can do a dd test from the operating >system to the tape drive and with that receive 2 GB per minute (32 MB/sec) >but when I do a test through TSM, I only get 1 GB per minute. > >My environment is: >TSM 5.7.0 on Solaris 8 >Server: Sunfire 880 >Tape drives are 9840 Fibre attached. > >As a result, we are questioning the value of putting in the more expensive >tape drives when we can't seem to pump the data through as expected. > >Any ideas of what I might look at would be appreciated. Now, why did you not tell us what the test was? :-) Perspective and context is everything when trying to respond to postings. You very much did the right thing in getting isolated benchmark numbers first. Was the test a single, very large file so as to keep database updating out of the picture, rather than many small files? Was the client co-resident on the server system as to keep network contention out of the picture? All them factors. Richard Sims, BU
Re: Tape performance
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> | | || | | 07/29/2003 07:17 | | | AM | | | Please respond to| | | "ADSM: Dist Stor | | | Manager" | | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Tape performance | >--| 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 to a large enough file and perform the `dd`-test again. I was able to fully load up to two FC-attached LTO-1 drives from a single system with or without compression. Maybe to utilize successfully several LTO-2 drives would be a real challenge :-() Zlatko Krastev IT Consultant Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 22.07.2003 22:19 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Tape performance >>I am wondering if there is something in TSM that throttles the tape >>performance we should be getting. I can do a dd test from the operating >>system to the tape drive and with that receive 2 GB per minute (32 MB/sec) >>but when I do a test through TSM, I only get 1 GB per minute. >The test to move data from the operating system was just a 10GB file, >although it was all zero's. ... Thanks, that extra info helps a lot... The T9840B FICON Tape Drive Specifications that I see on the vendor web site quote "Performance, native 19 MB/sec". I thought the 32 MB/s was a high number. I suspect that you did not disable tape drive compression in your all-zero's test, and so ended up with a number which was a great test of your FC, but not the drive->media. In context, your ~16 MB/s TSM speed seems excellent, then. I'd be happy with that number. Customers who also have 9840B drives might want to chime in on their experiences. Richard Sims, BU
Re: Collocation from nocollocation
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 switch to collocate will cause TSM to crash due to no scratch tapes. Also if there are any other gotcha's I would be greatly appreciated. Maybe even send you, some of our greatest pizza haha. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD
Re: ANR9999D admabbk.c on restore DB
If your libtype is set to manual in your devconfig file, check that SHARED=NO is not part of the DEFINE LIBR statement.. Clarence Beukes Advisory IT Specialist - Tivoli Certified Consultant Geomar SSO Mid Range and Application Support Discipline Location: IBM Park Sandton, IA2G Tel: +27 (0) 11 302-6622 Cell: +27 (0) 82 573 5665 E-mail: [EMAIL PROTECTED]
Re: ANR9999D admabbk.c on restore DB
>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 >> >ANRD admdbbk.c(4216) : Error 272 creating device class 359CLASS1 > >I have tried several variants of this command to no avail. Any ideas? Message 8476 explains that the operation failed because the libtype of the library is not supported for the operation. Investigate your device configuration file. Richard Sims, BU
Re: Win NT 4.2.2.8 Client Problem
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 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 BA GUI, we get the message:- |--+--| | ANS| The active policy set does not contain any backup copy groups. | | 126| If you continue with the incremental backup, any currently | | 2E | backed up files are deactivated on the server and assigned the | | | Backup Grace Period. | |--+--| I have looked on the TSM Server (4.2.2.12 running on Solaris 2.7) and can see that the active policy set that the client is bound to does indeed contain a backup copy group. In fact, nothing has changed on the server at all. So what could have happened here? But there is more, I hope you are following me. Whilst the NT guys were fixing the server, they also set up another server and put the name of the original node in the DSM.SYS file on the new machine. We then started a restore of the old machine onto the new one (but of course to TSM it looked like the original). However, having looked at the setting for the new machine that was registered to TSM, I can see that it was attached to a different policy domain. Could this have caused TSM to get confused somewhere along the line? I'm sorry if this all seems a little confusing, but no one is more confused that me right now. The client in question will be given a reboot later this afternoon, and I'd like to think that this would cure it (for some reason). If not, we have a massive backup to do all over again :) If anyone has any advice, then I'd love to hear it. Many thanks in advance Farren Minns - TSM & Solaris System Admin John Wiley & Sons Ltd * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
ANR9999D admabbk.c on restore DB
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 AMENG >> ANRD admdbbk.c(4216) : Error 272 creating device class 359CLASS1 I have tried several variants of this command to no avail. Any ideas? TSM 4.1.4.0 on Windows NT 4.0 Joshua Bassi
Win NT 4.2.2.8 Client Problem
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 BA GUI, we get the message:- |--+--| | ANS| The active policy set does not contain any backup copy groups. | | 126| If you continue with the incremental backup, any currently | | 2E | backed up files are deactivated on the server and assigned the | | | Backup Grace Period. | |--+--| I have looked on the TSM Server (4.2.2.12 running on Solaris 2.7) and can see that the active policy set that the client is bound to does indeed contain a backup copy group. In fact, nothing has changed on the server at all. So what could have happened here? But there is more, I hope you are following me. Whilst the NT guys were fixing the server, they also set up another server and put the name of the original node in the DSM.SYS file on the new machine. We then started a restore of the old machine onto the new one (but of course to TSM it looked like the original). However, having looked at the setting for the new machine that was registered to TSM, I can see that it was attached to a different policy domain. Could this have caused TSM to get confused somewhere along the line? I'm sorry if this all seems a little confusing, but no one is more confused that me right now. The client in question will be given a reboot later this afternoon, and I'd like to think that this would cure it (for some reason). If not, we have a massive backup to do all over again :) If anyone has any advice, then I'd love to hear it. Many thanks in advance Farren Minns - TSM & Solaris System Admin John Wiley & Sons Ltd * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: Ehm.. what's that??
Erik, I'm on 4.2.1.12 (W2K) - and indeed it looks like APAR IC33841 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 APAR IC33841. Which server level are you running? Since the APAR is closed, it's probably fixed in 5.1.7.0. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Rick Harderwijk [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 12:49 To: [EMAIL PROTECTED] Subject: Ehm.. what's that?? 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 get 'Internal server error detected'. The log gives me some more information: ANRD asvol.c(1734): ThreadId<55> Unknown result code (166) while deleting a volume. Anyone can shed some light on this? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED] ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
expected output from dsmserv audit db
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 corrupt from our production server to our DR server. Now, on the DR server I'm trying to run a database audit, just to find out how long it would have taken. I have tried dsmserv audit db with fix=yes and no and get the same kind of thing. Basically I get nothing telling me that a audit is taking place. It just seems to bring up TSM as normal. TSM is version 5.1.5.4 I would have expected it to show me the database pages being audited ? Has anyone got the output from their database audit for me to compare against mine? TIA _ On the move? Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile
Re: AW: Lotus Notes Non-TDP backups
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 Server is up even if the database is changing during backup. Even with the new Open File support, if a database is "open", you cannot absolutely guarantee that the database will be in a consistant state during the point in time the "freeze" happens. That is because there could be in-memory operations that would make it consistent. The Domino transaction logging introduced in Domino 5 make sure that the database can be made consistent even after a crash. Thanks, Del > 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 small domino > environment) i can not total agree with your absolute no to this topic. > Domino uses an underlaying simple database that has to maintain some > robustnes towards sudden failures like power off, lost connectivity to the > db on a networkshare or some bluescreens. From the other side if an openfile > agent waits (configurable) for seconds for inactivity there should not occur > a cut through a write operation. > I'm sure there are better and more saver ways doing backups of Domino, but > most need more efforts or resources.
Re: Windows client error rc=106
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- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2003 13:19 To: [EMAIL PROTECTED] Subject: Re: Windows client error rc=106 >PrivIncrFileSpace: Received rc=106 from fioGetDirEntries: ... >Anybody seen this error before? Eric - You can always check http://people.bu.edu/rbs/ADSM.QuickFacts which notes that this can be a permissions issue. Richard Sims, BU ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
nt client upgraded, point in time restore fails
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 Programmer [EMAIL PROTECTED] (717)975-8338
AW: Lotus Notes Non-TDP backups
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 small domino environment) i can not total agree with your absolute no to this topic. Domino uses an underlaying simple database that has to maintain some robustnes towards sudden failures like power off, lost connectivity to the db on a networkshare or some bluescreens. From the other side if an openfile agent waits (configurable) for seconds for inactivity there should not occur a cut through a write operation. I'm sure there are better and more saver ways doing backups of Domino, but most need more efforts or resources. Kind regards, Stefan Holzwarth -Ursprüngliche Nachricht- Von: David McClelland [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. Juli 2003 10:44 An: [EMAIL PROTECTED] Betreff: Re: Lotus Notes Non-TDP backups 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 have repercussions elsewhere in the db and before you know it you won't be able to open up the .nsf at all, and will get 'b-tree structure invalid' or similar complaints from Notes. You need to have the Notes server process 'down' in order to quiece the databases and prevent them from being written to before backing them up. The *usual* way of handling Notes backups without using TDP is to use a 'backup' server - the concept works like this: You have a separate Notes server (i.e. a 'backup Notes server) which contains replicas of the databases on the live Notes servers. Using Notes replication, all changes to the live databases are replicated to the replicas on the backup server. At a time controlled by you, you take the Notes server process down on the backup server (as no users connect directly to the backup Notes server, there will be no outage) and then perform the backups of the now quiesced .nsf files using the normal TSM BA client. Once the backup is complete, bring up the Notes server on the backup server and begin replication with the live servers to the backup .nsf's up to date again. Depending upon hardware, you can have many live Notes server's worth of .nsf's contained on a single backup Notes server - just ensure you have enough time to replicate the data from live to backup server. In terms of recoveries, as the backup Notes server is down during backups, you might want to have an additional Notes partition somewhere on a backup server which you can use as a 'recovery server' - a Notes server which is *always* up, regardless of whether a backup is taking place. Users can connect to this directly and pull back any recovered .nsf databases, or even just documents from a .nsf. Hope this helps :o) David McClelland Global Management Systems Reuters Ltd -Original Message- From: Stefan Holzwarth [mailto:[EMAIL PROTECTED] Sent: 29 July 2003 07:06 To: [EMAIL PROTECTED] Subject: AW: Lotus Notes Non-TDP backups 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 160Gb of Notes mail databases that need to be backed up nightly. Due to incompatabilities with the Notes TDP, our version of TSM (v4.2.2.5) and the way compaction runs on our Notes servers, we have to use the normal Tivoli backup client to backup the mailboxes. It takes about 12 hours for all the databases to get backed up each night but the vast amount of this time seems to be spend trying and then retrying to send mailboxes to the TSM server. A typical schedule log looks like this: 28-07-2003 19:51:53 Retry # 2 Normal File--> 157,548,544 \\sdbo5211\d$\notes\data\mail\beggsa.nsf [Sent] 28-07-2003 19:52:28 Normal File-->70,778,880 \\sdbo5211\d$\notes\data\mail\bingleyj.nsf [Sent] 28-07-2003 19:54:05 Retry # 1 Normal File--> 349,437,952 \\sdbo5211\d$\notes\data\mail\bignasck.nsf [Sent] 28-07-2003 19:55:10 Normal File--> 131,072,000 \\sdbo5211\d$\notes\data\mail\Bishnic.nsf Changed 28-07-2003 19:56:58 Normal File--> 265,289,728 \\sdbo5211\d$\notes\data\mail\bellm.nsf [Sent] 28-07-2003 19:58:08 Retry # 1 Normal File--> 131,072,000 \\sdbo5211\d$\notes\data\mail\Bishnic.nsf [Sent] 28-07-2003 20:00:46 Normal File--> 387,186,688 \\sdbo5211\d$\notes\data\mail\BLACKAD.NSF Changed 28-07-2003 20:03:52 Normal File--> 367,263,744 \\sdbo5211\d$\notes\data\mail\BERNECKC.NSF Changed 28-07-2003 20:06:18 Retry # 1 Normal File-->
Re: Tape performance
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 to a large enough file and perform the `dd`-test again. I was able to fully load up to two FC-attached LTO-1 drives from a single system with or without compression. Maybe to utilize successfully several LTO-2 drives would be a real challenge :-() Zlatko Krastev IT Consultant Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 22.07.2003 22:19 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Tape performance >>I am wondering if there is something in TSM that throttles the tape >>performance we should be getting. I can do a dd test from the operating >>system to the tape drive and with that receive 2 GB per minute (32 MB/sec) >>but when I do a test through TSM, I only get 1 GB per minute. >The test to move data from the operating system was just a 10GB file, >although it was all zero's. ... Thanks, that extra info helps a lot... The T9840B FICON Tape Drive Specifications that I see on the vendor web site quote "Performance, native 19 MB/sec". I thought the 32 MB/s was a high number. I suspect that you did not disable tape drive compression in your all-zero's test, and so ended up with a number which was a great test of your FC, but not the drive->media. In context, your ~16 MB/s TSM speed seems excellent, then. I'd be happy with that number. Customers who also have 9840B drives might want to chime in on their experiences. Richard Sims, BU
Re: export TSM server 4.1.4.1 fails
... >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 file involved, to examine its evidenced attributes and reasonableness. You may be able to have the client expire it out of existence by multiple Selective backups or the like to get it out of the way. Richard Sims, BU
Re: Ehm.. what's that??
... >ANRD asvol.c(1734): ThreadId<55> 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 answer to such error conditions. Remember that the ANRD error messages are essentially diagnostic catch-alls, meant to expose fringe conditions for appropriate handling. Richard Sims, BU
Re: Ehm.. what's that??
Hi Rick! This looks like APAR IC33841. Which server level are you running? Since the APAR is closed, it's probably fixed in 5.1.7.0. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Rick Harderwijk [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 12:49 To: [EMAIL PROTECTED] Subject: Ehm.. what's that?? 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 get 'Internal server error detected'. The log gives me some more information: ANRD asvol.c(1734): ThreadId<55> Unknown result code (166) while deleting a volume. Anyone can shed some light on this? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED] ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Multiple mounts for reclaimation/stgp backup
Hi Brenda! Well, not really... There is no maxproc parameter for the update stgpool command. As far as I know, you cannot reclaim more that one tape at a time. Not automatically that is, you can start an extra move data reconstruct=yes, but that's merely a bypass. I guess the fact that you can only run one reclamation at a time is a build-in limitation of TSM. Maybe to be 'fixed' in a future release? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Brenda Collins [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 14:38 To: [EMAIL PROTECTED] Subject: Re: Multiple mounts for reclaimation/stgp backup maxpr=# maximum processes = # Add this to your command to start reclamation. Brenda |-+> | | Gordon Woodward | | | | | || | | 07/28/2003 02:09 | | | AM | | | Please respond to| | | "ADSM: Dist Stor | | | Manager" | | || |-+> >--- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Multiple mounts for reclaimation/stgp backup | >--- ---| Just wondering what settings need to be changed to allow more then two drives to be used in a tape stgp reclaimation? I'd like to be able to reclaim more then one tape at a time per storage pool, such as two tapes but not sure how to do this. Our LTO device class in TSM is set to MOUNT LIMIT = DRIVES, should this be changed? There is 4 LTO drives in our library at present. Also we have offsite vaulting happening on a 2nd TSM server located at our DR site. Is there anyway to increase the amount of sessions our main TSM server uses to reclaim offsite volumes and send backup data to our DR server as it only every uses one session when reclaiming our OFFSITE storage pool or send data to it. Thanks in advance. Gordon Woodward Senior Support Analyst Deutsche Asset Management (Australia) Limited IT Infrastructure Ph. (02) 9249 9648 [EMAIL PROTECTED] -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Session table change
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- > Van: Aldrich, Jamie [mailto:[EMAIL PROTECTED] > Verzonden: dinsdag 29 juli 2003 12:37 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: Session table change > > > 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 new > and what went away from the tables. Any help would be > greatly appreciated. > > Thanks, > Jamie Aldrich > Verizon > > -Original Message- > From: Karel Bos [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 23, 2003 10:30 AM > To: [EMAIL PROTECTED] > Subject: Re: Session table change > > > I think STATE, but correct me if I am wrong... > > Regard, > > Karel > > > -Oorspronkelijk bericht- > > Van: Aldrich, Jamie [mailto:[EMAIL PROTECTED] > > Verzonden: woensdag 23 juli 2003 17:19 > > Aan: [EMAIL PROTECTED] > > Onderwerp: Session table change > > > > > > I have noticed that the SESSIONS table has changed > > from TSM v4.1 to TSM v5.1. I do not see MEDIA_STATE anymore. > > Does anyone know what that translates to in the new table > > definitions? > > > > Thanks, > > Jamie Aldrich > > Verizon > > >
Ehm.. what's that??
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 get 'Internal server error detected'. The log gives me some more information: ANRD asvol.c(1734): ThreadId<55> Unknown result code (166) while deleting a volume. Anyone can shed some light on this? Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED]
Re: Error in deleting filespace
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: Error in deleting filespace Hi Eric, Here is TSM server 5.1.5.0. Thanks, Zosi -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 1:45 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace 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 Hi, The TSM server 5.1 on AIX 5 and TSM client 5.1.5 on Windows 2000. Thanks, Zosi Noriega -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi Zosi! When posting a question to this list, please supply your TSM software level, maybe then we are able to assist you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 06:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table "Expiring.Objects". 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId<79> Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed,
Re: Session table change
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 new and what went away from the tables. Any help would be greatly appreciated. Thanks, Jamie Aldrich Verizon -Original Message- From: Karel Bos [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 10:30 AM To: [EMAIL PROTECTED] Subject: Re: Session table change I think STATE, but correct me if I am wrong... Regard, Karel > -Oorspronkelijk bericht- > Van: Aldrich, Jamie [mailto:[EMAIL PROTECTED] > Verzonden: woensdag 23 juli 2003 17:19 > Aan: [EMAIL PROTECTED] > Onderwerp: Session table change > > > I have noticed that the SESSIONS table has changed > from TSM v4.1 to TSM v5.1. I do not see MEDIA_STATE anymore. > Does anyone know what that translates to in the new table > definitions? > > Thanks, > Jamie Aldrich > Verizon >
Re: Empty volume does not return to scratch?
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 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: BASKET>q vol stat=empty f=d > > > Volume Status: Empty > Access: Read/Write > Pct. Reclaimable Space: 0.0 > -->> Scratch Volume?: Yes<<-- >In Error State?: No > > Am I missing something here? > yes: Volume Status: Empty Volumes that were taken from the scratch pool cannot be empty and defined in a storagepool... > Regards, > > Rick > -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdamhttp://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: Empty volume does not return to scratch?
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: BASKET>q vol stat=empty f=d > > > Volume Status: Empty > Access: Read/Write > Pct. Reclaimable Space: 0.0 > -->> Scratch Volume?: Yes<<-- >In Error State?: No > > Am I missing something here? > yes: Volume Status: Empty Volumes that were taken from the scratch pool cannot be empty and defined in a storagepool... > Regards, > > Rick > -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdamhttp://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: Empty volume does not return to scratch?
Remco, I missed the discussion, but this is what the output you gave said: tsm: BASKET>q vol stat=empty f=d Volume Status: Empty Access: Read/Write Pct. Reclaimable Space: 0.0 -->> Scratch Volume?: Yes<<-- In Error State?: No Am I missing something here? Regards, Rick -Oorspronkelijk bericht- Van: Remco Post [mailto:[EMAIL PROTECTED] Verzonden: 29 juli 2003 12:12 Aan: [EMAIL PROTECTED] Onderwerp: Empty volume does not return to scratch? Hi all, a few weeks back we had a discussion on empty volumes not returning to scratch, well, here is an example. tsm: BASKET>q vol stat=empty f=d Volume Name: U00122 Storage Pool Name: SANPOOL Device Class Name: 3494-3590 Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Read/Write Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 5 Write Pass Number: 0 Approx. Date Last Written: Approx. Date Last Read: Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): Last Update Date/Time: 07/27/03 11:11:32 This is with server level 5.1.6.4 on AIX 4.3.3. What is more surprising is that the last update of this volume was not reclamation, but allocation of this volume in the storagepool. It has been mounted for over two hours at that time, probably due to space-recamation running at that time, but apperently, there was never one bit written. Now I'm wondering, how could that be? The actlog shows: 07/27/03 11:11:32 ANR8337I 3590 volume U00122 mounted in drive 3590-6 (/dev/rmt6). 07/27/03 11:11:32 ANR1340I Scratch volume U00122 is now defined in storage pool SANPOOL. 07/27/03 11:11:58 ANE4991I (Session: 12641, Node: BASKET-C) API ANE4991 rmt0=leeg rmt1=leeg rmt2=leeg rmt3=leeg rmt4=leeg rmt5=leeg rmt6=U00122 (lots more ANE4991I here, this is generated by a applcation developped in house) 07/27/03 13:17:37 ANR8325I Dismounting volume U00122 - 2 minute mount retention expired. 07/27/03 13:17:38 ANE4991I (Session: 12911, Node: BASKET-C) API ANE4991 rmt0=leeg rmt1=000809 rmt2=000689 rmt3=leeg rmt4=leeg rmt5=U00261 rmt6=U00122 07/27/03 13:17:49 ANR8336I Verifying label of 3590 volume U00122 in drive 3590-6 (/dev/rmt6). 07/27/03 13:18:44 ANE4991I (Session: 12913, Node: BASKET-C) API ANE4991 rmt0=leeg rmt1=000809 rmt2=000689 rmt3=leeg rmt4=leeg rmt5=U00261 rmt6=U00122 07/27/03 13:18:47 ANR8468I 3590 volume U00122 dismounted from drive 3590-6 (/dev/rmt6) in library 3494LIB. And the volume doesn't show in the actlog ever since... As you can see, the is a volume that was a scratch vol, was written to (apperently, it could not have been read, since scratchvolumes don't contain any data) for over 2 hours and is empty afterwards. -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdamhttp://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
W2K: FS Backup with baclient
Hi There, I've got minor problem: Client level: 5.1.6.2 TSM Server level: 5.1.6.4 TDP level: 3.2.0.10 We are running a incremental backup on a Windows 2000 server everyday and the backups reports the following errors: Directory--> 0 \\eupmcchsap20\e$\oracle\D5A\saparch <\\eupmcchsap20\e$\oracle\D5A\saparch> ** Unsuccessful ** ANS1228E Sending of object '\\eupmcchsap20\e$\oracle\D5A\saparch <\\eupmcchsap20\e$\oracle\D5A\saparch> ' failed ANS4005E Error processing '\\eupmcchsap20\e$\oracle\D5A\saparch <\\eupmcchsap20\e$\oracle\D5A\saparch> ': file not found ANS1228E Sending of object '\\eupmcchsap20\e$\oracle\d5a\saparch\ <\\eupmcchsap20\e$\oracle\d5a\saparch\> ' failed ANS4042E Object name '\\eupmcchsap20\e$\oracle\d5a\saparch\ <\\eupmcchsap20\e$\oracle\d5a\saparch\> ' contains one or more unrecognised characters and is not valid. ANS1802E Incremental backup of '\\eupmcchsap20\e$\oracle\d5a\saparch <\\eupmcchsap20\e$\oracle\d5a\saparch> ' finished with 1 failure On the dsm.opt we've excluded all the redologs since they are covered by the TDP archive, which is executed successfully. The directory "saparch" is a mounted filesystem, and inside there is the system directory "System Volume Information" which I've excluded it in the dsm.opt. However this does not work and backup process keeps reporting the same error. When I execute a query of the filespace on the TSM server, the filespace information shows as being unicode (Is Filespace Unicode?: Yes). Does anyone have an idea. Many thanks in advance. Regards, Ivan Zbinden
Empty volume does not return to scratch?
Hi all, a few weeks back we had a discussion on empty volumes not returning to scratch, well, here is an example. tsm: BASKET>q vol stat=empty f=d Volume Name: U00122 Storage Pool Name: SANPOOL Device Class Name: 3494-3590 Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Read/Write Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 5 Write Pass Number: 0 Approx. Date Last Written: Approx. Date Last Read: Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): Last Update Date/Time: 07/27/03 11:11:32 This is with server level 5.1.6.4 on AIX 4.3.3. What is more surprising is that the last update of this volume was not reclamation, but allocation of this volume in the storagepool. It has been mounted for over two hours at that time, probably due to space-recamation running at that time, but apperently, there was never one bit written. Now I'm wondering, how could that be? The actlog shows: 07/27/03 11:11:32 ANR8337I 3590 volume U00122 mounted in drive 3590-6 (/dev/rmt6). 07/27/03 11:11:32 ANR1340I Scratch volume U00122 is now defined in storage pool SANPOOL. 07/27/03 11:11:58 ANE4991I (Session: 12641, Node: BASKET-C) API ANE4991 rmt0=leeg rmt1=leeg rmt2=leeg rmt3=leeg rmt4=leeg rmt5=leeg rmt6=U00122 (lots more ANE4991I here, this is generated by a applcation developped in house) 07/27/03 13:17:37 ANR8325I Dismounting volume U00122 - 2 minute mount retention expired. 07/27/03 13:17:38 ANE4991I (Session: 12911, Node: BASKET-C) API ANE4991 rmt0=leeg rmt1=000809 rmt2=000689 rmt3=leeg rmt4=leeg rmt5=U00261 rmt6=U00122 07/27/03 13:17:49 ANR8336I Verifying label of 3590 volume U00122 in drive 3590-6 (/dev/rmt6). 07/27/03 13:18:44 ANE4991I (Session: 12913, Node: BASKET-C) API ANE4991 rmt0=leeg rmt1=000809 rmt2=000689 rmt3=leeg rmt4=leeg rmt5=U00261 rmt6=U00122 07/27/03 13:18:47 ANR8468I 3590 volume U00122 dismounted from drive 3590-6 (/dev/rmt6) in library 3494LIB. And the volume doesn't show in the actlog ever since... As you can see, the is a volume that was a scratch vol, was written to (apperently, it could not have been read, since scratchvolumes don't contain any data) for over 2 hours and is empty afterwards. -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdamhttp://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: Error in deleting filespace
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 Hi, The TSM server 5.1 on AIX 5 and TSM client 5.1.5 on Windows 2000. Thanks, Zosi Noriega -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi Zosi! When posting a question to this list, please supply your TSM software level, maybe then we are able to assist you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 06:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table "Expiring.Objects". 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId<79> Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Lotus Notes Non-TDP backups
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 have repercussions elsewhere in the db and before you know it you won't be able to open up the .nsf at all, and will get 'b-tree structure invalid' or similar complaints from Notes. You need to have the Notes server process 'down' in order to quiece the databases and prevent them from being written to before backing them up. The *usual* way of handling Notes backups without using TDP is to use a 'backup' server - the concept works like this: You have a separate Notes server (i.e. a 'backup Notes server) which contains replicas of the databases on the live Notes servers. Using Notes replication, all changes to the live databases are replicated to the replicas on the backup server. At a time controlled by you, you take the Notes server process down on the backup server (as no users connect directly to the backup Notes server, there will be no outage) and then perform the backups of the now quiesced .nsf files using the normal TSM BA client. Once the backup is complete, bring up the Notes server on the backup server and begin replication with the live servers to the backup .nsf's up to date again. Depending upon hardware, you can have many live Notes server's worth of .nsf's contained on a single backup Notes server - just ensure you have enough time to replicate the data from live to backup server. In terms of recoveries, as the backup Notes server is down during backups, you might want to have an additional Notes partition somewhere on a backup server which you can use as a 'recovery server' - a Notes server which is *always* up, regardless of whether a backup is taking place. Users can connect to this directly and pull back any recovered .nsf databases, or even just documents from a .nsf. Hope this helps :o) David McClelland Global Management Systems Reuters Ltd -Original Message- From: Stefan Holzwarth [mailto:[EMAIL PROTECTED] Sent: 29 July 2003 07:06 To: [EMAIL PROTECTED] Subject: AW: Lotus Notes Non-TDP backups 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 160Gb of Notes mail databases that need to be backed up nightly. Due to incompatabilities with the Notes TDP, our version of TSM (v4.2.2.5) and the way compaction runs on our Notes servers, we have to use the normal Tivoli backup client to backup the mailboxes. It takes about 12 hours for all the databases to get backed up each night but the vast amount of this time seems to be spend trying and then retrying to send mailboxes to the TSM server. A typical schedule log looks like this: 28-07-2003 19:51:53 Retry # 2 Normal File--> 157,548,544 \\sdbo5211\d$\notes\data\mail\beggsa.nsf [Sent] 28-07-2003 19:52:28 Normal File-->70,778,880 \\sdbo5211\d$\notes\data\mail\bingleyj.nsf [Sent] 28-07-2003 19:54:05 Retry # 1 Normal File--> 349,437,952 \\sdbo5211\d$\notes\data\mail\bignasck.nsf [Sent] 28-07-2003 19:55:10 Normal File--> 131,072,000 \\sdbo5211\d$\notes\data\mail\Bishnic.nsf Changed 28-07-2003 19:56:58 Normal File--> 265,289,728 \\sdbo5211\d$\notes\data\mail\bellm.nsf [Sent] 28-07-2003 19:58:08 Retry # 1 Normal File--> 131,072,000 \\sdbo5211\d$\notes\data\mail\Bishnic.nsf [Sent] 28-07-2003 20:00:46 Normal File--> 387,186,688 \\sdbo5211\d$\notes\data\mail\BLACKAD.NSF Changed 28-07-2003 20:03:52 Normal File--> 367,263,744 \\sdbo5211\d$\notes\data\mail\BERNECKC.NSF Changed 28-07-2003 20:06:18 Retry # 1 Normal File--> 387,186,688 \\sdbo5211\d$\notes\data\mail\BLACKAD.NSF [Sent] 28-07-2003 20:10:11 Normal File--> 1,011,613,696 \\sdbo5211\d$\notes\data\mail\binneyk.nsf Changed 28-07-2003 20:11:52 Retry # 2 Normal File--> 953,942,016 \\sdbo5211\d$\notes\data\mail\andrewsj.nsf [Sent] 28-07-2003 20:12:01 Retry # 1 Normal File--> 367,263,744 \\sdbo5211\d$\notes\data\mail\BERNECKC.NSF [Sent] 28-07-2003 20:12:05 Normal File-->10,485,760 \\sdbo5211\d$\notes\data\mail\bousran.nsf [Sent] 28-07-2003 20:13:40 Normal File--> 720,633,856 \\sdbo5211\d$\notes\data\mail\BLACKC.NSF Changed 28-07-2003 20:18:58 Retry # 3 Normal File--> 1,863,057,408 \\sdbo5211\d$\notes\data\dbecna.nsf Changed Is there anything we can do reduce the window for this backup? Both the TSM server and our Notes server have dedicated 1Gb links so bandwidth isn't a problem. The Backup Copy Group for the Management Class the Notes data is allocated to has Copy Serialization set to 'Shared Static'. Would changing this
scheduled events status report
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 - - - 28-07-2003 19:10:00 28-07-2003 20:54:08 STOS1 STO_CR_AMNH Completed 28-07-2003 19:10:00 28-07-2003 20:37:02 WEBS1 WEB_IT_CPLX Completed 28-07-2003 19:10:01 29-07-2003 01:18:45 PERS1 PER_HQ_CNTR (?) 28-07-2003 19:10:08 28-07-2003 23:14:01 SIGS1 SIG_IT_CPLX Completed 28-07-2003 19:10:31 28-07-2003 21:48:06 ARCHQS1 ARC_HQ_CNTR Completed Thanks alot in advance This e-mail Message is Intended for the named Recipient Only. It May be Privileged and/or Confidential. If you are NOT the Intended Recipient of this e-mail then you Should NOT Copy it or Use it for any Purpose, Nor Disclose its Contents to any Person. You Should Contact The Housing Bank For Trade and Finance as Shown above So that we can Take Appropriate Action
Re: Lotus Notes Non-TDP backups
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 to umderstand your data and to test that the restores are usable. John Gordon Woodward <[EMAIL PROTECTED]> on 07/29/2003 03:00:33 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Lotus Notes Non-TDP backups We currently have over 160Gb of Notes mail databases that need to be backed up nightly. Due to incompatabilities with the Notes TDP, our version of TSM (v4.2.2.5) and the way compaction runs on our Notes servers, we have to use the normal Tivoli backup client to backup the mailboxes. It takes about 12 hours for all the databases to get backed up each night but the vast amount of this time seems to be spend trying and then retrying to send mailboxes to the TSM server. A typical schedule log looks like this: 28-07-2003 19:51:53 Retry # 2 Normal File--> 157,548,544 \\sdbo5211\d$\notes\data\mail\beggsa.nsf [Sent] 28-07-2003 19:52:28 Normal File-->70,778,880 \\sdbo5211\d$\notes\data\mail\bingleyj.nsf [Sent] 28-07-2003 19:54:05 Retry # 1 Normal File--> 349,437,952 \\sdbo5211\d$\notes\data\mail\bignasck.nsf [Sent] 28-07-2003 19:55:10 Normal File--> 131,072,000 \\sdbo5211\d$\notes\data\mail\Bishnic.nsf Changed 28-07-2003 19:56:58 Normal File--> 265,289,728 \\sdbo5211\d$\notes\data\mail\bellm.nsf [Sent] 28-07-2003 19:58:08 Retry # 1 Normal File--> 131,072,000 \\sdbo5211\d$\notes\data\mail\Bishnic.nsf [Sent] 28-07-2003 20:00:46 Normal File--> 387,186,688 \\sdbo5211\d$\notes\data\mail\BLACKAD.NSF Changed 28-07-2003 20:03:52 Normal File--> 367,263,744 \\sdbo5211\d$\notes\data\mail\BERNECKC.NSF Changed 28-07-2003 20:06:18 Retry # 1 Normal File--> 387,186,688 \\sdbo5211\d$\notes\data\mail\BLACKAD.NSF [Sent] 28-07-2003 20:10:11 Normal File--> 1,011,613,696 \\sdbo5211\d$\notes\data\mail\binneyk.nsf Changed 28-07-2003 20:11:52 Retry # 2 Normal File--> 953,942,016 \\sdbo5211\d$\notes\data\mail\andrewsj.nsf [Sent] 28-07-2003 20:12:01 Retry # 1 Normal File--> 367,263,744 \\sdbo5211\d$\notes\data\mail\BERNECKC.NSF [Sent] 28-07-2003 20:12:05 Normal File-->10,485,760 \\sdbo5211\d$\notes\data\mail\bousran.nsf [Sent] 28-07-2003 20:13:40 Normal File--> 720,633,856 \\sdbo5211\d$\notes\data\mail\BLACKC.NSF Changed 28-07-2003 20:18:58 Retry # 3 Normal File--> 1,863,057,408 \\sdbo5211\d$\notes\data\dbecna.nsf Changed Is there anything we can do reduce the window for this backup? Both the TSM server and our Notes server have dedicated 1Gb links so bandwidth isn't a problem. The Backup Copy Group for the Management Class the Notes data is allocated to has Copy Serialization set to 'Shared Static'. Would changing this to Dynamic be beneficial in reducing the amount of retries that occur and also setting CHANGERETRIES to a lower option help? Thanks in advance, Gordon Woodward Senior Support Analyst Deutsche Asset Management (Australia) Limited -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Antwort: Separate Domino server for restores
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. Note the Notes server does, and should not be running on the restore server Mit freundlichen Grüßen / Best Regards Markus Veit An: [EMAIL PROTECTED] Kopie: Thema: Separate Domino server for restores [EMAIL PROTECTED] Received : 28.07.2003 20:59 Bitte antworten an "ADSM: Dist Stor Manager" How would I go about creating another Domino server for restores?? I installed the TDP agent on another Domino server, configured the DSM.OPT file to use the production server nodename. I can do restores, but when I try to do an applylogs, I get ACD5769I that says I can't apply the logs. I was trying to follow the procedures in the TDP user's guide for alternate server restore, but it wasn't making much sense to us, as non-Domino literates. What we need is a simple way to get this server configured so that we can apply the logs during the activate process. They used to do this on their production Domino server until it crashed due to a resources shortage during an APPLYLOGS process. Now they're gun-shy and want to use a separate server, which is what the user's guide recommends. TIA, Bill Boyer "Some days you are the bug, some days you are the windshield." - ??
