Backing up nodes in a different Network Domain

[william dourado]

 


Hi all,
 
It's a possibility that our 3 sister companies on the same site currently 
sharing
the same LAN maybe split into 3 network domains using Vlans and firewalls.
 
 All 3 Domains will somehow, have access to central services like internet, 
accounting applications, etc.
 
We intend to retain the one TSM Server that we have. 
 
If the TSM Server is say in Domain A, is it possible to backup clients in 
domains B and C ?
 
Are there any drawbacks ?
 
TSM Server Windows V5.4.2.0
 
Many Thanks
 
Bill
 
 



View your Twitter and Flickr updates from one place – Learn more!
_
Get the best of MSN on your mobile
http://clk.atdmt.com/UKM/go/147991039/direct/01/

Re: Backing up nodes in a different Network Domain

[Tchuise, Bertaut]

Hello Bill,

Granted that have the appropriate trust relationships configured between
the domains, appropriate firewall rules and efficient performance
tuning, you can backup clients residing in a domain different to that of
your TSM server. In our Storage environment, we backup numerous clients
in our affiliate domains with the TSM server being in our domain; we
have no issue with our setup.

>>Are there any drawbacks ?<<
All depends in your environment and your setup. You may need to work
alongside your Infrastructure and Network Engineering for design and
implementation.

Good luck.

BERTAUT TCHUISE
Storage Support Administrator
Legg Mason Technology Services
*410-580-7032
btchu...@leggmason.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
william dourado
Sent: Wednesday, July 01, 2009 7:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Backing up nodes in a different Network Domain




Hi all,

It's a possibility that our 3 sister companies on the same site
currently sharing the same LAN maybe split into 3 network domains using
Vlans and firewalls.

 All 3 Domains will somehow, have access to central services like
internet, accounting applications, etc.

We intend to retain the one TSM Server that we have.

If the TSM Server is say in Domain A, is it possible to backup clients
in domains B and C ?

Are there any drawbacks ?

TSM Server Windows V5.4.2.0

Many Thanks

Bill





View your Twitter and Flickr updates from one place - Learn more!
_
Get the best of MSN on your mobile
http://clk.atdmt.com/UKM/go/147991039/direct/01/

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.

TSM Server 6.1 Dependency for Linux?

[Christian Svensson]

Hi everyone,
Just wonder if anyone have type down the total Dependency list to install TSM 
6.1 on Linux 86_64?

This is how far I got
* rpm
* jre-6
* libstdc++5
* libaio, libaio0 and libaio1
* glibc

Does anyone know anything else that should be added to this list?



Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson

Re: Backing up nodes in a different Network Domain

[Len Boyle]

Hello Bill, 

As other have posted, TSM should handle the backups without problems related to 
the use of different network domains. 

But. You might want to look at why there are different domains. Might you 
expect that in the future that one or more of the 3 sister companies might be 
sold or split off totally. 
If so you might want to set up your tsm domains, storage pools etc, so that the 
sister companies do not share resources such as tapes. 

len

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of 
william dourado
Sent: Wednesday, July 01, 2009 7:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Backing up nodes in a different Network Domain

 


Hi all,
 
It's a possibility that our 3 sister companies on the same site currently 
sharing
the same LAN maybe split into 3 network domains using Vlans and firewalls.
 
 All 3 Domains will somehow, have access to central services like internet, 
accounting applications, etc.
 
We intend to retain the one TSM Server that we have. 
 
If the TSM Server is say in Domain A, is it possible to backup clients in 
domains B and C ?
 
Are there any drawbacks ?
 
TSM Server Windows V5.4.2.0
 
Many Thanks
 
Bill
 
 



View your Twitter and Flickr updates from one place - Learn more!
_
Get the best of MSN on your mobile
http://clk.atdmt.com/UKM/go/147991039/direct/01/

Drive problem in AIX. I'm lost...

[Loon, EJ van - SPLXM]

People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l  -a
new_name= to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines


**
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.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**

Re: Backing up nodes in a different Network Domain

[Buddy Howeth]

We have one Windows NT domain and one Active Directory domain and back 
both up with the same TSM server without problem


Buddy Howeth
Computer Operations Specialist
Information Systems
Pacific Coast Producers
Corporate Offices
631 N. Cluff Ave
Lodi, CA  95240-0756
(209) 367-8800 - Main#
(209) 367-6288 - Computer Room
(209) 366-6240 - Alpha Pager





william dourado  
Sent by: "ADSM: Dist Stor Manager" 
07/01/2009 04:18 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
[ADSM-L] Backing up nodes in a different Network Domain






 


Hi all,
 
It's a possibility that our 3 sister companies on the same site currently 
sharing
the same LAN maybe split into 3 network domains using Vlans and firewalls.
 
 All 3 Domains will somehow, have access to central services like 
internet, accounting applications, etc.
 
We intend to retain the one TSM Server that we have. 
 
If the TSM Server is say in Domain A, is it possible to backup clients in 
domains B and C ?
 
Are there any drawbacks ?
 
TSM Server Windows V5.4.2.0
 
Many Thanks
 
Bill
 
 



View your Twitter and Flickr updates from one place – Learn more!
_
Get the best of MSN on your mobile
http://clk.atdmt.com/UKM/go/147991039/direct/01/

_
Scanned by IBM Email Security Management Services powered by MessageLabs. 
For more information please visit http://www.ers.ibm.com
_

Re: Drive problem in AIX. I'm lost...

[Richard Rhodes]

I'm a little confused on what you are trying to do.  Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?

Also, are you using Atape multi pathing?







 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:cc
 Dist Stor
 Manager"  Subject
 


 07/01/2009 10:00
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l  -a
new_name= to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines


**
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.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**



-
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: TSM vs Avamar

[Wanda Prather]

I agree entirely that "VCB" and "beauty" together does not compute, and the
2-phase vmdk restore is dorky.

But regarding the backup cycle, there is an "in between" option most TSM
folks can use without taking the hit of two complete backups ("virtual
drive" and "image" as described below) daily.

TSM has a "restore if newer" option.
Suppose you do your image backups weekly (and that's the one with the
biggest hit on your infrastructure, because it's the entire vmdk image), and
just your progressive incrementals daily.

You can put back the virtual machine by restoring the .vmdk image, then use
the "restore if newer" option to apply the incrementals back on top of the
.vmdk image.  Yes, it will take a bit longer, and more tape mounts.  But
many people, for a large number of their systems, will be able to get
sufficient coverage that way, without taking the hit of doing those full
image backups every day.

Just another strategy.

W




On Mon, Jun 29, 2009 at 7:48 PM, W. Curtis Preston wrote:

> john D. Schneider said:
>
> >The beauty of VCB is that it doesn't require a client install on each
> >machine; there is less administration per VM, which means less time.
>
> Hmmm. Not sure I'd use "beauty" and "VCB" in the same sentence. ;)  I
> usually say that VCB stands for Very Complicated Backup. ;)
>
> I'm not defending the Avamar method.  I'm just saying the VCB method is not
> all that great either -- regardless of which backup product is using it.
>
> With most backup software, you generally have two options with VCB. One
> option mounts the virtual disk as a drive letter on the proxy server
> allowing you to do progressive incrementals against it.  (I'll call this
> the
> virtual drive method.)  The other method copies the VMDK in its entirety to
> the proxy machine's staging disk; this copy is then copied again when it is
> backed up via TSM or any other backup software.  I'll call this the image
> method.
>
> The virtual drive method is alright, but gives you no way to recover a VM.
> The image method allows you to recover the VM, but it requires two full
> backups every night.  While you are right about moving the load off the ESX
> server, don't forget the load you're placing on your storage infrastructure
> doing two full backups every night if you choose the image methohd.  And
> don't forget that doing a restore requires two steps as well: restoring to
> the proxy server then copying from the proxy server to the ESX server.
>
> My summary statement is that I think that all VMware backup options kind of
> stink right now (short of moving your VMware filesystems to a N-series
> filer
> and doing SnapManager for VI).  I therefore think that people interested in
> (but not yet using) VCB should wait until TSM supports vSphere, which gets
> rid of the stupid two-step backup and two-step restore.
>
> Just my $0.02.
>

Re: Drive problem in AIX. I'm lost...

[Nicholas Rodolfich]

Confusing!!

1. In UNIX, special characters are reserved for special functions and
special care must be taken to not have these characters interpreted during
code execution. As a result, using UNIX specific device names as names for
your TSM resources is asking for trouble!
2.  Why aren't you using some mnemonic names that make sense to humans such
as IBM3584, or DRIVE1, DRIVE2, etc.?
3.  Why would you have written a script to do something that is done so
infrequently?  How many times a day do you rename you libraries and drives?



Regards,

Nicholas

Re: Backing up nodes in a different Network Domain

[Huebner,Andy,FORT WORTH,IT]

I am not sure of your use of the word domain.
Windows domains are not relevant because TSM does need a Windows account to 
work.  We have two domains, no problem.
DNS domains are only troublesome if the TSM server is unable to resolve the 
nodes IP address due to a DNS lookup problem.  We have 2 internal domains and 
sometimes one fails to forward the request to the other.
I have not heard a network guy refer to a VLAN, Subnet, DMZ or segment as a 
domain.  Perhaps I need to get out more.  We have a segment of our network that 
is firewalled, but the firewalls allow our TSM ports to pass so there is not an 
issue backing up the servers.  Our DMZs are much tighter and the TSM server is 
not allowed to pass, so the nodes are set to polling and they contact the TSM 
server to get their schedule.
TSM has its own domains, and as suggested, it might be a good idea to have each 
of the groups in a separate domain.


Andy Huebner

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of 
william dourado
Sent: Wednesday, July 01, 2009 6:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Backing up nodes in a different Network Domain

 


Hi all,
 
It's a possibility that our 3 sister companies on the same site currently 
sharing
the same LAN maybe split into 3 network domains using Vlans and firewalls.
 
 All 3 Domains will somehow, have access to central services like internet, 
accounting applications, etc.
 
We intend to retain the one TSM Server that we have. 
 
If the TSM Server is say in Domain A, is it possible to backup clients in 
domains B and C ?
 
Are there any drawbacks ?
 
TSM Server Windows V5.4.2.0
 
Many Thanks
 
Bill
 
 



View your Twitter and Flickr updates from one place - Learn more!
_
Get the best of MSN on your mobile
http://clk.atdmt.com/UKM/go/147991039/direct/01/


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

Re: Drive problem in AIX. I'm lost...

[Loon, EJ van - SPLXM]

Hi Richard!
It's a virtual library from EMC in which I created two libraries, one
for the first TSM instance, the other one for the other instance. TSM1
uses the renamed devices (/dev/253 with drives /dev/253_0 to 29) and I
could create paths to the drives succesfully on that TSM instance. On
the other TSM instance, I can only use the devices as long as the name
starts with rmt. As soon as I rename them to 254_0 to 29 (our standard
naming convention) I receive an I/O error when I try to create the path.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: woensdag 1 juli 2009 16:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Drive problem in AIX. I'm lost...

I'm a little confused on what you are trying to do.  Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?

Also, are you using Atape multi pathing?







 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:
cc
 Dist Stor
 Manager"
Subject
 


 07/01/2009 10:00
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l  -a
new_name= to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines


**
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.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**



-
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.
**
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 subsidiari

Re: Drive problem in AIX. I'm lost...

[Loon, EJ van - SPLXM]

Hi Nicholas!
1) I know, but it has always worked this way and it does still work for
the other TSM instance running on the same host!
2) Because we use multiple libraries and drives. In fact it's an AIX
cluster which runs two TSM instances on every node. Since it's a HACMP
cluster, one cluster node should be able to run all four TSM's and thus
all libraries and all drives should be available on both the HACMP
nodes. To be able to see which tape device belongs to which library
device in AIX, we decided to use this naming convention. Since the SCSI
id is a unique parameter which can be queried from AIX, it can be used
for automating (read scripting) the renames.
3) Each library contains 30 drives. If a host adapter dies, it will be
replaced by a new one. I have to re-zone (it's fiber channel attached)
all the drives and recreate the tape drives on the host and update them
in TSM. It's all scripted to make no mistakes and to fix it a.s.a.p.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Nicholas Rodolfich
Sent: woensdag 1 juli 2009 16:43
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Drive problem in AIX. I'm lost...

Confusing!!

1. In UNIX, special characters are reserved for special functions and
special care must be taken to not have these characters interpreted
during
code execution. As a result, using UNIX specific device names as names
for
your TSM resources is asking for trouble!
2.  Why aren't you using some mnemonic names that make sense to humans
such
as IBM3584, or DRIVE1, DRIVE2, etc.?
3.  Why would you have written a script to do something that is done so
infrequently?  How many times a day do you rename you libraries and
drives?



Regards,

Nicholas
**
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.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**

Re: Drive problem in AIX. I'm lost...

[Richard Rhodes]

I don't have any real idea, but if it works as /dev/rmtX, and not after
renaming - I wonder if the binding is getting messed up on the rename.

Check the device attributes before the rename, and then after, and see if
the scsi_id, wwn, lun_id is the same.

lsattr -El rmt9
lsattr -El r123_4






 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:cc
 Dist Stor
 Manager"  Subject
  lost...


 07/01/2009 10:56
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






Hi Richard!
It's a virtual library from EMC in which I created two libraries, one
for the first TSM instance, the other one for the other instance. TSM1
uses the renamed devices (/dev/253 with drives /dev/253_0 to 29) and I
could create paths to the drives succesfully on that TSM instance. On
the other TSM instance, I can only use the devices as long as the name
starts with rmt. As soon as I rename them to 254_0 to 29 (our standard
naming convention) I receive an I/O error when I try to create the path.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: woensdag 1 juli 2009 16:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Drive problem in AIX. I'm lost...

I'm a little confused on what you are trying to do.  Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?

Also, are you using Atape multi pathing?







 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:
cc
 Dist Stor
 Manager"
Subject
 


 07/01/2009 10:00
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l  -a
new_name= to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines


**
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.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**



-
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
communicat

DB size and expiration

[Ochs, Duane]

Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing out 
of control after the addition of a number of remote imaging sites. After much 
review I was able to find failures in the expiration process. I tracked it down 
to a single client and after a call to IBM it was recommended to run a cleanup 
exptable.
Needless to say it was running a very long time. After completion, the next 
expiration also ran for a very long time deleting hundreds of millions of 
objects. This should have translated to about 1/3 the database size being freed 
up.

The problem is that I'm seeing max reduction at 4gb.
The stats I'm seeing indicated 74 million usable pages and 52 million used.

Other than a unloaddb and loaddb. Is there any other way to reclaim this DB 
space ?


Thanks,
Duane

Re: Drive problem in AIX. I'm lost...

[Loon, EJ van - SPLXM]

Hi Richard!
They are identical...
It must be a TSM issue then. I will try to create a path to the renamed drive 
tomorrow (which will fail) and then try to create a path to the same drive on 
the other TSM server on the same host. If that one does not fail, it must be 
related to that specific TSM server instance (running the same TSM version) so 
I will have to schedule a stop/start to see if that solves anything.
I'll keep you guys posted, thanks for now!
Kind regards,
Eric van Loon



Van: ADSM: Dist Stor Manager namens Richard Rhodes
Verzonden: wo 7/1/2009 17:38
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: Drive problem in AIX. I'm lost...



I don't have any real idea, but if it works as /dev/rmtX, and not after
renaming - I wonder if the binding is getting messed up on the rename.

Check the device attributes before the rename, and then after, and see if
the scsi_id, wwn, lun_id is the same.

lsattr -El rmt9
lsattr -El r123_4






 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:cc
 Dist Stor
 Manager"  Subject
  lost...


 07/01/2009 10:56
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






Hi Richard!
It's a virtual library from EMC in which I created two libraries, one
for the first TSM instance, the other one for the other instance. TSM1
uses the renamed devices (/dev/253 with drives /dev/253_0 to 29) and I
could create paths to the drives succesfully on that TSM instance. On
the other TSM instance, I can only use the devices as long as the name
starts with rmt. As soon as I rename them to 254_0 to 29 (our standard
naming convention) I receive an I/O error when I try to create the path.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: woensdag 1 juli 2009 16:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Drive problem in AIX. I'm lost...

I'm a little confused on what you are trying to do.  Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?

Also, are you using Atape multi pathing?







 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:
cc
 Dist Stor
 Manager"
Subject
 


 07/01/2009 10:00
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l  -a
new_name= to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines


**
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.
Koninklijke Luchtvaart Maatschappij

SV: Drive problem in AIX. I'm lost...

[Christian Svensson]

Hi Eric,
If I understand you correct. 
You can define a drive and the path. 
As soon you rename the drive the path is stop working?
And now you can't you update the path anymore or delete / define it again?

Have you compare the output from q drive f=d before and after rename? 
Same thing with q path drive server srct=server f=d
Do also look on Devconf.out in your AIX filesystem. Maybe it tells you the 
wrong path in their and have problem to update that file for you? (Security or 
maybe something else)

Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson

Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Loon, EJ van - 
SPLXM [eric-van.l...@klm.com]
Skickat: den 1 juli 2009 22:47
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: Drive problem in AIX. I'm lost...

Hi Richard!
They are identical...
It must be a TSM issue then. I will try to create a path to the renamed drive 
tomorrow (which will fail) and then try to create a path to the same drive on 
the other TSM server on the same host. If that one does not fail, it must be 
related to that specific TSM server instance (running the same TSM version) so 
I will have to schedule a stop/start to see if that solves anything.
I'll keep you guys posted, thanks for now!
Kind regards,
Eric van Loon



Van: ADSM: Dist Stor Manager namens Richard Rhodes
Verzonden: wo 7/1/2009 17:38
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: Drive problem in AIX. I'm lost...



I don't have any real idea, but if it works as /dev/rmtX, and not after
renaming - I wonder if the binding is getting messed up on the rename.

Check the device attributes before the rename, and then after, and see if
the scsi_id, wwn, lun_id is the same.

lsattr -El rmt9
lsattr -El r123_4






 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:cc
 Dist Stor
 Manager"  Subject
  lost...


 07/01/2009 10:56
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






Hi Richard!
It's a virtual library from EMC in which I created two libraries, one
for the first TSM instance, the other one for the other instance. TSM1
uses the renamed devices (/dev/253 with drives /dev/253_0 to 29) and I
could create paths to the drives succesfully on that TSM instance. On
the other TSM instance, I can only use the devices as long as the name
starts with rmt. As soon as I rename them to 254_0 to 29 (our standard
naming convention) I receive an I/O error when I try to create the path.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: woensdag 1 juli 2009 16:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Drive problem in AIX. I'm lost...

I'm a little confused on what you are trying to do.  Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?

Also, are you using Atape multi pathing?







 "Loon, EJ van -
 SPLXM"
 ADSM-L@VM.MARIST.EDU
 Sent by: "ADSM:
cc
 Dist Stor
 Manager"
Subject
 


 07/01/2009 10:00
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 






People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l  -a
new_name= to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines


***

Re: DB size and expiration

[Shawn Drew]

Provide a "q db f=d"  output.
Also, might want to do a "ESTimate DBREorgstats" for more information.

But yes, most likely an unloaddb, loaddb is your only option (other than
upgrading to 6.1, which is supposed to let you optimize while running)

Regards,
Shawn

Shawn Drew





Internet
duane.o...@qg.com

Sent by: ADSM-L@VM.MARIST.EDU
07/01/2009 03:31 PM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
[ADSM-L] DB size and expiration






Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing
out of control after the addition of a number of remote imaging sites.
After much review I was able to find failures in the expiration process. I
tracked it down to a single client and after a call to IBM it was
recommended to run a cleanup exptable.
Needless to say it was running a very long time. After completion, the
next expiration also ran for a very long time deleting hundreds of
millions of objects. This should have translated to about 1/3 the database
size being freed up.

The problem is that I'm seeing max reduction at 4gb.
The stats I'm seeing indicated 74 million usable pages and 52 million
used.

Other than a unloaddb and loaddb. Is there any other way to reclaim this
DB space ?


Thanks,
Duane



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

DRM database tape processing

[Nicholas Rodolfich]

Hello All,

Thanks for your help!!

When using DRM, tapes are moved from the mountable state to the vault state
using the s=dbs option ,they remain in the Vault state until they are empty
and the reuse delay on the storage pool has elapsed and DRM moves them into
the "vault retrieve" state. My question is, do database tapes use the same
strategy. Do they use any reuse delay or are they changed to the"vault
retrieve" sate at the end of the DRMDBBACKUPEXPIREDAYS parameter?  All
snapshot backups are fulls done M-F.

The reason I ask, I have a client who is finding 4 or so extra volumes
every other week in his vault and it is driving him bonkers. He claims to
be following exacting standards when it comes to managing his daily off
site tape rotations. I have  looked at his setup and short of doing his
rotations for him for two weeks, I cannot see a problem. Any ideas?

Regards,

Nicholas

Re: DB size and expiration

[Huebner,Andy,FORT WORTH,IT]

I am not sure shrinking the amount of disk space used by the DB will be worth 
the time.  TSM will use the pages in the DB, even if they are not at the end.  
You will still have to add new disks at the same point in the future.

Andy Huebner

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ochs, 
Duane
Sent: Wednesday, July 01, 2009 2:31 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] DB size and expiration

Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing out 
of control after the addition of a number of remote imaging sites. After much 
review I was able to find failures in the expiration process. I tracked it down 
to a single client and after a call to IBM it was recommended to run a cleanup 
exptable.
Needless to say it was running a very long time. After completion, the next 
expiration also ran for a very long time deleting hundreds of millions of 
objects. This should have translated to about 1/3 the database size being freed 
up.

The problem is that I'm seeing max reduction at 4gb.
The stats I'm seeing indicated 74 million usable pages and 52 million used.

Other than a unloaddb and loaddb. Is there any other way to reclaim this DB 
space ?


Thanks,
Duane


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

Re: Problem with Mac TSM client and new Java

[Jim Neal]

Hi Andy,

   Do you know if the 6.1.0.1 version works for XSERVE as well?  I tried the
fix of switching the java version preferences, but it seems to have no
effect.  Thanks!


Jim Neal
Sr. TSM Administrator
U.C. Berkeley
IS&T Storage and Backup Group


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Andrew Raibeck
Sent: Monday, June 29, 2009 5:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Problem with Mac TSM client and new Java

Yes, 6.1.0.1 does indeed contain the fix for IC61544.

A 5.5.2.x-based interim fix for IC61544 is targeted for some time this
week, though that is subject to change as it completes testing. I think the
number will be 5.5.2.3.

If you see something that says 5.5.3 is due out shortly, I'd be interested
in knowing where. 5.5.3 is currently targeted for 2Q2010 (go to the URL in
my sig and do a search on "5.5.3".

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus
Internet e-mail: stor...@us.ibm.com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager
.html


The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 2009-06-29
19:17:44:

> [image removed]
>
> Re: Problem with Mac TSM client and new Java
>
> Roger Deschner
>
> to:
>
> ADSM-L
>
> 2009-06-29 19:18
>
> Sent by:
>
> "ADSM: Dist Stor Manager" 
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Last Friday, June 26, IBM posted Mac client version 6.1.0.1 on its FTP
> download site. I looked in the attached documentation at
> ftp://ftp.software.ibm.com/storage/tivoli-storage-management/
> patches/client/v6r1/Mac/v610/6.1.0.1-TIV-TSMBAC-Mac-README_enu.htm
> and it does not say what is different between 6.1.0.0 and 6.1.0.1.
>
> I know the URL below says it will be fixed in 5.5.3 and 6.1.1, but does
> this 6.1.0.1 perhaps contain the patch for IC61544, our big Mac Java
> issue?
>
> Elsewhere it says that 5.5.3 will be out "by the end of the month". They
> have one more day.
>
> Roger Deschner  University of Illinois at Chicago rog...@uic.edu
>Academic Computing & Communications Center
>
>
> On Wed, 24 Jun 2009, Paul Zarnowski wrote:
>
> >This problem now has APAR IC61544 assigned to it.  You can view the APAR
at
> >http://www-01.ibm.com/support/docview.wss?uid=swg1IC61544.  I am told
that
> >the "fix is in test" but I have not heard of an ETA for its
availability.
> >
> >..Paul
> >
> >
> >--
> >Paul ZarnowskiPh: 607-255-4757
> >Manager, Storage Services Fx: 607-255-8521
> >719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
> >

Re: DB size and expiration

[Markus Engelhard]

Dear Duane,

we currently face the same problem, as we had to expand one of our
databases beyond the limit we had set and cannot shrink it now. Short of
taking the System offline for dump and load of the database, we are going
to restore the database to another TSM instance and do the dump and load on
this (rename the instance and all that beforehand), transparent for
production. Once this has been accomplished, the productive instance will
be renamed, and the reloaded system will be presented to the clients.
Happily this is our "archiving" server with limited data movement monday
till friday, so an export/import with merge  from date will catch up with
no loss on data. As a planned coincidence, the new TSM will be on brand new
hardware, but enough resources given this would also work out on the same
machine.
Not planning for 6.x this year...

Kind regards,
_
Markus Engelhard
IBM certified deployment professional - TSM 5.4
Homepage: www.bundesbank.de




--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
__

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
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.