Sitecore App Service Backup Problems and solutions

 

 

1.       Backup Size crossing the threshold

a.       Problem

The Microsoft threshold for backups is 10 GB.

Sometimes there are situations encountered where the Web App size has crossed this limit and because of which the backups would fail.

b.       Solution

All files from /App_Data are either:

 

·         Temporary files for caching purposes

·         Diagnostic data for debugging purposes

They shouldn't affect any Sitecore functionalities if they are not restored from the backup files.

But in case if there are any missing files from /App_Data in the future, some of them would automatically populate itself with data.

 

Create a Backup Filter

1)       Create a file named _backup.filter in D:\home\site\wwwroot through Kudu console (https://<app-name>.scm.azurewebsites.net/DebugConsole)

2)      Add the following file paths in to the _backup.filter file

 

\site\wwwroot\App_Data\debug

\site\wwwroot\App_Data\DeviceDetection

\site\wwwroot\App_Data\diagnostics

\site\wwwroot\App_Data\logs

\site\wwwroot\App_Data\mediaIndexing

\site\wwwroot\App_Data\packages

\site\wwwroot\App_Data\serialization

\site\wwwroot\App_Data\Submit Queue

\site\wwwroot\App_Data\tools

\site\wwwroot\App_Data\viewstate

\site\wwwroot\logs

 

2.       Log Files not purging

a.       Problem

·         Observe the size of log folder.

o   There are situations where the error files are not getting archived and its ever growing. It will end up becoming a bottleneck for the application

·         Analyze the config files

o   If the logging level is not set to Error (For Production) then this will also contribute to the increasing log file size

 

b.       Solution

 

·         Observed the Sitecore.config -> cleanup Agent for the pattern for deletion of log files

·         Compare the patters with the actual log file names

·         The Sitecore config will have to be updated to match the file pattern of the standard log files and custom log files

·         Update the logging level and set to Error

 

 

3.       Device Detection databases

a.       Problem

·         Sitecore is not cleaning up old copies of the device detection & It is a known bug in Sitecore 9.0 rev. 171002 (Initial Release) and above version but has been fixed in 9.3 version

·         https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0872808

b.       Solution

§  Option 1 (Manual)

·         Delete obsolete device detection databases

§  Option 2

·         Configure Sitecore.Tasks.CleanupAgent agent to check /App_Data/DeviceDetection folder

 

<agent type="Sitecore.Tasks.CleanupAgent"> <files> <remove folder="$(dataFolder)/DeviceDetection" pattern="*.*" maxAge="07.00:00:00" recursive="false" /> </files> </agent>

 

 

§  Option 3

·         Update to latest version of Sitecore

 

 

Comments

Post a Comment

Popular posts from this blog

Sitecore: Performance issue on page load, Analytics?

Image
  Background of Infra: ·           The App service is hosted inside Isolated App Service Environment. ·          Sitecore XP Scaled topology used. ·          Sitecore Version: 9.1.1   Issue & Troubleshooting The website started experiencing slowness in Page load, sometimes it was taking more than a minute. On checking the Profiler trace it was found that the Sitecore analytics process is getting blocked while creating a tracker object.     StackTrace     ROOT    Sitecore.Mvc!Sitecore.Mvc.Routing.RouteHttpHandler.BeginProcessRequest     Sitecore.Mvc!Sitecore.Mvc.Pipelines.PipelineService.RunPipeline     Sitecore.Kernel!Sitecore.Pipelines.DefaultCorePipelineManager.Run     Sitecore.Kernel!Sitecore.Pipelines.DefaultCorePipelineManager.Run     Sitecore.Kernel!Sitecore.Pipelines.CorePipeline.Run     Sitecore.Mvc.Analytics!dynamicClass.     Sitecore.Mvc.Analytics!Sitecore.Mvc.Analytics.Pipelines.MvcEvents.RequestBegin.StartTracking.Process     Sitecore.Analytics.XConn
Read more

Sitecore - On-Premises to Azure PaaS (ASE) Cloud Migration - Part 3

  Automated Maintenance Heath status check and Auto heal Health Status In order automatically monitor the application’s health status, Health check feature was enabled. Using this feature there will be a ping to the specified health check path on all instances of the webapp every 2 minutes. If any web app instance does not respond within 10 minutes (5 pings), the instance is determined to be  unhealthy  and instance of the webapp will be taken out of the load balancer. The health probe will continue on the instance even though it is out of load balancer. Once the health probe receives a valid response, the instance will be added back into load balancer. Steps to enable the feature, 1.        Open the Resource explorer from the App Service blade in the portal under Development Tools. 2.        The resource explorer will open to the top-level view of your App Service. Expand the config section and click the web tab. 3.        Find the element named "healthCheckPath
Read more

Why , When and How To do a Sitecore Quality Assessment or Audit

Introduction Sitecore Assessment or Audit is a tedious exercise and here I’m trying to provide a high-level framework to carry out this activity. Of course, this would not be one size fit all kind of template, but it can certainly be used as guide or a template when conducting such audits. Bear in minds that such Quality assessment templates needs to be tailored to suit a particular project considering the environment, Technologies used, Sitecore version, Topology, System integrations and so on. When to do a Sitecore Assessment or Audit? ·          If the current partner did not deliver a quality implementation & if you are thinking of switching over to a new implementation partner, then it is certainly a good idea to conduct a Sitecore Audit to understand how bad or worse the situation is & also to decide on the next steps ·          As a pre cursor to any Sitecore upgrade activity or Cloud migration activity ·          As a regular hygiene, conduct an Sitecore Assessment or
Read more