One full backup job to run full backup of all databases and it failed. I post error message.Any help?

Question

Executed as user: abc\user1. ... 2004-2009, Quest Software Inc. Registered Name: abc INC 
Processed 1152 pages for database 'abc123', file 'abc123' on file 1. Processed 4 pages for database 'abc123', file 'abc123_log' on file 1. BACKUP DATABASE successfully processed 1156 pages in 0.725 seconds (13.051 MB/sec). 
Backup added as file number: 1  Native Size: 11.19 MB Backup Size: 1.87 MB CPU Seconds: 0.27 [SQ 
The backup set on file 1 is valid.  CPU Seconds: 0.25 [SQLSTATE 01000] (Message 1) 
LiteSpeed(R) for SQL Server Version 5.1.0.1293 Copyright 2004-2009, Quest Software Inc. Registered Name: abc INC 
Processed 456 pages for database 'WSS_Search_abc1', file 'WSS_Search_abc1' on file 1. Processed 24 pages for database 'WSS_Search_abc1', file 'WSS_Search_abc1_Data2' on file 1. Processed 1 pages for database 'WSS_Search_abc1', file 'WSS_Search_abc1_log'
...  The step failed.

Answer 1

Hi bestrongself,
Before you use a SQL Server Agent job to back up all database, I recommend you run the backup statement in query windows directly, and check if it can run well. I do a test by using the following statement,
DECLARE @name VARCHAR(50) -- database name
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @fileName VARCHAR(256) -- filename for backup
DECLARE @fileDate VARCHAR(20) -- used for file name
-- specify database backup directory
SET @path = 'C:\Backup\'
-- specify filename format
SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112)
DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb') -- exclude these databases
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name
WHILE @@FETCH_STATUS = 0
BEGIN
SET @fileName = @path + @name + '_' + @fileDate + '.BAK'
BACKUP DATABASE @name TO DISK = @fileName
FETCH NEXT FROM db_cursor INTO @name
END
CLOSE db_cursor
DEALLOCATE db_cursor
the script allow you to backup each database within your instance of SQL Server. 
Your account  need to have read and right permission to the path file.
If the above script can run well directly, then you can create a job and put your backup statement inside of it. There is a similar detail about how to create a simple backup job in SQL Server. You can review it.
http://www.petri.co.il/create-backup-job-in-sql-server.htm
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support