Sponsored Content
Full Discussion: Backup root disks
Operating Systems Solaris Backup root disks Post 302831485 by hicksd8 on Thursday 11th of July 2013 05:02:56 AM
Old 07-11-2013
If you have no backup devices directly attached the next best is probably to backup to another Solaris box over NFS. So do you have another Solaris box?

Alternatively, you could backup to a USB device.

What is the root filesystem? UFS or ZFS?

For completeness, what version of Solaris?
 

10 More Discussions You Might Find Interesting

1. Solaris

Backup for HW Mirrored Disks

We use SW mirroring (RAID1) using SVM for our SUN servers (which we OEM to end clients with our application on). When I need to make a tape backup for the server (disk), I disable mirroring and perform backup of the entire disk to tape using ufsdump. This process requires an outage and sensitive as... (8 Replies)
Discussion started by: StarSol
8 Replies

2. Solaris

Non-Root mode ... luxadm to show path(s) for Disks

Hi Gurus out there... I am pondering over a situation where I have non-root access (user account), where I am trying to determine paths (including multipaths) on a host. "luxadm display" seems very appropriate, but requires root access. Is there anyway I can get the FC path information? ... (1 Reply)
Discussion started by: verisund
1 Replies

3. Solaris

root backup

Hi I am using EBS 7.2 for backup. We have to shift server, before that i want to take root backup for all server. i don't know how to take entire root please help me (1 Reply)
Discussion started by: sijocg
1 Replies

4. Solaris

Disk mismatch while trying to zfs mirroring non-root disks

Hello All, I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me. --- iostat command shows the disk to be similiar --- format command shows disk to be different :confused: --- c1t2d0 is the active... (8 Replies)
Discussion started by: pingmeback
8 Replies

5. UNIX for Advanced & Expert Users

/root restore backup exec

Hi we use backup exec to backup our linux servers... question is what if the linux server is corrupted (/root) and doesnt boot up .. how would the backup exec restore /root if the server cant even start? woukld we have to restore to another server then boot into rescue mode and copy across... (0 Replies)
Discussion started by: halacil
0 Replies

6. Solaris

Mirorr Solaris 10 5/09 root disks at install time

I'm going to install a fresh Solaris 10 5/09 install on a UFS on a server with 2 disks attached to a SCSI controller and i want to mirror those disks at install time is there any to do this , As far as i know Jump start and live upgrade are the sole way to do this , is there anyways except... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies

7. Solaris

Get # of disks as non-root

I'm trying to figure if there are commands I can run as non-root/non-privileged users to figure out the number of disks. I know I can use format but it needs root. Any idea? (10 Replies)
Discussion started by: PPPP
10 Replies

8. AIX

rsync backup root files

Hi, I am trying to use rsync utility through ssh to synchronize some root files of 2 servers. I have a rsyncusr user in each server. I configured ssh with no password. I set NOPASSWD in the /etc/sudoers file: rsyncusr ALL= NOPASSWD:/usr/bin/rsync In order to make rsync able to sudo and be... (2 Replies)
Discussion started by: samalogo
2 Replies

9. Solaris

Root Backup

Hello, In what cases we take backup of Root file system. Can someone explain please. Thanks & Regards, Bar (7 Replies)
Discussion started by: bhargav90
7 Replies

10. Solaris

Backing up root disks

Hi ! I wonder if in solaris 10 there is a utility similar to ignite in HP-UX that backup entire file systems (/, /usr, /var, /tmp, /home). I have to backup only the root disk of a server, but ufsdump seem to be backing up individual file systems....only, am I correct? (1 Reply)
Discussion started by: fretagi
1 Replies
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)
All times are GMT -4. The time now is 03:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy