Jump to content
NAKIVO Community Forum

Leaderboard

Popular Content

Showing content with the highest reputation on 05/11/22 in all areas

  1. @AalHaiThank you for getting back to us! In this case, we could recommend the following workaround: 1. Create a script on the NAKIVO director's side with the following actions (please note that there should be a separate script for each physical machine that should be backuped): - Refresh the transporter that is assigned to a necessary physical machine. - Start the backup job for a necessary physical machine. 2. Create a task on the physical machine side that will initiate the above script remotely on some trigger (boot, wake up etc.). At the same time, such workflow was not tested by our QA Team, and we could not guarantee its reliability. Thank you so much for your attention and participation. We are looking forward to your feedback soon
    1 point
  2. would it not be possible to use the cli to create a script that remotely initiates a backup job and simply have said script run everytime the notebook is booted up ? this would obviously fail in case the notebook is connected to a different network, but should successfully start the backup of the notebook in case it is connected to the company network
    1 point
×
×
  • Create New...