Community
Showing results for 
Search instead for 
Do you mean 
Reply

Back up Clone casues many SQL Errors

Copper Contributor
Posts: 157
Country: United States

Back up Clone casues many SQL Errors

I do a weekly backup by cloning my whole hard drive.  For some reason, I receive about 60 various SQL errors in my event log every time I clone the drive.  If I stop the ACT SQL service before I do the clone these errors do not appear in the event log.

 

Any idea why the Act SQL service causes so many errors during the clone process?

 

 

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Back up Clone casues many SQL Errors

SQL databases are opened and locked by the service as soon as Windows boots (before you even login)

 

So cloning (unless the clone app understands SQL) won't work.

 

You might find this useful:

http://blog.glcomputing.com.au/2009/09/automating-backups-for-act-by-sage.html

New Member
Posts: 1
Country: USA

Re: Back up Clone casues many SQL Errors

Instead of cloning use something simple like SQLBackupAndFTP

Copper Contributor
Posts: 157
Country: United States

Re: Back up Clone casues many SQL Errors

I do not believe SQL backup will clone the whole hard drive.  I could be wrong though.

Copper Contributor
Posts: 157
Country: United States

Re: Back up Clone casues many SQL Errors

It looks like the MSSQL$ACT7 events I am getting are being generated by a failure in the VSS writer responsible for preparing the ACT! database(s) for the snapshot. The events get logged whenever I try to clone using the Volume Shadow Copy service to create a volume snapshot that includes system state data; this causes the volume shadow copy service to contact each of the volume shadow copy writers (e.g., SQL Server Writer, etc.) to prepare their data for the snapshot.

 

Is there something wrong with the Act data base that won't let the copy proceed without errors when cloning my entire drive?   

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Back up Clone casues many SQL Errors

It's the cloning software not able to handle an open/locked SQL file

Even most SQL backup tools usually need the sa password, with is only an option with ACT! Premium

Your best bet it to see if the cloning software can run a command before and after it's operation... then you can have it stop the SQL service, perform the clone and restart the service
Copper Contributor
Posts: 157
Country: United States

Re: Back up Clone causes many SQL Errors

These are the errors that show up in the event viewer.  Future System Solutions techs say the cause is the Act Data Base interfering or causing an error during the VSS snapshot.  Can this be fixed or addressed?

 

Error 8/15/2010 7:27:44 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:44 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:44 AM MSSQL$ACT7 3414 (2)
Error 8/15/2010 7:27:44 AM MSSQL$ACT7 824 (2)
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Warning 8/15/2010 7:27:43 AM VSS 8229 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 18210 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 18210 (2)
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 18210 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 18210 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLVDI 1 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM SQLWRITER 24583 None
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 3041 (6)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 17207 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 17207 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 17204 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 17207 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 17204 (2)
Error 8/15/2010 7:27:43 AM MSSQL$ACT7 17207 (2)

Copper Contributor
Posts: 157
Country: United States

Re: Back up Clone causes many SQL Errors

 

Apparently, ACT is not providing the necessary permissions for the System account to enable the VSS SQL writer to prepare the database for replication. What is the rationale for this?

 

I understand the corporate version does not have this limitation and allows a backup clone. 

 

One suggestion I found on another thread was to: 

 

"change the Logon account for VSS Service to a service account that has rights to SQL Server, such as a backup account to avoid this issue also, without compromising access restrictions"

 

Unfortunately, I'm not exactly sure what this means or if this suggestion is on the right track.