are backups not successful?

Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980s
Hi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer

are backups not successful?

Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killersql

are backups not successful?

Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
--
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer

append backups and other mtn plan stuff

Hello:
I am editing a backup maintenance plan. For some reason, the plan is doing
an append backup. I realize that the word "Append" appears in the window.
But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas o
n
how to fix this so that it will do a full backup rather than an Append?
Also, what is the difference between "Target server connection" and "Local
server
connection" when configuring maintenance plans?
Upon reviewing the .bak files in Windows Explorer where the maintenance
plans are placing database backups, I noticed the letter "A" in the Attribut
e
column. Does this mean that the backup job was an "Append" job?
I temporarily disabled my maintenance plans and re-enabled them this AM. In
SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the en
d
of the name of my jobs. Why is that, and is that "bad"?
Thanks!
childofthe1980sHi
"childofthe1980s" wrote:

> Hello:
You don't give the version you are using, have you applied SP2 and the
hotfixes?

> I am editing a backup maintenance plan. For some reason, the plan is doin
g
> an append backup. I realize that the word "Append" appears in the window.
> But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas
on
> how to fix this so that it will do a full backup rather than an Append?
The append/overwrite option is applicable when you choose the file/files to
backup to rather than the directory option.
You can create a maintenance cleanup task to remove unwanted files.

> Also, what is the difference between "Target server connection" and "Local
> server
> connection" when configuring maintenance plans?
A new connection must have been created with this name look at the manage
connections option in the maintenance plan designer to see the properties of
each one.

> Upon reviewing the .bak files in Windows Explorer where the maintenance
> plans are placing database backups, I noticed the letter "A" in the Attrib
ute
> column. Does this mean that the backup job was an "Append" job?
No the A is the archive file attribute.

> I temporarily disabled my maintenance plans and re-enabled them this AM.
In
> SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the
end
> of the name of my jobs. Why is that, and is that "bad"?
Not sure but it will only be part of the job description.

> Thanks!
> childofthe1980s
HTH
John

append backups and other mtn plan stuff

Hello:
I am editing a backup maintenance plan. For some reason, the plan is doing
an append backup. I realize that the word "Append" appears in the window.
But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas on
how to fix this so that it will do a full backup rather than an Append?
Also, what is the difference between "Target server connection" and "Local
server
connection" when configuring maintenance plans?
Upon reviewing the .bak files in Windows Explorer where the maintenance
plans are placing database backups, I noticed the letter "A" in the Attribute
column. Does this mean that the backup job was an "Append" job?
I temporarily disabled my maintenance plans and re-enabled them this AM. In
SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the end
of the name of my jobs. Why is that, and is that "bad"?
Thanks!
childofthe1980sHi
"childofthe1980s" wrote:
> Hello:
You don't give the version you are using, have you applied SP2 and the
hotfixes?
> I am editing a backup maintenance plan. For some reason, the plan is doing
> an append backup. I realize that the word "Append" appears in the window.
> But, it is grayed out. So, I cannot edit it and choose "Full". Any ideas on
> how to fix this so that it will do a full backup rather than an Append?
The append/overwrite option is applicable when you choose the file/files to
backup to rather than the directory option.
You can create a maintenance cleanup task to remove unwanted files.
> Also, what is the difference between "Target server connection" and "Local
> server
> connection" when configuring maintenance plans?
A new connection must have been created with this name look at the manage
connections option in the maintenance plan designer to see the properties of
each one.
> Upon reviewing the .bak files in Windows Explorer where the maintenance
> plans are placing database backups, I noticed the letter "A" in the Attribute
> column. Does this mean that the backup job was an "Append" job?
No the A is the archive file attribute.
> I temporarily disabled my maintenance plans and re-enabled them this AM. In
> SQL Server Agent, I noticed that the phrase ".Subplan" appears not at the end
> of the name of my jobs. Why is that, and is that "bad"?
Not sure but it will only be part of the job description.
> Thanks!
> childofthe1980s
HTH
John