Showing posts with label Restore. Show all posts
Showing posts with label Restore. Show all posts

Tuesday, July 31, 2012

Backup and Recover SharePoint like a time traveler


Backup and recover SharePoint faster than ever!
Crash happens. When it happens to your SharePoint farm it could put your users out of commission for hours. If only you had a magic time machine capable of fast, full-farm backup and restore, and crammed full of powerful search capabilities, easy item-level recovery, and the ability to alter the space-time continuum. Say no more. Idera SharePoint backup has most of that covered (we’re still working on the space-time thing), plus tools to schedule, manage, and monitor backups farm-wide. And you can do it three times faster than out-of-the-box SharePoint backup. 

Our fast, easy, space-time altering features include:
SharePoint backup screenshot
  • Lightning-Fast Backups - With powerful compression and encryption technology
  • Full-Farm Protection Covers content databases, farm config, service applications and more!
  • Real-Time Status Alerts Measure progress for backup and restore operations
  • Self-Service Document Recovery Recovery for site users that saves time
Idera SharePoint backup saves you from spending hours restoring backups after Crash happens. It’s the next best thing to a time machine for your SharePoint farm. Try it for free for 14 days and see for yourself.
Download a free 14-day trial now
Our time-travelling customers love SharePoint backup:

“The best part of working with Idera's SharePoint backup is that it’s easy to use and configure. Compared to similar products, it offers features that are easier to use and cost less!”
–Gerald Parish, SharePoint Architect, Resurgent Capital
 

“I’m so impressed, I’m not even going to complain about the complete lack of ninja protection.”
–Keith, Very busy SharePoint administrator, Taxes ‘R’ Us, Possibly not real

Saturday, June 16, 2012

Restore Web applicaton using SQL server tools in SharePoint 2010


There are some limitations to restore the whole web applicartion using SQL restore but we can use DB associated with Web Application using SQL tools

To restore databases associated with a Web application by using SQL Server tools

  1. The account must be a member of the sysadmin fixed server role.
  2. All stored procedures must be finished before a restore if any procedure is running stop SharePoint Timer service and wait for several minutes for any currently running stored procedures to finish.
  3. Do not restart the service until after you restore the databases.
  4. Now we are all set open SQL management studio and expand Database server
  5. Select the DB you want to restore > Right Click > Tasks > Restore > Database.
  6. In the Restore Database dialog box, specify all required information
  7. Open Options.
  8. In the Restore options section, select only Overwrite the existing database
  9. Recovery state section specify details as per your requirements
  10. Click OK

Restore a web applicaiton using Central Admin in SharePoint 2010


  1. Open Central Administration > Home page > Backup and Restore section > click Restore from a backup.
  2. The process consists of 3 steps
Step 1
Select Backup to Restore page > from the list of backups > select the backup job that contains the farm or Web application backup > and then click Next

Step 2
Select Component to Restore page > select the check box that is next to the Web application > and then click Next.

Step 3
Select Restore Options page > in the Restore Component section > make sure that Farm\<Web application> appears in the Restore the following content list.

3.      In the Restore Only Configuration Settings section, make sure that the Restore content and configuration settings option is selected.
4.      In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK
5.      Click Start Restore.

Restore a site collection using Windows PowerShell in SharePoint 2010


1.      Open SharePoint 2010 Management Shell.
2.      At the Windows PowerShell command prompt
3.      Type the following command, and then press ENTER:
Restore-SPSite -Identity <Site collection URL> -Path <Backup file> [-DatabaseServer <Database server name>] [-DatabaseName <Content database name>] [-HostHeader <Host header>] [-Force] [-GradualDelete] [-Verbose]
4.      If you want to restore the site collection to a specific content database, use the DatabaseServer and DatabaseName parameters to specify the content database.
5.      If you do not specify a content database, the site collection will be restored to a content database chosen by Microsoft SharePoint Server 2010.
6.      If you are restoring a host-named site collection, use the Identity parameter to specify the URL and use the HostHeader parameter to specify the URL of the Web application that will hold the host-named site collection.
7.      If you want to overwrite an existing site collection, use the Force parameter.

Sunday, June 10, 2012

Restore databases instantly


When disaster strikes, it can take hours to restore a database from backup. New SQL safe withinstant restore technology makes it possible to bring a database back on-line in minutes, not hours. With SQL safe instant restore, you can:
SQL safe screenshot
Virtually eliminate costly application down-time
Avoid impacting end-user productivity
Maintain database availability while the full restore completes in the background
Plus, SQL safe delivers fast, compressed backups (up to 95% compression!) so you can save time and storage space. Learn more.
Download a free 14-day trial now

Saturday, June 9, 2012

How to restore content database using SQL server in SharePoint 2010 ?


  1. If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish.
  2. Do not restart the service until after you restore the content databases.
  3. Open SQL Server Management Studio
  4. Connect to the database server.
  5. Right-click the Database that you want to restore > Tasks > Restore > Database.
  6. In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.
  7. In the Select a page pane, click Options.
  8. In the Restore options section, select only Overwrite the existing database.
  9. In the Recovery state section:
    • If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY.
    • If you must restore additional transaction logs, select RECOVER WITH NORECOVERY.
    • The third option, RECOVER WITH STANDBY is not used in this scenario.
  10. Click OK to complete the recovery operation.
  11. Repeat steps 4 through 10 for each database that you are restoring.
  12. Start the Windows SharePoint Services Timer service.

How to restore content database using Central Admin in SharePoint 2010 ?


  1. Open Central Administration
  2. On the Home page, in the Backup and Restore > Restore from a backup.
  3. The process contains 3 steps

Step 1
Select Backup > Select the backup job that contains the content database backup > Next.
Step 2
Select Component > select the check box that is next to the content database > Next.
Step 3
Select Restore Options > under Type of Restore > click the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK > Click Start Restore

  1. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section.
  2. You can view the status for the current recovery job in the lower part of the page in the Restore section.
  3. The status page updates every 30 seconds automatically.
  4. You can manually update the status details by clicking Refresh.
  5. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start.

Popular Posts

Disclaimer

The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.