Sponsored Content
Operating Systems AIX Write once on NFS file system Post 302707531 by gts1999 on Friday 28th of September 2012 09:02:02 PM
Old 09-28-2012
I'd be looking at Tape Archive if it was me, not disk.
Also, a time-expired backup (archive) is not really suitable for disk residency due to MTBF on disks.
How often would you Archive?
What volume of data?
How sensitive is the data? Compliance issues?
If the answers to these questions still leave cloud backup in scope, Amazon S3 is not a bad product!
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Is it possible to re-export a exported NFS file system?

Hi... Is it possible to re-export a exported NFS file system? If no, Why? Let me know, if any further details are required about the question. Thanks in advance Adams:) (5 Replies)
Discussion started by: Adams Nave
5 Replies

2. AIX

Cannot access NFS file system

I create a NFS file system. I can read this system from client, however, I cannot write anything in this folder. Why? (1 Reply)
Discussion started by: rainbow_bean
1 Replies

3. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies

4. AIX

How to export AIX File system NFS to Windows ?

Hello, Can someone please point to an easy document or steps how to export AIX file system /whatever to Windows O/S Basically Windows should see this filesystem / directory and should be able to write in this filesystem / directory Thanks (2 Replies)
Discussion started by: filosophizer
2 Replies

5. UNIX for Dummies Questions & Answers

How to check whether file system is local or NFS?

Hi, suppose I have file system path say /foo/bar/baz then how would I find out whether it is local file system or NFS? If it is NFS then I want to find out the host where file system is located. Thanks, Paresh (5 Replies)
Discussion started by: masaniparesh
5 Replies

6. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

7. AIX

For NIM: NFS file system problem

hello, i am trying to export a file system so that i can mount it on NIM server and make mksysb backup of the server on that fs. i get this message: mount: 1831-011 access denied for s_semdev:/dr_s_zeus/mksysb/dr_s_zeus mount: 1831-008 giving up on: s_semdev:/dr_s_zeus/mksysb/dr_s_zeus ... (5 Replies)
Discussion started by: omonoiatis9
5 Replies

8. AIX

NIM NFS file system cannot unmount

Hello, I have a script on my NIM Master that runs with crons and performs mksysb backups of all NIM Clients once a week. There is a problem with one of the clients as it stucks and never finishes the mksysb backups. I tried to unmount the NFS file system created by the NIM in order to perform... (5 Replies)
Discussion started by: omonoiatis9
5 Replies

9. Solaris

NFS - concurrent write to same file normal ?

Hi all, Sorry if I sound like a novice , I have always thought that for network file system which can be shared, there will be some access restriction in which when user A is writing/editing fileA, user B is able to view the same fileA but cannot write/edit it until user A has... (6 Replies)
Discussion started by: javanoob
6 Replies

10. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
vxconfigrestore(1M)													       vxconfigrestore(1M)

NAME
vxconfigrestore - restore disk group configuration SYNOPSIS
/etc/vx/bin/vxconfigrestore [-c | -d | -n | -p] [-l directory] {dgname | dgid} DESCRIPTION
The vxconfigrestore utility is used to restore a disk group's configuration information if this has been lost or become corrupted. The disk group whose configuration is to be restore is specified either by name or by ID. Any disks whose private region headers have become corrupted are reinstalled when the disk group configuration is restored. If you choose not to reinstall the VxVM headers for these disks, it may not be possible to restore the disk group. The disk group configuration backup files may have been automatically created by the vxconfigbackupd daemon, or manually by running the vxconfigbackup command. Restoration of a disk group configuration has two stages: precommit and commit. The precommit stage allows you to temporarily load the con- figuration that is to be restored, and examine it using the vxprint utility. At this stage, the disk group configuration is read-only. No permanent changes are written to disk until you choose to commit them. If desired, you can abandon the restore operation at the precommit stage. OPTIONS
-c (Commit) Permanently commits changes to the disks. The restoration must be at the precommit stage for this command to succeed. Volumes are synchronized in the background. For large volume configurations, it may take some time to perform the synchroniza- tion. You can use the vxtask -l list command to monitor the progress of this operation. -d (Decommit) Abandons the restore operation at the precommit stage. -n (Precommit: no installation of VxVM disk header) Loads the disk group configuration at the precommit stage. This option speci- fies that disks whose private region headers have become corrupted are not to be reinstalled. -l directory Specifies a directory other than the default (/etc/vx/cbr/bk) where the backup configuration files are located. -p (Precommit: load) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private region headers have become corrupted are to be reinstalled. The vxprint command can be used to examine the disk group configura- tion. Note: The volumes have not yet been synchronized at this stage. This is the default operation if no option is specified. EXAMPLES
Load the configuration of the mydg disk group from the default directory, and reinstall disks that have corrupted VxVM disk headers: vxconfigrestore -p mydg Load the configuration of the mydg1 disk group from the backup files in the directory /dgbackup/mydg1 without reinstalling any disks that have corrupted private region disk headers: vxconfigrestore -n -l /dgbackup/mydg1 mydg1 Abandon the restoration of the mydg2 disk group at the precommit stage: vxconfigrestore -d -l /dgbackup/mydg2 mydg2 Commit the restoration of the configuration of the mydg disk group from the backup files in the directory /dgbackup/mydg: vxconfigrestore -c -l /dgbackup/mydg mydg FILES
/etc/vx/cbr/bk/dgname.dgid/dgid.dginfo Default location of backup file for disk group information. /etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo Default location of backup file for disk attributes. /etc/vx/cbr/bk/dgname.dgid/dgid.binconfig Default location of backup file for binary configuration copy. /etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec Default location of backup file for configuration records in vxprint -m format. NOTES
A disk group must be restored on the same physical disks as are defined in the configuration backup files. The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other application data that is configured within VxVM objects. A shared disk group in a cluster is restored as a private disk group. After the commit phase has completed, you can deport the private disk group and re-import it as a shared disk group. SEE ALSO
vxconfigbackup(1M), vxconfigbackupd(1M) VxVM 5.0.31.1 24 Mar 2008 vxconfigrestore(1M)
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy