Data Backup and Recovery Discussions

Highlighted

Snapcreator 4.1P1: Error after successful execution of all SnapVault updates in configurations with multiple controllers

Hi,

We are having an issue in Snapcreator Version 4.1.P1 with configurations that use snapvault updates and where we have more 2 or more controllers as Snapvault source.

SC-Server:

--

SW-Version: 4.1P1

Java-Version: 1.6.0_24

OS-Version: CentOS 6.2

--

SC-Client:

--

SW-Version: 4.1P1

Java-Version: 1.7.0_55

OS-Version: RHEL 5.8

--

Snapvault settings from the configuration file

--

NTAP_SNAPVAULT_UPDATE=Y

SNAPVAULT_QTREE_INCLUDE=

NTAP_SNAPVAULT_NODELETE=N

NTAP_SNAPVAULT_RESTORE_WAIT=N

NTAP_SNAPVAULT_RETENTION_AGE=

NTAP_SNAPVAULT_SNAPSHOT=N

NTAP_SNAPVAULT_MAX_TRANSFER=

NTAP_SNAPVAULT_WAIT=1440

NTAP_SNAPVAULT_RETENTIONS=DAILY:8

SNAPVAULT_VOLUMES=siss-naa01b.spar.si:L_CLCACH_VG_CACHE_CEN,L_CLCACH_02;siss-naa01a.spar.si:L_CLCACH_01

--

The Error message we got in the logs are:

--

########## Running SnapVault update for source relationship siss-naa01a.spar.si:/vol/L_CLCACH_01/data2 ##########

[2014-04-29 05:22:42,157] INFO: SnapVault update for source relationship siss-naa01a.spar.si:/vol/S_SI_CACHECEN_01/data2 finished successfully

########## Running SnapVault update for source relationship siss-naa01b.spar.si:/vol/L_CLCACH_02/data1 ##########

########## Running SnapVault update for source relationship siss-naa01b.spar.si:/vol/L_CLCACH_VG_CACHE_CEN/vg_cache_cen ##########

[2014-04-29 07:32:35,896] INFO: SnapVault update for source relationship siss-naa01b.spar.si:/vol/S_SI_CACHECEN_01/data1 finished successfully

[2014-04-29 07:32:36,178] INFO: SnapVault update for source relationship siss-naa01b.spar.si:/vol/S_SI_CACHECEN_01/vg_cache_cen finished successfully

[2014-04-29 07:32:36,190] ERROR: Task: snapVault with config:CACHE@SICACHECEN failed

org.hibernate.service.UnknownServiceException: Unknown service requested [org.hibernate.service.jdbc.connections.spi.ConnectionProvider]

        at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:126) ~[hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.internal.AbstractSessionImpl.getJdbcConnectionAccess(AbstractSessionImpl.java:259) ~[hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75) ~[hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87) ~[hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249) ~[hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1558) ~[hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.EntityManagerImpl.getRawSession(EntityManagerImpl.java:121) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.EntityManagerImpl.getSession(EntityManagerImpl.java:97) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.AbstractEntityManagerImpl.setDefaultProperties(AbstractEntityManagerImpl.java:273) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.AbstractEntityManagerImpl.postInit(AbstractEntityManagerImpl.java:181) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.EntityManagerImpl.<init>(EntityManagerImpl.java:89) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:179) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at org.hibernate.ejb.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:174) ~[hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]

        at sun.reflect.GeneratedMethodAccessor435.invoke(Unknown Source) ~[na:na]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.6.0_24]

        at java.lang.reflect.Method.invoke(Method.java:616) ~[na:1.6.0_24]

        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.invokeProxyMethod(AbstractEntityManagerFactoryBean.java:376) ~[org.springframework.orm-3.1.2.RELEASE.jar:3.1.2.RELEASE]

        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean$ManagedEntityManagerFactoryInvocationHandler.invoke(AbstractEntityManagerFactoryBean.java:517) ~[org.springframework.orm-3.1.2.RELEASE.jar:3.1.2.RELEASE]

        at $Proxy47.createEntityManager(Unknown Source) ~[na:na]

        at com.netapp.snapcreator.repository.extended.impl.ExtendedRepositoryManagerImpl.get(ExtendedRepositoryManagerImpl.java:368) ~[catalog-impl.jar:na]

        at com.netapp.snapcreator.workflow.catalog.ExtendedRepositoryHelper.getSCCatalog(ExtendedRepositoryHelper.java:534) ~[workflow.jar:na]

        at com.netapp.snapcreator.workflow.catalog.ExtendedRepositoryHelper.updateSCCatalog(ExtendedRepositoryHelper.java:471) ~[workflow.jar:na]

        at com.netapp.snapcreator.workflow.task.ZAPITask.snapVaultUpdate(ZAPITask.java:1132) ~[workflow.jar:na]

        at com.netapp.snapcreator.workflow.task.SnapVaultTask.execute(SnapVaultTask.java:56) ~[workflow.jar:na]

        at com.netapp.snapcreator.workflow.impl.SCTaskCallableBlocking.call(SCTaskCallableBlocking.java:49) [workflow.jar:na]

        at com.netapp.snapcreator.workflow.impl.SCTaskCallableBlocking.call(SCTaskCallableBlocking.java:18) [workflow.jar:na]

        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [na:1.6.0_24]

        at java.util.concurrent.FutureTask.run(FutureTask.java:166) [na:1.6.0_24]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.6.0_24]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.6.0_24]

        at java.lang.Thread.run(Thread.java:679) [na:1.6.0_24]

--

Did someone else have a similar issue or even a workaround for this problem?

The issue does not occur on every run. I think, it may be a problem with transaction/session

handling, which behaviour has changed in hibernate 4.

I would appreciate any inputs

kr, Fidy

2 REPLIES 2
Highlighted

Re: Snapcreator 4.1P1: Error after successful execution of all SnapVault updates in configurations with multiple controllers

Update: currently this was a ressource allocation issues. The Follwing changes solved our Problem:

1. increase limits for open files on the SC Server

2. increase amount of physical RAM on the SC Server

Kr, Fidy

View solution in original post

Highlighted

Re: Snapcreator 4.1P1: Error after successful execution of all SnapVault updates in configurations with multiple controllers

Thank you for sharing the resolution - I had asked around and no one had seen this issue before.

Glad its working!

John

Check out the KB!
NetApp Insights To Action
All Community Forums