Sponsored Content
Full Discussion: /dev/rmt/0cn
Top Forums UNIX for Dummies Questions & Answers /dev/rmt/0cn Post 10129 by Perderabo on Thursday 8th of November 2001 09:26:30 AM
Old 11-08-2001
guest100, hmmm, I see you're right. That ability to specify a dump number doesn't exist on HP-UX and I never noticed it on Solaris. On both OS's I do restores the way I said, I fsf first to the proper file then do the restore.

Severd_Nerd, I don't understand at all what you are talking about. Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

/dev/rmt empty

hi all , i have just installed solris 9 on a sun 280R ,and i have appleid the recommended patches . after the installation i have found that /dev/rmt/ directory is empty , i thought that was normal , so i attached my DDS4 external tape drive and treid : devfsadm -C devfsadm -v reboot --... (1 Reply)
Discussion started by: ppass
1 Replies

2. UNIX for Dummies Questions & Answers

"/dev/rmt/0: No such device or address" when using mt command

/dev/rmt/0: No such device or address I get this when I do a "mt -f /dev/rmt/0 rewind" This is on a Solaris 7 system. I tried devfsadm -c tape and drvconfig ; tape and both didn't work. Help please....... :confused: (4 Replies)
Discussion started by: shorty
4 Replies

3. AIX

dev/rmt 0.1 block size is 0; variable; must be 1024 fixed.

Hi. After the shutdown for SWIFT Alliance Server, tape backup process will be done. Unfortunately, I encountered this error message when I performed the database tape backup. The error was "/dev/rmt 0.1 block size is 0; variable; must be 1024 fixed. Consider reconfiguration through 'chdev'... (2 Replies)
Discussion started by: MariaLuisa
2 Replies

4. Solaris

Empty /dev/rmt

Hi Guys, I a newbie in Unix environment. I need a help to detect my external SCSI tape drive. I tried with command drvconfig;devlinks;tapes.. but when I go to /dev/rmt/, the directory is still empty. I also tried with add_drv -v st but I'm getting this message # add_drv -v st exit... (8 Replies)
Discussion started by: akuslive
8 Replies

5. AIX

How to prevent /dev/rmt* re-assignments

Hi all, Sometimes, when I reboot my AIX server, my tape drive /dev/rmt# assignments change. This creates some tedious TSM work prior to and after a reboot of the server. Is there a way to ensure that the /dev/rmt# assignments come up the same every time? Thanks (5 Replies)
Discussion started by: jwholey
5 Replies

6. Solaris

/dev/rmt is empty - Trying to make Tape Drive Functional

I have an HP Proliant DL380 with Intel Processors that I recently loaded Solaris 10 with latest patches on it. I'm trying to do a ufsdump to an HP DAT 40 tape drive via SCSI, but I can't get it to do anything because /dev/rmt is empty. I've tried the following with luck: touch /reconfigure,... (7 Replies)
Discussion started by: cvaughn
7 Replies

7. Hardware

/dev/rmt/0mn: write protected or reserved

# mt stat HP DDS-4 DAT (Sun) tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 mt -f /dev/rmt/0mn erase /dev/rmt/0mn: write protected or reserved. Getting error while ufsdump .... --- Dumping / to /dev/rmt/0mn --- DUMP: Date... (1 Reply)
Discussion started by: vickyingle5
1 Replies

8. Solaris

/dev/rmt/0mn: write protected or reserved

# mt stat HP DDS-4 DAT (Sun) tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 mt -f /dev/rmt/0mn erase /dev/rmt/0mn: write protected or reserved. Getting error while ufsdump .... --- Dumping / to /dev/rmt/0mn --- DUMP: Date... (5 Replies)
Discussion started by: vickyingle5
5 Replies

9. AIX

/dev/rmt devices are missing

Hello, I attached a tape drive to one of my partitions but i cannot find the device. I run the command lsdev|grep rmt but i dont get anything in return. When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Discussion started by: omonoiatis9
6 Replies

10. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
RESTOREVOL(1)						       AFS Command Reference						     RESTOREVOL(1)

NAME
restorevol - Restore a volume from vos dump to the local file system SYNOPSIS
restorevol [-file <dump file>] [-dir <restore dir> ] [-extension <name extension>] [-mountpoint <mount point root>] [-umask <mode mask>] [-verbose] [-help] DESCRIPTION
restorevol takes an AFS volume in the format produced by vos dump and restores it to the local file system. Normally, the contents of a volume are maintained by the AFS File Server in an opaque format and copying a volume's raw data does not make it easily accessible. This utility will produce a directory tree that is equivalent to that seen via an AFS client, but without preserving the AFS-specific Access Control Lists (ACLs). It's primary use is to recover data from a volume dump or backup and make it available via a filesystem other than AFS. The dump output will read from standard input, or from a file if -file is specified. The restore process is as follows: 1. The dump file will be restored within the current directory or that specified with -dir. 2. Within this directory, a subdir is created. It's name is the RW volume name that was dumped. An extension can be appended to this directory name with -extension. 3. All mountpoints will appear as symbolic links to the volume name. The path name to the volume will be either that in -mountpoint, or -dir. Symbolic links remain untouched. 4. You can change your umask during the restore with -umask. Otherwise, restorevol uses your current umask. Mode bits for directories are 0777 (then AND'ed with the umask). Mode bits for files are the owner mode bits duplicated accross group and user (then AND'ed with the umask). 5. For restores of full dumps, if a directory says it has a file and the file is not found, then a symbolic link AFSFile-<#> will appear in that restored tree. Restores of incremental dumps remove all these files at the end (expensive because it is a tree search). 6. If a file or directory was found in the dump but found not to be connected to the hierarchical tree, then the file or directory will be connected at the root of the tree as __ORPHANEDIR__.<#> or __ORPHANFILE__.<#>. 7. ACLs are not restored. CAUTIONS
Normally, use vos_restore(1) instead of this command. restorevol is a tool of last resort to try to extract data from the data structures stored in a volume dumpfile and is not as regularly tested or used as the normal vos_restore(1) implementation. Using restorevol bypasses checks done by the fileserver(8) and salvager(8). OPTIONS
-file <dump file> Specifies the volume dump file to be read and restored to the local filesystem. If this option is not given, the volume dump will be read from standard input. -dir <restore dir> Names the directory in which to create the restored filesystem. The current directory is used by default. Note that any mountpoints inside the volume will point to the same directory unless the -mountpoint option is also specified. -extension <name extension> By default, the name of the directory created matches the RW volume name of the volume in the dump file. If this option is used, the directory name will be the RW volume name name extension as the suffix. -mountpoint <mount point root> By default, mountpoints inside the volume being restored point to the value given by -dir. This option allows mountpoints to be resolved relative to another path. A common use for this would be to specify a path under /afs as the mount point root so that mountpoints inside the restored volume would be resolved via AFS. The mount point root must exist, and the process running the command have read access to that directory, or the command will fail. EXAMPLES
The following command restores the contents of the dumpfile in sample.dump to the directory /tmp/sample.2009-05-17, but having all mountpoints inside the volume point to AFS (note that this requires knowledge of where sample is mounted in AFS): % restorevol -file sample.dump -dir /tmp -extension .2009-05-17 -mountpoint /afs/example.org/sample Restoring volume dump of 'sample' to directory '/tmp/sample.2009-05-17' PRIVILEGE REQUIRED
The issuer must have read access to the dump file and write access to the directory into which the dump is restored. If the -mountpoint flag is given, the issuer must also have read access to that directory. SEE ALSO
salvager(8), voldump(8), vos_dump(1), vos_restore(1) COPYRIGHT
Copyright 2009 Steven Jenkins <steven@endpoint.com> This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Steven Jenkins for OpenAFS. OpenAFS 2012-03-26 RESTOREVOL(1)
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy