Jobs Simply Not Executing and No Warnings - Veritas Backup Exec
This is a discussion on Jobs Simply Not Executing and No Warnings - Veritas Backup Exec ; I am completely frushtrated with this software. We upgraded from 8.5 to 8.6
for the backup to file feature. What a mistake. For example, we now have
trouble restoring and backing up SQL Server across a firewall because you
cannot ...
-
Jobs Simply Not Executing and No Warnings
I am completely frushtrated with this software. We upgraded from 8.5 to 8.6
for the backup to file feature. What a mistake. For example, we now have
trouble restoring and backing up SQL Server across a firewall because you
cannot connect to a SQL Server 2000 unless you have a name associated with
it, ie, you cannot use IP addresses.
Now down to the real problem. We are experiencing serious trouble. Our
backups will run for many days flawlessly then, without warning, they simply
stop working. No notifications, nothing. When you stop the services, the
job engine gets hung up and you have to use the all powerful kill command.
Below is the last error message you get before the suspended animation
problem occurs. Again, no notifications (including positive, which is the
only method to determine that a problem occured), nothing. When you pull up
the client, nothing refreshes properly as if it doesn't know what time a day
or what day of the month it is. Obviously a critical service is hanging the
whole BENT system.
Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 32770
Date: 6/6/2002
Time: 11:00:55 AM
User: N/A
Computer: HADES
Description:
A service specific error has occurred.
Backup Exec error: 6 SetServiceStatus
-
Re: Jobs Simply Not Executing and No Warnings
Just the same !!
It was working OK. I have done some updates (compaq/windows updates), and
it was over...
!! HELP !!
rgds,
Olivier Girard
"Walter Holm" wrote:
>I am completely frushtrated with this software. We upgraded from 8.5 to
8.6
>for the backup to file feature. What a mistake. For example, we now have
>trouble restoring and backing up SQL Server across a firewall because you
>cannot connect to a SQL Server 2000 unless you have a name associated with
>it, ie, you cannot use IP addresses.
>
>Now down to the real problem. We are experiencing serious trouble. Our
>backups will run for many days flawlessly then, without warning, they simply
>stop working. No notifications, nothing. When you stop the services, the
>job engine gets hung up and you have to use the all powerful kill command.
>Below is the last error message you get before the suspended animation
>problem occurs. Again, no notifications (including positive, which is the
>only method to determine that a problem occured), nothing. When you pull
up
>the client, nothing refreshes properly as if it doesn't know what time a
day
>or what day of the month it is. Obviously a critical service is hanging
the
>whole BENT system.
>
>Event Type: Error
>Event Source: Backup Exec
>Event Category: None
>Event ID: 32770
>Date: 6/6/2002
>Time: 11:00:55 AM
>User: N/A
>Computer: HADES
>Description:
>A service specific error has occurred.
>Backup Exec error: 6 SetServiceStatus
>
>
>