catalog backup finishes with error 35

[Zahid_Haseeb]

8/10/2009 3:49:23 PM - Error bpbackupdb(pid=8332) cannot make directory E:\Catalog for bpbackupdb, No such file or directory 

8/10/2009 3:49:23 PM - end Catalog Backup; elapsed time: 00:00:00

cannot make required directory(35)

8/10/2009 3:49:23 PM - Error bpbackupdb(pid=8332) Offline catalog backup to path E:\Catalog FAILED    

[Taqadus_Rehman]

 There could be different reason for error 35 such as

? A process does not have permission to create the directory
? The path to the directory is not valid
? An IO error occurs
? There was no space available on the device containing the directory 

What you can do is:

1. Check the NetBackup All Log Entries report to determine which directory could not 

be created and why it could not be created. In particular, check for a full disk partition. 

2. Check the permissions on the parent directory and verify that NetBackup services are 

started with a “Logon as” account that has permission to create the directory. 

3. For detailed troubleshooting information, create a debug log directory for the process 

that returned this status code, retry the operation, and check the resulting debug log. 

[Deepak_W]

I have not came across this error with offline catalog backup.

I came across one TN which says "extraspace in the mentioned path, permission to the specified folder for service account"  can retrurn with status code 35.

Check the below mentioned link for further reading.

http://seer.entsupport.symantec.com/docs/269631.htm

[rj_nbu]

What exactly is E:\Catalog ?
What is the version of netbackup ? 6.x or 5.x ?

[Zahid_Haseeb]

i dont know why it is going to E:\Catalog?????????????????????????

i assign another DSU but again it shows the same error with the E:\Catalog !!!!!!!!...............

i created a fresh brand new policy with different DSU and took the backup and it works fine....Why !!!!!   :(

[Marianne · Accepted solution]

Only HOT catalog policy is configured via a policy.

The error message above shows that an OFFLINE backup was attempted.

Check your offline catalog backup configuration: