Re: Extend DB
Hello, I have done these 3 steps successfully but now I am trying to DEFINE DBCOPY. The documentation says DEFINE DBCOPY volume_name copy_vol_name When I do this adsm comes back with copy_vol_name is not available Now what? Val -Original Message- From: Zlatko Krastev [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 3:15 AM To: [EMAIL PROTECTED] Subject: Re: Extend DB Kelli, just three steps: 1. Create raw volume (mklv -y volume name -t tsmdbvol volume group size in partitions) or file volume (dsmfmt -g -db file name size in GB). Commands have to be performed in AIX shell. 2. Define newly created volume to TSM - 'define dbvolume /dev/rvolume name' or 'define dbvolume file name'. Command has to be performed from administrative client session. 3. Extend the DB - 'extend db number of pages' Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Extend DB Can someone please give me the exact steps to add db space on TSM 4.1.5 running on AIX 4.3.3? I am certainly not an AIX guru so please spare no details! My db is running at 88% and I have 0 for for Maximum Extension. How do I go about doing this? Thanks so much! Kelli Jones Chesterfield County Information Systems Technology [EMAIL PROTECTED] phone: 804-748-1951 fax: 804-748-1571
Re: Extend DB
No - I found out that I needed to do the dsmfmt command for the copy volume. I'm all set. Thanks for your help -- Val -Original Message- From: Steve Argersinger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 2:39 PM To: [EMAIL PROTECTED] Subject: Re: Extend DB Did you do step 1 for the copy volume?? Steve Argersinger Ruan Transportation -Original Message- From: VALERIE FISHER [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 9:49 AM To: [EMAIL PROTECTED] Subject: Re: Extend DB Hello, I have done these 3 steps successfully but now I am trying to DEFINE DBCOPY. The documentation says DEFINE DBCOPY volume_name copy_vol_name When I do this adsm comes back with copy_vol_name is not available Now what? Val -Original Message- From: Zlatko Krastev [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 3:15 AM To: [EMAIL PROTECTED] Subject: Re: Extend DB Kelli, just three steps: 1. Create raw volume (mklv -y volume name -t tsmdbvol volume group size in partitions) or file volume (dsmfmt -g -db file name size in GB). Commands have to be performed in AIX shell. 2. Define newly created volume to TSM - 'define dbvolume /dev/rvolume name' or 'define dbvolume file name'. Command has to be performed from administrative client session. 3. Extend the DB - 'extend db number of pages' Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Extend DB Can someone please give me the exact steps to add db space on TSM 4.1.5 running on AIX 4.3.3? I am certainly not an AIX guru so please spare no details! My db is running at 88% and I have 0 for for Maximum Extension. How do I go about doing this? Thanks so much! Kelli Jones Chesterfield County Information Systems Technology [EMAIL PROTECTED] phone: 804-748-1951 fax: 804-748-1571
Preserving ownership - UNIX (AIX)
Hello, I would like to know how we would go about preserving file ownership of the files we need to restore. We just returned from a D/R test and had problems starting some apps since the file ownership is not preserved when you do a retrieve of archives. ADSM Server level 4.1.4.0 on AIX 4.3.3 Client level 4.1.4.0 - AIX Val Manager of Systems Database Administration Seneca Foods Corp 3736 S Main St Marion, NY 14505 315-926-8148 315-926-8300 - fax [EMAIL PROTECTED]
Re: Preserving ownership - UNIX (AIX)
But we restore our original system with a mksysb which should have the same UID's shouldn't it?? -Original Message- From: Thomas Denier [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 3:09 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Preserving ownership - UNIX (AIX) I would like to know how we would go about preserving file ownership of the files we need to restore. We just returned from a D/R test and had problems starting some apps since the file ownership is not preserved when you do a retrieve of archives. ADSM Server level 4.1.4.0 on AIX 4.3.3 Client level 4.1.4.0 - AIX We have sometimes seen anomalies like this on cross-system restores. The restore recreated the numeric user and group assignments the files had on their original host. Unfortunately, the /etc/passwd file on the target system had a different mapping between numeric user IDs and user names than the /etc/passwd file on the original host, and the /etc/group file had a different mapping between numeric group IDs and group names.
Re: DB Backups to specific tapes
Can this also be done with archives ? -Original Message- From: Nicholas Cassimatis [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 4:49 PM To: [EMAIL PROTECTED] Subject: Re: DB Backups to specific tapes Just list the volumes in the database backup command: backup db type=full devc=yourdevclasshere vol=volser To make this even easier, you can have a pool of volumes to use, in a comma separated list: backup db type=full devc=yourdevclasshere vol=vol1,vol2,vol3,vol4,vol5,vol6,vol7 TSM will go along the list until it finds a volume it can use for the backup. So if, with the command above, vol1 and vol2 already have dbbackups on them, TSM would use vol3. You'll want more volumes than you'll be keeping versions of your database, so you don't starve the database backup process for tapes (I've been told if none of the listed volumes are available, TSM will grab a scratch tape, but I've never tested that). So if you keep 7 versions of your database backup, you'll want at least 7 (I'd recommend 10) tapes, to protect against bad tapes, mistaken checkouts, or other issues. Also, make sure the volumes that you want to use are checked in as Private, not Scratch. Nick Cassimatis [EMAIL PROTECTED] Today is the tomorrow of yesterday.
Re: Archive problems
Don't know if this would help your platform but when I upgraded from ADSM 3.1 on AIX to 4.1.4.0 we had the same slowness - were advised from the TSM support folks to execute these commands on the TSM server on AIX and the 3 clients it serves from the dsmc prompt. clean archdir (nodename) delete duplicates convert archive (nodename) reorg=yes and it did make the archive of many files go faster. Good luck ! -Original Message- From: Hunley, Ike [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 5:27 PM To: [EMAIL PROTECTED] Subject: Archive problems Hi, I hope someone else out there has had this problem. I need answers pronto! TSM 4.3.1 is on OS/390 V2R9, AIX TSM is 3.1.06 Archive is SLOW! Sometimes the process stops for no reason we can find. File sizes range from 80 bytes to 800MB. 5 byte file: 4.17 seconds 6,144,000 byte file 7.15 seconds Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc.
volume dismount
Hello, Has anyone seen this error when a tape is dismounting?? We are on TSM Version 4.1.40 on AIX 4.3.3. 08/29/01 09:52:27 ANR8325I Dismounting volume ADSM26 - 60 minute mount retention expired. 08/29/01 09:52:27 ANR8336I Verifying label of 3570 volume ADSM26 in drive 3570TAPE_1 (/dev/rmt1). 08/29/01 09:52:44 ANR8311E An I/O error occurred while accessing drive 3570TAPE_1 (/dev/rmt1) for GETLOGSENSE operation, errno = 22.
Re: 3590 Tape Drive Errors
Yes - we cleaned the drive which helped but it may also be an old tape that
needs to be replaced.
-Original Message-
From: Bruce Kamp [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 28, 2001 10:17 AM
To: [EMAIL PROTECTED]
Subject: 3590 Tape Drive Errors
Has anybody seen these errors before? IBM has been here many times
replaced the read/write heads loaded the latest micro code on the drives
but I keep getting them.
---
LABEL: SIM_MIM_RECORD_3590
IDENTIFIER: D1A1AE6F
Date/Time: Tue Aug 28 07:42:06
Sequence Number: 2770
Machine Id: 00012953A300
Node Id: tsmserv
Class: H
Type:INFO
Resource Name: rmt4
Resource Class: tape
Resource Type: 3590
Location:00-08-01-3,0
VPD:
ManufacturerIBM
Machine Type and Model..03590E1A
Serial Number...000F3420
Device Specific.(FW)E32E
Loadable Microcode LevelA0B00E26
Description
TAPE SIM/MIM RECORD
Probable Causes
TAPE DRIVE
Failure Causes
TAPE DRIVE
Recommended Actions
REFER TO PRODUCT DOCUMENTATION FOR ADDITIONAL INFORMATION
Detail Data
DIAGNOSTIC EXPLANATION
3100 0044 6140 0130 3030 3030 3030 3233 3245 3537 3030 3941 3030 3030
3030
4646 4335 3539 4335 3539 3830 3030 4942 4D31 332D 3030 3030 3030 3046 3334
3230
3033 3539 3045 3141
---
LABEL: TAPE_DRIVE_CLEANING
IDENTIFIER: E507DCF9
Date/Time: Tue Aug 28 07:39:03
Sequence Number: 2769
Machine Id: 00012953A300
Node Id: tsmserv
Class: H
Type:INFO
Resource Name: rmt4
Resource Class: tape
Resource Type: 3590
Location:00-08-01-3,0
VPD:
ManufacturerIBM
Machine Type and Model..03590E1A
Serial Number...000F3420
Device Specific.(FW)E32E
Loadable Microcode LevelA0B00E26
Description
TAPE DRIVE NEEDS CLEANING
Probable Causes
TAPE DRIVE
Failure Causes
TAPE DRIVE
Recommended Actions
CLEAN TAPE DRIVE
Detail Data
SENSE DATA
0603 1B00 0102 7000 0100 0058
0017 FF03 C94B 4033 0005 0140 1B00
8000 3332
4520
2020 2000
---
--
Bruce Kamp
Network Analyst II
Memorial Healthcare System
P: (954)987-2020 x6008
F: (954)985-2274
E: [EMAIL PROTECTED]
Re: TSM Bare Restore AIX Different Arch
We do our mksysb's to the same tape drive that TSM uses. We bring down the TSM server so that it does not own the tape device anymore and then start the mksysb backup. Haven't had a problem with at all. Have tested this at our DR hotsite and works fine. -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 22, 2001 2:22 PM To: [EMAIL PROTECTED] Subject: Re: TSM Bare Restore AIX Different Arch We do the mksysb's to disk. Then TSM backs them up. Then we only need the tape version of mksysb for the TSM server itself. There is also a companion product to TSM called Bare-Metal restore, that will take care of this stuff for you. There is a link to the BMR info on the TSM home page: http://www.tivoli.com/products/index/storage_mgr/ -Original Message- From: Dave Z [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 22, 2001 10:42 AM To: [EMAIL PROTECTED] Subject: TSM Bare Restore AIX Different Arch Folks, I apologize if this is a FAQ (I cannot find a complete documented procedure) :0( Currently, we use the following procedure to restore systems: 1) Restore the OS using the cloaner method as published by IBM: a) Boot off of the AIX installation media b) Restore system from tape (mksysb) (This allows you to recover the OS to dissimilar hardware) 2) Reconstruct the network (including the TSM backup network). 3) Restore all application data (and system data if needed) via TSM. This methodology does not support a true DR test as our mksysb tapes are not cut regularly or vaulted. Unfortunately we do not have a solution that allows us to cut bootable AIX tapes on a regular basis. (Not all of the systems have local tape drives. The procedure can not be automated. etc.) In the future we must restore all RS/6000s with only our vaulted installation media (OS and TSM) as well as our vaulted TSM tapes. Due to this we must develop procedures for a total bare metal restore of an RS/6000 using only the OS installation media, TSM backup tapes, and any relevant TSM disaster recovery reports. We would like to develop a procedure that details the recovery of a generic RS/6000 using only installation media, TSM backup, and disaster recovery reports. Ideas/Things to consider: We can not assume that we will recover systems to identical hardware. As such we can not simply install a base OS and restore. What system files (/etc/passwd, /etc/hosts, etc...) are relevant to the recovery of the system. What system files should not be recovered? (I.e. kernel, driver specific, etc.) Can anyone help with any existing procedures or point me in the proper direction? Thanks! DaveZ
Re: TSM 4.2 (AIX), licensing..
Tom - I had the same problem - you need to remove the nodelock file and
re-register. Re-issuing the command
without removing the nodelock file just increases the number.
-Original Message-
From: Tom Tann{s [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 9:46 AM
To: [EMAIL PROTECTED]
Subject: TSM 4.2 (AIX), licensing..
Hello!
I upgraded a server from 4.1 to 4.2 today.
I've only managed to register one 50mgsyslan.lic whith the command
register lic file=50mgsyslan.lic number=12
additional attempts toregister more result in the same..
tsm: SUMOregister license file=50mgsyslan.lic
ANR2852I Current license information:
ANR2827I Server is licensed to support Managed System for LAN for a
quantity of 60.
ANR2853I New license information:
ANR2827I Server is licensed to support Managed System for LAN for a
quantity of 60.
tsm: SUMO
(Its 60 now because I successfully registered one 10mgsyslan.lic)
After several attempts I took a look at the nodelock-file, and this file
seems to be updated correctly, with one entry for each of my attempts..
.
.
.
.
# Managed System for LAN 50 Licen
6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 8umtikm47qkykpffafnaa 4.2
#[admin_comment] 0 0 0
# Managed System for LAN 50 Licen
6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 8umtikm47qkykpffafnaa 4.2
#[admin_comment] 0 0 0
So... Could this be a bug, or am I missing something here?
