Sponsored Content
Full Discussion: Regarding NFS mount point
Operating Systems Linux Red Hat Regarding NFS mount point Post 302923710 by gull04 on Tuesday 4th of November 2014 07:21:08 AM
Old 11-04-2014
Hi,

Much better, there is no problem with creating a volume of 27Tb and mounting it - you'll have to make sure that your testing can be done in isolation. So you should if possible sandbox the machine and data base.

The process I would look at is a simple JBOD using LVM to create a volume group that is big enough for the 25Tb restore - which will take some time I think. You'll have to install the netbackup client on the target host and restore.

Regards

Dave
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to change the file modification time of a file on nfs mount point

Hi I am accessing a file on nfs mounted device, after completing using of the file, i am tring to restore the access time and modification times of the file. So i got the previous modified time of the file using stat() function and trying to set the date and time for the file, To set these... (6 Replies)
Discussion started by: deepthi.s
6 Replies

2. Linux

one nfs mount point for many logical volumes

hi i am wondering if it is possible to use one nfs mount point for several logical volumes. i have a top level directory /imaging with data1 - data50 below it. each dataX directory is a logical volume configured through LVM. if i mount them separately on the client (i.e. 50 lines in fstab... (1 Reply)
Discussion started by: user23
1 Replies

3. AIX

NFS mount point monitoring script

Hi, I'm looking to create a NFS mount point monitoring shell script not sure if im going the right way about it so could do with some help. What i was thinking of doing was using the below command but am unsure how to handle the output. So if the filesyetem is active it will return "1" but if... (4 Replies)
Discussion started by: elmesy
4 Replies

4. Red Hat

NFS mount point problem

Hi Forum I am trying to mount /NFS as nfs mountpoint on two servers ( A & B ). After mounting the nfs filesystem, both of them behave normally for around 10 mins and after that the NFS file handle become stale and the mountpoints dont respond. While executing df -kh, the output hang out and the... (15 Replies)
Discussion started by: rajdasuwal
15 Replies

5. Solaris

No write permission on NFS mount point

hi all i have mounted one nfs mount point but i has no write permission on it. when i am going to make a directory it is giving an error # mkdir 1 mkdir: Failed to make directory "1"; Permission denied i shared using command # share -F nfs -o rw -d "backup" /backup mounted using... (3 Replies)
Discussion started by: nikhil kasar
3 Replies

6. Shell Programming and Scripting

Script for NFS mount point

Hi , i have create the bash script for nfs but in this script asking for mount point only once it is it prompting for second time. example: do you wants to create any other mount point ? note(if i give yes it should ask me to add the mount point else it should proceed with next step) it... (5 Replies)
Discussion started by: Rahulne25
5 Replies

7. Red Hat

NFS mount point

Hi, Can you tell me something about NFS mount point ? Regards, Maddy (3 Replies)
Discussion started by: Maddy123
3 Replies

8. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

9. Solaris

Sol 10 - Strange NFS behaviour - adminnfs prefix to mount point

Something has changed..... /etc/vfstab entry:- host1:/backup/RMAN - /RMAN nfs - no rw,hard,rsize=32768,wsize=32768,llockBut when I mount it, and run df -k | grep RMANResults are:- host1:/backup/RMAN 54971960832 26752241664 28219719168 49% ... (1 Reply)
Discussion started by: psychocandy
1 Replies

10. UNIX for Beginners Questions & Answers

How to create a new mount point with 600GB and add 350 GBexisting mount point? IN AIX

How to create a new mount point with 600GB and add 350 GBexisting mount point Best if there step that i can follow or execute before i mount or add diskspace IN AIX Thanks (2 Replies)
Discussion started by: Thilagarajan
2 Replies
vgcfgrestore(1M)														  vgcfgrestore(1M)

NAME
vgcfgrestore - display or restore LVM volume group configuration from backup file or kernel memory SYNOPSIS
vg_name vg_name old_pv_path] pv_path vg_conf_path vg_conf_path old_pv_path] pv_path pv_path Remarks cannot be performed if the volume group is activated in shared mode. cannot be performed on devices attached to activated volume groups. Prior to restoring a backup configuration to a disk, detach the physi- cal volume from the volume group using the command (see pvchange(1M)), or deactivate the volume group using the command (see vgchange(1M)). will refuse to restore a configuration to a physical volume with a block size different than the block size stored in the configuration backup file for that physical volume. DESCRIPTION
The command restores the LVM configuration data from a default option) or alternate option) configuration backup file, or from kernel mem- ory option), to the physical volume named by pv_path. Or, it displays the configuration data on standard output option). The configuration stored for one physical volume, old_pv_path, can be copied to another physical volume pv_path option). Options and Arguments recognizes the following options and arguments: pv_path The raw (character) device path name of a physical volume that is currently online. If the option is omitted, pv_path must specify a physical volume whose configuration is stored in the configura- tion backup file. Get configuration information from the alternate configuration backup file vg_conf_path. This option is applicable to input arguments belonging to volume groups version 1.0. Forcibly restore the LVM configuration data even if the physical volume has alternate block(s) allocated inside the user data area. This option should be used with extreme caution. User is advised to fix the problem because potential data corruption could occur. Get configuration information from LVM data structures in kernel memory. The volume group containing pv_path must be activated in order to use this option. List the configuration information saved in the specified configuration backup file. Get configuration information from the default configuration backup file: vg_name is the path name of the volume group. base_vg_name is the base name of vg_name. For example, if vg_name is specified as base_vg_name is Restore the configuration information saved for physical volume old_pv_path to physical volume pv_path. This option is useful when a physical volume's name has changed since the configuration backup file was created or updated. old_pv_path must be the path name of a physical volume whose configuration is stored in the configuration backup file. It needs not be currently online. pv_path must be the path name of a physical volume that is currently online. Its configuration needs not be stored in the configuration backup file. Forcibly restore the LVM configuration data even if there is a physical volume mismatch between the kernel and the configuration backup file with the volume group still active. This option should not be used unless the configuration file is absolutely valid and up-to-date. Restoring invalid configuration data can result in data corruption later. If there are alternate physical volume links configured in the system, the following message will appear when total number of physical volumes in the kernel does not match with the configuration backup file due to missing alternate physical volume links: Mismatch between the backup file and the running kernel: Kernel indicates X disks for /dev/vgname; /etc/lvm- conf/vgname indicates Y disks. Cannot proceed with the restoration. Deactivate the Volume Group and try again. In this case, the user is advised to deactivate the volume group first, then use the command to restore configu- ration data when the volume group is unavailable. But if the volume group has to stay available and the user is absolutely sure the configuration file is correct, this option will restore data from the configuration file when the volume group stays available. Provide additional information when invoked together with option. o Additional values displayed for each path: o Disk size in kilobytes o Starting block number (kb) of the user data. o The PVkey (see Note that paths with the same key are links to the same device. Additional values displayed for each volume group: o max_pv o max_pe o max_lv o vg_version o vg_size (only volume groups version 2.0 or higher, see vgcreate(1M)) RETURN VALUE
exits with one of the following values: Successful completion. Failure. Errors occurred during the restore operation. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Restore the LVM configuration information for the physical volume that was saved in the default file Force to restore the LVM configuration data when volume group is still active: Restore the LVM configuration information to physical volume using alternate configuration file List backup information saved in default configuration file Above command might display the following: Restore LVM configuration information stored for in default configuration file to physical volume Restore LVM configuration information to physical volume using LVM data structures in kernel memory. The volume group containing must be activated: AUTHOR
was developed by HP. SEE ALSO
pvchange(1M), vgcfgbackup(1M), vgchange(1M), intro(7), lvm(7). vgcfgrestore(1M)
All times are GMT -4. The time now is 05:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy