Problem Using EM Scheduler To Backup

ShandyShandy Posts: 3
edited February 21, 2005 9:42AM in SQL Backup Previous Versions
I get the following error message when performing a scheduled backup via EM. The command to run SQL Backup is pasted from the script window and works when I run it from within SQL Backup.
21/02/2005 18:07:54: SQL Backup 3.0.0, (c) Red Gate Software Ltd 2004 - 2005
21/02/2005 18:07:54:
21/02/2005 18:07:54: Backing up OnTimeDB (full database) to H:\Andy\Backup\MyDocuments\OnTime\2005\Backup\FULL_(local)_OnTimeDB_Daily_Backup.sqb ...
21/02/2005 18:07:54:
21/02/2005 18:07:54: BACKUP DATABASE [OnTimeDB] TO DISK = 'H:\Andy\Backup\MyDocuments\OnTime\2005\Backup\FULL_(local)_OnTimeDB_Daily_Backup.sqb' WITH NAME = 'Database (OnTimeDB), 21/02/2005 17:58:35', DESCRIPTION = 'Backup on 21/02/2005 17:58:35 Database: OnTimeDB Instance: (local) Server: SUTTONALAPTOP', INIT, VERIFY, MAILTO = '[email protected]', COMPRESSION = 1
21/02/2005 18:07:54:
21/02/2005 18:07:54: osql -S SUTTONALAPTOP -Q "BACKUP DATABASE [OnTimeDB] TO VIRTUAL_DEVICE = 'SQLBACKUP_195226580' WITH BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = 'Database (OnTimeDB), 21/02/2005 17:58:35', DESCRIPTION = 'Backup on 21/02/2005 17:58:35 Database: OnTimeDB Instance: (local) Server: SUTTONALAPTOP', FORMAT" -b -w 120 -U sa -P martins
21/02/2005 18:07:54: Thread 0 error: Error creating backup file(s). No files could be created.
Thread 0 warning:
Warning 600: Error creating backup file: H:\Andy\Backup\MyDocuments\OnTime\2005\Backup\FULL_(local)_OnTimeDB_Daily_Backup.sqb. Error message: Cannot create file "H:\Andy\Backup\MyDocuments\OnTime\2005\Backup\FULL_(local)_OnTimeDB_Daily_Backup.sqb". The system cannot find the path specified
Any idea what the issue might be? H is a mapped network drive. I am using XP Pro/MSDE 2000 and the server where the mapped drive is W2000. I have full rights to the share and folder I am trying to create the backup in.
Shandy, Microsoft VB MVP, vbCity Leader

Comments

  • It occurred to me half way home that was what the issue was or more probably the H drive was not mapped the same ;-) It had been a long day ...
    Shandy, Microsoft VB MVP, vbCity Leader
Sign In or Register to comment.