Backup of sharepoints?

I have a Mac mini with Snow Leopard Server which I use for sharing files between several Mac clients with Snow Leopard. I have a sharepoint named /Volumes/MiniHD1/Shared Items/Public.
So here is my question: *What is the best way to back up the shared data?*
My first idea was to turn on Time Machine on the server. When I wanted to restore something I ran into problems. First, I could not do it from a client Mac easily. I had to log in to the server and start Time Machine there. Then I realized I did not have permissions to all subfolders because on the server I can only log in as a local admin user.
Now I have my doubts if using Time Machine on the server for backing up sharepoints is a good idea.
*How do you do it? What is best practice?*
Any help is greatly appreciated.

I just found the following in the Advanced Server Administration:
+Time Machine is a limited tool for data backup and restoration of Mac OS X Server v10.6. It can back up some server configuration settings and the service state. Time Machine does not back up service data. For example, Time Machine doesn’t back up user and group directory records, email, DNS records, Address Book shared groups, iCal Server calendars, and so forth. It only saves the settings made in Server Preferences and Server Admin, and whether a service is on or off.+
So it seems it is not the tool to backup file sharing data. However, the document seems not to answer my question. It only gives very general remarks about backup and restoration.

Similar Messages

What is the order of restoring backups in sharepoint 2010

Hi
production form has
2 web application ,custom solutions and service applications configured(user profile,serarch)
here what is the order of restoring backups in my newly created test form
adil

Hi
in my production environment when i create new web application how
the custom solution included in _layouts folder?
this is the information from systemsettings>farmsolutions
Name: xyz.scan.wsp
Type: Core Solution
Contains Web Application Resource: Yes
Contains Global Assembly: Yes
Contains Code Access Security Policy: No
Deployment Server Type: Front-end Web server
Deployment Status: Deployed
Deployed To: http://spwf01:81/;
http://spwf01:83/; http://spwf01/;
http://spwf01:84/; http://spwf01:82/
here there is no webapplication with port 85 , but when i create new web application with port 85
this solution exists in _layouts folder
adil

Restore a PDF file from SharePoint Content DB backup

Hi Techys,
Could you please help me for below scenario,
I have only Content DB backup of SharePoint 2010, Now i want to restore a single file(madhu_Profile.docx) from that Backup. But, How?
Let me know if you need any further information regarding the same.
Many Thanks,
Madhu

You can also attach an unattached content database and restore it from there, if the db is already within a SQL instance.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Sharepoint 2010 farm full backup

I do full backup to sharepoint 2010 farm, in logs write
Estimated disk space required: 94,251 MB.
Backup
Backup Method: Full
Top Component:
Configuration only: False
Progress updated: 5
Backup threads created: 10
at the start of the backup is the approximate size of
94,251 MB (about 92.05 GB), and in the end
all backup files weigh
19 GB. At the start and at the end of
all sizes backup files
do not match. Why?

When you take backup, it require double size of the backup which is actually there, after this the compression happens.
Also check below:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/f93e5daf-575d-4565-8d25-9d74a0b7906a/backup-estimated-disk-space-required

How to backup SharePoint Document Library

I have SharePoint 2010 And I have used it as document management system, I wandered if make backup to SharePoint database is enough to backup our documents in another word Documents is stored in SharePoint database, please advise.

You're asking a good question, but the problem is that its one that can take a
great deal of time to answer in depth. I'll try to cover the broad strokes here...
Yes, backing up your SharePoint content databases will technically create a backup of the documents that you are uploading into the SharePoint sites stored in those content databases.
BUT , there's a lot more to consider than just that. The bullet points below cover some of the big ones off the top of my head:
SharePoint stores documents in its content databases using the Binary Large Object (BLOB) data type. It is not possible to directly extract a document from a SharePoint database without going through SharePoint, at least not in a manner supported by MS.
This means that you must re-attach the restored content database to a live SharePoint farm in order to get to those documents again once you've restored the database from backup.
And that means that you'll have to rebuild an entire farm and reattach that database to it, not something that can usually be done quickly.
In order to reattach that database backup to a SharePoint farm, your new farm must be patched to at least the same version as the farm where the content database originated. So you have to be careful to track the version of SharePoint you used in the farm
and rebuild to that level.
If the site collections in that content database used any custom code, site templates, web parts, etc, you must install those into your new farm, or there's a good chance your site's won't work and you won't be able to access your content.
You'll have to re-do all of the configuration settings you customized in your new farm as well, if you want it to be able to replace the functionality of your current farm. SharePoint 2010 does introduce configuration database backups, but they're not a
complete solution (they don't include ALL of the configuration data for your farm).
Changes to the configuration of your sites in IIS, files in the SharePoint root directories, Active Directory, etc, are not captured in SQL Server or SharePoint backups. You'll need to back them up yourself.
I will qualify my comments by saying that I'm talking about this stuff from an overall Disaster Recovery perspective, not from a targeted approach to protect some specific highly important documents you're putting into SharePoint. But this is all stuff you
have to consider if you're going to use SQL Server to protect those documents.
I would recommend also taking a look at SharePoint's ability to save a document library or list as a template with content included, this can allow end users to save content on their own through the SharePoint site's UI and protect it. Or, you can use the
Export-SPWeb PowerShell CMDLET (http://technet.microsoft.com/en-us/library/ee428301.aspx ) to script out the protection of that document library as well.
Does that all make sense?
John
MCTS: WSS v3, MOSS 2007, and SCOM 2007
MCITP: Enterprise Project Management with Project Server 2007
Now Available on Amazon - The SharePoint 2010 Disaster Recovery Guide. Also available -
The SharePoint 2007 Disaster Recovery Guide.
My blog: My Central Admin.

Fatal error when trying to backup SharePoint server (Failed to set request to pause search application)

I have powershell script that is used to backup SharePoint server. It was working correctly until last week. I found this error message indicate that search application cannot be paused. I don't know what happen and what should I do to solve this issue.
Please help me find solution for this.
[20/1/2557 18:53:53] FatalError: Object Search Service Application failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
InvalidOperationException: Failed to set request to pause search application

Hi,
According to your post, my understanding is that you got an error when you backup your SharePoint Server.
You can do the steps below, then check whether it works.
Look for any One-time timer job for Backup/Restore and delete it (From Central Administration > Monitoring > Review Job Definitions)
Clear the timer cache following the below link:
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
Run the below command from the SharePoint Management Shell:
$ssa = Get-SPEnterpriseSearchServiceApplication –Identity <SearchServiceApplicationName>
Suspend-SPEnterpriseSearchServiceApplication -Identity $ssa
Once the above steps are completed successfully start the full farm backup from the Central Administration > Backup and Restore > Farm Backup
Once backup is completed run the below command to resume the SSA
$ssa = Get-SPEnterpriseSearchServiceApplication –Identity <SearchServiceApplicationName>
Resume-SPEnterpriseSearchServiceApplication -Identity $ssa
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Sharepoint full farm backup generates sql logs for search application differential backups

We are running full farm backups for sharepoint. Backup completes normally but SQL logs are generated for differential backups for search service application.
it says something like:
Database differential changes were backed up: database: search_serv.......
Thanks,
Basit

This can happen for a few reasons, such as is disk contention or network issues. Are you backing up to a shared directory on the SQL Server? If not, try that.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint backup frequency?

Does DPM 2012 support 15 minute incremental backups of SharePoint when backing up as a SP farm or only Express Full? When creating the protection group there is only the option for Express Full. The SharePoint SQL DB recovery models are set to
FULL. Would expect it to do 15 minute incremental as this is what we can do with SQL.
Many thanks,
Marcus

Hi,
The backup frequency depends on your individual SLA needs - if it's a really active farm with lots of changes throughout the day, you may want to take two or more backups. The default catalog job runs 3 hours after the express full. In a large
farm - that catalog job may take several hours to complete, so you don't want to overlap backups if possible.
Worst case is you added an item to the farm and lost it (meaning it was deleted) within three hours of your last express full, under that condition it would not be listed for recovery. If it was not deleted, you can always run a manual catalog to make it show
up, or more likely just recovery it from the sharepoint recycle bin.
EXAMPLE: The powershell script below sets the incremental catalog to run at 30 minutes after the express full recovery point for that farm.
$pg = Get-protectiongroup -dpmservername (&hostname)
$pg
$mpg = Get-ModifiableProtectionGroup $pg[X] (Where X is zero based number of the returned PG names listed – select the sharepoint PG)
Set-ProtectionJobStartTime –ProtectionGroup $mpg –CatalogOffset 30
Set-Protectiongroup $mpg
After this runs, future catalog jobs will be scheduled to run after 30 minutes of every express full backup.
DPM does not natively protect CRM - therefor the writer is not used and DPM can you only protect the SQL databases. You can see what files CRM writer is responsible for and make sure those files are included in your backups. Run Diskshadow.exe
from administrative command prompt, then "list writers" - search the output for the CRM writer and see what files are included.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Getting my Sharepoint data back

Hi,
I am still working on trying to get Sharepoint back running.
I had a SQL2005 crash when a disk got full and have since been able to move the data files and get SQL to recognize the files.
The SQL databases are STS_config and STS_hca4_1 but I am still having an issue with the user/logins and owners of these files.
In Central Administration page - under the Virtual Server List it shows
Name: SharePoint Central Administration     Url: http://hca4:28882/    Version: Not Installed      Extend
If I Click on Sharepoint Central Administration, after a long time, I get the Extend Virtual Server page.
If I Click Extend and create a content Database I get this error:
Cannot connect to the configuration database. For tips on troubleshooting this error, search for article 823287 in the Microsoft Knowledge Base at http://support.microsoft.com.
I am at a loss on how to get things re-linked together and also how to start from scratch.   The SharePoint Server is integrated into the Server2003 Small Biz server.
Please help me find my way and get this back running.
Thanks,
Scott

This is a Video I prepared to answer this question .. I hope
it is useful :
https://www.youtube.com/watch?v=K_G_NADFfHE
In This Video , I take you through Step by Step instructions
answering two questions :
1-What should you backup (From SharePoint , SQL Server , IIS)
2-What should you do in every Disaster data loss.
I give 13 Disasters of Data loss and step by step what should
you do.
I also show you how to automate your backup process and schedule  it

My Sharepoint data is missing from pages. How do I get it back?

Hello All:
I have been putting together our firm Sharepoint site and nearly completed it when all of the sudden my site data disapears.
On any article page that was created, the text and images are simply gone. If I go in and edit the page, all of my applets are gone and I cannot add or edit anything for that page. Any page where a web part is seems to be fine.
Before this all happened, I added a data view web part using SP Designer that connected to our database and pulled down user information. I also may have edited one of the main default control pages on accident while trying to accomplish it. I have verified that the files are physically there on the server and tried doing a restore from with Central Administrator but no luck.
Any clue what I did wrong. At this point, it looks like I will be rebuilding the entire farm from scratch unless there is a simple answer. I have no server backups to restore to.
ADDITION:
This is a publishing site with Office SharePoint Server Publishing active.
I also reverted everything back to the way it was before adding the data
view but the problem persists.
These were the instructions I was following before everything went haywire:
http://sharepointblog.michaelrperry.com/2008/06/how-to-connect-to-sql-2005-database_12.html
Now that I think about it, I may have messed up the Master Page (or the file
named PageFromDocLayout.aspx, if they are the same thing)
Anyways, hope that gives a little more insight.
Thanks, Chris

This is a Video I prepared to answer this question .. I hope
it is useful :
https://www.youtube.com/watch?v=K_G_NADFfHE
In This Video , I take you through Step by Step instructions
answering two questions :
1-What should you backup (From SharePoint , SQL Server , IIS)
2-What should you do in every Disaster data loss.
I give 13 Disasters of Data loss and step by step what should
you do.
I also show you how to automate your backup process and schedule it

How to Restore a SharePoint 2010 Sitecollection from Prod to Pre-Prod?

How to Restore a SharePoint 2010 Sitecollection from Prod to Pre-Prod?
The patching levels are different from each environment.
Tools installation is same.
Note: Suggest me to restore a site from site template without content.
If you have any better approach please tell me.
Many Thanks,
Madhu

Hi Madhu,
It isn't possible (out of the box) to restore a production to a development site without the content.
If you're happy with restoring the content, it's quite easy to backup a SharePoint farm and then restore only a site (form the farm backup) to a development farm.
Have a look at these forum posts for more info (in the first link, I gave an example script):
http://social.technet.microsoft.com/Forums/sharepoint/en-US/f5e8165e-2fe1-4ca9-87bd-b0f45b1e0091/process-on-creating-a-uat-server-from-live?forum=sharepointadminprevious
http://social.technet.microsoft.com/Forums/sharepoint/en-US/8092c04f-ae2c-4cfa-8933-e7ecb3138fdf/how-to-backup-and-restore-a-site-along-with-its-corresponding-user-profile-data?forum=sharepointgeneralprevious
Regards, Matthew
MCPD | MCITP
My Blog
View
Matthew Yarlett's profile
See my webpart on the TechNet Gallery that allows administrative users to upload, crop and format user profile photos. Check it out here:
Upload and Crop User Profile Photos

DPm 2012 r2 problem after moving Sharepoint 2013 to a differnt SQL using another alias

Hi,
I have resently installed DPM 2012 r2 and I want to backup my Sharepoint 2013 farm. I can install the client on Sharepoint server and the SQL server. This is a new protection and I have earlier moved the Sharepoint 2013 farm to a different SQL server
not with the same name using the SQL alias method.
When I try to create a Sharepoint backup I get the old SQL server name and error to check the SQL wss is running. The wss is running and the DPM user is local admin and sysadmin og the new SQL server. I added in hosts the old SQL server name
pointing to the new sql server ip address.
I need to know if this is doable in DPM or must I do something else?
thanks.
Erró

Here is the information you needed.
* WRITER "SharePoint Services Writer"
- Writer ID = {da452614-4858-5e53-a512-38aab25c61ad}
- Writer instance ID = {b8787079-eacd-4ced-9c7d-1e9aa5ac240a}
- Supports restore events = TRUE
- Writer restore conditions = VSS_WRE_ALWAYS
- Restore method = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
- Requires reboot after restore = FALSE
- Excluded files:
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Config"
- Name: AVA_SP2013_Config
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Config
- Caption: Configuration Database AVA_SP2013_Config
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Config"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_State_Svc"
- Name: AVA_SP2013_State_Svc
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_State_Svc
- Caption: Generic Database AVA_SP2013_State_Svc
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_State_Svc"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Heimar"
- Name: AVA_SP2013_Content_Heimar
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Heimar
- Caption: Content Database AVA_SP2013_Content_Heimar
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Heimar"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Wiki"
- Name: AVA_SP2013_Content_Wiki
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Wiki
- Caption: Content Database AVA_SP2013_Content_Wiki
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Wiki"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_ActiveProjects"
- Name: AVA_SP2013_Content_ActiveProjects
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_ActiveProjects
- Caption: Content Database AVA_SP2013_Content_ActiveProjects
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_ActiveProjects"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite"
- Name: AVA_SP2013_Content_Mysite
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite
- Caption: Content Database AVA_SP2013_Content_Mysite
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite1"
- Name: AVA_SP2013_Content_Mysite1
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite1
- Caption: Content Database AVA_SP2013_Content_Mysite1
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite1"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite2"
- Name: AVA_SP2013_Content_Mysite2
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite2
- Caption: Content Database AVA_SP2013_Content_Mysite2
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite2"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite3"
- Name: AVA_SP2013_Content_Mysite3
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite3
- Caption: Content Database AVA_SP2013_Content_Mysite3
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite3"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite4"
- Name: AVA_SP2013_Content_Mysite4
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite4
- Caption: Content Database AVA_SP2013_Content_Mysite4
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite4"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content"
- Name: AVA_SP2013_SharePoint_Admin_Content
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content
- Caption: Content Database AVA_SP2013_SharePoint_Admin_Content
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB"
- Name: AVA_SP2013_Secure_Store_Service_DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB
- Caption: Generic Database AVA_SP2013_Secure_Store_Service_DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_PerformancePoint Service Application"
- Name: AVA_SP2013_PerformancePoint Service Application
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_PerformancePoint Service Application
- Caption: Generic Database AVA_SP2013_PerformancePoint Service Application
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_PerformancePoint Service Application"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Managed Metadata Service"
- Name: AVA_SP2013_Managed Metadata Service
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Managed Metadata Service
- Caption: Generic Database AVA_SP2013_Managed Metadata Service
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Managed Metadata Service"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Word_Automation"
- Name: AVA_SP2013_Word_Automation
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Word_Automation
- Caption: Generic Database AVA_SP2013_Word_Automation
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Word_Automation"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Profile DB"
- Name: AVA_SP2013_Profile DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Profile DB
- Caption: Generic Database AVA_SP2013_Profile DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Profile DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\Sync DB1"
- Name: Sync DB1
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\Sync DB1
- Caption: Generic Database Sync DB1
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\Sync DB1"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Social DB"
- Name: AVA_SP2013_Social DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Social DB
- Caption: Generic Database AVA_SP2013_Social DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Social DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_BDC_Service_DB"
- Name: AVA_SP2013_BDC_Service_DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_BDC_Service_DB
- Caption: Generic Database AVA_SP2013_BDC_Service_DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_BDC_Service_DB"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf"
- Name: Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf
- Caption: OSearch Administration Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e"
- Name: Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e
- Caption: OSearch Crawl Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9"
- Name: Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9
- Caption: OSearch Analytics Reporting Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50"
- Name: Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50
- Caption: OSearch Links Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea"
- Name: IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Caption: OSearch15 Content Index Catalog_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{0ff1ce15-0201-0000-0000-000000000000}:\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea"
Erró

Change Sql server of sharepoint 2013

I have instlled sharepoint 2013 with sql express edition. Now the issue is rising that my database grows up more than 10gb. Now i want to move it to sql express edition. Suggest me the best way to do?
I have database backup. Sharepoint site backup and stuff required to do.
Thanks in advance.

If you still have enough disk space, you can upgrade your Express Edition to Standard Edition on the same server and install the appropriate SQL Server updates. If you want to move the databases to a different server running SQL Server standard edition,
you can backup the databases from the Express Edition, restore it on the Standard Edition, copy the SQL Server logins between them and create a SQL Alias on the SharePoint servers to point to the new Standard Edition database server
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

I want to setup a Disaster Recovery Server for Sharepoint Server 2010

There are four production server running sharepoint server 2010 and one SQL server for
ContentDB management.

DR depends upon your backup stratgies, i.e
1) if you taking full backup of sharepoint using SharePoint tool
2) If you taking just SQL backup( Content DB and Services DB).
3) using the 3rd party tool for backup and recovery.
apart from above, you also have make a decision what point of time you want recovery.
from your questions, what i think for you.
Setup new farm with same SharePoint level.same customization, same services configuration, and same number of web apps.
then backup from Prod server( SQL content DBs) and then restore into new farm and mount them.
this is one time thing, Now you have to make decision, how data move from Prod to QA( i mean frequency i.e daily, monthly etc).
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

SSRS/SharePoint Migration 2010 to 2013 connection issues

We are currently attempting to move our SharePoint 2010 to 2013 and SSRS Information. The first attempt at this we were unable to get SSRS to show up in Central Admin. We decided to rebuild all servers and re-installed everything.
This time we have SSRS showing up in Central admin and we are able to run some reports from our sites now. In our 2010 environment we are using "Windows authentication (integrated) or Sharepoint user" option with SharePoint Lists. I am unable to
get this to work in our 2013 Environment, the stored credentials with windows authentication will work however.
I have read t through many different books, MS Guides, Blogs, Forums, etc but unable to solve this issue.
I have tried editing the rsreportserver.config to match our Production, did not help. (also tried different authentications)
I found an article saying to change the "Forms" Auth in some config files to "Windows" did not help
When I try to go to our \\localserver\reportserver (appserver) I get a blank page with this info:
HTTP/1.1 200 OK
Server: Microsoft-IIS/8.5
Date: Fri, 21 Nov 2014 22:30:03 GMT
Connection: close
I have tried going into Central Admin -> General Application Settings -> Report Server Integration. and fill out this information also but receive this error:
Failed to establish connection with report server. Verify the server URL is correct or review ULS logs for more information. Product area: SQL Server Reporting Services, Category: Configuration
Pages
I am not sure if I have missed some step along the way of migrating and setting up this information. Any help or other things to try would be very helpful.
Thanks!

Hi young99,
According to your description, you get connection issue after migration from SharePoint 2010 to SharePoint 2013. Right?
In this scenario, we are not clear how you did the migration. Please follow these steps and check if you miss anything:
Restore Reporting Services encryption keys
Backup the SharePoint content databases and detach it.
Backup Reporting Services catalog database.
Copy Reporting Services configuration files.
Restore SharePoint Content databases to the new farm.
Restore the Reporting Servicesencryption keys.
Restore the SQL database that is the Reporting Services catalog database (ReportServer).
Restore Reporting Services configuration files.
Create a new Reporting Services service application.
For more information, please see:
Migrate a Reporting Services Installation (SharePoint Mode)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Backup of sharepoints?

Similar Messages

Maybe you are looking for