Mt Xia: Technical Consulting Group

Business Continuity / Disaster Recovery / High Availability
Data Center Automation / Audit Response / Audit Compliance

-
Current Location
-

css
  GlobalSysAdmin
    AIX

-

digg Digg this page
del.icio.us Post to del.icio.us
Slashdot Slashdot it!


Business Web Site Hosting
$3.99 / month includes Tools,
Shopping Cart, Site Builder

www.siteox.com

FREE Domain Registration
included with Web Site Hosting
Tools, Social Networking, Blog

www.siteox.com

Synopsis:

 

Received instructions to evaluate status of production EDMS server for corporate IT.

Server was not operational, optical drives were not available.  IBM had been contacted ADSM server still in an inoperative status. 

 

Initial inspection indicated ADSM server was not active.  While attempting to initialize ADSM server start-up procedure indicated the lack of disk space forced start-up to abort thus forcing us to pursue a disk space problem.  In consultation with EDMS server administrator decided to pursue solution the following morning.

 

Evaluated existing file systems and found adequate space for recovery in the /adsm2 file system.  Defined and formatted 500MB of disk space to be utilized in the recovery log required to restart ADSM server. 

From AIX superuser command line , issued command: (from /usr/lpp/adsmserv/bin)

 

./dsmfmt –m /adsm2/dbxx.logxxx.dsm 500

 

Next command issued was:

 

./dsmserv extend log /adsm2/dbxx.logxxx.dsm 500

 

Issued DSM server start command rendering good results.

 

Command used was ./dsmserv &

 

Verified that all ADSM server configurations were configured correctly.

Next step was to exercise configured devices within ADSM server thus discovering inoperability within configured devices.

Next step was to verify configuration for adsm from the operating system side, and found that no devices were configured.

Lsdev –Cs scsi

 

cd0    Available 10-60-00-4,0  SCSI Multimedia CD-ROM Drive

rmt0   Available 10-60-00-5,0  SCSI 8mm Tape Drive

hdisk0 Available 10-60-00-8,0  16 Bit LVD SCSI Disk Drive

hdisk1 Available 10-60-00-9,0  16 Bit LVD SCSI Disk Drive

hdisk2 Available 10-60-00-10,0 16 Bit LVD SCSI Disk Drive

hdisk3 Available 10-60-00-11,0 16 Bit LVD SCSI Disk Drive

ses0   Available 10-60-00-15,0 SCSI Enclosure Services Device

omd0   Available 40-58-00-1,0  SCSI Read/Write Optical Drive

omd1   Available 40-58-00-2,0  SCSI Read/Write Optical Drive

omd2   Available 40-58-00-3,0  SCSI Read/Write Optical Drive

omd3   Available 40-58-00-4,0  SCSI Read/Write Optical Drive

lb0    Available 40-58-00-6,0  ADSM Library

 

 

Halted adsm server to define adsm devices on the operating system then restart adsm once devices were defined.

 

Instructed the AIX administrator to define the missing adsm devices, they should reflect the same addresses as the SCSI Read/Write Optical Drives found  previously.

After devices were defined issued same command as before to verify.

 

cd0    Available 10-60-00-4,0  SCSI Multimedia CD-ROM Drive

rmt0   Available 10-60-00-5,0  SCSI 8mm Tape Drive

hdisk0 Available 10-60-00-8,0  16 Bit LVD SCSI Disk Drive

hdisk1 Available 10-60-00-9,0  16 Bit LVD SCSI Disk Drive

hdisk2 Available 10-60-00-10,0 16 Bit LVD SCSI Disk Drive

hdisk3 Available 10-60-00-11,0 16 Bit LVD SCSI Disk Drive

ses0   Available 10-60-00-15,0 SCSI Enclosure Services Device

omd0   Available 40-58-00-1,0  SCSI Read/Write Optical Drive

omd1   Available 40-58-00-2,0  SCSI Read/Write Optical Drive

omd2   Available 40-58-00-3,0  SCSI Read/Write Optical Drive

omd3   Available 40-58-00-4,0  SCSI Read/Write Optical Drive

lb0    Available 40-58-00-6,0  ADSM Library

op0    Available 40-58-00-1,0  ADSM Read/Write Optical Drive

op1    Available 40-58-00-2,0  ADSM Read/Write Optical Drive

op2    Available 40-58-00-3,0  ADSM Read/Write Optical Drive

op3    Available 40-58-00-4,0  ADSM Read/Write Optical Drive

 

 

Restarted adsm server at this time and we were able to manipulate  optical drives.

 

With having adsm server operational attempted several recalls and migrates with favorable results.

 

Checked the adsm database status and found that it was running at 100% with no room to grow. Consulted with AIX admin and opted to define an additional 1gb  adsm db volume in the /adsm2 filesystem in order  for the database to operate at an acceptable utilization % and have room for growth.

 

Define dbvol /adsm2/db5.dsm 1000

 

Extend db 500

 

This process allocated a 1gb volume and extended the database by 500 mb thus keeping additional space available.

 

 

 

-
EDMS PROD Support Doc
-
 


FREE Domain Registration
included with Web Site Hosting
Tools, Social Networking, Blog

www.siteox.com

Business Web Site Hosting
$3.99 / month includes Tools,
Shopping Cart, Site Builder

www.siteox.com