Hi everyone,
I want to clone a AIX 5.2 system from a machine to another one.
So i modified bosinst.data and image.data files (according to future platform) before making mksysb on old platform.
After booting on CD and restoring system using mksysb tape, the installation is launched but ever... (2 Replies)
Hello,
With AIX 5.3 is it possible to run a mksysb with users logged into the system?
The users are accessing a database app that runs on a separate physical disk than the system files. Does this even matter?
Thanks (1 Reply)
I use AIX 5.2 I want to allow a non-root user to do a system backup with 'mksysb' command.
I try to add 'ManageBackup' Role to that non-root user but it have an error "ksh: mksysb: 0403-006 Execute permission denied."
What should I do? (8 Replies)
I have several Solaris 8,9 and 10 servers.
I need to refresh them and avoid doing any OS upgrades. I may have to apply patches when I am done due to the new hardware.
My current servers have internal disk and my new target servers (same processor types) will have only SAN storage. Once the... (0 Replies)
Hi,
In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way :
- Make a full system backup excluding the user file system (this... (7 Replies)
I have installed Solaris 11 Express on my machine and now I am wondering what is the best way to backup (to another hard disc) and restore the system hard disc content.
The backup should to be done every night using a script launched by cron and all previously done backups should be available to... (8 Replies)
Hi all
I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it?
right now i don't have veritas file system setup. i have only ufs file sysytem
please help some production data is to be restore.
backup was taken... (0 Replies)
Hello there,
I would like to protect a Linux system from cloning, I don't mind if the cloned hard drive works in the same computer, but I need to avoid it to work in other one, even if it uses exactly same mainboard model and rest of computer parts. I want the cloned system to get frozen or... (4 Replies)
Hi all,
I am trying to use archiveadm to backup/clone an existing Solaris11.4 system.
However, i failed at media creation with the error -> "Media can only be created from archives containing root-only data"
root@xxx:/mnt/opt/software# zpool list
NAME SIZE ALLOC FREE CAP DEDUP ... (6 Replies)
Discussion started by: javanoob
6 Replies
LEARN ABOUT NETBSD
mtio
MTIO(4) BSD Kernel Interfaces Manual MTIO(4)NAME
mtio -- generic magnetic tape I/O interface
SYNOPSIS
#include <sys/ioctl.h>
#include <sys/types.h>
#include <sys/mtio.h>
DESCRIPTION
Magnetic tape has been the computer system backup and data transfer medium of choice for decades, because it has historically been cheaper in
cost per bit stored, and the formats have been designed for portability and storage. However, tape drives have generally been the slowest
mass storage devices attached to any computer system.
Magnetic tape comes in a wide variety of formats, from classic 9-track, through various Quarter Inch Cartridge (QIC) variants, to more modern
systems using 8mm video tape, and Digital Audio Tape (DAT). There have also been a variety of proprietary tape systems, including DECtape,
and IBM 3480.
UNIX TAPE I/O
Regardless of the specific characteristics of the particular tape transport mechanism (tape drive), UNIX tape I/O has two interfaces: "block"
and "raw". I/O through the block interface of a tape device is similar to I/O through the block special device for a disk driver: the indi-
vidual read(2) and write(2) calls can be done in any amount of bytes, but all data is buffered through the system buffer cache, and I/O to
the device is done in 1024 byte sized blocks. This limitation is sufficiently restrictive that the block interface to tape devices is rarely
used.
The "raw" interface differs in that all I/O can be done in arbitrary sized blocks, within the limitations for the specific device and device
driver, and all I/O is synchronous. This is the most flexible interface, but since there is very little that is handled automatically by the
kernel, user programs must implement specific magnetic tape handling routines, which puts the onus of correctness on the application program-
mer.
DEVICE NAME CONVENTIONS
Each magnetic tape subsystem has a couple of special devices associated with it.
The block device is usually named for the driver, e.g. /dev/st0 for unit zero of a st(4) SCSI tape drive.
The raw device name is the block device name with an "r" prepended, e.g. /dev/rst0.
By default, the tape driver will rewind the tape drive when the device is closed. To make it possible for multiple program invocations to
sequentially write multiple files on the same tape, a "no rewind on close" device is provided, denoted by the letter "n" prepended to the
name of the device, e.g. /dev/nst0, /dev/nrst0.
The mt(1) command can be used to explicitly rewind, or otherwise position a tape at a particular point with the no-rewind device.
FILE MARK HANDLING
Two end-of-file (EOF) markers mark the end of a tape (EOT), and one end-of-file marker marks the end of a tape file.
By default, the tape driver will write two End Of File (EOF) marks and rewind the tape when the device is closed after the last write.
If the tape is not to be rewound it is positioned with the head in between the two tape marks, where the next write will over write the sec-
ond end-of-file marker.
All of the magnetic tape devices may be manipulated with the mt(1) command.
A number of ioctl(2) operations are available on raw magnetic tape. Please see <sys/mtio.h> for their definitions.
The manual pages for specific tape device drivers should list their particular capabilities and limitations.
SEE ALSO dd(1), mt(1), pax(1), tar(1), st(4), wt(4)HISTORY
The mtio manual appeared in 4.2BSD.
BUGS
The status should be returned in a device independent format.
If and when NetBSD is updated to deal with non-512 byte per sector disk media through the system buffer cache, perhaps a more sane tape
interface can be implemented.
BSD January 14, 1999 BSD