10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
I just want to throw something out there for opinions and viewpoints relating to a Disaster Recovery site.
Besides the live production environment, do you think a DR environment should include:
- pre-production environment
- QA Environment
......or would this be considered to be OTT... (3 Replies)
Discussion started by: Duffs22
3 Replies
2. UNIX for Dummies Questions & Answers
We have a SCO OpenServer Unix server that has been damaged. Fortunately we have a good backup of the entire system (using BackupEdge.) On a new server, if we install SCO from original SCO CD's (we have all necessary activation codes) then drop the tape (we can restore with tar), will the... (3 Replies)
Discussion started by: jmhohne
3 Replies
3. AIX
Hi Guys,
is it possible to failover a hacmp cluster in one datacentre via SRDF to a single node in another datacentre, or do I need a cluster there in any case? This is only meant as worst case scenario and my company doesn't want to spend more money than absolutely necessary.
I know the... (3 Replies)
Discussion started by: zxmaus
3 Replies
4. Solaris
Hello everyone I am Kevin and new to this forum.
I have encounter an issue I can't seem to resolve. I am currently using Solaris 8 02/04 on Sun V240 servers. I know how to create a flar image of the server and restore it using NFS (network server) or Local Tape (tape drive). What I need to do... (2 Replies)
Discussion started by: Kevin1166
2 Replies
5. AIX
Are there any products out there that provide a disk imaging solution for AIX (and HPUX and Solaris for that matter)? In a development environment where users are looking to restore an OS quickly back to a certain point in time, what is there available for this besides opening up the system,... (7 Replies)
Discussion started by: tb0ne
7 Replies
6. Solaris
Recovering Solaris to an alternate server
I was just wondering if anyone could give me some points on restoring a Solaris 9 backup to an alternate server. Basically, we use netbackup 6 and I was wondering what the best procedures are for doing this? What things do we need to take into... (3 Replies)
Discussion started by: aaron2k
3 Replies
7. UNIX for Dummies Questions & Answers
I am looking into disaster recovery and I wanted to know what files and/or other information do I need to keep copies of to sucessfully restore my system from the ground up..... Any help is greatly appreciated. I am running Solaris 8 on an Ultra 60. (5 Replies)
Discussion started by: rod23
5 Replies
8. UNIX for Advanced & Expert Users
Can anyone tell me of what to expect? I've been nominated to join a team of unix admins to do a DR testing. we already have the guys who are gono be doing the restores. besides the restore, anybody know what else to look forward to?? (2 Replies)
Discussion started by: TRUEST
2 Replies
9. Cybersecurity
Hello,
I am trying to make a disaster recovery of my Unix System.
Is there a site where I can find template from Disaster Recovery Domain. So this can help me to have the principals chapter to make a good report.
Thanks a lot ........ (5 Replies)
Discussion started by: steiner
5 Replies
10. Cybersecurity
please tell me if this thinkin is correct, if not, please corret me:
disaster recovery means when something bad happens and you need to retrieved a backed up file, all you have to do is cd into the tape drive and then look for the file you want and extract it from the drive.
is this... (3 Replies)
Discussion started by: TRUEST
3 Replies
vxiod(1M) vxiod(1M)
NAME
vxiod - start, stop, and report on Veritas Volume Manager I/O threads
SYNOPSIS
vxiod
vxiod [-f ] [set count]
DESCRIPTION
The vxiod utility starts, stops, or reports on Veritas Volume Manager (VxVM) I/O kernel threads. An I/O thread provides a process context
for performing I/O in VxVM.
When the vxio module is loaded, 16 I/O threads are created, plus 2 threads per additional CPU for a system with more than 8 CPUs, up to a
maximum of 64 threads. At least one I/O thread must be running while the vxio module is loaded, and the number of I/O threads cannot be
forced to zero.
When invoked with no arguments, vxiod prints the current number of I/O threads to the standard output.
The number of threads that is required for handling I/O requests depends on the system load and usage. If volume recovery seems to proceed
more slowly at times, it may be possible to improve its performance by increasing the number of I/O threads up to a maximum of 64.
KEYWORDS
set When invoked with the set keyword, vxiod creates the number of I/O threads specified by count. If more volume I/O threads exist
than are specified by count, the excess processes terminate. If more than the maximum number(64) are specified, the requested
number is silently truncated to that maximum.
OPTIONS
-f This option has no effect from release 5.0 onward. The number of I/O threads cannot be reduced to zero.
EXIT CODES
The vxiod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O request occurs within a I/O
thread, the state of that I/O request is not reflected in the exit status for vxiod. Otherwise, vxiod returns a non-zero exit status on
error.
Usage errors result in an exit status of 1 and a usage message. If the requested number of threads cannot be created, the exit status is
2, and the number of threads that were successfully started is reported. If any other error occurs, the exit status is 3.
FILES
/dev/vx/iod The device used to report on and start volume I/O threads.
NOTES
Veritas Volume Manager I/O threads cannot be killed directly through the use of signals.
Depending on the operating system, VxVM I/O threads may not appear in the list of processes that is output by the ps command. The number
of I/O threads that is currently running can be determined by running vxiod.
SEE ALSO
fork(2), ps(1), vxconfigd(1M), vxdctl(1M), vxintro(1M), vxio(7), vxiod(7)
VxVM 5.0.31.1 24 Mar 2008 vxiod(1M)