04-17-2008
why need to mirror disk if we had backups ?
hi.. newbie here, just wonder why there is a need for mirroring in some servers whereby we already had backups by cron jobs ?
10 More Discussions You Might Find Interesting
1. HP-UX
Being somewhat extremely new to Unix, I have just had a system crash
One of my Volume Groups has crashed
However, this Volume Group is actually mirrored
How do I switch to use the mirrored copy?
Any assistance greatly appreciated
Thanks (1 Reply)
Discussion started by: cobdeng
1 Replies
2. Solaris
Hi,
need some help.
I’m new to solaris and trying to find out how to mirror a data disk (not the root disk).
In AIX it is easy but with solaris 5.8 I don’t find my way even with the SUN docs (disk/suide is installed).
What is behind is I want to migrate a disk from 1 storage system to... (7 Replies)
Discussion started by: ccTester
7 Replies
3. Solaris
Is it possible to create a Mirror with zfs ??
I'm experimented user with Solstice Disk suite.
Or Sun Volume manager or veritas volume manager.
But, i would like switch from Disksuite to Zfs.
All my mirrored disks. (1 Reply)
Discussion started by: simquest
1 Replies
4. Solaris
Hi,
I want to know if one disk is failed in mirror in solaris and system is booted from another disk, is it possible to find out from which disk system is booted at command level? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
5. Filesystems, Disks and Memory
I have a SUN 440 running Solaris 8 that is generating funny errors on /dev/dsk/c1t0d0 and I would like to dupe the drive(the non offending drives are removed for this process), swap it with the dupe and reboot. From what I have read, the process seems simple:
dd if=/dev/dsk/c1t0d0... (1 Reply)
Discussion started by: hardyj
1 Replies
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. Solaris
Long time Linux, relatively new to Solaris.
Currently I have a Solaris 9 machine which has a mirrored root disk. We will be running some tests on this machine, and when those tests are done we want to restore it to "pre-test" status.
What I would like to do is break the mirror, pull the first... (2 Replies)
Discussion started by: brianr
2 Replies
8. AIX
Hi Admins,
I am new into aix.I was surfing aix pages and reading how to replace failed mirror disks.I read in one of the posts that we have to reboot the server to replace the disk. actually i was a HPUX admin and many times replaced root mirror disk online.Ofcourse it was hot swappable.
... (2 Replies)
Discussion started by: newaix
2 Replies
9. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
10. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
LEARN ABOUT X11R4
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)