Recovery Point Server (RPS)/Data Store Related

• The RPS datastore resides on volume with no drive letter (GUID Path)
• Symptom
• After the RPS server restarts, the datastore is shown in stopped state, and when you try to manually restart, the following error appears:
• Failed to start the datastore because of an invalid data store path. Verify if the verification file exists and has not changed in the backup destination folder or any of the deduplication folders.
• Solution
• For the datastore to be in running state across RPS reboots, enable automount on the RPS server. You can enable automount using the diskpart - automount command.
• Follow these steps:
1. Open an elevated command prompt.
2. In the elevated command prompt, type diskpart, and then press Enter.
3. Next, in the elevated command prompt, type automount enable, and press Enter.
4. Close the elevated command prompt.
5. To apply changes, restart the computer.
• The antivirus software unexpectedly deletes the data store file.
• Symptom
• Backup or replication job fails and the following error message is displayed:
• system cannot find the file specified.
• Verify Windows Event log as McAfee detects the data store file (for example, P0000000042.data) as Exploit-ScriptNull Trojan virus and deletes it.
• Solution
• Configure the antivirus setting to set the Recovery Point Server (RPS) Data Store location in the exclusion list.
• Note: For some antivirus software, you need to set the exclusion list on the server.
• If the following two conditions exist, the hash memory for the data store is displayed incorrectly while modifying the data store:
  • The memory of the RPS Server is less than or equal to 4 GB.
  • You did not select the maximum value for the hash memory while creating a data store.
• Using restore view, you cannot view previous recovery points.
• Symptom
• When the backup jobs are running Windows 10 as the RPS machine, at times you cannot view any previous recovery points when you browse the Files/Folders to Restore option in the restore view.
• Solution
• Wait for the running backup jobs to exit.
• The Console fails to add RPS if the server name has localized characters.
• Symptom
• When you add a server name to RPS in the destination, the Console fails to add RPS if the server name has localized characters.
• Solution
• As a workaround, change the server name to IP address.
• Datastore hosted on hidden volume cannot be started even after RPS is rebooted
• Symptom
• This issue occurs with Windows 2019 in which the hidden volume does not get auto mounted even after rebooting the RPS. Although the GUID is not changed, the auto mount issue causes the Datastore to stop.
• Solution
• As a workaround, use the following "mountvol" command for every hidden volume which is not accessible:
• mountvol <PATH/NEW DRIVE LETTER:> <GUID>
• mountvol <PATH/NEW DRIVE LETTER:> /D