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)
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
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
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
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
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
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
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
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
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
LEARN ABOUT SUSE
mpartition
mpartition(1) General Commands Manual mpartition(1)
Name
mpartition - partition an MSDOS hard disk
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
Description
The mpartition command is used to create MS-DOS file systems as partitions. This is intended to be used on non-Linux systems, i.e. systems
where fdisk and easy access to SCSI devices are not available. This command only works on drives whose partition variable is set.
mpartition -p drive
mpartition -r drive
mpartition -I [-B bootSector] drive
mpartition -a drive
mpartition -d drive
mpartition -c [-s sectors] [-h heads]
[-t cylinders] [-v [-T type] [-b
begin] [-l length] [-f]
Mpartition supports the following operations:
p Prints a command line to recreate the partition for the drive. Nothing is printed if the partition for the drive is not defined, or
an inconsistency has been detected. If verbose (-v) is also set, prints the current partition table.
r Removes the partition described by drive.
I Initializes the partition table, and removes all partitions.
c Creates the partition described by drive.
a "Activates" the partition, i.e. makes it bootable. Only one partition can be bootable at a time.
d "Deactivates" the partition, i.e. makes it unbootable.
If no operation is given, the current settings are printed.
For partition creations, the following options are available:
s sectors
The number of sectors per track of the partition (which is also the number of sectors per track for the whole drive).
h heads
The number of heads of the partition (which is also the number of heads for the whole drive). By default, the geometry information
(number of sectors and heads) is figured out from neighboring partition table entries, or guessed from the size.
t cylinders
The number of cylinders of the partition (not the number of cylinders of the whole drive.
b begin
The starting offset of the partition, expressed in sectors. If begin is not given, mpartition lets the partition begin at the start
of the disk (partition number 1), or immediately after the end of the previous partition.
l length
The size (length) of the partition, expressed in sectors. If end is not given, mpartition figures out the size from the number of
sectors, heads and cylinders. If these are not given either, it gives the partition the biggest possible size, considering disk
size and start of the next partition.
The following option is available for all operation which modify the partition table:
f Usually, before writing back any changes to the partition, mpartition performs certain consistency checks, such as checking for
overlaps and proper alignment of the partitions. If any of these checks fails, the partition table is not changes. The -f allows
you to override these safeguards.
The following options are available for all operations:
v Together with -p prints the partition table as it is now (no change operation), or as it is after it is modified.
vv If the verbosity flag is given twice, mpartition will print out a hexdump of the partition table when reading it from and writing it
to the device.
The following option is available for partition table initialization:
B bootSector
Reads the template master boot record from file bootSector.
See Also
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at `http://www.gnu.org/software/mtools/manual/mtools.html'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-4.0.13 28Feb10 mpartition(1)