Re: Drive Inconsistencies
Suggestion: go check your drive, see if it has a code on the front. My
guess is that it does. A drive being offline (as in 'q drive') is
separate from the path ('q path') being offline. They are related, but
independent.
Someone else probably has good technical explanation.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Rob Hefty
Sent: Thursday, April 13, 2006 9:56 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Drive Inconsistencies
Hello all,
As seen below, I have a library drive (DRIVE05) that is currently listed
as On-Line within the query drive command output but listed as not
On-Line in the query path command output. I have logged a call with IBM
support to verify the drive is functioning; however, I am curious as to
why the inconsistency?
TSM Server:5.2.3.2
SCSI Library IBM 3584
Library Name Drive Name Device Type On-Line
--- ---
LTO2 DRIVE01 LTO Yes
LTO2 DRIVE02 LTO Yes
LTO2 DRIVE03 LTO Yes
LTO2 DRIVE04 LTO Yes
LTO2 DRIVE05 LTO Yes
LTO2 DRIVE06 LTO Yes
Source Name Source Type Destination Destination On-Line
--- --- --- --- ---
TSMSRVR SERVER LTO2LIBRARY Yes
TSMSRVR SERVER DRIVE01 DRIVE Yes
TSMSRVR SERVER DRIVE02 DRIVE Yes
TSMSRVR SERVER DRIVE03 DRIVE Yes
TSMSRVR SERVER DRIVE04 DRIVE Yes
TSMSRVR SERVER DRIVE05 DRIVE No --
???
TSMSRVR SERVER DRIVE06 DRIVE Yes
Regards,
Rob
Privileged and Confidential: The information contained in this e-mail message
is intended only for the personal and confidential use of the intended
recipient(s). If the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any review,
dissemination, distribution, or copying of this message is strictly prohibited.
If you have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
What are the High/Low Level addresses?
ANR4740W Either the high level address, low level address, or both were never entered for the specified node( H6540N1 ) and the session initiation status is being changed. I received this message, and I have seen the fields on the client update screen. But the documentation and helps leave me cold. What do I need to put in them to get this message to go away? Node in this case is H6540N1 and assume IP is 12.34.56.78 Any idea what goes in the fields? Or please send me to RTFine Manual :) ... TIA, Jack Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: ANR8300E - I/O error on library desc= the destination slot or drive was full in an attemt to move a volume
I hope it worked for you. In the past I have cached out the volume where a problem was reported (both the one in the 'real slot' and the one that TSM says should be in the slot). Sometimes I had to check out several until there were no more 'unknown' tapes in the library. Then check them all back in after doing a TSM audit checkl=barcode. It did take some time, but it cured the issue for me. Just my .02 pesos worth! (this was on an IBM 3593 aka ADIC 100) ... I do remember one time I got so frustrated, I took out all the tapes, shut down tsm server (windows), power cycled the 3583, and brought it all back up with an empty library. Did a AUDIT LIBR in tsm, the loaded all the tapes back into TSM (using the bulk door and TSM commands). ... That cured the problem and let me have enough time for my frustration to subside ... I think that these processed did for me what forcing an 'inventory from the library side' did for you. Sounds like your method had less frustration after you found the right answer. ... Jack -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nancy L Backhaus Sent: Tuesday, April 11, 2006 7:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANR8300E - I/O error on library desc= the destination slot or drive was full in an attemt to move a volume Just an update... I had already tried auditing the library with checklabel=barcode for a first fix attempt and still saw the error.Yesterday afternoon working with ADIC tech support we ran an inventory process from the library side and then reran the audit on TSM server checklabel=barcodeand no errors after that. (fingers crossed) Nancy Backhaus Enterprise Systems HealthNow, NY 716-887-7979 Zoltan Forray/AC/VCU [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04/10/2006 04:39 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ANR8300E - I/O error on library desc= the destination slot or drive was full in an attemt to move a volume Been there - Done that. Seen it numerous times. Just perform an audit of your library, scanning the barcodes. There is an out-of-sync problem in the library inventory (internal). There is a tape who's barcode it didn't read during the last scan pass or you had some kind of library error. In fact, I just did one. AUDIT LIBR insert your library name here checkl=b Nancy L Backhaus [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04/10/2006 03:15 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] ANR8300E - I/O error on library desc= the destination slot or drive was full in an attemt to move a volume Anyone see this error below? Looking for direction/suggestions? The tape(s) do actually does dismount. The issue is occurring on different drives. All volumes are online, no unavail, no damaged, etc. I audited the library, it was a successful audit checklabel=barcode. **Background - Updated a week ago Library firmware from 3.1 to 4.1 and then backed out the library firmware code because internal barcode on the tapes could not be read. So we went back to our 3.1 firmware and thought we were ok again. Also, a couple other ADIC clients reported similiar issues with new firmware. Then we started seeing this error today with TSM sense data. Errpt - showing nothing Only TSM is reporting error, the library and aix are reporting no errors. Version: TSM Version - 5.3.2.2 AIX - 5.3 Mod 3 ADIC I2000 Scalar Library(LTO 2 drives), LTO2 tapes actlog: 04/10/06 13:16:44 ANR8300E I/O error on library BLUE (OP=6C03, CC=315, KEY=05, ASC=3B, ASCQ=0D, SENSE=70.00.05.00.00.00.00.0A.0- 0.00.00.00.3B.0D.00.CF.00.06., Description=The destination slot or drive was full in an attempt to move a volume). Refer to Appendix D in the 'Messages' manual for recommended action. (PROCESS: 302) 04/10/06 13:16:44 ANR8469E Dismount of LTO volume TS1430 from drive DRIVE13 (/dev/rmt13) in library BLUE01 failed. (PROCESS: 302) Sense Data= Key (05) = illegal request CC(315)= dest slot was full ASC=3B, ASCQ=OD = medium destination element is full Nancy Backhaus Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication
Re: Resend - Policy and DRP question
The question is: does this mean that we have to now keep the 10 latest tapes offsite for complete DRP? From what I am seeing it says you are now defining the process to keep 10 tapes un-used. If you keep them off site, so much the better for disaster preparedness. You do not have to change the retention of your database backups to retain additional versions of data. Changing the 'del volhist' you did is reasonable since you are changing the retention of database tapes too the same retention. Now I could be totally off base, lets see if a more experienced eye has an opinion too. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley Sent: Monday, April 10, 2006 11:49 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Resend - Policy and DRP question I sent this query a week ago but have not received a reply back. I am resending in the hope that someone can offer some advice. We have TSM version 5.2 I have changed the standard policy so that we now keep the 10 latest versions of each file rather than 7. I have also changed our del volhist to tod=today-10 where it was previously 7. I have been told that previously we had to keep the 7 latest copy tapes and db tapes offsite for DRP to ensure that we could recover complete servers. With the changes that I have made does this mean that we have to now keep the 10 latest tapes offsite for complete DRP? Paul Dudley ANL IT Operations Dept. [EMAIL PROTECTED] ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: Clustered Servers and Tivoli
I don't know the specifics about Novell, but on AIX and Windows, we are setting up N+1 backup services (N-nodes in a cluster, plus one for the cluster itself). One client on each node for its local files, and one client that works as a fail-over-service that follows the 'active' cluster node. The control files for the 'clustered' node also needs to be on a disk that fails over to the active cluster as well. That is the one that backs up the clustered data. At lease that works in our environment. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of John Bortscheller Sent: Monday, April 10, 2006 1:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Clustered Servers and Tivoli Hello, we are using Netware 6.5 OS and Tivoli 5.3.2 on clustered servers. There is something in the opt file that we are missing. It sees the local drives but not the netware volumes. Do you have a sample opt file that shows how to configure the opt file correctly for clustering to be able to see all of the volumes. Thanks John Bortscheller Network Administrator San Diego Data Processing Corporation (858) 581-9718 [EMAIL PROTECTED] Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Restoring Backed Up Storage Group and Oracle cross system restores
Someone else set this up and they are gone now and I need a little help. We have one storage group we keep only one backup in it. Every day we issue a 'backup stg onecopygroup offsitegroup' I have not been able to find out how long we keep the 'offsitegroup' or how many copies. I was told this 'offsitegroup' is kept for 30 days (or versions). We have a TDP used on AIX to backup Oracle that backs up to the 'onecopygroup'. I may need to restore a database from a week or so ago today. My gut feeling is to just bring back all my 'offsitegroup' tapes (or preferably just a few) and TSM is smart enough to just use data from those tapes to do the restore. And when we are done, send them offsite again. But I am not convinced I am right. So here are some questions: (1) Where should I look to see how long the 'offsitegroup' really keeps backups. (2) How could I determine which tape(s) I need to bring onsite from the 'offsitegroup'? (3) Do I need to move the data back into the 'onecopygroup' to be able to restore from it? (4) Any suggestions/tips/howto/RTFM on how to setup and perform a restore using RMAN with TSM? (5) This will be restoring to a different Oracle server (putting data back on a test Oracle Server that was backed up from a production Oracle Server. As always, Thanks for your assistance. ... Once I get this done, I will post a summary. Jack Coats Ardent Health Care Systems Engineer 7100 Commerce Way, Ste 180 Brentwood, TN 37027 615-296-3313 [EMAIL PROTECTED] - [EMAIL PROTECTED] Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
No unusual new clients being added? Retaining more data? Change of include/exclude files? ... Just grasping for straws... -Original Message- Subject: [ADSM-L] TSM Database Size Growing Since Upgrading to 5.2.4.5 On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: Rebuilding a TSM Server ?
I believe he means to 1) turn cache off on the backup pool 2) migrate down to 0 percent from the backup pool to your tape pool 3) and I might add, make sure your tape pool is mirrored on your copy pool as well. When I have done this, I have then run an expiration of the database, Then a full database backup. Now use THIS backup to restore from. When I have done this, I basically did these steps, then used the TSM DRM process scripts (from the planfile) as a go-by to ensure I didn't miss anything. I hope that helps. Jack Coats Ardent Health Care -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Friday, January 20, 2006 7:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Rebuilding a TSM Server ? Thanks Len As far as moving the data off the backuppool prior to the restore of the db etc, does that just mean doing a full migration to take? I assume it does but am happy to ask again just to make sure :-) Farren |-+---| | len boyle | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| ST.EDU| | | cc| | 20/01/2006 13:34 | | | |Subject| | Please respond to | Re: [ADSM-L] | | ADSM: Dist Stor| Rebuilding a | | Manager| TSM Server ? | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| Good Morning Farren I am sure that you will get a number of good answers, but here are a few points. I am sure I will be corrected for any faults in my logic. It been a little while since I have had to move the tsm server to a new box and there may be newer better thoughts. When you create the space on the new server, you only have to create the same or greater for the log and db volumes. You can use a new layout based on your best thoughts for performance. For the storage pools you might want to move all data off the disk storage pool volumes before the move. Then you will not have do a restore of the storage pools after the tsm server is restored on the new server. Otherwise you will have to restore the disk storage pools after you restore your db and have a running system. But for the restore of the db you do not need your full operating size. For the initial set up of the tape library and drives, you only need to define one tape drive. After you restore the db, your old device configuration will be in effect. Which means if it is different you will have to delete and redefine the hardware to TSM. You might want to look at the redbook for TSM DR. len - Original Message - From: Farren Minns [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Friday, January 20, 2006 7:25 AM Subject: [ADSM-L] Rebuilding a TSM Server ? Hi all *** TSM 5.1.6.2 on Solaris 2.7, moving to TSM 5.2.?.? on Solaris 2.9 *** OK, I'm in the process of building a new replacement TSM server (Solaris). When it's ready I will hopefully be able to turn the old machine off and bring the new one up again with the same host name/tcp address and away we'll all go. I have already got the server ready, patched, IBMTape and lmcpd drivers installed etc, so I'm about ready to move on to the TSM side of things. The procedures that I assume I now need to go through are as follows. Anything with a question mark is something I'm not sure about. 1) Install TSM - Done 2) Register necessary licenses 3) Define Tape/Library devices and paths for manual library ready for restore. 4) Create device configuration file for above and add entry into the dsmserv.opt file. 5) Copy volume history file from original server ? 6) Format Backuppool volume/s 7) Format Database volume/s 8) Format Log volume/s Question re above: If for example my present database is 10GB and made up of 5*2GB volumes, do I need to create the new volumes like for like or could I just create one 10GB volume. i.e. is it only important to make sure the necessary
Re: Insufficient space in storage pool -- but not true
Ok, you checked the maxscratch, but what is the high water mark on your log and db volumes (log especially). This one has bit me a few times. 'q log' and 'q db' should answer that. If they have hit 100% we have probably hit paydirt. If not, then I home someone with more experience than I is listening! Jack Coats Ardent Health Care -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lee, Gary D. Sent: Friday, January 20, 2006 12:17 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Insufficient space in storage pool -- but not true Tsm server v5.2.7.0 Solaris 2.8 Tried doing reclamation on my onsite pool bigtape this morning. All worked through yesterday, but this morning got message anr1086w insufficient space in storage pool. Below is a script of the last reclamation, with stgpool definition, scratch counts and volume counts. As shown, there should be 50 volumes available before maxscratch is reached. HELP!!! -- activity log follows --- Date/Time: 01/20/06 12:50:20 Message: ANR2017I Administrator GARY issued command: UPDATE STGPOOL bigtape recl=60 (SESSION: 1585) Date/Time: 01/20/06 12:50:20 Message: ANR2202I Storage pool BIGTAPE updated. (SESSION: 1585) Date/Time: 01/20/06 12:50:20 Message: ANR0984I Process 266 for SPACE RECLAMATION started in the BACKGROUND at 12:50:20. (PROCESS: 266) Date/Time: 01/20/06 12:50:20 Message: ANR1040I Space reclamation started for volume 225358, storage pool BIGTAPE (process number 266). (PROCESS: 266) Date/Time: 01/20/06 12:50:20 Message: ANR1044I Removable volume 225358 is required for space reclamation. (PROCESS: 266) Date/Time: 01/20/06 12:50:20 Message: ANR1044I Removable volume 225204 is required for space reclamation. (PROCESS: 266) Date/Time: 01/20/06 12:50:20 Message: ANR1142I Moving data for collocation cluster 1 of 1 on volume 225358. (PROCESS: 266) Date/Time: 01/20/06 12:51:08 Message: ANR8337I 3590 volume 225358 mounted in drive 821P0 (/dev/rmt/5stc). (PROCESS: 266) Date/Time: 01/20/06 12:51:08 Message: ANR0512I Process 266 opened input volume 225358. (PROCESS: 266) Date/Time: 01/20/06 12:51:10 Message: ANR8337I 3590 volume 226289 mounted in drive 823P1 (/dev/rmt/0stc). (PROCESS: 266) Date/Time: 01/20/06 12:51:10 Message: ANR0513I Process 266 opened output volume 226289. (PROCESS: 266) Date/Time: 01/20/06 12:53:24 Message: ANR8341I End-of-volume reached for 3590 volume 226289. (PROCESS: 266) Date/Time: 01/20/06 12:53:24 Message: ANR0515I Process 266 closed volume 226289. (PROCESS: 266) Date/Time: 01/20/06 12:53:25 Message: ANR0985I Process 266 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at 12:53:25. (PROCESS: 266) Date/Time: 01/20/06 12:53:25 Message: ANR1086W Space reclamation terminated for volume 225358 - insufficient space in storage pool. Date/Time: 01/20/06 12:53:25 Message: ANR1042I Space reclamation for storage pool BIGTAPE will be retried in 60 seconds. q stg bigtape f=d Storage Pool Name: BIGTAPE Storage Pool Type: Primary Device Class Name: 3590 Estimated Capacity (MB): 9,147 G Pct Util: 62.6 Pct Migr: 87.7 Pct Logical: 99.0 High Mig Pct: 75 Low Mig Pct: 15 Migration Delay: 0 Migration Continue: Yes Migration Processes: Next Storage Pool: Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Read/Write Description: primary backup tape Overflow Location: Cache Migrated Files?: Collocate?: Yes Reclamation Threshold: 100 Maximum Scratch Volumes Allowed: 625 Delay Period for Volume Reuse: 4 Day(s) Migration in Progress?: No Amount Migrated (MB): 0.00 Elapsed Migration Time (seconds): 0 Reclamation in Progress?: No Volume Being Migrated/Reclaimed: Last Update by (administrator): GARY Last Update Date/Time: 01/20/06 12:54:38 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No run vol-cnt Storage Pool Name: BIGTAPE Device Class Name: 3590 # VOLUMES: 571 . . . ANR1462I RUN: Command script VOL-CNT completed successfully. run scratch-count number of scratch tapes: 85 ANR1462I RUN: Command script SCRATCH-COUNT completed successfully. Gary Lee Senior System Programmer Ball State University -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.21/235 - Release Date: 1/19/2006 Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail
Re: DB LOG Volume layout - new
Just curious, and playing a little devils advocate, but does it buy anything to mirror over raid5? Wouldn't it be more efficient (processor on the san, and storage) just to put volumes out there and let TSM manage them? You would want to have the mirrored volumes on separate physical drives (preferably in different trays, etc) also. Suggestions? Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: Backup larger than data on server
There is also the 'chitchat' that the client and server do when discussing whether an individual file has been backed up or is missing. That increases the network transmissions significantly if you have a large number of files and are not using local journaling. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley Sent: Wednesday, January 18, 2006 9:18 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backup larger than data on server We have TSM version 5.2. The client server I am referring to here is Redhat linux. In the /var/log/tsm/dsmsched.log it lists Total number of bytes transferred:79.18 GB However there is only around 60 Gb of data on the server (see df below) FilesystemSize Used Avail Use% Mounted on /dev/sda1 9.7G 2.1G 7.1G 23% / /dev/sdb2 104G 57G 43G 58% /opt Can someone explain why the number of bytes transferred exceeds the amount of data on the server? Thanks Paul Paul Dudley ANL IT Operations Dept. ANL Container Line [EMAIL PROTECTED] ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Error log...
In my dsmerror.log I am getting messages: 01/06/06 08:27:42 Error -50 sending ht request 01/06/06 08:27:42 Error writing to http socket. It is showing over and over again with the date/time stamp changing. Server is AIX w/TSM 5.2.3.0 Client is AIX with 5.2 client No apparent issues are showing up in my clients dsmsched.log Suggestions? Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: 100.0% full and still Filling?
On Dec 29, 2005, at 4:37 AM, Dksh Cssc wrote: Wondering why the volume status is filling when the pct utilization is 100%? ... Yes it happens. Depends on what you specify when you specify tape capacity. I found that it would seldom go beyond 100% if you are using client compression, but will regularly go well beyond 100% if there is no client compression and there are compressible files (think standard ASCII files versus binary type files). You can keep it from doing this by re-stating the drive capacity, but I like to state the drive capacity as the stated uncompressed capacity of the drive and anything over that is pure gravy. The volume, even if over 100%, will stay in filling status until the volume reaches its end of volume. It is possible to be full even if 89% full (or at least something less than 100%) if the end of volume is reached. It is possible to see this if you specify the volume capacity to be larger than the uncompressed capacity, or if there is some media. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
3583 SAC Codes?
Where can I find the SAC codes for a IBM 3583? I have a library that says SAC: 01 00 Jack Coats Ardent Health Care Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: Adding additional sticker to lto tapes for Disaster Recovery Test
In my experience, there is no good label to add to LTO tapes. I started using either a white marker or paint pen when needing to add information to the tapes. If you MUST put an extra label on the tapes, I suggest some lablels I have run across, they are VERY thin plastic/mylar with perminant type adhesive. I did, long ago now, try other stickers on some LTO tapes for a similar reason, and managed to get an LTO drive gummed up inside. Not a pretty site, and I was nicely but firmly chastized my my IBM service person too :( ... We all like to keep them happy. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: TSM Migration
There may be technical issues, but from what I can tell it is a religious issue for AIX vs Linux. Both are good solutions. Even a well configured Windows solutions works, but it is not my preferred solution. IMHO, a best fit solution for TSM is probably an AIX solution. But if you have no AIX experience on staff, and do have solid Linux people available, then there is a reason for Linux in your environment. If you are primarily a LINUX shop (or going to be), then going to LINUX makes sense to me. As always, YMMV. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
