Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Access to a remote tape drive
- Thread starter gato
- Start date
not sure what your real question is...........
The doc below is how to access a remote tape device?
A SNA server can have tcpip up and running...not sure what the actual question is...
In relation to the tape drive
Type | DDS|||| | DDS2 |
| Format | 2GB | 4GB |
|______________|____________ _|__________|
7206-001 (2GB) | R/W| R/W | No | No |
Drive and Media Interchange
MRS Media Recognition System - Special markings on the tape that are
recognized by the drive to determine that the tape has Data Grade
media.
DDS|||| Tape cartridge type for 90 meter tape with MRS. DDS-1 Format
DDS-1 Format of the tape with 2GB capacity on a 90 meter tape.
DDS-2 Format of the tape with 4GB capacity on a 120 meter tape
( not supported on a 7206-001 and the internal 2gb tape drive.
------------------------------
how to determine unknown tape attribute:
------------------------------------
tape drive attributes
Attributes for 4.0GB 4mm Tape Drives (Type 4mm4gb)
Block Size
The default value is 1024.
Device Buffers
The general information for this attribute applies to this tape drive type.
Density Setting #1 and Density Setting #2
The user cannot change the density setting of this drive; the device reconfigures itself
automatically depending on the Digital Data Storage (DDS) media type installed, as
follows:
Media Type Device Configuration
DDS Read-only.
DDS |||| Read/write in 2.0GB mode only.
DDS2 Read in either density; write in 4.0GB mode only.
non-DDS Not supported; cartridge will eject.
Data Compression
The general information for this attribute applies to this tape drive type.
Attributes with Fixed Values
If a tape drive is configured as a 4.0GB 4mm tape drive, the Retension, Reserve
Support, Variable Length Block Size, Density Setting #1, and Density Setting #2
attributes have predefined values that cannot be changed.
Not sure any of this helps...but maybe?
The doc below is how to access a remote tape device?
A SNA server can have tcpip up and running...not sure what the actual question is...
In relation to the tape drive
Type | DDS|||| | DDS2 |
| Format | 2GB | 4GB |
|______________|____________ _|__________|
7206-001 (2GB) | R/W| R/W | No | No |
Drive and Media Interchange
MRS Media Recognition System - Special markings on the tape that are
recognized by the drive to determine that the tape has Data Grade
media.
DDS|||| Tape cartridge type for 90 meter tape with MRS. DDS-1 Format
DDS-1 Format of the tape with 2GB capacity on a 90 meter tape.
DDS-2 Format of the tape with 4GB capacity on a 120 meter tape
( not supported on a 7206-001 and the internal 2gb tape drive.
------------------------------
how to determine unknown tape attribute:
------------------------------------
tape drive attributes
Attributes for 4.0GB 4mm Tape Drives (Type 4mm4gb)
Block Size
The default value is 1024.
Device Buffers
The general information for this attribute applies to this tape drive type.
Density Setting #1 and Density Setting #2
The user cannot change the density setting of this drive; the device reconfigures itself
automatically depending on the Digital Data Storage (DDS) media type installed, as
follows:
Media Type Device Configuration
DDS Read-only.
DDS |||| Read/write in 2.0GB mode only.
DDS2 Read in either density; write in 4.0GB mode only.
non-DDS Not supported; cartridge will eject.
Data Compression
The general information for this attribute applies to this tape drive type.
Attributes with Fixed Values
If a tape drive is configured as a 4.0GB 4mm tape drive, the Retension, Reserve
Support, Variable Length Block Size, Density Setting #1, and Density Setting #2
attributes have predefined values that cannot be changed.
Not sure any of this helps...but maybe?
Guest_imported
New member
- Jan 1, 1970
- 0
try this,
ON THE SERVER:
1. check portmap & NFS, using root ID
# lssrc -s portmap
# lssrc -g nfs
*** if not, try
# startsrc -s portmap
# startsrc -g nfs
2. FS must be mounted, say cdrom - mount it.
3. add FS to NFS exporting, using root ID;
# smity mknfsexp and fill-up appropriate "a must" field (the one with *).
4. verify if you done it right, by
# showmount -e (see if the FS is listed)
ON THE CLIENT:
1. check portmap & NFS, using root ID
# lssrc -s portmap
# lssrc -g nfs
*** if not, try
# startsrc -s portmap
# startsrc -g nfs
2. verify that server has the FS exported, by;
# showmount -e <server_name>
***<server_name> will be the hostname of the server.
3. create a directory that you are going to use to access the exported F; say
# mkdir /mnt
MOUNT THE FS ON THE CLIENT
1. type;
# smit mknfsmnt -> then enter
***and provide required field
hopefully, this should be able to access FS remotely.
ON THE SERVER:
1. check portmap & NFS, using root ID
# lssrc -s portmap
# lssrc -g nfs
*** if not, try
# startsrc -s portmap
# startsrc -g nfs
2. FS must be mounted, say cdrom - mount it.
3. add FS to NFS exporting, using root ID;
# smity mknfsexp and fill-up appropriate "a must" field (the one with *).
4. verify if you done it right, by
# showmount -e (see if the FS is listed)
ON THE CLIENT:
1. check portmap & NFS, using root ID
# lssrc -s portmap
# lssrc -g nfs
*** if not, try
# startsrc -s portmap
# startsrc -g nfs
2. verify that server has the FS exported, by;
# showmount -e <server_name>
***<server_name> will be the hostname of the server.
3. create a directory that you are going to use to access the exported F; say
# mkdir /mnt
MOUNT THE FS ON THE CLIENT
1. type;
# smit mknfsmnt -> then enter
***and provide required field
hopefully, this should be able to access FS remotely.
- Status