Restored SP2010 site "broken" in an odd way - home.aspx is not accessible, but default.aspx is.

So we are testing out a 3rd party backup and recovery tool. The testing for individual pages and list items went pretty well. However, we are seeing really odd behavior when attempting to recover the sites. Obviously we will be working with the vendor on the issue from their side of things.

I just don't know if there is something that we might have configured oddly that might be contributing to the issue.

I created a from scratch test site using the team template on our SP 2010 service pack 2 farm.

We have an F5 load balancer handing traffic off two 2 web front end servers, with two application servers behind the scenes along with a sql server.

The product backed up the content, then I deleted the site so that we could test the restore ability.

There are a number of problems that we see right off the bat when trying to recover a site.

1. The Site Pages/Home.aspx appears to have a problem - attempting to access it creates an error page that the ULS describes as:

Timestamp                        Process                                              TID         Area                                     Category                             EventID               Level                    Message             Correlation

04/10/2014 10:50:29.92 w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                Logging Correlation Data              xmnv    Medium              Name=Request (GET:http://myfarm:80/sites/IT/d27/col/SecondTestSite/SitePages/Home.aspx)a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.93 w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                Logging Correlation Data              xmnv    Medium              Site=/sites/IT     a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.93 w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                Monitoring                                  b4ly        High      Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=7.44193745294444               a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.96 w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                Runtime                                     tkau       Unexpected      System.FormatException: Input string was not in a correct format.   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)    at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)    at System.Convert.ToInt32(String value, IFormatProvider provider)    at Microsoft.SharePoint.Utilities.SPUtility.CreateSystemDateTimeFromXmlDataDateTimeFormat(String strDT, Boolean fPreserveMilliseconds)    at Microsoft.SharePoint.ApplicationPages.Calendar.SafeFieldAccessor.GetDateTimeFieldValue(SPItem item, String fieldName)    at Microsoft.SharePoint.ApplicationPages.Calendar.CalendarItemRetriever.<RetrieveInternal>b__0(SPItem item)    at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext() ...            a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.96*              w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                       Runtime                              tkau      Unexpected       ...   at System.Linq.Enumerable.<ExceptIterator>d__92`1.MoveNext()    at System.Linq.Buffer`1..ctor(IEnumerable`1 source)    at System.Linq.OrderedEnumerable`1.<GetEnumerator>d__0.MoveNext()    at Microsoft.SharePoint.ApplicationPages.Calendar.CalendarItemRetriever.ConvertItemType(IEnumerable`1 items)    at Microsoft.SharePoint.ApplicationPages.Calendar.DefaultCalendarListAccessor.Retrieve(String selectedDate, String scope, Dictionary`2 entityInfo)    at Microsoft.SharePoint.ApplicationPages.Calendar.CalendarService.CreateStartupResponse(ICalendarAccessor accessor, Dictionary`2 parameters, String viewType, String selectedDate)    at Microsoft.SharePoint.ApplicationPages.WebControls.AjaxCalendarView.CreateStartupData(String viewType, String selectedDate)    at Microsoft.SharePoint.Appl...              a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.96*              w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                       Runtime                              tkau      Unexpected               ...icationPages.WebControls.AjaxCalendarView.CreateBodyOnLoadScript(SPWeb web)    at Microsoft.SharePoint.ApplicationPages.WebControls.AjaxCalendarView.OnPreRender(EventArgs e)    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Control.PreRenderRecursiveInternal()    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStag...               a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.96*              w3wp.exe (NTPSSPFE01NEW:0x0E14)                   0x13DCSharePoint Foundation                       Runtime                              tkau      Unexpected       ...esAfterAsyncPoint)   a7a882f4-71c9-40aa-aeb5-8d089467ad4b

04/10/2014 10:50:29.96 w3wp.exe (NTPSSPFE01NEW:0x0E14)                    0x13DC SharePoint Foundation                Monitoring                                    b4ly        Medium               Leaving Monitored Scope (Request (GET:http://myfarm:80/sites/IT/d27/col/SecondTestSite/SitePages/Home.aspx)). Execution Time=50.8621207443963               a7a882f4-71c9-40aa-aeb5-8d089467ad4b

2. What we did find was a

http://myfarm/sites/IT/d27/col/SecondTestSite/default.aspx page that displayed what SitePages/Home.aspx used to be.

However, that page is not marked as the home page. I know I can mark that page as the home page to get around the problem - but why would the original page not load any longer? I tried going into the Site Pages library and the how to use the featurees page still works okay - just not the home page.

I also am finding that the them of the site was lost, a workflow attached to a list was lost - I don't just mean one instance of the workflow; the list no longer has a workflow attached to it. Also the default view of a calendar part on the front page was lost.

Is this common for SharePoint site recoveries - to lose various fundamental settings?

I am just wondering whether this sounds like something site specific or if it sounds like every other recovery out there.

Thank you