Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Need help with MOD Disk copying Post 302413927 by drew_holm on Sunday 18th of April 2010 11:36:00 AM
Old 04-18-2010
Need help with MOD Disk copying

Hello,

we are running Irix 6.5 on our octane/sgi computers - these computers come with an external Sony MOD drive attached via a scsi cable. We have backed info to 2.3 gig MOD disks over the years and woule like to duplicate the MOD's. I believe there are 3 ways to do this:
  1. add a second drive to the SGI possibly using the instructions at Installation Guide SGI. System Administration. Adding a magneto-optical drive to the computer and make copies/clones of our current MOD disks. (I believe once we physically attach another MOD drive we will have to 'load' the drive(s) and enter some commands that copy the first MODs' disk and then transfer to the second MODs' disk. We would also want to verify the files made it to the new MOD disk a list of the files with details).
  2. I also understand there are MOD disks duplicators that will do the job (minus the verification step?)
  3. Copy all of the MOD's data to our harddrive, eject the original MOD, put in a new MOD and make a new copy to the MOD drive and verify.
We could use any/all help with the above and have limited IRIX skills -

Thanks in advance

Steve
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

copying oracle tables from raw disk

I have been tasked with archiving Oracle tables. The data is on raw devices, and possibly will span multiple logical volumes. Has anyone ever had to do this? How did you accomplish it? Any references to accomplish this would be greatly appreciated. Thanks, (2 Replies)
Discussion started by: isenhart
2 Replies

2. UNIX for Dummies Questions & Answers

Copying files unto a usb pendrive/external disk from Solaris 9

Hi all, Can anybody help me with how I can connect a usb pendrive or external disk to a Sun Server which runs on Solaris 9? I am able to connect the usb drive to a windows server easily and copy files but am wondering if it is possible to do that with Solaris. Any help will be appreciated. thanks. (3 Replies)
Discussion started by: rahmantanko
3 Replies

3. UNIX for Advanced & Expert Users

Listing/copying files from magnetic optical disk

I am trying to list the name of files on an MOD - I use the command tar vtf /MOD_DRIVE|more and I get a nice list of filenames/directories on this particular MOD. When I put in another MOD that contains software options I get the error "directory checksum error". I would like to be able to... (2 Replies)
Discussion started by: drew_holm
2 Replies

4. Solaris

Solaris 6.5 MOD disk copy help needed

Hello, we are running Irix 6.5 on our octane/sgi computers - these computers come with an external Sony MOD drive attached via a scsi cable. We have backed info to 2.3 gig MOD disks over the years and woule like to duplicate the MOD's. I believe there are 3 ways to do this: add a second... (1 Reply)
Discussion started by: drew_holm
1 Replies

5. Solaris

Copying disk - dd or lucreate?

Got server that I want to have an 'image' of disk to keep in case of failure. What I want to be able to do is, in the event of disk failure, remove system disk replace with cloned disk (same slot) and reboot. Trouble is I cant take this server down to single user. Is dd still a viable... (6 Replies)
Discussion started by: psychocandy
6 Replies
vxdiskadd(1M)															     vxdiskadd(1M)

NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager SYNOPSIS
vxdiskadd disk_address_pattern_list DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or allows the user to ask to make the decision for each disk individually. One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more examples: all: all disks c3 c4t2: all disks on controller 3 and controller 4, target 2 c3t4d2: a single disk (in the c#t#d# naming scheme) xyz_0 : a single disk (in the enclosure based naming scheme) xyz_ : all disks on the enclosure whose name is xyz The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec- ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0. All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate. Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message. OPERATIONS
Reconnecting a drive that was temporarily inaccessible This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the vxrecover utility. Initialization of a disk with reserved regions Initialization of the disk is performed by calling vxdisksetup. Adding a disk to an existing disk group This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free space. Creation of new disk groups in which to import a new disk If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is offered. Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the force option. The force option ignores any such storage-specific guidelines. FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations. /etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations. /etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations. NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted as CDS disks. SEE ALSO
vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)
All times are GMT -4. The time now is 01:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy