I'm going to attempt a ufsrestore of a Solaris 9 machine from a connected NAS containing the ufsdumps. The idea is to be able to take ufsdumps of a failed machine (machine 1), and use them to set up a backup machine (machine 2). (I'm testing for disaster recovery)
Note that my backup machine (2) has already been imaged by doing a (RAID1) drive replacement on machine 1, then moving that drive to machine 2, then creating the RAID1 mirror drive on machine 2. In other words, the second machine is already a duplicate of the first, just a couple of months out of date.
Is this this what I will use or is there something simpler?:
Last edited by rbatte1; 12-05-2017 at 09:14 AM..
Reason: Changed some CODE tags to be ICODE tags to make for easier reading
Hi there,
I have a problem at the moment trying to restore a directory from a Super DLT tape with about 3 weeks worth of backups on it. I need to be able to get the last backup performed on this tape but using ufsrestore -i it only restores the first backup which is no good to me. There is... (4 Replies)
on sparc solaris 2.8 hosts, HOSTB, after changing to /dir1 need to:
connect to tape drive on HostA. change directory to /dir0/dir1 on tape and
restore everything under that path to /dir1 directory.
could i get help?. (1 Reply)
I'm trying to restore a server from a backup tape. I've partitioned my drive, and I've run into a problem; After extracting everything from the tape, It seems as if only the directory structure is intact. Here are my steps:
1. booted from cdrom to single user mode boot cdrom -s
2. used... (3 Replies)
HI Gurus,
I have a sunfire V445 server running SAP ECC 6.0 with an Oracle database on Solaris 9 (SunOS 5.9). I recently completed a ufsdump to tape of the following files:-
/,
/usr,
/oracle,
/export,
/sapr3,
I want to restore these files from tape onto a different server of the same... (5 Replies)
Hi , I accidentally deleted crontab entries and I need to restore back urgently ! we use a ufsdump with 0cfu option. I like to know how to restrore / retrieve to different location for crontab file only from the backup. Thanks. (4 Replies)
hey all,
i did a ufsdump/restore from a mirrored system and i'm not able to get the new system to boot off of the dump.
system 1 is a v245 mirrored with disk suite. metadb's are in place
d3 -m d23 d13 d33 1
d23 1 1 c1t1d0s3
d13 1 1 c1t0d0s3
d33 1 1 c1t2d0s3
d0 -m d20 d10 d30 1
d20 1... (3 Replies)
hi, on my sol9 box i create my backup using the below command:
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u1
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u2
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u3
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u4
now on the new sol10 box, to restore i use this commands:
cd /u1... (3 Replies)
Hi Friends
we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there?
Regards
Rajasekar (5 Replies)
Good Morning,
I'm running through a Solaris 9 ufsrestore process on a Sunblade 2500 that folks here helped me write a year ago. Here: https://www.unix.com/303011447-post11.html
Hicksd8 tells me to # rm restoresymtable. I see this file in the other slices as well. Do I remove it from... (8 Replies)
Discussion started by: Stellaman1977
8 Replies
LEARN ABOUT POSIX
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)systemd 237SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)