Sponsored Content
Full Discussion: AIX disaster recovery
Operating Systems AIX AIX disaster recovery Post 302130178 by tb0ne on Friday 3rd of August 2007 12:03:46 PM
Old 08-03-2007
I took the above advice and set up a NIM server and took a sysb via NIM. Now my question is, if there's a disk failure on a box and you aren't able to access the OS, how do you go about restoring a NIM sysb image?
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

Please Tell Me About Disaster Recovery

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

2. Cybersecurity

Template for Disaster Recovery

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

3. UNIX for Advanced & Expert Users

Disaster Recovery

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

4. UNIX for Dummies Questions & Answers

disaster recovery

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

5. Solaris

Disaster Recovery

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

6. Solaris

Solaris 8 using Flash Archive for Disaster Recovery

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

7. AIX

hacmp and disaster recovery question

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

8. UNIX for Dummies Questions & Answers

Disaster Recovery - Help needed

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

9. Red Hat

Disaster Recovery

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
POSIX_MADVISE(3)					     Linux Programmer's Manual						  POSIX_MADVISE(3)

NAME
posix_madvise - give advice about patterns of memory usage SYNOPSIS
#include <sys/mman.h> int posix_madvise(void *addr, size_t len, int advice); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): posix_madvise(): _POSIX_C_SOURCE >= 200112L DESCRIPTION
The posix_madvise() function allows an application to advise the system about its expected patterns of usage of memory in the address range starting at addr and continuing for len bytes. The system is free to use this advice in order to improve the performance of memory accesses (or to ignore the advice altogether), but calling posix_madvise() shall not affect the semantics of access to memory in the speci- fied range. The advice argument is one of the following: POSIX_MADV_NORMAL The application has no special advice regarding its memory usage patterns for the specified address range. This is the default behavior. POSIX_MADV_SEQUENTIAL The application expects to access the specified address range sequentially, running from lower addresses to higher addresses. Hence, pages in this region can be aggressively read ahead, and may be freed soon after they are accessed. POSIX_MADV_RANDOM The application expects to access the specified address range randomly. Thus, read ahead may be less useful than normally. POSIX_MADV_WILLNEED The application expects to access the specified address range in the near future. Thus, read ahead may be beneficial. POSIX_MADV_DONTNEED The application expects that it will not access the specified address range in the near future. RETURN VALUE
On success, posix_madvise() returns 0. On failure, it returns a positive error number. ERRORS
EINVAL addr is not a multiple of the system page size or len is negative. EINVAL advice is invalid. ENOMEM Addresses in the specified range are partially or completely outside the caller's address space. VERSIONS
Support for posix_madvise() first appeared in glibc version 2.2. CONFORMING TO
POSIX.1-2001. NOTES
POSIX.1 permits an implementation to generate an error if len is 0. On Linux, specifying len as 0 is permitted (as a successful no-op). In glibc, this function is implemented using madvise(2). However, since glibc 2.6, POSIX_MADV_DONTNEED is treated as a no-op, because the corresponding madvise(2) value, MADV_DONTNEED, has destructive semantics. SEE ALSO
madvise(2), posix_fadvise(2) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 POSIX_MADVISE(3)
All times are GMT -4. The time now is 10:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy