Share Blade IBM Tape drive with Windows Server


 
Thread Tools Search this Thread
Operating Systems AIX Share Blade IBM Tape drive with Windows Server
# 1  
Old 03-03-2010
Share Blade IBM Tape drive with Windows Server

Hi ,
We have a Blade Chassis H housing 4 servers. It has a single tape drive. Can i share this tape drive with a HP Server Running Windows Server 2003? They are in the same LAN btw.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. AIX

How can we share a AIX drive on to Windows 2012 server?

Hi, How can we share a AIX drive on to Windows 2012 server. or vise versa. Note: Not using NFS/CIFS/samba. (*we are not able to use samba/NFS/CIFS for some reason) Requirement: How to have real time file sharing over the network between Windows and UNIX Do you guys have any ... (4 Replies)
Discussion started by: System Admin 77
4 Replies

2. Solaris

Share Tape drive between Solaris servers

Hi, I have two solaris servers running Oracle Applications. One is SPARC 5.9 and other one is SPARC 5.10 I want to share the tape drive attached to 5.10 with other machine so that i can enhance my backup strategy for backing up Oracle DB. I tried to share my tape drive by performing the... (2 Replies)
Discussion started by: Srinathkiru
2 Replies

3. Hardware

IBM 3583 Tape Drive License Feature Code

Team , currently I am doing some inventory on our hardware. I know that the old school IBM 3583 tape drive has some license feature enable but I dont know where can I check If the feature currently enable or not on our drive... Ive checked trough Web Base and Panel base but nowhere I... (0 Replies)
Discussion started by: thermometer
0 Replies

4. Solaris

Is it possible to setup a samba share to always mount to a specific Windows drive letter???

I'm trying to setup Samba in a solaris zone... Is there a way to setup Samba so that every Windows machine that tries to connect to the share always gets it mounted under the same drive letter (e.g. H:)??? My Samba share (in smb.conf) /home/pickup I want that all Window users get it mounted... (3 Replies)
Discussion started by: verdepollo
3 Replies

5. AIX

savevg/tar/mksysb of server-A on remote tape drive possible ?

Every 3 months we have to do backups (smitth mksysb/lsmksysb + tar) on at least 30 workstations. We have to carry around 2 external tape drives to connect to them. It is a pain to do because it takes at least 3 days to do (evening/night shift) and users sometimes complain that there desk is not put... (1 Reply)
Discussion started by: Browser_ice
1 Replies

6. SCO

Sco 5.0.7 on ibm server, no floppy drive.

I cannot install sco on this particular ibm server because sco cannot find the raid controller and thefore the logical drive. I have a floppy disk that I use in other machines when boot: shows on the screen. I usually type restart link=ad320 and it works but this time i have no floppy drive. ... (1 Reply)
Discussion started by: iNetForce
1 Replies

7. UNIX for Advanced & Expert Users

How to Mount a Unix share drive on Windows

We are trying to mount a Unix share drive on a Windows 2003 server to avoid transfering files accross the network using sftp. I can see shared drives on the Solaris server using the "share" command. How can I mount the drives on my Windows server so that I can read them directly. Do I need... (2 Replies)
Discussion started by: rbdenham
2 Replies
Login or Register to Ask a Question
BACKUP_STATUS(8)					       AFS Command Reference						  BACKUP_STATUS(8)

NAME
backup_status - Reports a Tape Coordinator's status SYNOPSIS
backup status [-portoffset <TC port offset>] [-localauth] [-cell <cell name>] [-help] backup st [-p <TC port offset>] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup status command displays which operation, if any, the indicated Tape Coordinator is currently executing. OPTIONS
-portoffset <TC port offset> Specifies the port offset number of the Tape Coordinator for which to report the status. -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8). -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8). -help Prints the online help for this command. All other valid options are ignored. OUTPUT
The following message indicates that the Tape Coordinator is not currently performing an operation: Tape coordinator is idle Otherwise, the output includes a message of the following format for each running or pending operation: Task <task_ID>: <operation>: <status> where <task_ID> Is a task identification number assigned by the Tape Coordinator. It begins with the Tape Coordinator's port offset number. <operation> Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command: Dump The backup dump command. Restore The backup diskrestore, backup volrestore, or backup volsetrestore commands. Labeltape The backup labeltape command. Scantape The backup scantape command. SaveDb The backup savedb command. RestoreDb The backup restoredb command. <status> Indicates the job's current status in one of the following messages. number Kbytes transferred, volume volume_name For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume currently being dumped. number Kbytes, restore.volume For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far. [abort requested] The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator. [abort sent] The operation is canceled by the backup kill command. Once the Backup System removes an operation from the queue or stops it from running, it no longer appears at all in the output from the command. [butc contact lost] The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out. [done] The Tape Coordinator has finished the operation. [drive wait] The operation is waiting for the specified tape drive to become free. [operator wait] The Tape Coordinator is waiting for the backup operator to insert a tape in the drive. If the Tape Coordinator is communicating with an XBSA server (a third-party backup utility that implements the Open Group's Backup Service API [XBSA]), the following message appears last in the output: <XBSA_program> Tape coordinator where <XBSA_program> is the name of the XBSA-compliant program. EXAMPLES
The following example shows that the Tape Coordinator with port offset 4 has so far dumped about 1.5 MB of data for the current dump operation, and is currently dumping the volume named "user.pat.backup": % backup status -portoffset 4 Task 4001: Dump: 1520 Kbytes transferred, volume user.pat.backup PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. SEE ALSO
backup(8), butc(8) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 BACKUP_STATUS(8)