can anyone provide a short step-by-step information, what i need to select within a new created SharePoint 2016 Farm Backup for a GRT Backup job?
Backup of the farm to disk is fine.
But BE 20.4 still fails with a Catalog of the backup data.
The sgmon show some problem within the BE 20.4 release.
Authorized Tape drive count = -1 Actual Virtual Tape drive drive count = 0 Actual Standalone Tape drive Count= 0 Actual Robotic Tape drive count = 1
PVLSVR: [05/13/19 15:00:00]  [StorageManager::NagLicenseChecking()] SPO is licensed: NO
PVLSVR: [05/13/19 15:00:00]  [StorageManager::IsLimitedLicenseConformant()] Detected enclosures: 0 (limit 1)
SIHOST: [05/13/19 15:00:01]  onecore\ds\security\umstartup\usermgr\cli\usermgrcli.cxx(165)\usermgrcli.dll!00007FFF806611F6: (caller: 00007FFF889063DF) ReturnHr(1841) tid(26b4) 80070005 Access is denied.
SIHOST: [05/13/19 15:00:01]  onecoreuap\base\appmodel\execmodel\modern\lifetimemanager\appxexecutionutil.cpp(41)\modernexecserver.dll!00007FFF889064C0: (caller: 00007FFF889190B5) ReturnHr(1885) tid(26b4) 80070005 Access is denied.
SIHOST: [05/13/19 15:00:01]  onecore\ds\security\umstartup\usermgr\cli\usermgrcli.cxx(165)\usermgrcli.dll!00007FFF806611F6: (caller: 00007FFF889063DF) ReturnHr(1842) tid(26b4) 80070005 Access is denied.
You have asked how to define a Sharepoint 2016 GRT backup, but the process is the same as with previous Sharepoint versions;
Running that job will now backup all data and then catalog that after. If the GRT restore data is not showing for the Content DB after, but the complete data size has been backed up, that implies the Catalog process may have failed in the background, for some reason and it is probably better to rerun the job with the Catalog defined to be run as a separate job, as that may give a better indication of issues. That also allows you to use SGMon with Catalog debugging enabled during that separate Catalog job, to establish the cause, which could be permissions related.
this is the basic setup that worked for our old sharepoint 2013 and 2016 without GRT for the last years.
With BE 20.4 Backup with GRT fails and it´s not clear why (case is open).
I am looking for some details, what has to be modfied in SharePoint 2016 (Farm Config, SiteAdmin, etc....).
All Web Apps have the BE Service account as a Site Admin, but it still fails.
There is no difference in the way the backup will be created except that GRT is enabled in the Sharepoint job properties. Nothing needs to be done within Sharepoint to prepare for GRT backup. If you've already been doing non-GRT backups then the credentials used for the job should be sufficient for GRT backup. If the jobs are now failing, we'd have to see the job log to see how the failure is GRT related. If you have a support case open then this will be done.