Re: Dsmcad listening port

[Mike De Gasperis]

You don't need to run the dsmcad technically speaking. You can just run a dsmc 
sched daemon or service. 

> On Dec 18, 2015, at 10:47 AM, Henrik Ahlgren  wrote:
> 
>> On Fri, Dec 18, 2015 at 12:40:46PM +0300, Efim wrote:
>> 
>> CAD opens random port because the option WEBPORT has default value "0 0" and 
>> CAD randomly assign a free TCPport (the first parameter for CAD, the second 
>> for WEB client).
>> I think it’s impossible to prevent this.
>> As workaround you can set fixed port(s) and close it using firewall.
>> Example: WEBPORT 55000 0 or WEBPORT 55000 55001
> 
> Am I the only one that finds this design totally unacceptable? If
> you're not using the webclient functionality and are only using
> schedmode polling, I don't see any reason why dsmcad (often running as
> root, so the security implications are obvious) should listen to a
> network port. Perhaps there is something I am not aware of?
> 
> One might think that setting tcpclientaddress to 127.0.0.1 (localhost)
> would somewhat migitate this, but no - it does not have any effect if
> you are not using schedmode prompted. Yes, of course it is always
> possible to use host-based firewalls to close the ports, but it is a
> workaround that really should not be necessary.

Re: help with designing a backup system for Teradata

[Mike De Gasperis]

Do you have DDboost licensed?  Could always use the boost plugin and go right 
to the DD and skip the TSM server. 



> On Jul 30, 2015, at 1:00 PM, Rhodes, Richard L.  
> wrote:
> 
> We purchased a Teredata database system.
> It currently is in test/dev stage with little data.
> We don't really know the ultimate backup requirements.
> To get things started we setup a simple backup system:
> 
>   Teradata
>-> to Bar server (Win) with TSM interface sftw
>-> to TSM server (AIX)
>-> to filepool on DataDomain (getting ~5x dedup)
> 
>   From the Bar server to TSM server is a standard 1GB ethernet.
> 
> Now we need to scale up/out!
> 
> The consultants are saying we will need to backup 30TB in a 6hr window,
> but maybe has high as 50TB in 6hr.
> That is (roughly):
> 30TB in 6hr = 1,400 MB/sec
> 50TB in 6hr = 2,300 MB/sec
> 
> So we need to design a TSM backup system to support this.
> 
> My thoughts:
> 
> 1) Put a storage agent on the Bar server (Win server)
> and feed a VTL via 4x8gb san connections via a bunch of virtual tape.
> 
> 2) Put the TSM server directly on the Bar server for just
> local tape and still feed a VTL as above.
> No library sharing.
> 
> 3) I'd really like to not use tape (even virtual tape),
> but I can't think of any way to feed file devices
> with that throughput.
> 
> I'd appreciate any thought/comments anyone might have!
> 
> Thanks
> 
> Rick
> 
> 
> 
> 
> -
> The information contained in this message is intended only for the personal 
> and confidential use of the recipient(s) named above. 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, and delete the original 
> message.

Re: TS3500 and S24/S54 frames with TSM?

[Mike De Gasperis]

Like Paul mentioned, great price point for storage you get out of them. No 
drives allowed in the frame though if that's an issue for you, I also believe 
it will require the enhanced node cards and ALMS feature to be purchased from 
what I recall when we purchases ours. There is the ability to disable slots in 
them as well if they go bad or are damaged which will be useful. You also don't 
have to license the full capacity right off the bat if you don't require it. 
S54 is the LTO model, S24 is the 3592 model if you weren't aware already.

- Original Message -
Hi Wanda,

Yeah, we've got two 3584's with S54 frames. I love the price point and density. 
They have worked pretty well. We've had the usual drive problems (they do wear 
out after awhile), and one picker issue, but nothing specific to the S54. We 
use ALMS which gets us slot virtualization, which works very nicely too. We've 
had the S54s since just after they were announced, so we've got a long track 
record with them. I'd buy them again if I had it to do all over again.

..Paul

At 03:30 PM 4/14/2014, Prather, Wanda wrote:
>Anybody using a TS3500 library S24/S54 frame with TSM?
>Any gotchas?
>Good/bad news?
>
>
>
>**Please note new office phone:
>Wanda Prather | Senior Technical Specialist | 
>wanda.prat...@icfi.com | 
>www.icfi.com | 410-868-4872 (m)
>ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md 
>|443-718-4900 (o)


--
Paul Zarnowski Ph: 607-255-4757
Assistant Director of Storage Services Fx: 607-255-8521
IT at Cornell / Infrastructure Em: p...@cornell.edu
719 Rhodes Hall, Ithaca, NY 14853-3801

Re: Redundant Tape SAN

[Mike De Gasperis]

I personally think it's worth the effort, not so much for the fail-over but for 
the fact the Atape driver will do some HBA load balancing for you to maximize 
performance across less utilized HBA ports. We do have a few ProtecTier's in 
the mix and also a Windows 2008R2 based LAN Free server, the LF server actually 
utilizes some of this redundancy as well and the IBM Tape driver load balancing 
as well. For the VTL based devices what we typically do is rename the rmt 
entries in AIX based on their serial number since they've typically been just 
different drives behind the same front end WWPN's.

We're running 60 physical LTO5's and 128 emulated LTO3 devices from the PT for 
comparisons sake. With some scripts work wise it isn't too much more effort.


- Original Message -
Is it worth the work?
Are there any VTLs involved?

I may be doing 4 TSM servers to 18x 3952's, 8x LTO6 shared drives and 120x 
LTO1's for each server non-shared in multiple DataDomains. I also have LANFree 
clients that do not support redundant fabrics.

Thank you,

Andy Huebner


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mike 
De Gasperis
Sent: Wednesday, February 26, 2014 8:44 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Redundant Tape SAN

We utilize a redundant tape SAN at our main data centers with multiple host 
site HBA ports. Using the Atape control and data path fail-over options we have 
twelve device entries for each physical tape device. Works really well and this 
is in an AIX/LPAR/VIO environment, we've virtualized the HBA ports and are 
using NPIV. We have some scripts created that rename each rmt entry via chdev 
to utilize the last four digits of the WWPN and the AIX fiber channel adapter 
to make things easier to line up as well when defining drives in TSM.

- Original Message -
Is anyone using redundant tape SAN with TSM on AIX?

Andy Huebner

Re: Redundant Tape SAN

[Mike De Gasperis]

We utilize a redundant tape SAN at our main data centers with multiple host 
site HBA ports. Using the Atape control and data path fail-over options we have 
twelve device entries for each physical tape device. Works really well and this 
is in an AIX/LPAR/VIO environment, we've virtualized the HBA ports and are 
using NPIV. We have some scripts created that rename each rmt entry via chdev 
to utilize the last four digits of the WWPN and the AIX fiber channel adapter 
to make things easier to line up as well when defining drives in TSM.

- Original Message -
Is anyone using redundant tape SAN with TSM on AIX?

Andy Huebner

Re: Another VE mystery - restoring from tape - but shouldn't be

[Mike De Gasperis]

To go along with Andy's recommendations I've seen in TSM server 6.2.3.0
where a query occupancy and a select from occupancy don't match up.   Might
be worthwhile to do a:

select * from occupancy where node_name='DC1' and
filespace='\VMFULL-HWDDMZOCULARX1'

See how they compare

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Andrew Raibeck
Sent: Wednesday, June 19, 2013 12:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Another VE mystery - restoring from tape - but
shouldn't be

Hi Wanda,

Identify one of the tapes being mounted from TAPEPOOL2, then do a QUERY
CONTENT on it. See if there is anything for DC1. There has to be
*something* even if we haven't yet put our finger on it.

Best regards,

- Andy



Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Stor
age_Manager

Online documentation:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli
Documentation Central/page/Tivoli Storage Manager Product Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli
+Storage+Manager/page/Home

"ADSM: Dist Stor Manager"  wrote on 2013-06-19
11:53:07:

> From: "Prather, Wanda" 
> To: ADSM-L@vm.marist.edu,
> Date: 2013-06-19 11:55
> Subject: Re: Another VE mystery - restoring from tape - but shouldn't
> be Sent by: "ADSM: Dist Stor Manager" 
>
> Richard,
> Here is the Q OCC result.
> The Q OCC shows all the data for FSID 86 is in VMCTLMC (seq disk),
> SLOWDEDUP (seq disk) or the COPYPOOL (tape COPY pool).
>
> But when the customer tries a restore, the tapes getting mounted are
> from primary pool TAPEPOOL2.
> How can a restore be calling for tapes in a pool where the filespace
> has no data according to Q OCC?
> I suggested they open a sev 1 with Tivoli.  This can't be right.
>
>
> tsm: HCG-TSM-SERVER>q occ dc1 86 nametype=fsid
>
> Node Name  Type Filespace   FSID Storage
> Number of  Physical   Logical
> Name Pool Name
> Files Space Space
>
> Occupied  Occupied
>
> (MB)  (MB)
> --  -- - --
> - - -
> DC1Bkup \VMFULL-H-86 COPYPOOL
> 8,928 99,057.72 99,062.73
>  WDDMZOCU-
>  LARX1
> DC1Bkup \VMFULL-H-86 SLOWDEDUP
> 4,464 - 98,733.95
>  WDDMZOCU-
>  LARX1
> DC1Bkup \VMFULL-H-86 VMCTLMC
> 4,464315.14315.14
>  WDDMZOCU-
>  LARX1
>
> -Original Message-
> From: Prather, Wanda
> Sent: Wednesday, June 19, 2013 11:03 AM
> To: Richard Cowen
> Subject: RE: Another VE mystery - restoring from tape - but shouldn't
> be
>
> >>Did the MOVE NODEDATA result in a zillion new volumes (.BFS's) ?
> No, we don't use scratch volumes in the seq disk pool
>
>
> >>Can you get the activity log for the time the process(es) ran ?
> Any chance you have query occupancy node=dcname filespace=victim1
> stgpool= before and after move?
> If not, does the query for tape pool now show zero?
>
> Don't have them and right now I don't have access, but those are great
> ideas, will ask the customer for them.
>
> Thanks!
>
> Wanda
>
> -Original Message-
> From: Prather, Wanda [mailto:wanda.prat...@icfi.com]
> Sent: Tuesday, June 18, 2013 11:35 AM
> To: Richard Cowen
> Subject: RE: Another VE mystery - restoring from tape - but shouldn't
> be
>
> Hi Richard,
>
>
> >>Did you get a "zillion" tape mounts during the MOVE NODEDATA?
> Yes
>
>
> >>Do you know it finished without errors?
> Yes.  And we ran another MOVE NODEDATA to verify there was no more
> data to move for that filespace.
>
> >>How, exactly, did the data go from sequential fast disk ->
> sequential slow disk - > tape ?
> Ordinary migration, at different times, as the pools hit migration
thresholds.
>
> >>I didn't think TSM would "migrate" more than one level, so maybe
> the last step was using a MOVE command?
> Yes, your migration hierarchy can have as many levels as you want, as
> long as you don't try to go from a sequential pool back to a disk
> (random) pool.
>
> >>What does a QUERY NODEDATA show for primary pools and copy pools?
> Would not be informative, as we only moved some of the filespaces, not
> all of them.
>
> >>Are you running aggressive reclamation on the tape pool?
> No, and it's not collocated.  Which is why we decided to move the
> filespace back to the seq disk pool.
> I don't think it's odd the data was too spread out to make the restore
> from tape not work well.
> What is odd is that all the da

Re: Implementing Encryption

[Mike De Gasperis]

Forgot to include this link from IBM regarding their EKM support.

http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000504


- Original Message -
Wanda,

As always, thanks for the detailed explanation. However, it brings up lots
of questions.

>>> With externally-managed encryption, the keys are managed by the EKM.

Since this would be hardware-based and encrypts everything, this is the way
we would go.

>>> You set the encryption mode on the library to library-managed. The EKM
has to be run on a server. It is a pay-for product.

Huh? I downloaded EKM from the IBM FTP sight. It is Java based and nobody
ever said anything about paying for it? As I understand it, in this
scenario with our 3494 (soon to be replace with a TS3500/3584), the "EKM
server" has to talk to the tape library to get the keys from it
(DRIVEE=ALLOW). When Googling, one doc/comment we saw the person simply
installed it on the TSM server. My question, since I am running 7-servers,
do I need multiple instance - one per TSM server or just one and it gets
everything from the 3494? I am confused..

>>> High learning curve. Lots of testing required to make sure you can
recover.

Agreed. We are still digging through the docs on just installing and
implementing EKM and who connects to who and where..

>>> You have to be careful about protecting the EKM; you have to recover
the EKM at a DR site before you can read your tapes.
(If you have a hot site, better to share the keys between the libraries.)

More like a "lukewarm sight" - I have an offsite vault/TSM server where the
tapes are stored and daily each production TSM server does a DB backup to
the offsite TSM server.

>>> But with the EKM, your security group can control the key management,
certificate changing, etc. And then DB backup tapes, EXPORT, and BACKUPSET
tapes can be encrypted.

This totally throws me off - I really need a "paint by numbers" diagram on
how all the pieces connect - I have never dealt with encryption.


On Thu, Apr 4, 2013 at 12:10 PM, Prather, Wanda wrote:

> With externally-managed encryption, the keys are managed by the EKM.
> TSM doesn't' know it's happening.
> You set the encryption mode on the library to library-managed.
> The EKM has to be run on a server. It is a pay-for product.
> But the cost of the software is trivial compared to the implementation
> cost.
> High learning curve. Lots of testing required to make sure you can
> recover.
>
> You have to be careful about protecting the EKM; you have to recover the
> EKM at a DR site before you can read your tapes.
> (If you have a hot site, better to share the keys between the libraries.)
> It is possible (not likely, but possible) to get yourself in a DR
> situation where NOBODY, including IBM, can read those encrypted tapes.
> Test, test, CYA, test.
> But with the EKM, your security group can control the key management,
> certificate changing, etc.
> And then DB backup tapes, EXPORT, and BACKUPSET tapes can be encrypted.
>




--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: Implementing Encryption

[Mike De Gasperis]

I've never dealt with the EKM but it looks to be a legacy product that will be 
phased out by IBM.

You'll want to look at the TKLM product which does require licensing for the 
drives that will be encrypting as well as for the actual TKLM servers 
themselves. We ended up setting up four TKLM servers in our environment. Two at 
our prod site and two at DR to protect against failure.

- Original Message -
Wanda,

As always, thanks for the detailed explanation. However, it brings up lots
of questions.

>>> With externally-managed encryption, the keys are managed by the EKM.

Since this would be hardware-based and encrypts everything, this is the way
we would go.

>>> You set the encryption mode on the library to library-managed. The EKM
has to be run on a server. It is a pay-for product.

Huh? I downloaded EKM from the IBM FTP sight. It is Java based and nobody
ever said anything about paying for it? As I understand it, in this
scenario with our 3494 (soon to be replace with a TS3500/3584), the "EKM
server" has to talk to the tape library to get the keys from it
(DRIVEE=ALLOW). When Googling, one doc/comment we saw the person simply
installed it on the TSM server. My question, since I am running 7-servers,
do I need multiple instance - one per TSM server or just one and it gets
everything from the 3494? I am confused..

>>> High learning curve. Lots of testing required to make sure you can
recover.

Agreed. We are still digging through the docs on just installing and
implementing EKM and who connects to who and where..

>>> You have to be careful about protecting the EKM; you have to recover
the EKM at a DR site before you can read your tapes.
(If you have a hot site, better to share the keys between the libraries.)

More like a "lukewarm sight" - I have an offsite vault/TSM server where the
tapes are stored and daily each production TSM server does a DB backup to
the offsite TSM server.

>>> But with the EKM, your security group can control the key management,
certificate changing, etc. And then DB backup tapes, EXPORT, and BACKUPSET
tapes can be encrypted.

This totally throws me off - I really need a "paint by numbers" diagram on
how all the pieces connect - I have never dealt with encryption.


On Thu, Apr 4, 2013 at 12:10 PM, Prather, Wanda wrote:

> With externally-managed encryption, the keys are managed by the EKM.
> TSM doesn't' know it's happening.
> You set the encryption mode on the library to library-managed.
> The EKM has to be run on a server. It is a pay-for product.
> But the cost of the software is trivial compared to the implementation
> cost.
> High learning curve. Lots of testing required to make sure you can
> recover.
>
> You have to be careful about protecting the EKM; you have to recover the
> EKM at a DR site before you can read your tapes.
> (If you have a hot site, better to share the keys between the libraries.)
> It is possible (not likely, but possible) to get yourself in a DR
> situation where NOBODY, including IBM, can read those encrypted tapes.
> Test, test, CYA, test.
> But with the EKM, your security group can control the key management,
> certificate changing, etc.
> And then DB backup tapes, EXPORT, and BACKUPSET tapes can be encrypted.
>




--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: TSM for VE 6.4 Questions/Recommendations

[Mike De Gasperis]

Good information Keith, we were really shooting to eliminate any in guest 
backups if possible with the exception of any hosts that have physical RDM's. 
Licensing wise are you guys capacity based or PVU based? We're utilizing PVU 
right now so that was another big reason we wanted to pull the agents out of 
the guests to save some costs there as well. We've found however that the file 
level recovery with TSM for VE is really too slow and unusable with any other 
back-end storage other than VTL or disk in our opinion.

Are you utilizing one overall policy for all your TSM for VE backups? Sounds 
like with the way you're capturing mainly the OS that would work really well in 
your environment.

- Original Message -
Hi Ken,
We have been using TSMVE 6.4 for a couple months, I wouldn't call the following 
a set of best practices, but they work well for the restore service we provide.

File restore services are still provided with TSM Extended Edition. Nothing 
different there. Recovery of the first disk on virtual machines is provided 
with TSMVE 6.4. Should disaster strike, the frst disk is restored by TSMVE, 
then files and directories are restored with TSM Extended Edition. We only 
snapshot the first disk.

Our standard virtual machine is created here with a first disk of 60 GB and 
additional disks for data storage. VM admins are encouraged to install their OS 
on the first disk. We snapshot the first disk only by adding this statement to 
dsm.opt for each data mover; INCLUDE.VMDISK "*" "Hard Disk 1"

If the first disk of a virtual machine is greater than 60 GB, that guest is 
excluded from snapshots by appending '-NB' to its display name in the vSphere 
client. Then, '*-NB' [ star dash NB ] is added to the exclusion filter in the 
TSMVE plug-in when a scheduled or run-now backup is created.

We use one data mover per cluster, and put the data mover on the cluster it 
backs up for performance reasons. We exclude the data mover from the backup 
using the filter, and back it up with TSM/EE. Each cluster is scheduled for 
backups once a week, and two versions are kept. Our largest cluster has 12 
hosts and about 420 guests. Our 'vmlimit' options are fairly conservative, and 
could change with more experience. Here they are:

VMMAXPARALLEL 8
VMLIMITPERHOST 0
VMLIMITPERDATASTORE 1

So far, so good.

Best wishes,
Keith Arbogast
Indiana University

TSM for VE 6.4 Questions/Recommendations

[Mike De Gasperis]

I posted this up on the adsm.org forum but I'm hoping I get more hits here.

We're getting ready to implement the agent at one of our facilities and I'm 
curious to see how everyone else is accomplishing some things we did relatively 
easy the "old" way.

How are you scheduling certain VM's at different time frames? Wondering if 
folks are using the TSM scheduler to do it and how that looks or if the vCenter 
plugin has been an easier option for you.

Policy and retention wise how are you handling VM's that may require a longer 
retention than others? Wondering if folks are just using separate management 
classes within the same policy or using multiple data move nodes. I'm also 
wondering if you're using multiple management classes are you just using 
includes within the dsm.opt or specifying in the TSM schedule somehow?

Collocation wise we're using physical tape to store these VM backups, control 
data will be in a disk area. Are you collocating by file space for these VM 
backups given the way they're stored or are you using multiple data mover nodes 
to work what needs collocation what doesn't? My main concern is the file level 
recovery is painfully slow on physical tape, going and buying a bunch of disk 
or VTL isn't a very cost effective option for us unfortunately.

I'm struggling to come up with the best practices on how to accomplish these 
items which to me we did so simply before with the in guest backup method. I 
know a lot of questions but recommendations and real world experience on these 
items would be invaluable.

Select Help

[Mike De Gasperis]

I've played around with this select before and I've never been able to get it 
perfected.

I'm looking for something that will tell me the information below for the 
active policy set and default management class

associations.node_name

client_schedules.schedule_name
client_schedules.startdate
client_schedules.starttime
client_schedules.period
client_schedules.perunits
client_schedules.dayofweek

bu_copygroups.domain_name
bu_copygroups.class_name
bu_copygroups.verexists
bu_copygroups.verdeleted
bu_copygroups.retextra
bu_copygroups.retonly

This is the closest I've gotten with a select, the problem is it returned bogus 
information for other domains. I know it's wrong I just have no idea how to 
correct it or if it's possible with the TSM SQL engine. If any of you SQL 
wizards have an idea or even an alternate better solution to get this 
information I'd greatly appreciate hearing what you have.

select associations.node_name, client_schedules.schedule_name, 
client_schedules.startdate, client_schedules.starttime, 
client_schedules.period, client_schedules.perunits, client_schedules.dayofweek, 
domains.domain_name, domains.defmgmtclass, bu_copygroups.verexists, 
bu_copygroups.verdeleted, bu_copygroups.retextra, bu_copygroups.retonly from 
client_schedules, domains, bu_copygroups, associations associations where 
client_schedules.schedule_name=associations.schedule_name and 
bu_copygroups.class_name=domains.defmgmtclass

TSM V6 Instance ID

[Mike De Gasperis]

I was wondering what everyone else has done for instance ID's on their AIX or 
other UNIX systems for the DB2 instance ID. Are there any issues having the ID 
with no password but not being allowed to login via telnet/ssh outside of 
su'ing from root?

I was also going to request the file ulimit being set to unlimited, are there 
any other specific ulimit's I should change to unlimited or increase in 
general? For the user home directory did you just use the default /home or did 
you split it off in to a separate file space, we're thinking separate file 
space at this time.

I wasn't able to find too much on specifics for the user ID so I apologize if 
this has been asked before or covered in depth somewhere.

- Mike

Re: Ang: ANR0361E Database initialization failed

[Mike De Gasperis]

Are you sure nothing else was possibly using that raw volume?

Wondering if this is the only instance of TSM on this server? I know in my past 
experience with SUN systems that you can mistakenly grab raw volumes like this 
that may have been in use by something else.

Do you have a q dbv, q logv, and q vol devc=disk output?

- Original Message -
From: "Lance Nakata" 
To: ADSM-L@VM.MARIST.EDU
Sent: Wednesday, September 8, 2010 12:48:03 PM
Subject: Re: [ADSM-L] Ang: ANR0361E Database initialization failed

On Wed, Sep 08, 2010 at 08:26:16AM +0200, Daniel Sparrman wrote:
> The first APAR you linked is also about volume size over
> 250GB, not the entire database. I'm guessing your database
> voluimes are below 250GB.
...
> Do you know if the volume /dev/rdsk/c0t7d0s4 was allocated
> before the extend, or if TSM started using it after you
> have extended the database?

My TSM-mirrored database volumes are on dedicated 1TB disks,
where each disk's slice 4 partition is 512GB. The 512GB
size was set during the initial install. I extended the DB
from 200GB to 300GB without changing the volume's 512GB
size.

> Are you able to start TSM (while still getting the errors)
> or does the server crash upon starting it?

The TSM server will not start up:

ANR7800I DSMSERV generated at 12:43:45 on Mar 15 2010.
ANR7801I Subsystem process ID is 6464.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 12296 megabytes.
ANR0201I Database assigned capacity is 304800 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0207E Page address mismatch detected on database volume /dev/rdsk/c0t7d0s4, 
logical page 0
(physical page 256); actual: 67108864.
ANR0207E Page address mismatch detected on database volume /dev/rdsk/c1t7d0s4, 
logical page 0
(physical page 256); actual: 67108864.
ANR0248E Unable to read database page 0 from any alternate copy.
ANRD_3229212849 DbAllocInit(dballoc.c:1353) Thread<1>: Error reading space 
map page from
disk.
ANR0361E Database initialization failed: error initializing database page 
allocator.

> If you're unable to start the server, I'd say it's either
> a database restore, or, if you want to try to salvage the
> database, a database audit.

Thanks Daniel. I'm also trying to get help from IBM TSM support.

--
Lance Nakata
SLAC National Accelerator Laboratory

Novell Support

[Mike De Gasperis]

We had a question come up due to some new systems coming online, is IBM
continuing to support the Novell platform after the 5.5 version of it's
TSM client?

The best I can find on the IBM page says it will be supported with the
5.5 client as long as TSM 6.1 is supported but there's no detailed
requirements on it as the link for it comes up with a page error.
Document not found when you click on the actual NetWare link next to the
client

Supported with 5.5-level client

   * NetWare 6.5 only

   * Not supported


NOTE: 5.5-level client included in 6.1 is supported in use with
6.2-level server for as long as TSM 6.1 is in service

http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&uid=swg21243309&loc=en_US&cs=utf-8&lang=en#NetWare

TSM 6.2 Raw Logical Volume Ownership

[Mike De Gasperis]

I was reading through the upgrade guides on IBM's site and I came accross a 
section about modifying ownership of any disk volumes so they would be 
read/write for the instance owner. I'm assuming this is true for RAW logical 
volumes as well but can anyone confirm? For example I was wondering if it needs 
to be modified on the /dev/rsp01_lv1 link or the actual /dev/sp01_lv1 device?