error 1 job status in netbackup

[-The_GodFather-]

Hi toall,

    We did a test backup for a file level backup, after the job finished it has code 1 status. Saying that some of the files are in use or busy, we might need those files in the future if we need to restore and recover the whole system and files. What should be done to back it up and so that we could have a complete full backup job???  The client is a file server only..Thanks... 

[Andy_Welburn · Accepted solution]

1. client OS?
2. files that are being skipped?
3. Is WOFB enabled for client? Could be your solution - Host Properties>Master Servers>master>Client Attributes>client>WOFB tab

((Ignore the red circles - these were for another post!!)

[Rajesh_s1]

What is your Netbackup Master server Version and what 's the Client OS and Netbackup version .

Fallow the below procedue and check , If the client is a  windows servers and this applicables for windows 2003 and above ,


Go to the Master server Host properties in GUI and then on the Client attributes add the windows client and click on the windows open file backup tab and Select the VSS option and close and then try the backup again .


Regards,
rajesh

[-The_GodFather-]

whoah! Thanks a lot. Will try this when I get back on site. Thanks again pal

[-The_GodFather-]

Master server is Windows Server 2003 64bit, and the client is Windows Server 2003 x86...What is WOFB defined???? Thanks..

[Andy_Welburn]

allows for backups to be taken of files that are currently open or in use (using snapshot technology).

From the Admin Guide:
"...
The Windows Open File Backup properties specify whether a client uses Windows Open File Backup. The properties also specify whether Volume Snapshot Provider or Volume Shadow Copy Service is used as the snapshot provider.
Snapshots are a point-in-time view of a source volume. NetBackup uses snapshots to access busy or active files during a backup job. Without a snapshot provider, active files are not accessible for backup.
..."

***EDIT***
Additional documentation that may (sorry, will!) explain it better:

About the Client Attributes properties

If you find that your client is not in the list for Client Attributes then I would add it (or any clients for that matter) as it is more than likely that it could be using VSP as its default snapshot provider. It has been proven in many instances that VSP can cause issues.

[Rajesh_s1]

Andy is correct . 

As it is a windows client you can enable VSS option for that client and verify the backup . 

Regards,
Rajesh

 

[Rick_Brown]

You will need to run "vssadmin list providers" on the windows client to make sure only 1 VSS provider is registered. We've have the Veritas & Microsoft VSS provider be registered and have it cause all kinds of odd problems with a Windows file system backup. We unregister the Veritas VSS provider when backing up a Windows system with great success.
To remove the Veritas VSS provider typ in a CLI:
"VxVSSProvider /unregserver"

[MOHAMED_PATEL]

Alternatively, add the files to the exclusion list - if these files are not nrequired -
Generally these are anti-virus apps, monitoring log lock files.

Please note that the status code 1 should not be ignored but rather investigated thoroughly prior to adding directories/files to the exclusion list.

Please monitor disk space usage when using WOFB - we have seen systems hang/freeze up when backups start.

[Andy_Welburn]

which was why I was hoping an example of the files would be shared - there is a list of files that can generally be excluded, I'll see if I can dig out a copy.

The disk space one is often overlooked - has caught us out a few times, not necessarily initially but certainly when a new system has 'grown' over a period of time.

[Andy_Welburn]

https://www-secure.symantec.com/connect/forums/windows-open-files

Referenced this whilst investigating our status 1 backups some time ago.