This article will guide you on how to recognize and troubleshoot the most commun scenarios related to SynetoFileRecovery VM

SynetoFileRecovery virtual machine is only used for file recovery, migration and cloning operations in SynetoOS. It uses few resources and can either be stopped, canceled or left running. 
If left running, the file recovery feature will work faster.

When in health the VM console output shows:

Warnings, Notifications and Errors


It's possible that in some occasions the VM status indicates a warning signal.
When VM functionality is confirmed it can be ignored. In case features related to the VM are failing it is required to reconfigure the VM 

The "Guest OS "warning can also be ignored


Few notifications that are directly associated with SynetoFileRecovery VM status, these are the most common ones


"Critical: disk space usage on rpool/datastores/syneto-file-recovery-SNxxxxxxxxx is above 90%"

For this specific notification, please contact our technical support team

"Syneto Service VM failed to start" 
 In this scenario reconfiguration of the SynetoFileRecovery virtual machine is required


Any of the below output errors require to recover the SynetoFileRecovery configurations, in the following part of this article we will explain step by step how to proceed 

How to reconfigure SynetoFileRecovery virtual machine

 Before starting the process:
  * Confirm that datastore1 has at least 15GB of available space
  * Please make sure that SynetoOS who acts as a gateway for SFR goes out on the    internet. Also ensure that there is no firewall or proxy to filter or block the connection to SynetoOS.
You can consult our documentation: Firewall Ports and Addresses

Step 1: Power off the SynetoFileRecovery VM

  • Access ESXI GUI to find the VM in the "Virtual Machines" dashboard and proceed to power off the VM

Step 2: Unregister the SynetoFileRecovery VM

  • After the machine is confirmed to be turn-Off proceed to unregister the VM

Step 3: Delete SynetoFileRecovery folder from Datastore1 directory catalog

  • Go to Storage->Datastore browser select Datastore1 you should see  the folder "SynetoFileRecovery".
    Proceed to select it and delete it

Step 4: Connect trough SSH to the SynetoOS 

Step 5: Verify is file "syslog_config" is present on luna directory

  • Confirm if the file "syslog_config" already exist on luna directory
cd /usr/share/luna
  • If the file is not present on the directory, proceed to create it using vim.
    In cases you've logged on an unsupported shell to use vim you must first remove bash profile, logout and login again to the ssh session
    rm ~admin/.bash_profile
  • To create the file using vim 

    vim /usr/share/luna/syslog_config

    This will generate an empty file, that must stay empty.

  • Save and exit the file 

    1.-  esc 
    2.- :wq + enter

Step 6: Run, Luna run

  • Now that the "syslog_config" file is confirmed/created. Proceed to invoke the SynetoFileRecovery Install script
    # luna run

The deploy might take approximately 10-15 min. 
After the VM reappear on the virtual machine list, give it some time to finish. 
Proceed to test feature functionality, if they fail contact our Technical Support Team