Re: moving a 3494 library

2007-10-05 Thread Sandeep Jain
Hi

How to check the WWN of fiber devices on linux system.

Tape devices on linux are

/dev/st0
/dev/st1

   

 ( o )
 ---
I,I ' ' I,I
  ((

))



With Best Regards,

Sandeep Jain

 

 

** Legal Disclaimer
*

This email may contain confidential and privileged material for the sole
use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message in error,
please advise the sender by reply email and delete the message. Thank you. 


* 

 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Larry Clark
Sent: Monday, October 01, 2007 8:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] moving a 3494 library

There are two TSM servers, one at SiteA, the 2nd at SiteB

SiteA  manages two 3494 tape libraries, one at SiteA and the 2nd at SiteB
(connected via longwave fibre), and is the tape library manager for  both
TSM servers. The 3494 at SiteB is defined at shared.

All the volumes on the tape library at SiteB are now owned by the TSM server
at SiteB.

The goal is to remove the client instance and have ServerB locally manage
the library, and retain  its  current volumes.

The suggested procedure / sequence is:

1). Checkout the vols in the library at SiteB

2). Remove the 3494 defs for the 3494 at SiteB from the TSM server at SiteA

3). Remove and redefine the library on the TSM server at SiteB (non-shared)

4). Checkin the vols (private) in SiteB

5). Remove references in volhist on SiteA to volumes in 3494 in SiteB.

Anyone see a problem with this sequence?




DISCLAIMER “The information contained in this e-mail is
intended only for the person or entity to whom it is addressed
and may contain confidential or privileged information.
If you are not the intended recipient, any dissemination,
use, review, distribution, printing or copying of information
in this e-mail is strictly prohibited, and  you are requested
to contact the sender by reply e-mail and destroy all copies
of the original message.Thank you


This email has been scanned for any virus
infection at the sending end.

Re: moving a 3494 library

2007-10-02 Thread Larry Clark

? 3). Remove and redefine the library on the TSM server at SiteB (non-
shared)

- Original Message -
From: Robert Clark [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Monday, October 01, 2007 10:43 PM
Subject: Re: [ADSM-L] moving a 3494 library



You don't address making sure the 3494 will allow access by the TSM
server at site B.

[RC]

On Oct 1, 2007, at 7:30 AM, Larry Clark wrote:


There are two TSM servers, one at SiteA, the 2nd at SiteB

SiteA  manages two 3494 tape libraries, one at SiteA and the 2nd at
SiteB
(connected via longwave fibre), and is the tape library manager
for  both
TSM servers. The 3494 at SiteB is defined at shared.

All the volumes on the tape library at SiteB are now owned by the
TSM server
at SiteB.

The goal is to remove the client instance and have ServerB locally
manage
the library, and retain  its  current volumes.

The suggested procedure / sequence is:

1). Checkout the vols in the library at SiteB

2). Remove the 3494 defs for the 3494 at SiteB from the TSM server
at SiteA

3). Remove and redefine the library on the TSM server at SiteB (non-
shared)

4). Checkin the vols (private) in SiteB

5). Remove references in volhist on SiteA to volumes in 3494 in SiteB.

Anyone see a problem with this sequence?


moving a 3494 library (resend)

2007-10-01 Thread Larry Clark

didn't get a ack, so resending...

There are two TSM servers, one at SiteA, the 2nd at SiteB

SiteA  manages two 3494 tape libraries, one at SiteA and the 2nd at SiteB
(connected via longwave fibre), and is the tape library manager for  both
TSM servers. The 3494 at SiteB is defined at shared.

All the volumes on the tape library at SiteB are now owned by the TSM server
at SiteB.

The goal is to remove the client instance and have ServerB locally manage
the library, and retain  its  current volumes.

The suggested procedure / sequence is:

1). Checkout the vols in the library at SiteB

2). Remove the 3494 defs for the 3494 at SiteB from the TSM server at SiteA

3). Remove and redefine the library on the TSM server at SiteB (non-shared)

4). Checkin the vols (private) in SiteB

5). Remove references in volhist on SiteA to volumes in 3494 in SiteB.

Anyone see a problem with this sequence?


moving a 3494 library

2007-10-01 Thread Larry Clark

There are two TSM servers, one at SiteA, the 2nd at SiteB

SiteA  manages two 3494 tape libraries, one at SiteA and the 2nd at SiteB
(connected via longwave fibre), and is the tape library manager for  both
TSM servers. The 3494 at SiteB is defined at shared.

All the volumes on the tape library at SiteB are now owned by the TSM server
at SiteB.

The goal is to remove the client instance and have ServerB locally manage
the library, and retain  its  current volumes.

The suggested procedure / sequence is:

1). Checkout the vols in the library at SiteB

2). Remove the 3494 defs for the 3494 at SiteB from the TSM server at SiteA

3). Remove and redefine the library on the TSM server at SiteB (non-shared)

4). Checkin the vols (private) in SiteB

5). Remove references in volhist on SiteA to volumes in 3494 in SiteB.

Anyone see a problem with this sequence?


Re: moving a 3494 library

2007-10-01 Thread Robert Clark

You don't address making sure the 3494 will allow access by the TSM
server at site B.

[RC]

On Oct 1, 2007, at 7:30 AM, Larry Clark wrote:


There are two TSM servers, one at SiteA, the 2nd at SiteB

SiteA  manages two 3494 tape libraries, one at SiteA and the 2nd at
SiteB
(connected via longwave fibre), and is the tape library manager
for  both
TSM servers. The 3494 at SiteB is defined at shared.

All the volumes on the tape library at SiteB are now owned by the
TSM server
at SiteB.

The goal is to remove the client instance and have ServerB locally
manage
the library, and retain  its  current volumes.

The suggested procedure / sequence is:

1). Checkout the vols in the library at SiteB

2). Remove the 3494 defs for the 3494 at SiteB from the TSM server
at SiteA

3). Remove and redefine the library on the TSM server at SiteB (non-
shared)

4). Checkin the vols (private) in SiteB

5). Remove references in volhist on SiteA to volumes in 3494 in SiteB.

Anyone see a problem with this sequence?