SharePoint Disaster Backup

-
Steps to make a disaster back up:
  • Record which Web applications are associated with the SSPs
·         Perform a full back up of the SSPs.
·         Completely stop the farm by stopping the services associated with Office SharePoint Server 2007 and by stopping Internet Information Services (IIS).
·         Back up the following databases by using SQL Server 2005 tools:
o        Content databases
o        Central Administration content database
o        Configuration database
o        Windows SharePoint Services Help Search database
o        Back Up the SQL Server logins, fixed server roles, fixed database roles, and permissions for these databases
o        Backup System Databases
·         Start all services again
·         Back up a farm by using Central Administration (Office SharePoint Server 2007 or using STSADM command.
·         Backup the IIS Metabase
http://technet.microsoft.com/en-us/windowsserver/cc706954.aspx
and document SSL Certificate, Host Header, IP address binding
 Backup C:\WINNT\assembly
  • Backup  %SYSTEMDRIVE%\%COMMONPROGRAMFILES% \Microsoft Shared\Web server extensions\12.0
  • Backup C:\Inetpub\wwwroot\wss\Virtual Directories\...
  • Backup %SYSTEMDRIVE%\%COMMONPROGRAMFILES% \Microsoft Shared\Microsoft Office 12 Single Sign-on

The following needs to be documented
·         Application pool settings.
·         External service connection settings.
·         Alternate access mapping settings.
·         E-mail settings.
·         Recycle Bin settings and other Web application general settings.
·         A/V settings.
·         Usage analysis processing settings.
·         Diagnostic logging settings.
·         Content deployment settings.
·         Timer job settings.
·         HTML viewer settings.
·         Database names and locations.
·         Web application names and databases. Be sure to document the content database names associated with each Web application.
·         Activated features.
·         Default quota templates.

·         Blocked file types

Comments

Post a Comment

Popular posts from this blog

Adjust the Search SharePoint Performance level

-
-Set-SPEnterpriseSearchService -PerformanceLevel PartlyReduced On all search app servers -Open NodeRunner process configuration file below in Notepad C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config. Update  <nodeRunnerSettings memoryLimitMegabytes=”0 ″ /> . This is the configuration to limit NodeRunner process memory usage, replace  0  to 500 or 1000 -Restart  SharePoint Search Host Controller  service
Read more

SharePoint 2013 User Profile synchronization versus import

-
Reference is : 2013 advanced Training User Profile Service administrators in SharePoint 2013 can use profile synchronization to manage and synchronize the user and group profile data stored in the SharePoint 2013 profile store with profile data stored in directory services and BDC systems. There are two distinct forms of profile import and synchronization available in SharePoint 2013: ·          One-way profile import. This is a new implementation of a simple import process that was first provided in SharePoint Server 2007. It uses the SharePoint Active Directory Import option to import user profile data from Active Directory Domain Services (AD DS). Note: One-way profile import only works with Active Directory and does not support other directory services. ·          Two-way profile synchronization. This uses the SharePoint Server 2013 profile synchronization method that was first introduced in SharePoint Server 2010. It uses Microsoft Forefront Identity Manager (FIM)
Read more

Usage and Popularity Trends Report not showing correct numbers

-
Recently came into issue that popularity trends showing zero while users are accessing documents so I have that there is a parameter called TailTrimming as mentioned in this reference blog   https://blogs.technet.microsoft.com/tothesharepoint/2014/01/23/view-and-configure-usage-analytics-reports-in-sharepoint-server-2013/ For example, for the Views usage event the TailTrimming parameter is by default set to 3. This means that the usage analytics reports will be updated for an item when the item has been viewed a minimum three times within the last 24 hours. For example, if the item Fabrikam Laptop16 M6000 has been viewed twice within the last 24 hours, these two views won’t show up in the usage analytics reports. If within the next 24 hours the Fabrikam Laptop16 M6000 item is viewed 4 times, the usage analytics report will be updated with 4 views. to adjust it needs to run the following commands $SSP = Get-SPEnterpriseSearchServiceApplicationProxy $tenantConfig = $SSP.GetAn
Read more