At 1:25, what I get is "Unable to find SQL Server VM hosting the content database for the selected SharePoint site. Start File Level Recovery on the required VM, then launch SharePoint item recovery from the toolbar." I have no idea what that means...
@veeam2 жыл бұрын
Hi Conax! Sounds like a technical issue. Please reproduce the issue, and open a support case with logs from the Sharepoint Explorer. Be sure to enable "Extended Logging" as per here: statics.teams.cdn.office.net/evergreen-assets/safelinks/1/atp-safelinks.html .
@veeam2 жыл бұрын
Support checked your comment, and if you need an urgent restore, try the following: Start a File Level Restore ( helpcenter.veeam.com/docs/backup/vsphere/guest_restore_windows.html?ver=110 ) from the backup of the Sharepoint Site's backing SQL server Once the FLR window loads, launch an application restore as shown here: helpcenter.veeam.com/docs/backup/vsphere/guest_restore_save_vm.html?ver=110#launching-application-item-restore
@conaxlearn85662 жыл бұрын
@@veeam Thank you for your reply. Sorry I wasn't aware of the reply until today. But I have already found the solution on your discussion forum. The issue was caused by the use of SQL Alias on the SharePoint App Server and a registry key needs to be created/configured so that Veeam knows the actual name of the database server. forums.veeam.com/veeam-backup-replication-f2/sharepoint-explorer-is-unable-to-find-content-database-t26781.html That article was posted in 2016 so I'm wondering why hasn't it been fixed in the product yet?