Himmat Singh Dulawat (3x Sitecore MVP)

Sitecore Managed Cloud Service provides the default setting for the Custom Backup of our CD instance. In your environment, you can see all default settings from the Backup Action tab. As our custom backup had a limit of 10GB with a linked database of 4 GB so due to the size of the logs and other files we are sometimes getting failed custom backups. Automatic vs. Custom Backups Hence regarding your backup failures, that is mostly due to " The website + database size exceeds the 10 GB limit ". I did a quick check and it seems that the folder in site/wwwroot/App_Data/Logs is using up to 6GB of available space. To view the file usage of each folder, you can go to KUDU, open the PowerShell console, and run this command in the WWWroot: Solutions: Regarding the solution to the failed backups and why Sitecore prefers the use of Custom Backup as it supports. It is due to Partial backups being supported for custom backups. Partial b...

After deploying the application on Sitecore Managed Cloud Service(MCS) CM and CD instances, both environments were unresponsive and taking too much time to respond. To observe the issue and find the reason behind the issue you can perform the following operations. I am explaining the reason and the solution in this blog post. Here for better understanding, I am taking an example of one instance that is CM. Collect a performance Profile from the CM server: To investigate the issue in detail you can collect a performance profile. This will affect the performance of the CM server during profile capture. To collect the performance profile you can refer to the Sitecore KB article: Collecting a Performance Profile Razor Generator Tool: Sitecore stores compiled code in the Azure file system which is known to be slow due to relying on Blob storage internally. You can pre-compile all custom views via the Razor Generator tool ...

After upgradation the Sitecore project from version 8.2 to 10.2, I deployed the application on the Azure PASS environment. Everything was working perfectly fine and when I browsed the Unicorn.aspx page to sync the Sitecore items. It was asking me for the login. After clicking on the Sign in to Sitecore as an administrator and I entered the credential and it redirected me to the unicorn.aspx page with the same message. Solution: After some research, I have found that Sitecore 9.1 has introduced Sitecore Identity. Sitecore Identity (SI) is a mechanism to log in to Sitecore. It was introduced in Sitecore 9.1. It builds on the Federated Authentication functionality introduced in Sitecore 9.0 and the Sitecore Identity server, which is based on IdentityServer4. It provides a separate identity provider and allows you to set up SSO (Single Sign-On) across Sitecore services and applications. Then I explored the configs under the unicorn folder in my proj...