learn linux and unix commands - unix shell scripting

StorageTek In-Drive Reclaim Accelerator for the StorageTek T10000B Tape Drive and StorageTek Virtual

 
Thread Tools Search this Thread
# 1  
Old 02-07-2011
StorageTek In-Drive Reclaim Accelerator for the StorageTek T10000B Tape Drive and StorageTek Virtual

Learn how Oracle is redefining tape storage wiith the StorageTek In-Drive Reclaim Accelerator for the StorageTek T10000B tape drive and StorageTek Virtual Storage Manager.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Storagetek problem?

Hi everyone, I have a big problem and i hope u can help me. I have brand new sun server X4-2 with Solaris 10-update 10. I have to install oracle StorageTek but there is no guide or help on the internet. Can anybody help me? CU (1 Reply)
Discussion started by: selocan
1 Replies

2. Hardware

StorageTek 2500

Hi, I recently got StoragaTek 2500 and I would like to connect it to my solaris machine, since I don't have much experience with storages, could someone point me how to do so, how can i present disks from storage on my solaris os? (everything is already connected) thanks in advance (1 Reply)
Discussion started by: sprehodec
1 Replies

3. Hardware

Storagetek 2540

Hi Guys and Gals, Wionder if you could help me, got a problem with a controller on a storagetek 2540, dead when fully powered up but if you reboot, it is ok for a couple of seconds (and you can ping it). Then once the array is fully up, it goes faulty and is un-pingable. Had anyone... (4 Replies)
Discussion started by: callmebob
4 Replies

4. Hardware

Storagetek 2540

Hello all ! I am a beginner about system and networking , and after some research on internet , i didn't find any relevant information , so i post here , if someone have an experience with this kind of material or if some documentation about how to connect my storage device on my server. I... (2 Replies)
Discussion started by: acorradi
2 Replies

5. Solaris

Storagetek 2540

Hi peeps, Was wondering if anyone can help me, got a couple of storagetek 2540's that I need to configure. Trouble is I think they were brought as second user as all that came with them was cables. Does anyone know how to configure them (i.e. create raid sets and map to Luns and present... (1 Reply)
Discussion started by: callmebob
1 Replies

6. AIX

SUN StorageTek tape drive with AIX 5.1

Hi, I have recently purchase a SUN Storage Tek desktop LTO 4 HH tape drive and connected to a IBM AIX 5.1 server. The server can detect the tape device. Can someone please advice urgently. Thanks (4 Replies)
Discussion started by: Caully
4 Replies

7. Solaris

One StorageTek 6140 vs Two (2) 2540 's?

We're moving our production 3510FC to development, so we need to replace the production 3510FC. The 6140 is nice, but pricey. Here's the question: Would two 2540's (RAID 10) be 'faster' than one 3510? (RAID 10) and faster than one 6140 (RAID 10)? One StoregeTek 6140 (16x72GB 15k rpm fc-al... (12 Replies)
Discussion started by: buddhavelvet
12 Replies
Login or Register to Ask a Question
mms(5)							Standards, Environments, and Macros						    mms(5)

NAME
mms - MMS service overview DESCRIPTION
MMS is a distributed removable media management system. It is based on the standard, IEEE 1244, Media Management System (MMS). The current implementation of MMS manages tapes and cartridges in a Sun StorageTek ACSLS tape library and emulated tapes on a file system. MMS is capable of sharing drives among multiple hosts. An important feature of MMS is that it provides a uniform and consistent tape inter- face to its client applications. MMS consists of a media manager (MM) which manages the entire MMS system. Information about the system is maintained by MM in a database. Every library managed by MMS has an active library manager (LM). An LM provides library access and mounting service to MMS. A drive managed by MMS has a drive manager (DM) on each host that has access to the drive. A DM provides device specific operations. A DM also provides label processing. The current implementation supports only ANSI labels. MMS client applications request MM to mount and unmount cartridges and process them after they are mounted. Applications use the Media Man- agement Protocol (MMP) to make requests. A library of client application functions is available. The Solaris implementation of the MMS uses the mmsinit(1M) command to configure and start the MMS service and the mmsadm(1M) command to list and set parameters required by the service. The MMS service instances, as reported by svcs(1), are: mms:wcr watcher mms:db Media Manager PostgreSQL database mms:mm Media Manager The MMS service RBAC (see rbac(5)) authorizations are: o solaris.smf.manage.mms o solaris.smf.value.mms The following are the MMS service configuration data accessible through the service management facility (see smf(5)): config/type Host is media manager or watcher only. Valid values are server or client. manager/host Host name where the media manager is running. manager/port Port the media manager is using. ssl/enabled Media Manager is using SSL. Valid values are true or false. Note the Media Manager needs an SSL RSA certificate and Diffie-Hellman parameters must be 'true'. ssl/verify Media Manager-only value, determines whether two-way authentication is enabled, which requires all Media Manager clients to have SSL RSA certificate. Valid values are are true for two-way authentication and false for one-way authentication. ssl/cert_file Name of file that contains the SSL RSA certificate, private key, and RSA certificate chain. ssl/pass_file Name of file for the private key password phrase if the RSA certificate is encrypted. ssl/dh_file Media Manager-only value, name of file that stores the Diffie-Hellman parameters. ssl/crl_file Name of optional CRL file. ssl/cipher Optional cipher change from EDH-RSA-DES-CBC3-SHA. ssl/peer_file Optional client only, name of file that stores the media manager certificate. The certificate is checked against the certificate returned by SSL_get_peer_certificate() function. The following are the MMS Database fault management resource identifier (FMRI) configuration data: postgresql/bin Directory where the PostgreSQL binaries are located. The directory is specific to the version of PostgreSQL qualified for use by the MMS software. postgresql/data Directory where the PostgreSQL database is located. The default location is a version-specific subdirectory of /var/mms/db. The following are the MMS Media Manager FMRI configuration data: db/host For future use. Set to localhost. db/port Port number to use for PostgreSQL login. The default value is 7656. db/user PostgreSQL user name. The default user name is postgres. db/name Name of PostgreSQL database to which to connect. The default value is mms. option/trace Optional. The Media Manager trace level before connecting to the PostgreSQL database. option/db_reconnect_max_retry Number of times to wait for the database to accept a Media Manager connection. option/db_reconnect_timeout Number of seconds to wait between reconnect tries. The following are the MMS Watcher FMRI configuration data: option/ssi_path Path to ACSLS SSI daemon. option/libapi_path Path to ACSLS API library. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), mmsadm(1M), mmsclient(1M), mmsexplorer(1M), mmsinit(1M), mmsclient_script(4), attributes(5), rbac(5), smf(5) SunOS 5.11 11 Nov 2008 mms(5)