Hi:
The policy type for this backup is MSSQL. The way this type
of Backup works is the MSQL agent queieses the database
and takes a snapshot. This snapshot is then dumped to the media server
and the meta data for the catalog is passed to the Master Server.
Please note the following error from the detail status you posted:
2015/03/24 09:29:47 AM - Error bpbrm(pid=12260) from client stlmsql: ERR - failure reading file:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump100000.txt (WIN32 2: Unknown error)
This is a Windows error. The file that Windows cannot read is the SQLDump. A good place to start
looking for the cause would be The Windows Event Viewer.
A status code 4207 occures when Netbackup could not fetch the snapshot metadata or state files. See:
http://www.symantec.com/docs/HOWTO105218
1. Has this backup every worked before?
2. Verify that the Client can do a forward/reverse lookup on the Master
Program Files\Veritas\Netbackup\bin >bpclntcmd -pn (reverse lookup)
Program Files\Veritas\Netbackup\bin > bpclntcmd -host <master server>
3. Verify required ports are not blocked between client and master.
From Master: Program Files\Veritas\Netbackup\bin\admincmd > bptestbpcd -hn stlmsql -verbose
4. Verify the state file location on the client has write permission:
<from client stlmsql: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.stlmsql_1427119622.1.0>
5. Provide bpcd log from client that matches the time frame of the detail status for
more information on failure.