Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Cloned Sun OS 10 HD using replicator machine Post 303034700 by ayyahma on Thursday 2nd of May 2019 10:57:47 PM
Old 05-02-2019
Cloned Sun OS 10 HD using replicator machine

Dear all,

I have Sun Oracle 10 SPARC T4-1 machine with 4 units SAS2 300GB configure with 2 set Raid1.
Is it possible to take out all 4 hd and cloned the 4 HD using disk clone/replicator machine with same HD size and model?

After the cloned completed put back the new cloned HD at original bay.

Did this cloned method will work?

Thanks
AYY
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sun Machine Rebooted

Hi , My Sun Machine Rebooted by itself 2 days back . Its running fine now , But i wanted to find out wat caused it to reboot... This is wat the var/adm/messages show . Kern.notice:- System booting after fatal error FATAL... Wat causes this message ... And wat tasks should i do to ensure it... (6 Replies)
Discussion started by: DPAI
6 Replies

2. Solaris

how to change IP of my SUN solaris machine

Hello, I want to change the IP of my SUN solaris machine but i am not bale to find the right way. I tried the following steps: 1) edit /etc/inet/hosts and change IP address for host listed in /etc/hostname.le0 2) ifconfig le0 down 3) ifconfig le0 inet NEW_IP_ADDR netmask + broadcast + ... (5 Replies)
Discussion started by: er_aparna
5 Replies

3. Solaris

Sun machine boot up

Hi I am trying to bring up our Sun V100 machine remotely using hyper terminal. We have connected LOM port A to COM1 of our windows server and have lom promt available. Now when we type poweron it starts booting and goes through the booting process and stops at the following step... .... ... (7 Replies)
Discussion started by: chimpu
7 Replies

4. Solaris

Installation os on sun machine

I had one sun ultra enterprise1 cpu. it's not giving any disply,which operating system it's support. How can install os on this CPU. (2 Replies)
Discussion started by: jagadeesh
2 Replies

5. Solaris

Sun Machine Crashed

During system startup the following warnings are appear. Warning: /pci@8, 700000/scsi@6, 1 (g1m1) Connected command timeout for target 9.0 Warning: /pci@8, 700000/scsi@6, 1 (g1m1) Target 9 reducing sync, transfer rate Warning: /pci@8, 700000/scsi@6, 1... (5 Replies)
Discussion started by: tabreaz
5 Replies

6. Solaris

How to configure IP in SUN Machine

Hi Experts, I am new for solaris, i am using Solaris10,can you anyone assist me how to configure IP in my machine. Thanks (4 Replies)
Discussion started by: daya.pandit
4 Replies

7. Solaris

Sun is not able to ssh another machine of sun

My one Sun machine is not able to ssh another machine of Sun. Although I have configured the ssh successfully ( SunOS sunbox2 5.9 Generic_118558-34 sun4u sparc SUNW,Sun-Blade-2500 ) ERROR bash-2.05# ssh sunbox2 /etc/ssh/ssh_config: line 34: Bad configuration option: PermitRootLogin... (0 Replies)
Discussion started by: z_haseeb
0 Replies

8. Solaris

Old Sun machine documentation needed

Hi all. Last year, after registering on Sun support site, I downloaded for free all available documentation (in PDF) and support files of a couple of old Sun workstations (Ultra 5 and Ultra 10). Now I need the documentation and support files of other old Sun workstations (SPARCstation 20 and... (4 Replies)
Discussion started by: wisechip
4 Replies

9. UNIX for Beginners Questions & Answers

Start /SYS on SUN SPARC does not start machine [SUN SPARC ENTERPRISE T-5240]

-> start /SYS Are you sure you want to start /SYS (y/n)? y Starting /SYS ]-> show HOST /HOST Targets: bootmode diag domain Properties: autorestart = reset autorunonerror = false bootfailrecovery = poweroff ... (29 Replies)
Discussion started by: z_haseeb
29 Replies
VOS_COPY(1)						       AFS Command Reference						       VOS_COPY(1)

NAME
vos_copy - Make a copy of a volume SYNOPSIS
vos copy [-id] <volume name or ID of source> [-fromserver] <machine name for source> [-frompartition] <partition name for source> [-toname] <volume name for new copy> [-toserver] <machine name for destination> [-topartition] <partition name for destination> [-offline] [-readonly] [-live] [-cell <cell name>] [-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve] [-help] vos cop [-i] <volume name or ID of source> [-froms] <machine name for source> [-fromp] <partition name for source> [-ton] <volume name for new copy> [-tos] <machine name for destination> [-top] <partition name for destination> [-o] [-r] [-li] [-c <cell name>] [-noa] [-lo] [-v] [-e] [-nor] [-h] DESCRIPTION
The vos copy command makes a copy of a volume with a new name. It is equivalent to vos dump followed by vos restore, but doesn't require the volume be stored locally by the client. CAUTIONS
Currently, the maximum size of a volume is 2 terabytes (2^31 bytes). OPTIONS
[-id] <volume name or ID> Specifies either the complete name or volume ID number of a read/write volume. [-fromserver] <machine name for source> Identifies the file server machine where the source volume resides. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1). [-frompartition] <partition name for source> Names the partition where the source volume resides. Provide the full partition name (for, example, /vicepa) or one of the abbreviated forms described in vos(1). [-toname] <volume name for new copy> The complete name of the new volume to create. [-toserver] <machine name for destination> Identifies the file server machine to which to copy the volume. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1). [-topartition] <partition name for destination> Names the partition to which to copy the volume. Provide the full partition name (for, example, /vicepa) or one of the abbreviated forms described in vos(1). -offline Leaves the new volume flagged as off-line in the volume database. -readonly Flags the new volume as read-only in the volume database. -live Copies the live volume without cloning. This is normally not necessary and causes the volume to be kept locked for longer than the normal copy mechanism. -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 vos(1). -noauth Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1). -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1). -verbose Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear. -encrypt Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. -noresolve Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
This command has no output unless "-verbose" is specified or there is an error. EXAMPLES
The following example makes a verbose copy of the "test" volume named "test2" in the cell "localcell". The volume and copy both reside on "/vicepa" of "server1". % vos copy test server1 a test2 server1 a -cell localcell -verbose Starting transaction on source volume 536870921 ... done Allocating new volume id for clone of volume 536870921 ... done Allocating new volume id for copy of volume 536870921 ... done Cloning source volume 536870921 ... done Ending the transaction on the source volume 536870921 ... done Starting transaction on the cloned volume 536870926 ... done Setting flags on cloned volume 536870926 ... done Getting status of cloned volume 536870926 ... done Creating the destination volume 536870927 ... done Setting volume flags on destination volume 536870927 ... done Dumping from clone 536870926 on source to volume 536870927 on destination ... done Ending transaction on cloned volume 536870926 ... done Starting transaction on source volume 536870921 ... done Doing the incremental dump from source to destination for volume 536870921 ... done Setting volume flags on destination volume 536870927 ... done Ending transaction on destination volume 536870927 ... done Ending transaction on source volume 536870921 ... done Starting transaction on the cloned volume 536870926 ... done Deleting the cloned volume 536870926 ... done Ending transaction on cloned volume 536870926 ... done Created the VLDB entry for the volume test2 536870927 Volume 536870921 copied from server1 /vicepa to test2 on server1 /vicepa PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument and on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root". SEE ALSO
vos(1), vos_clone(1), vos_move(1) COPYRIGHT
Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com> This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS. OpenAFS 2014-04-08 VOS_COPY(1)
All times are GMT -4. The time now is 03:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy