Unsolved

This post is more than 5 years old

2.2K Posts

797

September 4th, 2007 09:00

RM/SE Clone Sync Failure

I am running RM/SE 3.1.0.4 and have a nightly job that clones a SQL Server 2000 database. Been running fine for months and then on Sunday morning the following errors appeared in the RM/SE job window. The sync completed, but during the final process of freezing the database using the SQL VDI to get a consistent clone of the data the process failed:

024024 failed to prepare the virtual device interface. check the sql server error and vdi logs for more information.

026003 application agent operation freeze has failed with an error. no additional information is available.

Each successive retry of the replication fails with the following errors:
000033 function sweclarsyncclone failed

000034 function dcclarsyncclone failed with an error as follows: error from: dcclarsyncclone


When the first failure occurred the only errors on the source host (Windows Server 2003 x64, SP1) I could find were in the application log, and they were SQL VDI errors:
sql vdi error 1
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 9/2/2007
Time: 3:29:49 AM
User: N/A
Computer: SQL1-N1
Description:
SQLVDI: Loc=CVDS::Close. Desc=Open devices!. ErrorCode=(0). Process=1232. Thread=8100. Client. Instance=sql1. VD=Global\ECCRM_BACKUP_FILE_"DBNAME"_3366181489_SQLVDIMemoryName_0


... And there were more like this.


Any ideas? I have looked through the knowledge base but all the articles I found that contained these errors did not fit the situation.

Thanks,
Aran

2.2K Posts

September 4th, 2007 10:00

Update, there was an error in the SQL log when the first failure occurred:

BACKUP failed to complete the command BACKUP DATABASE ""DATABASE_NAME"" TO VIRTUAL_DEVICE='ECCRM_BACKUP_FILE_"DATABASE_NAME"3366181489' WITH SNAPSHOT

I opened up a support case as well and will post the solution if they are able to resolve it. The clones feed our development environment so am trying all avenues for an answer.

2.2K Posts

September 5th, 2007 11:00

I actually found the answer in the knowledge base after searching some more, emc163367 has the details.
The first failure of the clone was caused by an issue with the sql cluster; there was a process running that did not allow the sql vdi snapshot to be taken on the data. So the synchronization was complete but the sql consistent snap of the data could not be executed. The successive failures of the clone job were due to the fact that after the first failure the clones were not fractured. So the successive attempts to sync the clones failed because the clone luns were already syncing and could not be used in additional clone jobs.
Once I fractured the clones manually through navisphere the clone job in RMSE ran without error.

0 events found

No Events found!

Top