Sponsored Content
Full Discussion: Reel to reel tape!!!!
Top Forums UNIX for Dummies Questions & Answers Reel to reel tape!!!! Post 32675 by LivinFree on Tuesday 3rd of December 2002 06:20:06 PM
Old 12-03-2002
I thought so, but I wasn't sure.
I'm looking at some of our manuals here as to the tape format defaults.

I'm checking with some people here too, since they write tapes all the time. Also, a BLOCKSIZE of 60 seems a little odd - the default on LIBRARY/MAINTENANCE tapes are 2701.

And another thing would be the number and size of headers. You have Volume Headers, Header Labels, Tape Directories, all seperated by TAPEMARKS before the data ever starts.

And yet another problem could be the exact OS and version.
I don't recall if it was a OS/2200 or an MCP machine - it might not matter though.

Yet all of this could be irrelevant if they decided to use some other format than the usual.

I'll look into it some more.
 

9 More Discussions You Might Find Interesting

1. Solaris

copy tape to tape using dd

I have two tape drives attached to my system , and i am trying to copy one tape to another using both tape drives and using the following command : dd if=/dev/rmt/1 of=/dev/rmt/2 but unfortunitly i am getting the following error : read: Not enough space 0+0 records in 0+0 records... (2 Replies)
Discussion started by: itsgeorge
2 Replies

2. UNIX for Advanced & Expert Users

Space free on tape /delete a single file on tape

Hi, I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape. Thanks DOMENICO (3 Replies)
Discussion started by: Minguccio75
3 Replies

3. UNIX for Dummies Questions & Answers

Mounting DLT tape and to backup file to tape

Hi there: I'm new here Can anyone help me: I have DS15 Alpha server : Unix 5.1B Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit. What is the exact comman to mount the DLTape IV?? How do i make backuo @ copy file to the tape? Thanx to all (0 Replies)
Discussion started by: ayzeayem
0 Replies

4. AIX

How to copy a tape into another tape ?

I am new to AIX. I want to make a duplicate tape. How can I do that ? (1 Reply)
Discussion started by: Anonno
1 Replies

5. UNIX for Dummies Questions & Answers

Sony Reel to Reel TC 366 help

HI I am recording some live music on my Sony Reel to Reel TC 366 and keeping the needles below the red but when I play it back the needles are way over in the red producing distorted sound. There is no volume out button on this model, just RCA out to my amp. Could it be a internal electronics... (0 Replies)
Discussion started by: jamt
0 Replies

6. SCO

Tape Status shows 2 Hard errors and 5 Underruns on new tape

when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several: Status : ready beginning-of-tape soft errors : 0 hard errors: 2 underruns: 5 My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies

7. AIX

How to make a copy of a tape to another tape?

Hello, We need to make a copy of a backup tape, using the 2 tape recorders in IBM 3582 Tape Library We tried tu use "tcopy", it seems to work fine (no error messages) but we aren't sure if we can rely on it. my question is how to check if the copy succeded or not, but i also want to know... (3 Replies)
Discussion started by: fastlane3000
3 Replies

8. UNIX for Dummies Questions & Answers

Copying tape-to-tape on UNIX

I am using a 4mm tape to backup my Unix system. However, I wanted to make a copy all of the files and archive headers (or just the archive headers if that's possible) created on one of my tapes to another 4mm tape. I only have one tape drive. Is there a command that will complete such task? ... (1 Reply)
Discussion started by: acoco
1 Replies

9. AIX

Ejecting tape on AIX & Some Tape commands

I am trying to use this command to eject the tape mt -f /dev/rmt/0 unload but it gives me error mt -f /dev/rmt/0 unload mt: 0511-575 unload is not a recognized subcommand. Usage: mt Subcommand Valid subcommands are: weof eof fsf bsf ... (5 Replies)
Discussion started by: filosophizer
5 Replies
BACKUP_LABELTAPE(8)					       AFS Command Reference					       BACKUP_LABELTAPE(8)

NAME
backup_labeltape - Creates the magnetic label on a tape SYNOPSIS
backup labeltape [-name <AFS tape name, defaults to NULL>] [-size <tape size in Kbytes, defaults to size in tapeconfig>] [-portoffset <TC port offset>] [-pname <permanent tape name>] [-localauth] [-cell <cell name>] [-help] backup la [-n <AFS tape name, defaults to NULL>] [-s <tape size in Kbytes, defaults to size in tapeconfig>] [-po <TC port offset>] [-pn <permanent tape name>] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup labeltape command creates a magnetic label, readable by the Backup System, at the beginning of a tape. The label records the tape's name (either a permanent name, or an AFS tape name that reflects the tape's contents in a prescribed format) and its capacity. (If the "FILE YES" instruction appears in the /var/lib/openafs/backup/CFG_device_name file on the Tape Coordinator machine associated with the specified port offset, then the backup command writes label information to the first 16 KB block in the backup data file listed for that port offset in the Tape Coordinator's /var/lib/openafs/backup/tapeconfig file, rather than at the beginning of a tape. For the sake of clarity, the following text refers to tapes only, but the Backup System handles backup data files in much the same way.) Relabeling a tape that already contains AFS backup data effectively makes the data unusable, because the command removes the Backup Database record of the complete dump set of which the tape is a part. Use this command to enable recycling of a tape that contains unexpired dumps that are not actually still needed. To write a permanent name on the label, include the -pname argument to specify a string of up to 32 characters. The permanent name persists until the -pname argument is again included on the backup labeltape command, regardless of the tape's contents and of how often the tape is otherwise relabeled or recycled. Include this argument or the -name argument, but not both. If this argument is included, the AFS tape name is set to "<NULL>". The permanent name is set to "<NULL>" if this argument is omitted and no permanent name already exists. The issuer must ensure that a permanent name is unique among the tapes used for AFS backup in the cell, because the backup command interpreter does not verify that another tape does not already have the same permanent name. When a tape has a permanent name, the Backup System uses it instead of the AFS tape name in most prompts and when referring to the tape in output from backup commands. The permanent name appears in the "tape name" field of the output from the backup readlabel command. To write an AFS tape name on the label, provide a value for the -name argument in the required format described in OPTIONS. Include the -name argument or the -pname argument, but not both. If this argument is omitted, the AFS tape name is set to "<NULL>", but the Backup System automatically assigns the appropriate name when the tape is used in a future backup dump or backup savedb operation. The AFS tape name appears in the "AFS tape name" field of the output from the backup readlabel and backup scantape commands. The backup command interpreter does not accept the -name argument if the tape already has a permanent name. To erase a tape's permanent name, provide a null value to the -pname argument by issuing the following command: % backup labeltape -pname "" To record the tape's capacity on the label, specify a number of kilobytes as the -size argument. If the argument is omitted the first time a tape is labeled, the Backup System records the default tape capacity recorded for the specified port offset in the /var/lib/openafs/backup/tapeconfig file on the Tape Coordinator machine. Subsequently, the value in the size field persists until the -size argument is again included on the backup labeltape command. To determine how much data can be written to a tape during a backup dump or backup savedb operation, the Tape Coordinator reads the capacity recorded on the tape's label (or uses the value associated with its port offset in the /var/lib/openafs/backup/tapeconfig file, if the tape was never labeled). For further description, see the backup dump reference page. The Tape Coordinator's default response to this command is to access the tape by invoking the "MOUNT" instruction in the local /var/lib/openafs/backup/CFG_device_name file, or by prompting the backup operator to insert the tape if there is no "MOUNT" instruction. However, if the "AUTOQUERY NO" instruction appears in the CFG_device_name file, or if the issuer of the butc command included the -noautoquery flag, the Tape Coordinator instead expects the tape to be in the device already. If it is not, the Tape Coordinator invokes the "MOUNT" instruction or prompts the operator. OPTIONS
-name <AFS tape name> Specifies the AFS tape name to record on the label. Include this argument or the -pname argument, but not both. If this argument is omitted, the AFS tape name is set to "<NULL>". If this argument is provided, it must have the following format: <volume_set_name>.<dump_level_name>.<tape_index> for the tape to be acceptable for use in a future backup dump operation. The <volume_set_name> must match the volume set name of the initial dump to be written to the tape, <dump_level_name> must match the last element of the dump level pathname at which the volume set will be dumped, and <tape_index> indicates the order of the tape in the dump set (indexing begins with 1). To disable this type of name checking, include the "NAME_CHECK NO" instruction in the CFG_device_name file. For the tape to be acceptable for use in a future backup savedb operation, the value specified for the -name argument must have the following format: Ubik_db_dump.<tape_index> where <tape_index> indicates the order of the tape in the set of tapes that house the Backup Database dump; indexing begins with 1 (one). -size <tape size> Specifies the tape capacity to record on the label. Provide an integer value followed by a letter that indicates units, with no intervening space. A unit value of "k" or "K" indicates kilobytes, "m" or "M" indicates megabytes, and "g" or "G" indicates gigabytes. If the units letter is omitted, the default is kilobytes. If this argument is omitted the first time a tape is labeled, the Backup System records the capacity that is associated with the specified port offset in the /var/lib/openafs/backup/tapeconfig file on the Tape Coordinator machine. The value recorded the first time then persists until the -size argument is provided on a future issuance of the command. -portoffset <TC port offset> Specifies the port offset number of the Tape Coordinator handling the tape for this operation. -pname <permanent tape name> Specifies the permanent name to record on the label. It can be up to 32 characters in length, and include any alphanumeric characters. Avoid metacharacters that have a special meaning to the shell, to avoid having to mark them as literal in commands issued at the shell prompt. Include this argument or the -name argument, but not both. If this argument is provided, the AFS tape name is set to "<NULL>". If this argument is omitted, any existing permanent name is retained. -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. EXAMPLES
The following command records the AFS tape name "user.monthly.1" on the label of the tape in the device with port offset 3: % backup labeltape -name user.monthly.1 -portoffset 3 The following three commands are equivalent in effect: they all record a capacity of 2 GB on the label of the tape in the device with port offset 4. They set the AFS tape name to "<NULL>" and leave the permanent name unchanged. % backup labeltape -size 2g -portoffset 4 % backup labeltape -size 2048M -portoffset 4 % backup labeltape -size 2097152 -portoffset 4 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
butc(5), backup(8), backup_readlabel(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_LABELTAPE(8)
All times are GMT -4. The time now is 11:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy