HOWTO - How to verify Windows Open File Backup operation using VSSADMIN and BPFIS before contacting Symantec Technical Support

Article:TECH47808  |  Created: 2006-01-15  |  Updated: 2014-01-10  |  Article URL http://www.symantec.com/docs/TECH47808
Article Type
Technical Solution



Issue



How to verify Windows Open File Backup operation using VSSADMIN and BPFIS before contacting Symantec Technical Support


Solution



The NetBackup Support organization often encounters customer cases for VSS Open File Backup problems that are not directly attributed to NetBackup. Often, the problem is due to Volume Shadow Copy configuration, File Locking, an Operating System problem, a resource issue or a compatibility issue with another 3rd Party Vendor application.

Provided below are some tests to verify Open File Backup operation with NetBackup on Windows Server platforms prior to contacting Symantec Support and confirm Microsoft VSS is working as expected.

=============================================================================

TEST #1 - Create, list & delete a Shadow Copy using VSSADMIN 

(This test verifies that Windows and the Volume Shadow Service is operating correctly)

a) Add the storage location for a volume first

C:\>vssadmin Add ShadowStorage /For=C: /On=D: /MaxSize=900MB

b) Create a shadow

C:\>vssadmin create shadow /for=C:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Successfully created shadow copy for 'C:\'
Shadow Copy ID: {c4695448-3cab-4bd5-a7ae-2af61c509dfd}
Shadow Copy Volume Name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
 

c) List the shadow 

C:\>vssadmin list shadows

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Contents of shadow copy set ID: {d0db889e-2e79-42f0-8716-605a5c18965f}
Contained 1 shadow copies at creation time: 5/3/2006 11:36:20 AM
Shadow Copy ID: {7f0bc357-1915-44d7-ab4c-c2988c9d1049}
Original Volume: (C:)\\?\Volume{33c37ee9-d389-11da-a17d-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2 
Originating Machine: client01
Service Machine: client01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential


d) Delete the shadow 

C:\>vssadmin delete shadows /for=C:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Do you really want to delete 1 shadow copies (Y/N): [N]? y
Successfully deleted 1 shadow copies.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IF RESULT = SUCCESS

VSS appears to be working. Continue to Test #2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IF RESULT = FAILURE 

-- Check for any File Locks on the volume being backed up
       Open Computer Management > System Tools > Shared Folders > Open Files.
       Verify that number of File Locks is zero. If there are file locks, investigate the cause to prevent the locks from occuring during backups.
-- Next, reboot the affected System out of hours and retry the VSSADMIN steps above as it may be a resource issue.
-- If a reboot fails to resolve the problem, 
VSS is not working correctly. 
       Symantec recommends contacting Microsoft Support at this point because NetBackup has not been involved in the testing as yet. 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


TEST #2) Create, list & delete a snapshot using BPFIS and VSS

(This test verifies that the NetBackup 'bpfis' process can communicate properly with Microsoft's Volume Shadow Service)

a) Create a VSS Snapshot using bpfis command

C:\>bpfis create -fim VSS -id test1 D:\

C:\VERITAS\NetBackup\online_util\fi_cntl>bpfis create -fim VSS -id test1 D:\
INF - BACKUP START 1568
INF - FIS_ID=test1
INF - REMAP FILE BACKUP D:\ USING \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13\ <file://\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13\> OPTIONS:ALT_PATH_PREFIX=C:\VERITAS\NetBackup\temp\_vrts_frzn_img_1568,FITYPE=MIRROR,MNTPOINT=D:\,FSTYPE=NTFS
INF - EXIT STATUS 0: the requested operation was successfully completed


b) List the Snapshot using VSSAdmin command

C:\>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Contents of shadow copy set ID: {7aaede74-9ff8-402b-9512-38d803654e84}
Contained 1 shadow copies at creation time: 5/15/2006 8:36:47 AM
Shadow Copy ID: {327cd784-54c2-4950-b639-30a6de190230}
Original Volume: (D:)\\?\Volume{33c37eea-d389-11da-a17d-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
Originating Machine: client01
Service Machine: client01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential


c) Check that the config file for the snapshot matches vssadmin output

C:\VERITAS\NetBackup\online_util\fi_cntl>more bpfis.fim.test1.0

FIS-VERSION=1.0
FIS-TIME=1147678605
FIS-OWNER=GENERIC
FIS-RHOST=LOCALHOST
FIS-IS_PRIMARY
FAILED_DELETES=0
STREAM_IN_CONTROL=unknown+1568+1
STREAM_NAME=unknown+1568+1
STREAM_ID=unknown+1568
STREAM_NUM=1
STREAM_PID=1568
STREAMS=1 1
PFI_BACKUP=0
NBU_CATALOG=0
ALT_CLIENT=0
POLICY_NAME=unknown
POLICY_TYPE=13
SCHED_NAME=unknown
SCHED_TYPE=unknown
FILELIST=FILENAME=D:\
FIM_NAME=VSS
FSDEV-type=0
FSDEV-fs_name=D:\
FSDEV-fs_type=NTFS
FSDEV-mnt_device=\Device\HarddiskVolume3
FSDEV-raw_device=
FSDEV-fi_mnt_device=
FSDEV-fi_raw_device=
FSDEV-fi_args=
FSDEV-mnt_flag=0
FSDEV-fi_flag=1
FSDEV-fm_flag=0
FSDEV-cs_flag=0
FSDEV-fi_fs_name=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13\
PATH_INFO=
PLUGIN=START
PLUGIN=END
FSDEV=NEXT
FIM_NAME_END

d) Test Snapshot deletion and clean up

C:\>bpfis delete -id test1 -copy 1
INF - BACKUP START 2392
INF - EXIT STATUS 0: the requested operation was successfully completed

Note: Copy 1 is added to the end of the command to designate the copy number of the snapshot.

e) Verify the snapshot removal with vssadmin

C:\>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

No items found that satisfy the query
.
 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IF RESULT = SUCCESS >>> BPFIS and VSS appear to be working correctly 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IF RESULT = FAILURE 

-- Check the Microsoft website for available hot-fixes for VSS
-- Verify that the system is not low on disk or memory resources. Often, a shortage of memory or disk resources will result in a failed VSS snapshot.
-- Confirm that sufficient Shadow Storage has been allocated to the volume
-- Last, rebooting the Server out of production hours and try the snapshot creation process immediately after reboot.

If the reboot resolves the problem, then a there may be an application memory leak and Microsoft should be engaged to debug the issue further.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



What To Gather When Contacting Symantec Support for Open File Backup Issue


When contacting Symantec Support for a Windows Open File Backup issue, please gather the following information for the call:

A) Client Logs  

Please enable the following logs on the client and set General Level = 2 in the Backup, Archive and Restore GUI. Then retry the Snapshot creation until failure.

cd C:\Program Files\Veritas\NetBackup\logs

mkdir bpbkar bpcd bpfis

B) NBSU Output

Open a Command Prompt and navigate to C:\Program Files\VERITAS\NetBackup\bin\support
Execute the nbsu.exe Support Tool. It will gather information about the client and save it to a Microsoft CAB file in the following path:

C:\Program Files\VERITAS\NetBackup\bin\support\output\nbsu\<hostname_nbu-role_date_time>\<hostname_nbu-role_date_time>.cab

C) MPS Reports output from the client

Download Microsoft Product Support's Reporting Tools from the Microsoft website and gather an output from the affected client.

Microsoft Product Support's Reporting Tools
http://www.microsoft.com/en-us/download/details.aspx?id=24745


 

 

 

 

 



Legacy ID



283377


Article URL http://www.symantec.com/docs/TECH47808


Terms of use for this information are found in Legal Notices