Tag Info

Hot answers tagged

16

Backing up with SQL Server is a good scenario if you know what the limitations are. Essentially, this only works fine with normal content databases. Backing up the configuration database is possible, but it's not supported to restore it. In case of a disaster, you'll have to build a new farm. This means that detailed documentation is essential. When you ...


11

I'm glad you included an image of the operation in progress, because it makes it easier to clear up some confusion and answer your question. I think previous respondents missed the fact that you're actually working in SharePoint Designer 2007 -- not Central Administration or the command line. First, let me clear up some confusion: the operation you're ...


11

There are lots of point to discuss before coming to a conclusion here. But I will just explain the different possible ways you could do backup in SharePoint in an order of good to best. Central Admin Backup - This is a default UI option that comes within Central Administration. It allows to take full and differential backups. You have the additional ...


8

Actually, that's going to depend on what release and build version of SharePoint you're using. If you have a SharePoint 2007 farm that hasn't yet been patched to Service Pack 2, you're going to have to manually lock the site collection before you back it up, regardless of whether its a Full or Differential backup. (And for goodness sakes, please patch it ...


8

As of now, there is no out of the box facility to backup an entire SharePoint site and restore it to another farm as you do for on premise SharePoint applications. The only option currently available would be to use the "Save site as template" option for sites, which would take a backup of max 50 MB. Visit this blog for more details. You can check out for ...


6

I don't think it was intentional, but this is actually something of a trick question. Let me explain. There are basically two different types of backups that you can perform: farm-level (catastrophic) backups and site collection backups. The former is used to back up components such as the entire farm, a Web application, a content database, etc. The ...


6

The biggest determining factor here between SharePoint Backups and SQL Server backups is going to be how much content you have in your farm. Based on what I could find on TechNet, SharePoint backups are not supported for content databases over 200 GB in size (http://technet.microsoft.com/en-us/library/cc262787.aspx) and site collections over 100 GB in size ...


6

You would only need to backup your 14 folder if you made added files or changed files in the 14 folder manually (meaning not through a deployed package). I would, however, make a backup of your web.config files if you have any custom connection strings, app settings, or service bindings.


6

I recently ran into the exact same issue in SP 2013 where my Dev machine had the RTM install and the target server the June CU. We ended up copying the Content Database from SQL directly, reattaching and associating it to a Web Application and it worked flawlessly. It seems the Restore command is no longer backwards compatible and can't be relied to restore ...


6

I've had this discussion with Microsoft Support in June 2014. They told me that backups are performed on all site collections on a daily basis and kept for 14 days. In order to get a restore to happen you need to add a service request from your Office 365 tennant admin center (support link in the left navigation). Unfortunately they can only restore on ...


5

If you've created the blog as a site collection, I would recommend going with STSADM's Backup operation, using the -URL parameter to indicate that you're doing a site collection backup instead of a catastrophic backup. Here's the TechNet article on the Backup operation for more info: STSADM's Backup Operation - TechNet I would recommend the Backup operation ...


5

The two main options I would consider are: Create a template with content from the Blog site. This will give you a .stp file that can be added to the site template gallery of any new site. This can be done completely through the UI. Run the stsadm export command to do a backup of the sub-site.


5

Two options. For site collection administrators you can backup sites (with content as long as it's under 10mb) by saving the site as a site template. The template will be stored in the root site collection and any SC admin can use it to create a new site on another site collection. Not however this doesn't give you full fidelity as several things (namely ...


5

There is just a subtle difference: Workflows are included when you use the Backup-SPSite cmdlet. If you backup a root web of a site collection the site collection recycle bin will obviously not be included.


5

There are a couple of things you can try... such as 1. Get-SPDeletedSite & Remove-SPDeletedSite You may already have restored this site before. In that process you also deleted the site first (automatically), which you can find running the command... >Get-SPDeletedSite You'll see the site (or sites) listed, like this: WebApplicationId : ...


5

I can't see that you have run the SharePointBAC.ps1 in your script, which is downloaded from the Codeplex page SharePoint Backup Augmentation Cmdlets. The scripts Get-SPBackupCatalog Set-SPBackupCatalog Remove-SPBackupCatalog Export-SPBackupCatalog is not out-of-the-box native cmdlets in SharePoint Management Shell or PowerShell ISE with the reference of ...


4

As you stated - "create a sheduled task that runs either power-shell or stsadm command". No other options for now and it would be nice to have option of built-in automatic backup in future version of sharepoint And here is a good post how to do it - Backup site collection.


4

The most robust, free, plug-n-play solution I've found was this vbscript: Option Explicit ' Email source address Const strFrom = "email@example.com" 'Email destination address Const strTo = "email@example.com" ' Mail server address Const strMailserver = "smtp.host.com" 'Mail Server Schema Const strSchema = ...


4

If you look at the various packages you should see some similar capabilities, but they perform the work in different ways. As an example, Quest's tools basically mounts the SQL Server backups. If you are already doing SQL backups then that might be an advantage, but if you are using a different backup solution it would be redundant with some other ...


4

Saumil, that is not possible. What you coud do: * restore the content database to another sitecollection * synchronize the permissions between the two sitecollections with some custom written powershell. I don't think there's an easier way.


4

The regular SharePoint backups will grab content, and configuration (when doing the farm backup). This does not backup any changes made to the SharePoint files on the server(s) such as images, templates, etc. Any customizations or third party tools that were deployed; note all should be deployed via a WSP. Some manual web.config changes may not be saved ...


4

You can use PowerShell to do that, check Restore-SPSite cmdlet. Restore-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak


4

As you need to move your SQL servers, this can and will be treated as a simple SQL server move, which requires a farm migration. This is because the domain name of the SQL server changes. For farm migration, you can find instructions at http://technet2.microsoft.com/Office/en-us/library/42511e01-ecdd-4dc5-b06f-35aaada8a5d81033.mspx?mfr=true. Make sure you ...


4

Doing the SQL Server backup of the content databases is almost identical to what you are doing with the PowerShell script: protecting your content. This is of course the most important thing that you will want to protect. The advantage that doing these backups through a maintenance plan on SQL gives you is that you can perform both full and differential ...


3

Here is some info on MS TechNet that covers some of the options and the limitations of each: http://technet.microsoft.com/en-us/office/sharepointserver/bb736212.aspx I would read through that and figure out specifically what you would like to do and how often you need to do it. For a system of any size, I really like what some of the third-party tools ...


3

In your example you are backing up the root site collection of machine1 and restoring it under a managed path on machine2. You may want to make those consistent. Emad is correct about step #2, as long as the application is setup on the server you will not need to create a content db. One last tip, make sure that you have any customizations or solutions ...


3

PowerShell is the preferred method, you have more options, and will be the supported method going forward (STSADM is depreciated and only included in 2010 for 2007 compatibility). The command is Backup-SPFarm -Directory -BackupMethod Here is the TechNet reference http://technet.microsoft.com/en-us/library/ff607881.aspx One of the biggest benefits is ...


3

In the past, what I've done is restore the backup to a spearate site collection via stsadm. Then from that backup, I export the subsite. I then import that into the original site collection. Check out the STSADM commands, ther are a lot of switches for export. Some 3rd party tools make recovery a lot easier like things from Docave, Quest and the like, ...


3

This has long been an issue as the workflow data is actually kept separately from the actual form itself. However, the best way to manage this to be able to restore is to have the data contained within the form. Let the workflow run, but the actual statuses should be based on fields in the workflow, then your status will always be restored when you restore ...


3

I'm not sure if this would work or not, but I wonder if you first should try creating a blank site collection in the root of the 3000 web application, and then use the -Force switch (heh, inadvertent geek humor there) with Restore-SPSite to see if you can get it to overwrite the new blank site with your backed up site collection. Just something to try, I'm ...



Only top voted, non community-wiki answers of a minimum length are eligible