June 27, 2008 at 5:16 am
Hi everyone,
When I configure auto backup through maintenance plans but it
does work? Please give me some idea to configure.
Thanks,
Sunil
June 27, 2008 at 6:50 am
What error are you getting?
Gethyn Elliswww.gethynellis.com
June 27, 2008 at 7:02 am
Here are a few questions that you may need to answer:
Are there any messages being written to the SQL Log/ SQL Agent Log?
Is the SQL Agent running?
What is the SQL Agent running under (Local System, Domain account etc.)?
Are you writing the backup to a path to which the SQL Agent does not have permission?
Is there sufficient space for the backup?
Regards,
Regards,
Phil
June 27, 2008 at 7:11 am
Wonderful Phil 🙂 Adding to that also apply the latest service pack i.e SP2 for Sql Server 2005.
[font="Verdana"]- Deepak[/font]
June 27, 2008 at 10:43 am
What version of SQL are you using, I have noticed that on 2005 maintenance plans the backup will run without error but will not backup db's set to lower compatability?
June 28, 2008 at 6:54 am
Hi,
No any message written to the SQL Log/ SQL Agent Log.
yes, the SQL Agent running.
SQL Agent running under Local System.
Yes there is sufficient space for the backup.
but how to check the permission for following question --
Are you writing the backup to a path to which the SQL Agent does not have permission?
June 28, 2008 at 2:35 pm
can you backup the database manually...i.e. not through maintenace plan?
Also what's the compability mode of the database?
Gethyn Elliswww.gethynellis.com
June 28, 2008 at 5:31 pm
By the way: Which EDITION/version of SQL are you using
Are you backing up to the default Location or Other Location than \MSSQL\Backups Folder.
If you have different location, Pl check your PErmissions to the FOLDER. by right click on the Folder and Security. Check if the Service account Running the SQL Agent has access to this location.
Change your SQL Agent Service Account to domain Account, if you store the Backup across Servers.
Maninder
www.dbanation.com
June 28, 2008 at 10:32 pm
[font="Verdana"]Hi,
Add a log file to the job and then try executing it, if it fails then analyze the log file, you will get some information.
You can also try the alternative to take backup through script, check the link below
Backup Script with Retention[/url][/font]
Regards..Vidhya Sagar
SQL-Articles
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply