Verify following steps followed for setting NFS staging and remote storage for Prime backup.
Configurations:-
Steps to be done on the Active Server/Source Server:-
[1] Configure the staging URL to the Server where you want to take the backup.
Ex:- If 10.106.33.78 is the active server and 10.106.33.105 is the inactive instance where you want to put the backup, You can create the staging url along with mentioning the path where you want the staging to trigger. Staging is the path where the initial data will be transferred temporarily to tar the file later.
backup-staging-url nfs://10.106.33.105://localdisk/defaultRepo/staging
[2] Now Configure the repository pointing to the other instance of the prime along with the target location accordingly.
Note:- The staging and storage folders can be on the same NFS server, or on separate NFS servers. If you plan to stage and store on separate NFS servers, you will need IP addresses for both servers
Ex:-
repository nfs
url nfs://10.106.33.105://localdisk/defaultRepo/storage/
[3] Login to Shell of the Prime and start the nfs
ade # service nfs start
Do not miss the command:
Steps to be done on the In-Active Server/Target Server where you put the backup:-
[1] Login to Shell of the Target Prime and start the nfs,rpcbind
ade # service nfs start
ade # service rpcbind start
[2] Create the Target locations ( Both Storage and Staging )
mkdir -p /localdisk/staging
mkdir -p /localdisk/storage
[3] Give Complete permissions to those directories:-
chmod 777 /localdisk/storage
chmod 777 /localdisk/staging
[4] Create the exports accordingly. Steps to do as below:-
sudo su -
vi /etc/exports
Type Esc + i . Now you will be able to input the text in to the exports file. You can give the permissions as below:- ( 10.106.33.78 is the Active Primary instance)
/localdisk/defaultRepo/staging 10.106.33.78(rw,sync)
/localdisk/defaultRepo/storage 10.106.33.78(rw,sync)
[5] Export the locations using the command:-
exportfs -arv
Sample output:-
ade# exportfs -arv
exporting 10.106.33.78:/localdisk/defaultRepo/storage --------à This must result like this as staging and storage must be exported successfully to Prime server for mounting.
exporting 10.106.33.78:/localdisk/defaultRepo/staging
[+] Modify the services as below:-
service iptables stop
chkconfig iptables off
service rpcbind restart
Verify:-
[1] On the Primary server after Successful configuration of the Target server, Enter the shell and type the command:- ( Target server used here is 10.106.33.105 )
ade # rpcinfo -p 10.106.33.105
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
Check whether you are able to see the shared stage and storage folders on the remote NFS server from the Prime Infrastructure server.
If the output of this command does not show the NFS service and its associated ports on the NFS server. you need to restart the NFS service on the Prime Infrastructure server.
[2] From the admin mode of Prime, Please verify using the command:-
PI33/admin# show repository nfs
a1
test-180428-0313.tar.gz
Once Everything has been verified, Point the backup trigger to the NFS configured server in the UI Under Administration -> Jobs -> Server backup -> Edit You can Trigger the backup in the target location Successfully.
- Ideally the Prime server file system partition must show like this:
-bash-4.1# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/smosvg-rootvol
3.9G 327M 3.4G 9% /
tmpfs 5.9G 1.8G 4.1G 31% /dev/shm
/dev/mapper/smosvg-altrootvol
124M 5.6M 113M 5% /altroot
/dev/sda1 485M 41M 419M 9% /boot
/dev/mapper/smosvg-home
124M 6.0M 112M 6% /home
/dev/mapper/smosvg-localdiskvol
44G 18G 24G 44% /localdisk
/dev/mapper/smosvg-optvol
203G 57G 136G 30% /opt
/dev/mapper/smosvg-recvol
124M 5.6M 113M 5% /recovery
/dev/sda2 97M 5.6M 87M 7% /storedconfig
/dev/mapper/smosvg-storeddatavol
9.7G 151M 9.0G 2% /storeddata
/dev/mapper/smosvg-tmpvol
2.0G 42M 1.8G 3% /tmp
/dev/mapper/smosvg-usrvol
6.8G 1.2G 5.3G 18% /usr
/dev/mapper/smosvg-varvol
3.9G 192M 3.5G 6% /var
10.106.33.105://localdisk/defaultRepo/staging ------------à This mount point was happening since exportfs from NFS server was not working from NFS remote server.
203G 28G 166G 15% /opt/backup
