SureBackup network configuration

[BChavetnoir]

Good Afternoon,

Let me introduce myself, we are hosting applications in Heathcare for several hospitals in our region.
We are using ExaGrid Storage for storing production Backups.

In our network architecture, we have many vlan and firewalls. Due to security, each application belong to a specific vlan.
We are using firewalls with DHCP lease (and DNS) functionality with vm mac address reservation to assign the IP address to a VM in a vlan.

Without doing any mistake, FYI, each time I execute a SureBackup, the MAC address of the vm change duing the boot process.
For example : on our production environment we have two vms that have
- vm1 the IP address : 172.19.50.100
- vm2 the IP address : 172.19.50.101

Without activating the DHCP/DNS functionality in SureBackup settings, the VMs will boot without getting any IP address and all SureBackups are failing.
When you active the DHCP/DNS functionality inside the SureBackup settings, it will assign the first IP addresses available in the subnet 172.19.50.xxx like 172.19.50.1 and 172.19.50.2 but not the identical production IP address.

We are not able to test many applications inside the SureBackup (like for example Oracle Database needs the specific production IP address to start correctly otherwise it fails).

A solution should be using some scripts in producton Linux and Windows VMs and making Surebackups settings.

During Surebackup execution execution (at vm boot process), How can we set up the same IP address as inside the production environment to be able to test applications in SureBackups ?
What are the settings (scripts and menu settings we should put in SureBackup menus to be sure get the same network IP configuration as production ?

I don't know how to set up this correctly, Are you already encounter this issue ?
Not being able to get the identical IP address as production vm ?

Which king of script(s) (linux b-shell, and windows) should we use on vm side (any example) ?
What king of SureBackup settings we should set to be sure the at boot process the vm we get the same IP address as the production one ?
Is there many différent(s) solution(s) available ?

For you, is it possible to get such configuration working to manage correctly Surebackups in our environment ?

Many Thanks for your help, advices and/or feedback.

Have a good day.

Bertrand Chavetnoir.

[Egor Yakovlev]

Hi Bertrand.

Interesting case!
Off the top of my head, there is no clear working solution (i.e., no fully tested and supported way to achieve the goal). However, some ideas might help solve the riddle:
- on Windows machines, you can set up an Alternate Configuration in the server's network adapter settings. These settings are used when the primary configuration fails. This is exactly what will happen in the lab if DHCP is not enabled - the machine will expect a DHCP address, but it won't receive one. The Alternate Configuration will then take effect, and the network interface will use whatever you set there, such as a static "172.19.50.101".
- [I'm not a Linux guy] on Linux machines, I believe you could use a script that performs the same function on boot or via a cron job (i.e., "check if the DHCP profile failed > switch to a static profile"). [/I'm not a Linux guy]

Hope that helps.

[mdippold]

You could include an additional VM in the application group which provides the necessary DHCP and DNS functioniality for the virtual lab, replicating the DHCP configuration of your firewalls.