β12-03-2013 10:33 PM
Hi guys.
I triggered a BMR backup a months ago and it was successful. But when I triggered again a BMR backup yesterday, it failed and i got an error message.
This error messages display while im performing BMR backup on a SQL server.
Netbackup version: 7.1.0.4
Client OS: windows 2003 r2 standard SP2
Snapshot provider: Microsoft Volume Shadow Copy Service (VSS)
This is the detailed status of the failed backup job.:
12/4/2013 12:57:31 AM - Info nbjm(pid=4440) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=139050, request id:{5FF2E43A-42B7-4293-B093-D1D8E92DAE36})
Solved! Go to Solution.
β12-11-2013 06:41 PM
Hi guys!
Thanks for the info!
I manually specified a VSS provider on the client machine by this command:
w2koption.exe -backup -snapshotprovidertype 1
then I ran a backup on the Master server and It backed up successfully!
Cause:
When backing up a windows 2003, the VSS provider must be a Microsoft Software Shadowss Copy by default
If you have more than one provider registered on a Windows Server 2003-based computer. the Microsoft Software Shadow Copy Provider (a.k.a. the System Provider) will likely not be used by default and that causes an error
Solution:
In the NetBackup version 7.1 and higher client , there is a w2koption command to force NetBackup to use a manually specified provider.
The 'w2koption' command located in the ....netbackup\bin\ directory provides functionality to force the NBU Client to use a particular provider type.
w2koption -backup -snapshotprovidertype <0, 1, 2, 3>
0 (Let Microsoft Windows decide which provider to use)
1 (Selects System VSS provider)
2 (Selects Software VSS provider)
3 (Selects Hardware VSS provider)
Example to configure NBU to use the System Provider:
w2koption -backup -snapshotprovidertype 1
See the link below for TECHNOTE:
http://www.symantec.com/business/support/index?page=content&id=TECH158127
β12-03-2013 11:03 PM
need help
β12-03-2013 11:50 PM
Hello Jaime,
What is your policy selection list?
ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
This is related to VSS issue.
Run Vssadmin List Writers ....
Verify if there are any errors.
Visit Microsoft site for latest VSS hotfix for your client.
some times reboot will fix these kind of issues.
β12-04-2013 12:32 AM
Hi,
Thanks for your response.
ALL_LOCAL_DRIVES is my backup selection
Ran Vssadmin list writers: results are stable and No errors.
β12-04-2013 12:35 AM
Please check the state of VSS and associated Writers.
Have you seen this?
Have you checked state of VSS writers?
Please check the Microsoft Support site for latest VSS hotfixes.
I believe this is one of the 'newer' VSS hotfixes : http://support.microsoft.com/kb/940349
Please also add all SQL database files to the Client's Exclude List:
*.mdf
*.ldf
These database files cannot be backed up with normal MS-Windows backup while SQL is up and running.
β12-04-2013 07:03 PM
Tried to reboot the client, test backup but it still failed
I also tried to access the client and backup the System State using NTbackup (win2003) but it still failed
I'm very confuse why my previous backup was successful. I didnt change anything with its configuration including the policy but still failing.
β12-04-2013 07:12 PM
I check the list writers before I perform a NTbackup.
β12-04-2013 07:16 PM
VSS writers are all stable and no error but when i perform NTbackup it still fails
β12-04-2013 07:28 PM
yes, please see my comments
β12-04-2013 07:39 PM
Hi,
Thanks for your response.
ALL_LOCAL_DRIVES is my backup selection
Ran Vssadmin list writers: results are stable and No errors.
tried to reboot but still the backup failed
β12-04-2013 07:54 PM
β12-04-2013 08:05 PM
Good thing that you tried ntbackup. This takes NBU completely out of the picture and makes it a Microsoft issue.
Excellent blog in above post!
β12-11-2013 06:41 PM
Hi guys!
Thanks for the info!
I manually specified a VSS provider on the client machine by this command:
w2koption.exe -backup -snapshotprovidertype 1
then I ran a backup on the Master server and It backed up successfully!
Cause:
When backing up a windows 2003, the VSS provider must be a Microsoft Software Shadowss Copy by default
If you have more than one provider registered on a Windows Server 2003-based computer. the Microsoft Software Shadow Copy Provider (a.k.a. the System Provider) will likely not be used by default and that causes an error
Solution:
In the NetBackup version 7.1 and higher client , there is a w2koption command to force NetBackup to use a manually specified provider.
The 'w2koption' command located in the ....netbackup\bin\ directory provides functionality to force the NBU Client to use a particular provider type.
w2koption -backup -snapshotprovidertype <0, 1, 2, 3>
0 (Let Microsoft Windows decide which provider to use)
1 (Selects System VSS provider)
2 (Selects Software VSS provider)
3 (Selects Hardware VSS provider)
Example to configure NBU to use the System Provider:
w2koption -backup -snapshotprovidertype 1
See the link below for TECHNOTE:
http://www.symantec.com/business/support/index?page=content&id=TECH158127
β12-11-2013 07:27 PM
Thanks Jamie for sharing the resolution :)