Tag Info

New answers tagged

1

It would throw errors at you if the web part is not deployed as a feature on the destination server. You need to package the web part via the Publish option, then use powershell to deploy the feature on the destination server and any errors present will no longer appear.


0

As you mentioned you need a test farm to increase your expertise. Big question is what you want, just explore the more features of sharepoint or want to do some development with exploring the Enterprise features. If you just want to learn advance feature then no need of test web app, simple create another web app and create the site collection and have ...


1

priyanka is correct, a site collection would create a new content database on the server which would have conflicting ID's using backup and restore. You would rather need to use export and import: Export-SPWeb http://technet.microsoft.com/en-us/library/ff607895(v=office.15).aspx Import-SPWeb ...


3

You try to restore a site collection backup to the same content database from which the site backup was taken , there will be a GUID conflict. GUID for a site collection is unique and it gets stored along with the site collection backup.


0

You cannot restore a site collection from SP2 farm to Sp1. You can restore from Sp1 to Sp2 farm only if you take the Content DB backup not sharepoint site collection backup. In your current scenario, Only thing is Update your farm to SP2 level and then restore the site collection, Otherwise it will give you version mismatch error.


3

Couple of things to check: Make Sure Farm admin accounts having the write permission on the path. try to use different path Make sure the site is not locked check the ULS / Application Logs for clue. Also try to take the backup from powershell to isolate the issue. Backup-SPSite -Identity <SiteCollectionGUIDorURL> -Path <BackupFile> Some IIS ...


1

Okay, I've already accepted the answer from the fellow who answered me when I asked the question. But I want to add my own answer here, too, to report my experience. No, you don't have to stop Sharepoint. I took a Windows Server (2008) backup with Sharepoint running using the "full" "bare metal" option. I put the backup on a network folder. Then I ...


1

I dont think you need to stop the any services on the server. We took the backup of our OS & Drives every day. We never stop our SharePoint as our it is working 24/7. Sometimes(very rare) performance goes down other wise no issue.


0

Another solution is there. If you are only concern about single document library, then you can export it or you can save it as template(with Content) and download it in you as your backup file.


0

There are many 3rd party tools available in the market which help you for item level recovery with less efforts. I am not big fan of DPM we tried it but rejected. I think DocAve get a lot of market reputation for the backup&recovery tool. For me backup is not issue but i want how quickly we restore the a file. here are the list of available tools, you ...


1

That is certainly one option. Another option is to do individual site collection backups as well as full content db backups. This way, you can restore a single site collection to a separate farm, grab the file, then delete the site collection.


1

There is the out-of-box solution to provide backup restore on app webs. Apps are separated from SharePoint, their backup and restore paths are also separate, i.e. you will not manage them from the B/R utilities that SharePoint provides. In most cases, you treat your entire SharePoint environment as a single solution, and so piecemeal restoration is not ...


2

Yes, You can move it. But one thing you keep in mind if you hard coded the URL in your sites then those will cause the issue and you have to manually adjust it. Couple of options to move it. 1) Moving using the PowerShell tool. Move-Spsite Move-SPSite http://servername.com/sites/sitename -DestinationDatabase ContentDb2 Only catch in this case, you ...


0

I did this a while back, and it's a little fuzzy, but I think your web application has to have the URL "http://abd.spdev", whereas I see you're trying to restore it to the Port 80 web application. Restore it as a site collection to the Port 80; if it's an empty web application, restore it as "" or if there's already something there, try "". If you want to ...


0

Activate daily backups for all selected users with office 365 domain. Backup for office 365 you gain all emails, daily automated backups and more. Easily export user data for local archive to recover without overwriting existing information data. http://www.cloudally.com/Blog/2013/03/12/office-365-do-we-need-to-backup-our-own-data/



Top 50 recent answers are included