<Temporary_Dump_Location>\<Backup_Name>\<Portal_Site_Name>\<Site_Collection_Name>\<Site_Collection_Name>.dat Note: Portal Site name and site collection name will be modified as per the following rules and used as file/folder name.
The character colon (:) in the portal site URL will be replaced with "@".
The Characters \<>/*?"| and space characters in the portal site/site collection will be replaced with underscore(_). Other characters will remain the same.
"http://" or "https://" will be removed. For example consider the following assumption:
Take the portal URL as "http://winserver3:9090".
Let one of the site collections under it be "http://winserver3:9090/sites/first-No.1site". Let the temporary dump path be "C:/TEMPORARYDUMP".
Backup name be "MyShareBackup".
For the above assumptions, the dump file will be at the location,
C:\TEMPORARYDUMP\MyShareBackup\winserver3@9090\winserver3@9090_sites_first-No.1site\winserver3@9090_sites_first- No.1site.dat
Note: Backup file for a site collection will have ".dat" extension.
Troubleshooting Tips
SharePoint Sites not listed in the site selection tree in "Backup -> Plugin Backups -> SharePoint" page.
Cause 1 : If there is no portal site available to list [mostly this occurs for WSS2.0/SPS2003 only and there will not be any issues for WSS3.0/MOSS2007 or MS SharePoint 2010]
Solution 1: Enter a valid portal site URL and add to the list through the menu "Settings -> Advanced Options -> SharePoint Settings(Left Tab) -> Portal Site Settings(tab)". Check if the added portal site is listed in the table below. Only the portal sites listed in this table will be listed in the "backup -> Plugin Backups -> SharePoint" page. Refer the help document for SharePoint Settings for more details
Cause 2: If the path of the STSADM.EXE provided in the "Settings -> Advanced Options -> SharePoint Settings(Left Tab) -> Path Settings (tab)" is incorrect or empty.
Solution 2: Enter the exact path of the STSADM.EXE through the menu "Settings -> Advanced Options -> SharePoint Settings(Left Tab) -> Path Settings(tab)".
For WSS2.0/SPS2003, normally found inside C:/Program Files/Common Files/Microsoft Shared/web server extensions/60/BIN folder.
For WSS3.0/MOSS2007, normally found inside C:/Program Files/Common Files/Microsoft Shared/web server extensions/12/BIN folder.
For MS SharePoint 2010, normally found inside C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/14/BIN folder. Refer the help document for SharePoint Settings for more details
Cause 3 : SQL Server service is not running.
Solution 3: Check if the SQL Server instance associated with the SharePoint farm is running. If the SQL Server service is stopped StoreGrid will not be able to list the site collections under a portal site.
SharePoint portal sites are listed in "Add SharePoint Site Backup" page, but unable to list the site collections under a portal site when expanding the node of a portal site.
Cause 1 : No such portal site exists (the portal site might have been deleted from SharePoint central admin) Solution 1: Check if the portal site that you try to list exists, valid and accessible via browser.
Cause 2 : Not even one valid site collection that is accessible via browser is available to list using STSADM.exe tool. Solution 2: Check if the portal site you are trying to list has at least one valid, error free site collection under it which is accessible via web browser.
Cause 3 : SQL Server service is not running.
Solution 3: Check whether the SQL Server instance that is associated with the SharePoint farm is running or not. If the SQL Server service is stopped StoreGrid will not be able to list the site collections under a portal site.
Cause 4 : STSADM.EXE tool location invalid or not provided
Solution 4: Check if the STSADM.EXE tool exists in the location that is given in "Settings -> Advanced Options -> SharePoint Settings(Left Tab)" page.
Limitations
1. For WSS2.0/SPS2003, only the sites added from 'SharePoint Settings' page will be listed in 'Add SharePoint Site Backup' page.
2. Though the whole SharePoint Server or a whole portal site is selected for backup, only a site-collection level of backup will be done. Hence, to restore all the site-collections under a portal site, you need to restore the site- collections under that portal site one by one using STSADM.EXE.
3. Restoring default site-collections in WSS2.0/SPS2003 is not permitted. This attempt is strictly not recommended for WSS2.0/SPS2003.
4. A site-collection whose total size exceeds 15 GB cannot be backed up as this is being a limitation with STSADM.EXE [which StoreGrid uses] itself. However, in such cases, you can use StoreGrid's SQL Server backup feature for backing up the SQL databases being used by the SharePoint Server.
5. StoreGrid should be run with Administrator privileges to list and backup SharePoint sites as STSADM.EXE can be run only with Administrator permissions.
6. If the dump path of the SharePoint backup exceeds 255 characters, dump process will fail. Hence, make sure, you have entered a shorter dump path to enable the dump to complete successfully.
7. Restoring SharePoint 'Central Administration' may not bring the original Central Administration's whole UI and its functionalities.
8. Currently you can seed the local data to the remote server only. After performing the seed migration, you can continue this backup schedule only to the remote server, not to both remote server and local backup.