When attempting to restore a database using the SQL Backup GUI, you encounter the following error messages:
Error 507: No valid backup sets found from provided folder(s).
DBCC CHECKDB: Database consistency check completed with errors.
SQL error 18456: Login failed for user 'sa'.
This particular issue with PCC Backups is due to the configuration of the restore job via the SQL Backup GUI. The job does not include the necessary keywords to correctly process the transaction logs provided by Point Click Care (PCC).
To resolve this issue and successfully restore your database, you need to modify the restore job syntax from the relevant SQL Server Instance via SQL Server Management Studio (SSMS). Follow the steps below to make the required changes:
-
Open SSMS
- Connect to your SQL Server instance using SSMS
-
Modify the Restore Job
- Locate the restore job that was created via the SQL Backup GUI
-
Edit the Syntax
- Remove the following keywords from the restore job script:
LATEST_ALL
SOURCE = 'PCC'
REPLACE
CHECKDB
- Change the command
RESTORE DATABASE
toRESTORE LOG
- Remove the following keywords from the restore job script:
By following these steps, you should be able to resolve the errors and successfully restore your database using the transaction logs provided by Point Click Care (PCC).
Was this article helpful?
Articles in this section
- Resolving Error 507 and SQL Error 18456 in PCC Backup Restores
- SQL Backup error 605
- SQL Backup Error: Cannot access resource
- SQL Error 3203
- Error - Cannot load the DLL xp_sqlbackup.dll, or one of the DLLs it references
- Failed to obtain the list of cluster nodes
- Log Copy Queue is stuck in SQL Backup
- SQL Backup Network Share Permissions Test
- SQL Backup troubleshooting
- Errors when running a scheduled job with SQL Backup