Windows Server 2012 Backup stops working on Virtual Machine with SharePoint 2013 after SQL Server 2012 is installed.
I believe that there is no problem with SQL SERVER. Please see this link:
Saeid Hasani, sqldevelop.wordpress.com
Download Books Online for SQL Server 2012
You need to run the following command to be able to backup SharePoint:
stsadm -o registerwsswriter
If you are using SharePoint, the best way to get a backup of SharePoint without losing data is to perform the following procedure:
- Edited by Alberto MorilloMVP, Moderator Friday, September 27, 2013 1:02 AM
Thank you for your reply.
I followed the instructions from the link you provided, but I am still getting the original error I described in my initial post and my Event Log does not contain the entry the link says to look for when the system writer is not in the list returned from the 'vssadmin list writers' command.
The reason why I posted to the 'SQL Server Setup & Upgrade' forum is because this error started immediately after I installed SQL Server 2012 on one of my Virtual Machines configured with Windows Server 2012 and SharePoint 2013.
SQL Server 2012, by itself, is probably not the sole reason for this error ...
So, I thought is was important in my initial post to mention I am running Windows Server 2012 and that SharePoint 2013 is also installed on this Virtual Machine. The Windows Server Backup was running daily without any errors on this VM before specifically installing SQL Server 2012.
Therefore, it appears there is something caused by the combination of at least 2 specific products ... 1) SharePoint 2013 and 2) SQL Server 2012 ... The combination of these 2 products seem to be causing the error.
- Edited by Dean R. Henderson Friday, September 27, 2013 4:56 AM
I would check the logs as shown here
and then go on to fix VSS using one of these strategies:
It's possible that the VM is vetoing the backup. Have a look at all Event Viewer logs (App & Sys) on host as well as VMs.
Octavio, Tech Support for http://backupchain.com/