Restoring databases using veritas Netbackup from 3 node prod cluster to 3 node dev cluster
I'm trying to restore database using veritas Netbackup client from 3 node production cluster into 3 node stg cluster. The database is not a part of AG group. when I tried to restore I'm below error:
CODEPAGE UTF-8
This batch file was created for an operation on host SQL01P using
the SQL Server instance <default>.
Move this file to the Veritas\NetBackup\dbext\MSSQL\ directory
on host <SQL01P>. Execute it there using the NetBackup
Database Extension GUI or the NetBackup Scheduler.
This is a template for the database MOVE command.
OPERATION RESTORE
OBJECTTYPE DATABASE
RESTORETYPE MOVE
Replace the database name in the following line with the name of the database that you
want to move to. Also remove the hash mark <#> which precedes the keyword <DATABASE>.
DATABASE "sharepoint_abc_Restore"
Replace the file path <S:\INST01\Data\MSSQL11.MSSQLSERVER\MSSQL\Data\sharepoint_abc.mdf>
with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
The target of the MOVE keyword must be "sharepoint_abc".
MOVE "sharepoint_abc"
TO "S:\INST01\Data\sharepoint_abc.mdf"
Replace the file path <S:\INST01\Log\MSSQL11.MSSQLSERVER\MSSQL\Data\sharepoint_abc.ldf>
with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
The target of the MOVE keyword must be "sharepoint_abc_log".
MOVE "sharepoint_abc_log"
TO "S:\INST01\Log\sharepoint_abc_log.ldf"
The following image is type: Full
NBIMAGE "SQL123.yvw.com.au:SQL1P/MSSQL7/SQLAGP/db/~/7/001of001/20220308075755//C"
SQLHOST "SQL1P"
NBSERVER "***************"
BROWSECLIENT "SQLS...**"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
RESTOREOPTION REPLACE
RECOVEREDSTATE RECOVERED
NUMBUFS 2
ENDOPER TRUE
ERR - Unable to determine fci cluster name for MSSQLSERVER
INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\ADB_database_Restore.bch>:
<0> operations succeeded. <1> operations failed.
Please let me know what's blocking while doing restore? Is it netbackup client issue or Windows cluster issue?