Tag Info

New answers tagged

0

Go to folder C:\Windows\inf. Copy 3 files setupapi.ev1, setupapi.ev2 and setupapi.ev3 from a working server if these files are not present. Restart Cryptographic and Volume Shadow Copy service. Now run the command "Vssadmin list writers" and you will be able to see System Writers.


0

There are various solutions to this which includes: Re-register VSS dll files Simply restart the server Run the command "Sc.exe sdset eventsystem D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)" Replace the folder ...


0

A backup strategy we had employed was every night the content databases were backed as well as the individual site collections. Our topology in that environment was only using about 5 content databases so this gave us flexibility if someone botched their site collection, we didn't need to restore the whole content db. It also allowed for an easy port to a ...


0

1st thing, having one site collection a web app is really bad idea. Because for each site collection you creating more web apps, which put more load on the SharePoint Farm, make the tough job to monitor, maintaining also too hard. Same thing with backup. Their is limit from MSFT that you have 10 app pools and 20 Web Apps per farm. What I would recommend, ...


1

Granular restore operations require the use of Powershell as no UI in Central Administrator exists. This cmdlet is used to restore sites, list, and libraries exported with “export site or list” option in central administrator or using export-spweb cmdlet. For Example: import-spweb -identity http://contosoweb/ -path \\appserver\bu\list.cmp Note: You ...


1

Thanks for your reply. I managed to sort this yesterday. I had to edit the versions of the database due to a Schema mismatch error. After that I was able to create a new Site Collection and add the restored database as the Content Database for that site.


0

We just had a similar problem that was caused by running out of space on the database server.


0

Yes, the native backup/restore features in SharePoint have never been the most robust. SharePoint 2013 is much better but still not 100% perfect. From your question, I am not sure if you are trying to "backup" a site collection from an unattached DB and restore or simply backup the DB itself. For the process you linked, you are only backing up a site ...



Top 50 recent answers are included