03-25-2015 07:26 AM
Solved! Go to Solution.
03-25-2015 10:59 AM - edited 08-02-2018 01:08 AM
Seems you are doing flat file backup of SQL dump. Important that you ensure that the dump is completed before NBU backup starts.
About snapshot error, herewith my own experience :
https://vox.veritas.com/t5/NetBackup/Failing-backups-status-156/m-p/710476#M190301
03-25-2015 08:00 AM
First take a look at I179L4
2015/03/23 04:10:39 PM - Error bptm(pid=520) ioctl (MTWEOF) failed on media id I179L4, drive index 0, The media is write protected. (19) (bptm.c.22854)
2015/03/23 04:10:39 PM - Error bptm(pid=520) FROZE media id I179L4, could not write tape mark to begin new image
It could look like you are hitting the upper limit for a VSS snpashot and as a result the snapshot is discolved
1: Check event log - does it mention snap was delete ?
2: Take a look at the tech note - you may need to change maximum VSS snap size.
Troubleshooting Status Code 156 "snapshot error encountered" occurs when using VSS for Open file backups or snapshots
http://www.symantec.com/docs/TECH156750
You may also want to enable the bpfis debug directory in [INSTALL_PATH]\Netbckup\logs as well
03-25-2015 08:54 AM
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.
03-25-2015 10:59 AM - edited 08-02-2018 01:08 AM
Seems you are doing flat file backup of SQL dump. Important that you ensure that the dump is completed before NBU backup starts.
About snapshot error, herewith my own experience :
https://vox.veritas.com/t5/NetBackup/Failing-backups-status-156/m-p/710476#M190301
03-25-2015 11:57 PM
Thank you guys, Im on it. There is a lot of reading ;)