Sponsored Content
Full Discussion: Trouble with backup
Operating Systems Solaris Trouble with backup Post 302959763 by dreiak on Thursday 5th of November 2015 08:42:09 PM
Old 11-05-2015
Trouble with backup

At work I am running a solaris 10 server with a ZFS filesystem. I am unfortunately not a solaris expert by any stretch of the imagination, and the relative difficulty in doing what I consider to be a super basic operation using solaris is driving me insane.

It is my job to figure out some way (or ideally make a script) that will make a complete bootable clone of an entire hard disk from one drive to another.

Drive one is c1t0d0 (bay 0), drive two is c1t1d0 (bay 1).

I must be able to remove the 2nd drive for off site storage, and I must be able to swap the drive in bay 0 with the off site drive and boot the server up completely from the backup.

I have been trying to figure this out for weeks. I tried using raidctr -c c1t0d0 c1t1d0, now I can't boot from either drive. (including when both are inserted). The server will just stick in a looped boot sequence.

I tried using dd commands as well, which appeared to work, but I couldn't boot off the drive. Part of the problem is that I am not a solaris guru, and I am definitely missing something to make this work. dd seemed like the best candidate, as the hard disks are identical. If someone knows that this will work, I need to know EXACTLY what to do, and not approximately.

I am avoiding using snapshots because it sounds so complicated, and though I have seen that it is possible to make a clone from snapshots, it does not sound like I will really get what I am looking for out of this solution, but I am open to anything.

TLDR: How do I get two HDDs to be independently bootable and have exactly the same information on them? Why isn't there some super easy command for this in Solaris?
 

9 More Discussions You Might Find Interesting

1. OS X (Apple)

OS X Server: Trouble restoring mail from backup...

So I had some bad RAM in my server. Of course I didn't know it at the time. And it kept making the 10.3.5 updater crash. And that last crash did it. My drive was messed up. So I had to reformat and reinstall. Luckily I had a whole slew of fresh backups. But I'm really hung up on the mail. I backed... (0 Replies)
Discussion started by: l008com
0 Replies

2. UNIX for Dummies Questions & Answers

The trouble about SU ...

Hi all, having read lots of posts about SU I don't quiet understand this : I'm doing regular backups of my database (u betta do) and therefore use su - username -c "sqlscript special data_base" in a unixscript which is even using cron. (yep!) Now I need some other script, still with this... (4 Replies)
Discussion started by: nulnul7
4 Replies

3. UNIX for Dummies Questions & Answers

X trouble

Hi there, I'm new to unix-environments. I'm richard, and i'm mostly a web-developer, under php. I've done work in unix env before, but never had my own. Today, I've got debian 3.1 r4 from the official site, and i've attempted to install it twice. I installed it initially as "Desktop... (0 Replies)
Discussion started by: izua
0 Replies

4. UNIX for Dummies Questions & Answers

Check backup file size on backup tape

Hi, I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies

5. SCO

Backup to SCSI Tape Backup aborts

I am trying to make a full backup of my system using the cpio command. The Tape Unit is a SCSI DDS. The process started fine but after about 30 minutes, it just stopped and showed the following message: 1755 Signal 31 - Core dumped Any idea of what is causing this and how to fix it? ... (4 Replies)
Discussion started by: zionpc
4 Replies

6. UNIX for Advanced & Expert Users

backup a file and keep every version of the backup

I am trying to backup my .bash_history and I want to keep every version of the backup. I am thinking to put one of these in my crontab. 0 0 * * 0,3 cat .bash_history > boo 0 0 * * 0,3 cp .bash_history boo I would like the backups to be called boo1, boo2, boo3, etc. I would like to keep... (7 Replies)
Discussion started by: cokedude
7 Replies

7. Programming

Trouble with C

Hey, i am having a problem First, i know java well and i have used C++ on occasion so i thought i would be able to deal with a class where they program in C. unfortunately i have hit some speed bumps that i am having problems. Here is my problem: I have a structure cache_t in the sample... (0 Replies)
Discussion started by: zephoid
0 Replies

8. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies

9. Shell Programming and Scripting

Help with Backup Shell Script for Network Device Configuration backup

HI all, im new to shell scripting. need your guidence for my script. i wrote one script and is attached here Im explaining the requirement of script. AIM: Shell script to run automatically as per scheduled and backup few network devices configurations. Script will contain a set of commands... (4 Replies)
Discussion started by: saichand1985
4 Replies
BOOT0CFG(8)						    BSD System Manager's Manual 					       BOOT0CFG(8)

NAME
boot0cfg -- boot manager installation/configuration utility SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted. Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi- cally, only non-removable disks are sliced. The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con- figured. On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to which control is passed by the PC BIOS) and data (an embedded table of defined slices). The options are: -B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table. -b boot0 Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS are active.) -d drive Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80 for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here. -e bell character Set the character to be printed in case of input error. -f file Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced if it does. -i volume-id Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block. -m mask Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled). Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig- nificant bit of the mask corresponds to slice 4. -o options A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary): packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O. This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'. setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is 'nosetdrv'. update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only. -s slice Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE. -t ticks Set the timeout value to ticks. (There are approximately 18.2 ticks per second.) -v Verbose: display information about the slices defined, etc. FILES
/boot/boot0 The default 'boot0' image /boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM) EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs. EXAMPLES
To boot slice 2 on the next boot: boot0cfg -s 2 ada0 To enable just slices 1 and 3 in the menu: boot0cfg -m 0x5 ada0 To go back to non-interactive booting, use fdisk(8) to install the default MBR: fdisk -B ada0 SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8) AUTHORS
Robert Nordier <rnordier@FreeBSD.org> BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support. Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ- ous content. Be careful. BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 10:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy