DR settings after setup
How to change CPU, RAM and network cards of the recovery machine once the DR is active. Why applying the Sefthy Agent proposal is the better option when the server network changes.
The resources and the network configuration registered in the wizard determine the characteristics of the machine that boots in the cloud at restore time. When the server changes, this data has to be updated in advance, not during the emergency.
Opening the settings
- Open the DR from the Disaster Recovery list.
- Top right, click the three dots menu, More actions.
- Choose Settings.
Anteprima video temporaneamente non disponibile.
Apri il file direttamente →At the top of the window a line summarises the scope of the changes, “CPU, RAM and network interfaces that will be applied to the VM the next time you start a DR”. Changes made here have no effect on the protected server.
Resources
The Resources section has two controls, CPU from 1 to 32 cores and RAM from 1 to 128 GB. Drag the slider or type the value in the field on the right. Keep the recovery machine close to the specifications of the real server. With fewer resources the services restart more slowly.
Network cards
Each network card is shown as a block with the IP Address, Netmask, DNS and VLAN fields. The Gateway field only appears on the first card, the primary one. If a connector is associated with the DR, the gateway is prefilled with the Emergency VPN gateway and can still be changed.
The VLAN field accepts values from 1 to 4094. Left empty it counts as 1, meaning no VLAN. Add network card adds a new card and the bin icon at the top right of a card removes it. The last remaining card cannot be deleted.
When you confirm, the Console automatically rebuilds the network extensions towards the cloud, one for each distinct VLAN configured on the cards. There is no need to contact support or to change anything on the connector. How several cards on different VLANs work is covered in Multiple network cards and VLANs in the DR.
The agent proposal
The Sefthy Agent, installed on the server, checks the network cards on every heartbeat. When it detects a configuration different from the one on record, an amber notice appears on the DR page titled The server network has changed. with a three column table. The columns show the field, the Registered value and the value Detected by the agent.
The notice offers two buttons.
- Review and apply opens the settings window with the fields already filled in with the new values. Under each changed field the previous value is shown struck through. Each card carries a chip stating whether it changed or is new, and cards the agent no longer detects stay at the bottom as dashed blocks. Review the values and confirm.
- Reject discards the proposal. The proposal is not shown again until the server network changes again.
Applying the proposal is better than retyping the values by hand. The data comes straight from the server and the proposal closes automatically when you save. If you close the window without confirming, the proposed values are discarded. The amber notice stays on the page and you can start again.
The seven health indicators are described in full in Server health and network drift.
Troubleshooting
If a restore is started while the window is open, the save is not performed. The window closes and the Console shows the message “Settings cannot be changed while a DR is in progress”. Try again once the cloud machine is off.
If a field fails validation, for example an invalid IP address or a VLAN out of range, the window stays open, the field is highlighted in red and nothing is saved.