Sharepoint Farm backup with powershell timeout

Hello experts.
I have faced with the problem using powershell script to manage automatic full farm backups with file rotations.
I use common script taken from this page
http://gallery.technet.microsoft.com/office/9b99c435-8831-4c9e-a70b-1f13158ef22a
And every was fine until backup procedure of wss_content database grew up to 1 hour
I have MS RBS configured for wss_content database and files in BLOB store have about 100Gb in summary
Now i can't build full backup and have error in spbackup.log
[12/4/2012 12:59:21 AM] Progress: [WSS_Content_MP27] 80 percent complete.
[12/4/2012 1:02:03 AM] Warning: [WSS_Content_MP27] Time is out. Server did not respond within the timeout period.
The backup or restore was aborted.
After that script try to repeat failed command 3 times using next statement
SQL command timeout is set to 1.00 hours
Question is how i can increase timeout for this operation?
Because for our database 1 hour is dramatically low value.
One week ago full backup of wss_content database takes 50 minutes.
Thanks.
ruslanin

Hi,
have you tried to used backupthread parameter like
Backup-SPFarm -Directory C:\Backup -BackupMethod full -BackupThreads 10 -ForceBackupThreads
Specifies the number of threads to be used during the backup. The fewer the threads, the easier the backup log file is to read and understand. The more the threads, the more components that can be backed up in parallet, potentially resulting in a faster backup operation. The minimum value is 1 and the maximum value is 10.
The default value is 3.
If a backup is performed with the –ShowTree parameter, then the BackupMethod parameter is not used.
http://technet.microsoft.com/en-us/library/ff607881.aspxWhere you are backing up ur data local drive or shared drive, also check connectivity and speed incase of shared drive.thx
iffi

Similar Messages

After restoring SharePoint farm backup ( The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connection)

Hi,
I have taken farm back and restore it in new UAT environment, while access to the main site getting the below error:
Error
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 866476f3-23dd-4e1e-97af-bffc62cc2d57
Date and Time: 7/15/2014 11:26:35 AM
When i checked in log i got below error
System.Data.SqlClient.SqlException: A network-related or instance-specific
error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40
- Could not open a connection to SQL Server) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecu...
Thanks in advance
Said Al Balushi

Hi Wendy,
i have checked all below points, every thing is fine but still i am getting the same error.
Check SQL services are runing
Check remote conenctions are enabled
Check SQL Browser service is runing
Check TCP/IP protocal enabled at SQL server
Check out windows firewall setting
Thanks,
Said

Unable to restore SharePoint farm with Backup Exec - Farm Topolgy appears to be locked and job repeatedly fails

Hi All
I'm attempting a full restore of a SharePoint 2010 farm, single server housed on the same server as the SQL server that holds the SharePoint databases. Backup and restore is via Backup Exec, the backup job was carried out via BE 2012 and the Restore is via
BE 2104. The server I'm attempting to restore to has also been restored by using the system state and a copy of the drives from the original source server - hence its pretty much a clone of the source server.
Irrespective of the account used to run the restore job I'm seeing repeated failures with the error "Unable to lock the Microsoft SharePoint Farm Topology. You must unlock the farm topology and retry the job".
By restoring the admin databases directly by taking a SQL backup of the source databases and restoring these to the server I'm attempting to restore SharePoint to I have succeeded in bringing the SharePoint admin console back to
life, none of the sites are in a locked state, and they can be locked and unlocked both via the admin console or via Powershell. Locking and unlocking the makes no difference.
Any ideas where I can look to from here, could the above error be a cryptic Backup Exec error that doesn't actually mean what it says?

Hi,
Reviewing the DPMRACurr log on the target server during the Date/Time of restore may assist with potential paths to why the job is failing. The logs can be found in the
following path on the target server <DPM Install path>/Program Files Microsoft Data Protection Manager/DPM/Temp
The logs may uncover why we face the current issue. For example the following “ATTACH " – Failed <and also reason why>
Also the DPM server MSDPMCurr log during the Date/Time of restore may also assist with the issue you face. For example the following may be seen “MountDatabaseFailed”
Also note the below process is carried out with the method of restore which was used.
DPM restores the DB to the destination SQL server once the DB is attached, then the restore process is complete and now will be SharePoint front end server connecting to
that DB using the account that was setup with configuresharepoint.exe -enablesharepoint protection. That account needs permissions to connect to that database. The attach phase itself is using the system account from DPMRA process on the local SQL Server.
If you identify the issues are permission related first ensure
the DPMRA service [logon account] has access within SQL for the SQL instance that we are restoring to this account will need DB creator for the following system DB master.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II.
[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

SharePoint Foundation: Error when performing a Farm Backup

Hi,
I am trying to create a full farm backup of my organisations SharePoint Foundations installation.
I've tried doing it via the Central Administration and PowerShell. However both ways give me errors. Here are some of the errors associated with the Central Administration way of doing a full backup:
Requested By Domain\Administrator
Start Time 1/10/2012 2:49 PM
Finish Time 1/10/2012 3:06 PM
Directory D:\SharePoint\Backup\Test Back ups\spbr0000\
Backup ID 553b4f4f-7542-4e80-b129-d3d294285486
Warning Count 72
Error Count 16
Failure Message Object Query-0 (C: on SharePoint Server) failed in event OnBackupComplete. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
I've also got error reason 15105 coming up a lot too.
Can anyone please tell me how I overcome this problem please.
Regards
Stephen

Hi Trevor,
I've looked through the whole file and I cannot make any sense of it. The following list is the errors that where within the log file:
[10/01/2012 14:49:58] Warning: [SharePoint_Config] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005C.bak'. Operating system error 5
(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:50:03] Warning: [StateService_121a4c703edd4d8485f22be52edb71a5] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005E.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:50:06] Warning: [WSS_Content] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000061.bak'. Operating system error 5(failed to
retrieve text for this error. Reason: 15105).
[10/01/2012 14:50:15] Warning: [SharePoint_Config] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005C.bak'. Operating system error 5
(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:50:18] Warning: [StateService_121a4c703edd4d8485f22be52edb71a5] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005E.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:50:21] Warning: [WSS_Content] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000061.bak'. Operating system error 5(failed to
retrieve text for this error. Reason: 15105).
[10/01/2012 14:51:15] Warning: [SharePoint_Config] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005C.bak'. Operating system error 5
(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:51:18] Warning: [StateService_121a4c703edd4d8485f22be52edb71a5] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005E.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:51:21] Warning: [WSS_Content] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000061.bak'. Operating system error 5(failed to
retrieve text for this error. Reason: 15105).
[10/01/2012 14:53:31] FatalError: Object SharePoint_Config failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the
backup directory.
SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005C.bak'. Operating system error 5(failed to retrieve text for this error.
Reason: 15105).
[10/01/2012 14:53:32] Warning: [Temp2_Content] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000062.bak'. Operating system error 5(failed to
retrieve text for this error. Reason: 15105).
10/01/2012 14:53:33] FatalError: Object StateService_121a4c703edd4d8485f22be52edb71a5 failed in event OnBackup. For more information, see the spbackup.log or
sprestore.log file located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000005E.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
[10/01/2012 14:53:37] FatalError: Object WSS_Content failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup
directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000061.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:53:50] Warning: [Temp2_Content] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000062.bak'. Operating system error 5(failed to
retrieve text for this error. Reason: 15105).
[10/01/2012 14:53:52] Warning: [SharePoint_AdminContent_61a49b6b-f3d6-4b98-af1b-78ca06dc3fcf] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\00000065.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:54:11] Warning: [SharePoint_AdminContent_61a49b6b-f3d6-4b98-af1b-78ca06dc3fcf] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\00000065.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:54:20] Warning: [Secure_Store_Service_DB_26fc8782f473423f8b6fd76ec0222ead] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\00000066.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
[10/01/2012 14:54:35] Warning: [Secure_Store_Service_DB_26fc8782f473423f8b6fd76ec0222ead] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\00000066.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:54:50] Warning: [Temp2_Content] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000062.bak'. Operating system error 5(failed to
retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:55:11] Warning: [SharePoint_AdminContent_61a49b6b-f3d6-4b98-af1b-78ca06dc3fcf] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\00000065.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:55:35] Warning: [Secure_Store_Service_DB_26fc8782f473423f8b6fd76ec0222ead] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\00000066.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:05] FatalError: Object Temp2_Content failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file located in the backup
directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000062.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:08] Warning: [WebAnalyticsServiceApplication_StagingDB_2504a5a5-71bc-4046-aa29-4766c031e70f] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\00000067.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:23] Warning: [WebAnalyticsServiceApplication_StagingDB_2504a5a5-71bc-4046-aa29-4766c031e70f] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\00000067.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:26] FatalError: Object SharePoint_AdminContent_61a49b6b-f3d6-4b98-af1b-78ca06dc3fcf failed in event OnBackup. For more information, see the
spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000065.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:28] Warning: [WebAnalyticsServiceApplication_ReportingDB_f9e3ab00-ef34-4562-b9e6-e512ea466ad5] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\00000068.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:43] Warning: [WebAnalyticsServiceApplication_ReportingDB_f9e3ab00-ef34-4562-b9e6-e512ea466ad5] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\00000068.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:50] FatalError: Object Secure_Store_Service_DB_26fc8782f473423f8b6fd76ec0222ead failed in event OnBackup. For more information, see the spbackup.log
or sprestore.log file located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000066.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:57:57] Warning: [Bdc_Service_DB_9a70ba5cb7e04a7386306c203fdf9dd0] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000069.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:58:12] Warning: [Bdc_Service_DB_9a70ba5cb7e04a7386306c203fdf9dd0] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000069.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:58:23] Warning: [WebAnalyticsServiceApplication_StagingDB_2504a5a5-71bc-4046-aa29-4766c031e70f] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\00000067.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:58:43] Warning: [WebAnalyticsServiceApplication_ReportingDB_f9e3ab00-ef34-4562-b9e6-e512ea466ad5] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\00000068.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 14:59:12] Warning: [Bdc_Service_DB_9a70ba5cb7e04a7386306c203fdf9dd0] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000069.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:00:39] FatalError: Object WebAnalyticsServiceApplication_StagingDB_2504a5a5-71bc-4046-aa29-4766c031e70f failed in event OnBackup. For more information,
see the spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000067.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:00:51] Warning: [Search_Service_Application_1_PropertyStoreDB_45c02022f59f474f951968c1af057ae0] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\0000006C.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:00:51] Warning: [Search_Service_Application_1_CrawlStoreDB_1efdf6e816ac49afa9187bbe008f4ba9] Cannot open backup device 'D:\SharePoint\Backup\Test Back
ups\spbr0000\0000006B.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:00:51] Warning: [Search_Service_Application_1_DB_fff3b084e2104326a6bdf065cc1bddfe] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\0000006A.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:00:59] FatalError: Object WebAnalyticsServiceApplication_ReportingDB_f9e3ab00-ef34-4562-b9e6-e512ea466ad5 failed in event OnBackup. For more
information, see the spbackup.log or sprestore.log file located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000068.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:01:08] Warning: [Search_Service_Application_1_CrawlStoreDB_1efdf6e816ac49afa9187bbe008f4ba9] Cannot open backup device 'D:\SharePoint\Backup\Test Back
ups\spbr0000\0000006B.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:01:11] Warning: [Search_Service_Application_1_PropertyStoreDB_45c02022f59f474f951968c1af057ae0] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\0000006C.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:01:11] Warning: [Search_Service_Application_1_DB_fff3b084e2104326a6bdf065cc1bddfe] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\0000006A.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:01:27] FatalError: Object Bdc_Service_DB_9a70ba5cb7e04a7386306c203fdf9dd0 failed in event OnBackup. For more information, see the spbackup.log or
sprestore.log file located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\00000069.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:02:09] Warning: [Search_Service_Application_1_CrawlStoreDB_1efdf6e816ac49afa9187bbe008f4ba9] Cannot open backup device 'D:\SharePoint\Backup\Test Back
ups\spbr0000\0000006B.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:02:11] Warning: [Search_Service_Application_1_PropertyStoreDB_45c02022f59f474f951968c1af057ae0] Cannot open backup device 'D:\SharePoint\Backup\Test
Back ups\spbr0000\0000006C.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:02:11] Warning: [Search_Service_Application_1_PropertyStoreDB_45c02022f59f474f951968c1af057ae0] SQL command failed and needs to be restarted. The
command will be re-started a total of three times before throwing an exception.
[10/01/2012 15:02:11] Warning: [Search_Service_Application_1_DB_fff3b084e2104326a6bdf065cc1bddfe] Cannot open backup device 'D:\SharePoint\Backup\Test Back ups
\spbr0000\0000006A.bak'. Operating system error 5(failed to retrieve text for this error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:04:56] FatalError: Object Search Service Application 1 failed in event OnBackup. For more information, see the spbackup.log or sprestore.log file
located in the backup directory.
    SqlException: Cannot open backup device 'D:\SharePoint\Backup\Test Back ups\spbr0000\0000006A.bak'. Operating system error 5(failed to retrieve text for this
error. Reason: 15105).
BACKUP DATABASE is terminating abnormally.
[10/01/2012 15:06:11] FatalError: Object Search_Service_Application_1_DB_fff3b084e2104326a6bdf065cc1bddfe failed in event OnBackupComplete. For more information, see
the spbackup.log or sprestore.log file located in the backup directory.
    Aborted due to error in another component.
[10/01/2012 15:06:12] FatalError: Object Admin (C: on SharePoint) failed in event OnBackupComplete. For more information, see the spbackup.log or sprestore.log file
located in the backup directory.
    Aborted due to error in another component.
[10/01/2012 15:06:13] FatalError: Object Search_Service_Application_1_CrawlStoreDB_1efdf6e816ac49afa9187bbe008f4ba9 failed in event OnBackupComplete. For more
information, see the spbackup.log or sprestore.log file located in the backup directory.
    Aborted due to error in another component.
[10/01/2012 15:06:13] FatalError: Object Crawl-0 (C: on SharePoint) failed in event OnBackupComplete. For more information, see the spbackup.log or sprestore.log file
located in the backup directory.
    Aborted due to error in another component.
[10/01/2012 15:06:15] FatalError: Object Search_Service_Application_1_PropertyStoreDB_45c02022f59f474f951968c1af057ae0 failed in event OnBackupComplete. For more
information, see the spbackup.log or sprestore.log file located in the backup directory.
    Aborted due to error in another component.
[10/01/2012 15:06:16] FatalError: Object Query-0 (C: on SharePoint) failed in event OnBackupComplete. For more information, see the spbackup.log or sprestore.log file
located in the backup directory.
    Aborted due to error in another component.
[1/10/2012 3:06:22 PM] Progress: Completed with errors and warnings, please refer to the log file for details.
[1/10/2012 3:06:22 PM] Finished with 72 warnings.
[1/10/2012 3:06:22 PM] Finished with 16 errors.
[1/10/2012 3:06:22 PM] FatalError: Backup failed for Object Query-0 (C: on SharePoint) failed in event OnBackupComplete. For more information, see the spbackup.log or
sprestore.log file located in the backup directory.
Hopefully you can make more sense of it than me.
Regards,
Stephen

Creation of SharePoint Search service with the help of powershell.

Hi Team,
Upgraded WSS 3.0 to SharePoint 2013 Foundation red the SharePoint search.
We found log backup on the subjected server was failing due to database name,
which is more than max allowed legth. To fix the same, we may need to rename the
same to short name.
failed-1073548784)
Executing the query "BACKUP LOG [Search_Service_Application_AnalyticsRe..."
failed with the following error: "Invalid device name. The length of the
device name provided exceeds supported limit (maximum length is:259). Reissue
the BACKUP statement with a valid device name.
BACKUP LOG is terminating
abnormally."
Database Name :
Search_Service_Application_AnalyticsReportingStoreDB_2e7b13e23fde4c8397ed0be06474966f
To rename SharePoint Search it took more than 5 hours.
Is it possible to create SharePoint search using PowerShell and will get support from Microsoft for search application built this way ?
Please share information on how create SharePoint search using powershell.
Our environment: SharePoint 2013 Foundation.
Best Regards,
Mahesh

Hi Mahesh,
To create Search Service Application in SharePoint Foundation 2013 by using PowerShell, you can refer to the links below for more details:
http://www.andrewjbillings.com/sharepoint-2013-foundation-creating-the-search-service-with-powershell-and-removing-those-pesky-guids/
http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
Best regards,
Victoria Xia
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint writer metadata information in a SharePoint farm with multiple WFE servers.

I am working on Microsoft Volume Shadow Copy Service (VSS) framework. I know that in a 3-Tier SharePoint environment the SharePoint writer metadata on WFE server gives all the information related to that farm.
My question is -
a) How would i get all the information related to the SharePoint farm from the SharePoint writer metadata in an environment where multiple WFE servers are configured?
b) Is it possible that in a SharePoint farm where multiple WFE servers are deployed, SP writer of only one WFE server (Master/Main server) contains all the information about the respective SP farm servers in its metadata?

Hi Aaditya,
All Writer Metadata is stored in Writer Metadata Document which is produced by writer. The backup application uses the Writer Metadata document to get information about that writer, the data it owns,
and how to restore that data. Once the writer produces it, the Writer Metadata Document is a read-only document to the backup application.
The Writer Metadata Document contains three sets of data: writer identification and classification information, writer-level specifications, and component data.
For getting Writer Metadata, you can use
IVssBackupComponents::GetWriterMetadata method.
For more information, you can refer to the articles:
http://msdn.microsoft.com/en-us/library/aa384992(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/aa384996(v=vs.85).aspx
http://blogs.technet.com/b/dpm/archive/2011/06/02/explaining-sharepoint-data-source-enumeration-with-data-protection-manager-2010.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Sharepoint full farm backup generates sql logs for search application differential backups

We are running full farm backups for sharepoint. Backup completes normally but SQL logs are generated for differential backups for search service application.
it says something like:
Database differential changes were backed up: database: search_serv.......
Thanks,
Basit

This can happen for a few reasons, such as is disk contention or network issues. Are you backing up to a shared directory on the SQL Server? If not, try that.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2010 backup and restore to test SharePoint environment - testing Disaster recovery

We have a production SharePoint 2010 environment with one Web/App server and one SQL server.
We have a test SharePoint 2010 environment with one server (Sharepoint server and SQL server) and one AD (domain is different from prod environment).
Servers are Windows 2008 R2 and SQL 2008 R2.
Versions are the same on prod and test servers.
We need to setup a test environment with the exact setup as production - we want to try Disaster recovery.
We have performed backup of farm from PROD and we wanted to restore it on our new server in test environment.Backup completed successfully with no errors.
We have tried to restore the whole farm from that backup on test environment using Central administration, but we got message - restore failed with errors.
We choosed NEW CONFIGURATION option during restore, and we set new database names...
Some of the errors are:
FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified user or domain group was not found.
Warning: Cannot restore object User Profile Service Application because it failed on backup.
FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
Verbose: Starting object: WSS_Content_IT_Portal.
Warning: [WSS_Content_IT_Portal] A content database with the same ID already exists on the farm. The site collections may not be accessible.
FatalError: Object WSS_Content_IT_Portal failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified component exists. You must specify a name that does not exist.
Warning: [WSS_Content_Portal] The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
RESTORE DATABASE is terminating abnormally.
FatalError: Object Portal - 80 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname.
FatalError: Object Access Services failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: Object parent could not be found. The restore operation cannot continue.
FatalError: Object Secure Store Service failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified component exists. You must specify a name that does not exist.
FatalError: Object PerformancePoint Service Application failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: Object parent could not be found. The restore operation cannot continue.
FatalError: Object Search_Service_Application_DB_88e1980b96084de984de48fad8fa12c5 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
Aborted due to error in another component.
Could you please help us to resolve these issues?

I'd totally agree with this. Full fledged functionality isn't the aim of DR, getting the functional parts of your platform back-up before too much time and money is lost.
Anything I can add would be a repeat of what Jesper has wisely said but I would very much encourage you to look at these two resources: -
DR & back-up book by John Ferringer for SharePoint 2010
John's back-up PowerShell Script in the TechNet Gallery
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Unable to create web app with PowerShell - An update conflict has occurred

I am trying to create a new Web Application using PowerShell. I need to use PowerShell because I need to create the Web App using classic authentication and not Claims authentication. the first time I created the Web App, everything went great. Ever since
the first time, I get an error and the web app creation does not complete. Just as an FYI, I can create a new Web App using Central Admin, but that creates it with Claims authentication which I cannot use.
Here is my PowerShell script
New-SPWebApplication -Name "SharePoint2013 (82)" -ApplicationPool "SharePoint2013-82" -AuthenticationMethod "NTLM" -ApplicationPoolAccount (Get-SPManagedAccount "GLOBAL\SP_AppPool") -Port 82 -URL "http://sharepoint2013"
Here is the error I get in PowerShell
New-SPWebApplication : An update conflict has occurred, and you must re-try this action. The object SPWebApplication
Name=SharePoint2013 (82) was updated by DOMAIN\SP_Administrator, in the powershell (13020) process, on machine SPWEB01.
View the tracing log for more information about the conflict.
At line:1 char:1
+ New-SPWebApplication -Name "SharePoint2013 (82)" -ApplicationPool "SharePoint201 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...PWebApplication:SPCmdletNewSPWebApplication) [New-SPWebA
pplication], SPUpdatedConcurrencyException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWebApplicationUnknown SQL Exception 547 occurred. Additional error information from SQL Server is included below.
The DELETE statement conflicted with the REFERENCE constraint "FK_Dependencies1_Objects". The conflict occurred in database "SP_Config", table "dbo.Dependencies", column 'ObjectId'.
The statement has been terminated.
I also get this error from the trace
Unknown SQL Exception 547 occurred. Additional error information from SQL Server is included below.
The DELETE statement conflicted with the REFERENCE constraint "FK_Dependencies1_Objects". The conflict occurred in database "SP_Config", table "dbo.Dependencies", column 'ObjectId'.
The statement has been terminated.
I have tried to resolve the issue by performing the following:
Delete the partially created web app using Central Admin or PowerShell
Clear the file system cache on all servers in the farm (Stopping wss timer job, Saving Copy of the
cache.ini file from C:\Documents and Settings\All Users\application data\Microsoft\SharePoint\Config folder. Clearing all the .xml files from the location except cache.ini but Edit the cache.ini to have value 1. Starting the timer job)
Use Products Configuration Wizard (no detach, just 'upgrade') - People have said to select the option to disconnect the server from server farm and revert back again at next step (so you actually do not disconnect), but there is no next step that I have
encountered. You select 'disconnect', hit next, and the server disconnects.
Restart all the servers in the farm
Run the PowerShell script again...still get the same error
I have tried it on multiple servers in the farm too.

Hi Michael,
I found a similar thread for you reference:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/9ccef7bf-87a9-4849-b086-4db2d898f1d7/cannot-create-new-web-application-wss-30?forum=sharepointadminlegacy
If it doesn’t work, sometimes the issue might be caused by long time keep powershell opening and generating some cache files. So please try re-opening the powershell and test the issue again.
http://blogs.msdn.com/b/ronalg/archive/2011/06/24/mount-spcontentdatabase-errors-on-2nd-and-subsequent-attempts-of-same-database.aspx?Redirected=true
http://www.oakwoodinsights.com/sharepoint-powershell-surprise/
In addition, here is an article which explains the possible reason of the SQL error:
http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Set multi user column with PowerShell used to work in 2010 but no longer works in 2013

In SharePoint 2010 I used PowerShell to set the value of multi user people columns and it worked really well. I attempt to use the same PowerShell to set the same column type in SharePoint 2013 and it fails.
here is the PowerShell that I use in 2010:
$web = Get-SPWeb "http://intranet"
$list = $web.lists["TestList"]
$item = $list.items.add()
$item["Title"] = "Test multi user column"
$users = @("Domain\user1", "Domain\user2")
$userList = new-object Microsoft.SharePoint.SPFieldUserValueCollection
foreach($user in $users)
$spUser = $web.EnsureUser($user)
$userValue = new-object Microsoft.SharePoint.SPFieldUserValue($web, $spUser.ID, $spUser.Name)
$userList.Add($userValue)
$item["MultiUserColumn"] = $userList
$item.update()
I have used this on three SharePoint 2013 farms with differing results. On two of them I receive an error when running $item.update(): Exception calling "Update" with "0" argument(s): "Invalid look-up value. A look-up
field contains invalid data. Please check the value and try again."
If I take one of the users out of the $users list then it works fine, but it will not allow multiple users to be set with PowerShell. I can use the GUI to add more than one user but not PowerShell.
Does anyone know if these methods have changed in 2013? I haven't been able to find anyone else with this issue.
mmm... coffee...

Not sure but maybe something to do with casting. Below is the code snippet from one of the blogs. Try modifying your script like below and see if still you get the error
[Microsoft.SharePoint.SPFieldUserValueCollection]$lotsofpeople = New-Object Microsoft.SharePoint.SPFieldUserValueCollection
$user1 = $w.EnsureUser("domain\user1");
$user1Value = New-Object Microsoft.SharePoint.SPFieldUserValue($w, $user1.Id, $user1.LoginName)
$user2 = $w.EnsureUser("domain\user2");
$user2Value = New-Object Microsoft.SharePoint.SPFieldUserValue($w, $user2.Id, $user2.LoginName);
$lotsofpeople.Add($user1Value);
$lotsofpeople.Add($user2Value);
$i["lotsofpeoplefield"] = $lotsofpeople;
$i.Update();
#-or-
$l.Fields["lotsofpeoplefield"].ParseAndSetValue($i,$lotsofpeople);
$i.Update();
Reference to the link
http://social.technet.microsoft.com/wiki/contents/articles/20831.sharepoint-a-complete-guide-to-getting-and-setting-fields-using-powershell.aspx
Geetanjali Arora | My blogs |

Content Database removed from protected SharePoint Farm

Hi,
We have a SharePoint 2007 farm protected with DPM 2012. We have removed a content database and now DPM is complaining about it, which is the expected behaviour in order to get noticed of accidentally missing databases. According to several sources, the right
way to get rid of these alerts is to stop protection - retaining data - and reprotecting it using the same parameters, so the DPM agent finds the retained data as a starting point.
However, our farm has about 4Tb allocated and we have less than 1 additional Tb free now in the DPM Pool, so if we stop protection and retain data, DPM will complain about the farm not fitting in that Tb (looks like DPM does not take into account that pertinent
data exists previously when estimating the replica and shadow sizes), so we will not be able to protect the farm again if we stop protection retaining data.
Funny, eh? any suggestions? Thanks in advance.

Hi,
When you stop protection and retain the replica, DPM will move the sharepoint data source into an inactive protection group. When you re-protect the same sharepoint farm, DPM will first query the inactive protection group to see if a replica exists
for that data source and if so will reuse that replica. It will then do a consistency check to bring the replica up to date, then resume normal backups. Be sure the use the same recovery goals if you are not adding it back to the same protection group.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

When Deploying SharePoint 2010 solution using Powershell gives me nothing

When Deploying SharePoint 2010 solution using Powershell gives me nothing
And when go to Central Admin >> System Settings >> Farm Management >> Manage Farm Solution
I found my Solution Status is Deploying and still deploying and nothing.

Hi,
According to your description, my understanding is when you deploy the SharePoint solution, the deploy status stuck on the deploying status.
To resolve this issue, I suggest you can do as the followings:
1. On any server, start, run, services.msc, enter, this will open the services console.
2. Now type s, this will give you all the services that start with S, look for SharePoint timer service and make sure it’s in started mode.
3. This service should be started on all the front ends as well as application server.
More information:
Solution deployment stuck on deploying: SharePoint 2010
Thanks
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

How to Prevent SharePoint Farm Password from Changing

I have been trying to stop the SP farm account, spfarm, from password changing. SharePoint Central Administration is used and I go to Central Security -> Configure managed accounts. I set spfarm not to change but it makes no difference.
It still changes. When that happens it screws up the SharePoint VSS Writer service account and backups fail (the password synch script has to run to fix). When the setting in SP CA is changed to allow password changes, the SharePoint VSS Writer
service account still has a problem and backups fail.
Additionally, I have run the two below scripts when necessary to try to correct the problem and it works until the password changes again. It seems as though the password changes whenever the server restarts or at least once every week or so.
Can anyone help me with this? I don't care if the password changes on a schedule as long as it doesn't cause the SharePoint VSS Writer service to fail during backup.
Repair-SPManagedAccountDeployment (This checks synch of passwords)
set-spmanagedAccount -UseExistingPassword
This is on a Windows Small Business Server 2011, which runs SharePoint 2010.
Tony

Hi Tony,
In SBS 2011, use 3 different accounts to run Windows SharePoint Foundation. The accounts are spfarm (SharePoint
Farm Account), spsearch, and spwebapp. For security reasons the passwords on these accounts are periodically reset. The password for spfarm is reset every 7 days that the Windows SBS Manager service is running.
à
How to Prevent SharePoint Farm Password from Changing
I will suggest that set the password expiry to be longer (such as: a month or 365 days or even more) and apply
it. Maybe a workaround.
By the way, the Windows SBS Manager service manages the spfarm account. This spfarm account will be found under
MyBusiness-> Users-> SBS Users in ADUC. If you navigate to the spfarm account in ADUC and open the Properties of it, then select
“Password never expires” under Account options in Account tab. Please check if this can help you to achieve target.
Hope this helps.
Best regards,
Justin Gu

Trying to link SharePoint 2010 Enterprise with SharePoint 2013 Search Server raises error

Hi,
I am currently working for a multinational who has SharePoint 2010 Enterprise Edition installed, 2 WFE SERVERS, 3 APP SERVERS, 1 DB SERVER. They also installed SharePoint 2013 Exterprise recently.
   Microsoft have recently come in and set up the SharePoint 2013 Search Server to crawl content in SharePoint 2010 as the replacement search to SharePoint 2010 Search. So they have gone through process of certificates and permissions
setups I guess. I was told it was working, but recently failed. When I type in the search box on a web site for SharePoint 2010 I get the message:
         The search request was unable to connect to the Search Service.
I checked the Event log and the Critical error (in Task Category:Timer) I get is the notorious:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID fa882704-80d9-415b-9b9d-eae5e9bdefd4) threw an exception. More information is included below.
        The search service is not able to connect to the machine that hosts the administration
        component. Verify that the administration component 'e9172a05-22ec-4904-9508-
        e5431a180c2b' in search application 'Search_Service_Application' is in a good state and
        try again.
I know administration component is the crawler. I am assuming this is permissions.
The SharePoint 2013 Search Server is picking up SharePoint 2010 site collections items fine i.e. The SharePoint 2013 search shows items from 2010 as expected.
On the SharePoint 2010 central admin box the search service enabled and running (checked with powershell). (SharePoint Server Search 14)
The Search Service id: e9172a05-22ec-4904-9508-e5432a180c2b
I also get the message in event log for gatherer on SharePoint 2010 CA and Search Server:
       Could not access the Search database. A generic error occurred while trying to access the database to obtain
       the schema version info.
       Context: Application 'e9172a05-22ec-4904-9508-e5431a180c2b'
Details:
            (0x80040e09)
Is this permissions to delete something from crawler??????
I would appreciate if someone could help on this. I have tried to be as concise as possible.
Thanks.
John.

It was a case that someone had fiddled with the Service App Associations. Hadn't ticked SharePoint 2013 search. Was still point at 2010. Thanks.
The SharePoint 2013 Search works correctly for SharePoint 2010.
Can someone confirm that the Search Service Application on SharePoint 2010 still needs to exist and hence SharePoint Server Search 14 Service still needs to be running? I am guessing it would as you search from 2010 interface not 2013. I am getting a critical
error in the Event Viewer:
CrawlReportJobDefinition (Id <SharePoint 2010 Crawler>)
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component <crawler id> in search application "Search Service Application" is in a good state and try
again.
I think this is related to the fact we have SharePoint 2013 doing the search instead of 2010.
Any ideas?
John.

Can you install Workflow Manager 1.0 on Central Admin App Server Machine in 3-tier SharePoint Farm?

Hi,
I have just realised when looking at doing a Workflow that 2013 Workflows not available (you need to install Workflow Manager Farm). I understand why from a tenant installation perspective, but we are on-premise.
Can someone tell me if I can install Workflow Manager 1.0 (seen you have to now install WM 1.0 Refresh version) on the Central Admin App Server Machine in a 3 tier SharePoint farm. 3 WFE, 4 APP Servers, 1 DB Server and 1 DB Analysis Services Server.
I did test on a test farm 1WFE, 1 APP Server (with CA) and 1 Database Server. We are getting issues with the WFE Server having issues booting up or losing connection - possibly faulty network card. This may in no way be related to the install,
but just in case.
Any help appreciated.
Thanks.
John.

Yes, you can install WFM on any server in a SharePoint farm.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Sharepoint Farm backup with powershell timeout

Similar Messages

Maybe you are looking for