If you can find an open scores project that will give you that option it is possible. I have just found it easy to use SCSI Target. Proable to get better perfomance using a Linux Box with a SCSI Target.
I have couple of questions: 1. I see your Ethernet1 IP address is 192.168.20.4 (at 3:35 mins), so ideally this should be your LocalNodePrivateIP, however you put LocalNodePrivateIP as your LocalNodePublicIP ie. 192.168.10 (at 8:16 mins). Why? 2. Why do you copy PADR.ini, user.ini and Vault.ini(at 20:44 min), from S:\PrivateArk\PADR, to C:\Program Files (x86)\PrivateArk\PADR\conf?
The 192.168.20.4 is the IP address Ethernet1 needed to talk to the ISCSI storage (192.168.20.1). Note in the dbparm.ini the storage needed to be allowed with the firewall rule. You cannot run the LocalNodePrivateIP on the Ethernet1 as this talks to the storage only. The 192.168.10.15 is the IP Address of the Ethernet0. This is the IP address needed to DRP to the Vault. The IP Address 192.168.10.16 is needed to talk to Vault (Port 1858). This interface is able to talk to any device on 192.168.10. subnet. It is possible to add a sub interface on this ethernet adapter for the LocalNodePrivateIP(192.168.50.15) to talk to the other servers LocalNodePrivateIP(192.168.50.17). You are able to use a third IP address (PeerNodePrivatelP) for the heartbeat between the two clustered Vault services (Vault-01-C2 to Vault-02-C2 only). It is possible to reuse the IP address (PeerNodePublicI) that you have assigned to the Vault (RDP) for the heartbeat. Heartbeat is the check for if the server is up and running and to ensure that only one server is Cluster is up. I copy the PADR.ini, user.ini and Vault.ini from the S drive to the C drive so do not have to recreate them again. (fewer steps to do and to prevent misconfiguration as these are known working details from the first vault)
@@dru0pa damn that's exactly the explanation I needed, thanks again. I still have questions on the file copy of the PADR.ini user.ini and Vault.ini. Technically if we follow the documentation, we need to bring the storage up on the Vault-02-C2 before PADR installation. And if we do that then the file will catch up with the PADR installation on Vault-02-C2. My question specifically is around the copying, does it have any significance around the workability of PADR or its just for back up and copy purpose?
![Gucci Mane & Sexyy Red - You Don't Love Me [Official Music Video]](http://i.ytimg.com/vi/j7IBqyFKT4c/mqdefault.jpg)
I will be taking this Cluster Vault from 12.2 and 14.2 this was the prep work
can we have the capacity planning and sizing discussed in the upcoming videos
Is there a way to do share storage thing using SAN in this workstation lab, instead of windows scsi target
If you can find an open scores project that will give you that option it is possible. I have just found it easy to use SCSI Target. Proable to get better perfomance using a Linux Box with a SCSI Target.
What Storage are you using?
iscsi storage presented from a windows server, it dose slow every thing down so slpit the cluster servers and the storage from the rest.
@@dru0pa Thanks. Your videos are really good.
I have couple of questions:
1. I see your Ethernet1 IP address is 192.168.20.4 (at 3:35 mins), so ideally this should be your LocalNodePrivateIP, however you put LocalNodePrivateIP as your LocalNodePublicIP ie. 192.168.10 (at 8:16 mins). Why?
2. Why do you copy PADR.ini, user.ini and Vault.ini(at 20:44 min), from S:\PrivateArk\PADR, to C:\Program Files (x86)\PrivateArk\PADR\conf?
The 192.168.20.4 is the IP address Ethernet1 needed to talk to the ISCSI storage (192.168.20.1). Note in the dbparm.ini the storage needed to be allowed with the firewall rule. You cannot run the LocalNodePrivateIP on the Ethernet1 as this talks to the storage only.
The 192.168.10.15 is the IP Address of the Ethernet0. This is the IP address needed to DRP to the Vault. The IP Address 192.168.10.16 is needed to talk to Vault (Port 1858). This interface is able to talk to any device on 192.168.10. subnet. It is possible to add a sub interface on this ethernet adapter for the LocalNodePrivateIP(192.168.50.15) to talk to the other servers LocalNodePrivateIP(192.168.50.17).
You are able to use a third IP address (PeerNodePrivatelP) for the heartbeat between the two clustered Vault services (Vault-01-C2 to Vault-02-C2 only). It is possible to reuse the IP address (PeerNodePublicI) that you have assigned to the Vault (RDP) for the heartbeat. Heartbeat is the check for if the server is up and running and to ensure that only one server is Cluster is up.
I copy the PADR.ini, user.ini and Vault.ini from the S drive to the C drive so do not have to recreate them again. (fewer steps to do and to prevent misconfiguration as these are known working details from the first vault)
@@dru0pa damn that's exactly the explanation I needed, thanks again.
I still have questions on the file copy of the PADR.ini user.ini and Vault.ini. Technically if we follow the documentation, we need to bring the storage up on the Vault-02-C2 before PADR installation. And if we do that then the file will catch up with the PADR installation on Vault-02-C2. My question specifically is around the copying, does it have any significance around the workability of PADR or its just for back up and copy purpose?