10-03-2019
With the costs of disks so cheap these days, you are better to clone the disks and put them in a development / test server instead of removing the critical disks and testing them, with a plan to rush them back to the original server if something goes wrong.
This is especially true if you are talking about a critical production asset.
If you are talking about a "mom and pop" server which does not serve a critical business need, then you can certainly consider some "quick, disk shuffle" method, but not for a business-critical production server.
Just fully recreate the current computer with clones of the application and data disks in a your new OS build / server; and then cut over too it when all is tested and ready to go live (syncing data as necessary).
This User Gave Thanks to Neo For This Post:
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I am trying to write a bash script function to present the user a menu of options. The following is what I have so far:
function MainMenu {
while ]
do
echo "--------------------------------------------------------------------------------"
echo... (4 Replies)
Discussion started by: ckoeber
4 Replies
2. Red Hat
Hiya,
Is there a known method from converting LVM data to VxVM data..
ie we have a load of local and SAN (HPDM) mounts on RHEL 4u5/5u1 servers which are now required to be clustered with SFS (VxFS,VxVM,CFS,VCS etc)
I've come across the vxvmconvert, but thought that was HP-UX only?
Many... (0 Replies)
Discussion started by: itsupplies
0 Replies
3. Filesystems, Disks and Memory
Hiya,
Is there a known method from converting LVM data to VxVM data..
ie we have a load of local and SAN (HPDM) mounts on RHEL 4u5/5u1 servers which are now required to be clustered with SFS (VxFS,VxVM,CFS,VCS etc)
I've come across the vxvmconvert, but thought that was HP-UX only?
Many... (3 Replies)
Discussion started by: itsupplies
3 Replies
4. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
5. Red Hat
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies
6. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
7. Red Hat
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies
8. Red Hat
Hi All,
I have one logical volume with size as 900G and it is mounted as xfs file system.
Now I want to reduce this partition to 500G.
So I followed the below steps.
unmount the mount point /home
Reduced the volume using the command
Now I remounted the partition.
But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies
9. UNIX for Beginners Questions & Answers
I have written a script that that takes file names and breaks them apart.
File names are :
aal_mock.war.deployed
AuroralMockService-1.0.war.deployed
consumerProfile.war.deployed
EbillMock.war.deployed
IAMAOGServices.war.deployed
IAMPermission.war.deployed... (5 Replies)
Discussion started by: Junaid Subhani
5 Replies
LEARN ABOUT DEBIAN
ns_csinit
Ns_CritSec(3aolserver) AOLserver Library Procedures Ns_CritSec(3aolserver)
__________________________________________________________________________________________________________________________________________________
NAME
, Ns_CsDestroy, Ns_CsEnter, Ns_CsInit, Ns_CsLeave - Manage and use critical section locks
SYNOPSIS
#include "ns.h"
void
Ns_CsDestroy(Ns_Cs *csPtr)
void
Ns_CsEnter(Ns_Cs *csPtr)
void
Ns_CsInit(Ns_Cs *csPtr)
void
Ns_CsLeave(Ns_Cs *csPtr)
_________________________________________________________________
DESCRIPTION
Critical section locks are used to prevent more than one thread from executing a specific section of code at one time. They are implemented
as "objects", which simply means that memory is allocated to hold the lock state. They can also be called "sychronization objects".
While a thread is executing a critical section of code, all other threads that want to execute that same section of code must wait until
the lock surrounding that critical section has been released.
This is crucial to prevent race conditions which could put the server into an unknown state. For example, if a section of code frees a
pointer and then decrements a counter that stores how many pointers exist, it is possible that the counter value and the actual number of
pointers may be different. If another section of the server relies on this counter and reads it when the pointer has been freed, but the
counter has not yet been decremented, it could crash the server or put it into an unknown state.
Critical section locks should be used sparingly as they will adversely impact the performance of the server or module. They essentially
cause the section of code they enclose into behaving in a single-threaded manner. If a critical section executes slowly or blocks, other
threads that must execute that section of code will begin to block as well until the critical section lock is released.
You will normally want to wrap sections of code that are used to both read and write values, create and destroy pointers and structures or
otherwise look at or modify data in the system. Use the same named lock for both read and write operations on the same data.
Threads that are waiting for a critical section lock to be released do not have to poll the lock. The critical section lock functions use
thread condition functions to signal when a lock is released.
Ns_CsDestroy(csPtr)
Destroy a critical section object. Note that you would almost never need to call this function as synchronization objects are typi-
cally created at startup and exist until the server exits.
The underlying objects in the critical section are destroyed and the critical section memory returned to the heap.
Ns_CsEnter(csPtr)
Lock a critical section object, initializing it first if needed. If the critical section is in use by another thread, the calling
thread will block until it is no longer so.
Note that critical sections are recursive and must be exited the same number of times as they were entered.
Ns_CsInit(csPtr)
Initialize a critical section object. Memory will be allocated to hold the object's state.
Ns_CsLeave(csPtr)
Unlock a critical section once. A count of threads waiting to enter the critical section is kept, and a condition is signaled if
this is the final unlock of the critical section so that other threads may enter the critical section.
SEE ALSO
nsd(1), info(n), Ns_MasterLock(3), Ns_MasterUnlock(3), Ns_CondDestroy(3), Ns_CondSignal(3), Ns_CondWait(3), Ns_MutexLock(3), Ns_MutexUn-
lock(3)
KEYWORDS
AOLserver 4.0 Ns_CritSec(3aolserver)