Enterprise Vault Clustered SQL database backups using EV agent

[d_0]

HI - We are trying to use the new Netbackup agent for EV , works for the EV data side but will not work for the SQL side which is hosted on a Windows server 2003 cluster

I did find  that only Windows Server 2008 clustered environments support Enterprise Vault SQL database backups accoriding to the install guide ,

Please confirm

thanks

[d_0]

error we get "snapshot preparation failed - Error attempting to find volumes to snap., status 130"

read http://seer.entsupport.symantec.com/docs/328434.htm but then we found

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/279048.pdf that states

Minimum support level Windows 2008 R1 for EV agent .

We are running EVault 7.5 (Server 2003 ) SQL hosted on Server 2003 64 bit cluster  , Netbackup 6.5 ,

Can i presume the error in backing up SQL  is due to the fact we are using Server 2003 cluster  ?

[d_0]

anybody ?

[Kenneth_Hansen]

The EV agent is supportet on Windows 2003 for EV 7.5 so the problem is not there.
Can you give us a better understanding on how your backup is set up?

EV installed on MS Cluster 2003, ok.
SQL server installed on different server/cluster?
How are your policy set up?

[d_0]

Hi - EV 7.5 server is on server 2003 (vm) , ev backup agent works fine

the issue is with the EV databases stored on SQL 2005 running on a windows 2003 cluster


I look after EV and requested the backup team setup the backups of EV using the new EV agent (so things are in read only for backups and this is set automatically)

The backup team came back and advised they were getting error on the SQL backup and release notes stated the SQL cluster server had to be server 2008 cluster ...cluster server 2003 not supported


Error for SQL backups "snapshot preparation failed - Error attempting to find volumes to snap., status 130"

If the SQL backups are supported on a server 2003 cluster i can request they have another look ,


thanks

[Kenneth_Hansen]

Ok, I must admit I never used th EV agent at all, but sins you SQL DB is not located on the EV server it self should you not use SQL agent to back up the DB's?. 
Would this mean that you are using 2 different policies to backup EV?
1 policy for the EV server, EV Agent puts EV in read only or backup mode.
1 policy for SQL backups?

Are you on NBU 6.5 or 7?

[Marianne · Accepted solution]

d_0, my interpretation of the Compatibility Guide is that the installation of Enterprise Vault is referred to on page 2, not SQL:

DB Agent	Notes/Links
Enterprise Vault	Minimum support level Windows 2008 R1.

Have you verified credentials as per the Resolution section of TN 328434?

If the Enterprise Vault Server is not installed on an SQL Server system, you must specify the Enterprise Vault user name credentials for that system. You can use the NetBackup Administration Console to specify the user name credentials.

Enterprise Vault user name credentials are specified in NetBackup client property: (NetBackup Administration Console -> Host Properties -> Client -> Specific  SQL client -> Windows clients -> Enterprise vault > user name and password)



The NBU for EV Guide also mensions the NBU Client Service logon. Check and verify on both SQL cluster nodes.
p.22:
To perform Enterprise Vault backups and restores the NetBackup Client Service must have sufficient privileges for read and write access on the file system. You must configure the log on account for the NetBackup Client Service on every system where it (is) required.

[MillerMan]

I have

EV Clustered 2 nodes 2008 64bit SP2
EV 8.0 SP3
SQL Clustered 2 nodes 2003 64bit SP2
SQL 2005

Below is my error message.  Appeared to be similar, was there any fixes here?

snapshot preparation failed - Error attempting to find volumes to snap., status 130

4/15/2010 10:59:11 AM - requesting resource File-Disk-Pool
4/15/2010 10:59:11 AM - requesting resource usflbua0.NBU_CLIENT.MAXJOBS.usfldbe4
4/15/2010 10:59:11 AM - requesting resource usflbua0.NBU_POLICY.MAXJOBS.WIN_EVA1_VAULT
4/15/2010 10:59:11 AM - granted resource usflbua0.NBU_CLIENT.MAXJOBS.usfldbe4
4/15/2010 10:59:11 AM - granted resource usflbua0.NBU_POLICY.MAXJOBS.WIN_EVA1_VAULT
4/15/2010 10:59:11 AM - granted resource MediaID=@aaaak;Path=F:\File-Disk-Pool;MediaServer=usflbua1
4/15/2010 10:59:11 AM - granted resource File-Disk-Pool
4/15/2010 10:59:13 AM - estimated 0 kbytes needed
4/15/2010 10:59:13 AM - begin Parent Job
4/15/2010 10:59:13 AM - begin Enterprise Vault Snapshot, Step By Condition
Status 0
4/15/2010 10:59:13 AM - end Enterprise Vault Snapshot, Step By Condition; elapsed time: 00:00:00
4/15/2010 10:59:13 AM - begin Enterprise Vault Snapshot, Read File List
Status 0
4/15/2010 10:59:13 AM - end Enterprise Vault Snapshot, Read File List; elapsed time: 00:00:00
4/15/2010 10:59:13 AM - begin Enterprise Vault Snapshot, Create Snapshot
4/15/2010 10:59:13 AM - started
4/15/2010 10:59:15 AM - started process bpbrm (2104)
4/15/2010 10:59:21 AM - begin Create Snapshot
4/15/2010 10:59:33 AM - Critical bpbrm(pid=2104) from client usfldbe4: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130
4/15/2010 10:59:33 AM - Critical bpbrm(pid=2104) from client usfldbe4: FTL - snapshot preparation failed, status 130  
4/15/2010 10:59:41 AM - end Create Snapshot; elapsed time: 00:00:20
4/15/2010 10:59:43 AM - end writing
Status 130
4/15/2010 10:59:43 AM - end Enterprise Vault Snapshot, Create Snapshot; elapsed time: 00:00:30
4/15/2010 10:59:43 AM - begin Enterprise Vault Snapshot, Stop On Error
Status 0
4/15/2010 10:59:43 AM - end Enterprise Vault Snapshot, Stop On Error; elapsed time: 00:00:00
4/15/2010 10:59:43 AM - begin Enterprise Vault Snapshot, Delete Snapshot On Exit
4/15/2010 10:59:43 AM - begin Enterprise Vault Snapshot, Delete Snapshot On Exit
4/15/2010 10:59:45 AM - started process bpbrm (6360)
4/15/2010 10:59:54 AM - end writing
Status 0
4/15/2010 10:59:54 AM - end Enterprise Vault Snapshot, Delete Snapshot On Exit; elapsed time: 00:00:11
Status 130
4/15/2010 10:59:54 AM - end Enterprise Vault Snapshot, Delete Snapshot On Exit; elapsed time: 00:00:11
system error occurred(130)

[dmc123]

Were you able to ever resolve this?  I have the same error message and can't figure out the cause.  Regular backups work with out issue, but the Evaul Agent reports the 130 error on the database server.  I'm running same enviro (2008 Evault server with SQL Cluster on 2003 x64).

[Marianne]

Has anyone tried the Resolution section of TN http://seer.entsupport.symantec.com/docs/328434.htm yet??