Hi:
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
John
Hi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John
|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>
>
|||See this old post:-
http://groups.google.co.in/group/mic...141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
|||Hi
No. Look at the backup job logs to see what is going on.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Thursday, March 29, 2012
Backup File Deletions not Working
Hi:
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>
>|||See this old post:-
http://groups.google.co.in/group/mi...4141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>
>|||See this old post:-
http://groups.google.co.in/group/mi...4141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>
Backup File Deletions not Working
Hi:
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> > Hi:
> >
> > We configured a backup job in the database maintenance plan for a database
> > for both "Complete Backup" and the "Transaction Log". We told the job to
> > delete files after one day. It has not been deleting these files, though.
> >
> > Why is that?
> >
> > John
>
>|||See this old post:-
http://groups.google.co.in/group/microsoft.public.sqlserver.server/browse_thread/thread/f24fa621edb472b/04141cc02159d2bc?lnk=st&q=maintenance+plan+not+deleting+old+files&rnum=4&hl=en#04141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> > Hi:
> >
> > We configured a backup job in the database maintenance plan for a database
> > for both "Complete Backup" and the "Transaction Log". We told the job to
> > delete files after one day. It has not been deleting these files, though.
> >
> > Why is that?
> >
> > John
>
>|||See this old post:-
http://groups.google.co.in/group/microsoft.public.sqlserver.server/browse_thread/thread/f24fa621edb472b/04141cc02159d2bc?lnk=st&q=maintenance+plan+not+deleting+old+files&rnum=4&hl=en#04141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>
Sunday, February 19, 2012
Backup / Restore script
One of my coworkers needs to programmatically ask a bunch of different SQL
Servers for the default location of where they are configured to put .BAK
files.
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave MustaneMike,
Use the BackupDirectory key.
HTH
Jerry
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:ebE3t010FHA.404@.TK2MSFTNGP09.phx.gbl...
> One of my coworkers needs to programmatically ask a bunch of different SQL
> Servers for the default location of where they are configured to put .BAK
> files.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||> Use the BackupDirectory key.
I'm not too sure what you mean, but if you mean a Windows Registry Key,
that's no good in this example. He's writing an automated backup utility
that will tell many different SQL Servers via ODBC to backup their
databases. Since his application does not run on the actual SQL servers, he
doesn't have access to their registries.
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane|||Mike,
Ok...try the SQL-DMO Backup Directory Property (in SQL BOL).
HTH
Jerry
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:OeYlsB20FHA.2888@.TK2MSFTNGP10.phx.gbl...
> I'm not too sure what you mean, but if you mean a Windows Registry Key,
> that's no good in this example. He's writing an automated backup utility
> that will tell many different SQL Servers via ODBC to backup their
> databases. Since his application does not run on the actual SQL servers,
> he doesn't have access to their registries.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||I agree that using DMO is the way to go. In case you absolutely can't do tha
t, you can use the
*unsupported and undocumented* xp_instance_regread extended proc. All usual
warnings apply:
http://www.sqldev.net/misc/SQLLocationFunctions.htm
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23aVzyR20FHA.2964@.TK2MSFTNGP10.phx.gbl...
> Mike,
> Ok...try the SQL-DMO Backup Directory Property (in SQL BOL).
> HTH
> Jerry
> "Mike Labosh" <mlabosh@.hotmail.com> wrote in message news:OeYlsB20FHA.2888
@.TK2MSFTNGP10.phx.gbl...
>
Servers for the default location of where they are configured to put .BAK
files.
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave MustaneMike,
Use the BackupDirectory key.
HTH
Jerry
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:ebE3t010FHA.404@.TK2MSFTNGP09.phx.gbl...
> One of my coworkers needs to programmatically ask a bunch of different SQL
> Servers for the default location of where they are configured to put .BAK
> files.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||> Use the BackupDirectory key.
I'm not too sure what you mean, but if you mean a Windows Registry Key,
that's no good in this example. He's writing an automated backup utility
that will tell many different SQL Servers via ODBC to backup their
databases. Since his application does not run on the actual SQL servers, he
doesn't have access to their registries.
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane|||Mike,
Ok...try the SQL-DMO Backup Directory Property (in SQL BOL).
HTH
Jerry
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:OeYlsB20FHA.2888@.TK2MSFTNGP10.phx.gbl...
> I'm not too sure what you mean, but if you mean a Windows Registry Key,
> that's no good in this example. He's writing an automated backup utility
> that will tell many different SQL Servers via ODBC to backup their
> databases. Since his application does not run on the actual SQL servers,
> he doesn't have access to their registries.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||I agree that using DMO is the way to go. In case you absolutely can't do tha
t, you can use the
*unsupported and undocumented* xp_instance_regread extended proc. All usual
warnings apply:
http://www.sqldev.net/misc/SQLLocationFunctions.htm
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23aVzyR20FHA.2964@.TK2MSFTNGP10.phx.gbl...
> Mike,
> Ok...try the SQL-DMO Backup Directory Property (in SQL BOL).
> HTH
> Jerry
> "Mike Labosh" <mlabosh@.hotmail.com> wrote in message news:OeYlsB20FHA.2888
@.TK2MSFTNGP10.phx.gbl...
>
Friday, February 10, 2012
backing up to an external drive
Hello:
About three weeks ago, I configured a "Complete Backup" and "Transaction Log
Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN files
to an external drive attached to the server through a USB port. These plans
run between 10 and 11 PM weeknights.
I tested these two plans before I left the client, that afternoon. The
backups were successful and I have reports that proved this.
Now, I reviewed the client's server remotely just today and found that only
the transaction logs backed up that night (10PM). The database backups did
not backup. And, that was the last time that the logs backed up.
I am going to review the SQL log report in a little while. But, why would
backups to an external drive (a mapped "Q" drive) work upon testing but
apparently stop working in production? Other than reviewing the report, is
there anything that I can do to get these backups to work?
Can the database maintenance plans simply not backup to an external drive?
Thanks!
childofthe1980s
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B46F190C-E2CF-4ABD-80D3-7C8A2F6C3AC2@.microsoft.com...
> Hello:
> About three weeks ago, I configured a "Complete Backup" and "Transaction
> Log
> Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN
> files
> to an external drive attached to the server through a USB port. These
> plans
> run between 10 and 11 PM weeknights.
> I tested these two plans before I left the client, that afternoon. The
> backups were successful and I have reports that proved this.
> Now, I reviewed the client's server remotely just today and found that
> only
> the transaction logs backed up that night (10PM). The database backups
> did
> not backup. And, that was the last time that the logs backed up.
> I am going to review the SQL log report in a little while. But, why would
> backups to an external drive (a mapped "Q" drive) work upon testing but
> apparently stop working in production? Other than reviewing the report,
> is
> there anything that I can do to get these backups to work?
I'm confused. Is this an external drive or a mapped drive?
In any case, if it's external, make sure the drive letter hasn't been
changed.
If it's mapped, you're far better off using UNCs.
> Can the database maintenance plans simply not backup to an external drive?
They can be. Bee there, done that.
> Thanks!
> childofthe1980s
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
About three weeks ago, I configured a "Complete Backup" and "Transaction Log
Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN files
to an external drive attached to the server through a USB port. These plans
run between 10 and 11 PM weeknights.
I tested these two plans before I left the client, that afternoon. The
backups were successful and I have reports that proved this.
Now, I reviewed the client's server remotely just today and found that only
the transaction logs backed up that night (10PM). The database backups did
not backup. And, that was the last time that the logs backed up.
I am going to review the SQL log report in a little while. But, why would
backups to an external drive (a mapped "Q" drive) work upon testing but
apparently stop working in production? Other than reviewing the report, is
there anything that I can do to get these backups to work?
Can the database maintenance plans simply not backup to an external drive?
Thanks!
childofthe1980s
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B46F190C-E2CF-4ABD-80D3-7C8A2F6C3AC2@.microsoft.com...
> Hello:
> About three weeks ago, I configured a "Complete Backup" and "Transaction
> Log
> Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN
> files
> to an external drive attached to the server through a USB port. These
> plans
> run between 10 and 11 PM weeknights.
> I tested these two plans before I left the client, that afternoon. The
> backups were successful and I have reports that proved this.
> Now, I reviewed the client's server remotely just today and found that
> only
> the transaction logs backed up that night (10PM). The database backups
> did
> not backup. And, that was the last time that the logs backed up.
> I am going to review the SQL log report in a little while. But, why would
> backups to an external drive (a mapped "Q" drive) work upon testing but
> apparently stop working in production? Other than reviewing the report,
> is
> there anything that I can do to get these backups to work?
I'm confused. Is this an external drive or a mapped drive?
In any case, if it's external, make sure the drive letter hasn't been
changed.
If it's mapped, you're far better off using UNCs.
> Can the database maintenance plans simply not backup to an external drive?
They can be. Bee there, done that.
> Thanks!
> childofthe1980s
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
backing up to an external drive
Hello:
About three weeks ago, I configured a "Complete Backup" and "Transaction Log
Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN file
s
to an external drive attached to the server through a USB port. These plans
run between 10 and 11 PM weeknights.
I tested these two plans before I left the client, that afternoon. The
backups were successful and I have reports that proved this.
Now, I reviewed the client's server remotely just today and found that only
the transaction logs backed up that night (10PM). The database backups did
not backup. And, that was the last time that the logs backed up.
I am going to review the SQL log report in a little while. But, why would
backups to an external drive (a mapped "Q" drive) work upon testing but
apparently stop working in production? Other than reviewing the report, is
there anything that I can do to get these backups to work?
Can the database maintenance plans simply not backup to an external drive?
Thanks!
childofthe1980s"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B46F190C-E2CF-4ABD-80D3-7C8A2F6C3AC2@.microsoft.com...
> Hello:
> About three weeks ago, I configured a "Complete Backup" and "Transaction
> Log
> Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN
> files
> to an external drive attached to the server through a USB port. These
> plans
> run between 10 and 11 PM weeknights.
> I tested these two plans before I left the client, that afternoon. The
> backups were successful and I have reports that proved this.
> Now, I reviewed the client's server remotely just today and found that
> only
> the transaction logs backed up that night (10PM). The database backups
> did
> not backup. And, that was the last time that the logs backed up.
> I am going to review the SQL log report in a little while. But, why would
> backups to an external drive (a mapped "Q" drive) work upon testing but
> apparently stop working in production? Other than reviewing the report,
> is
> there anything that I can do to get these backups to work?
I'm confused. Is this an external drive or a mapped drive?
In any case, if it's external, make sure the drive letter hasn't been
changed.
If it's mapped, you're far better off using UNCs.
> Can the database maintenance plans simply not backup to an external drive?
They can be. Bee there, done that.
> Thanks!
> childofthe1980s
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
About three weeks ago, I configured a "Complete Backup" and "Transaction Log
Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN file
s
to an external drive attached to the server through a USB port. These plans
run between 10 and 11 PM weeknights.
I tested these two plans before I left the client, that afternoon. The
backups were successful and I have reports that proved this.
Now, I reviewed the client's server remotely just today and found that only
the transaction logs backed up that night (10PM). The database backups did
not backup. And, that was the last time that the logs backed up.
I am going to review the SQL log report in a little while. But, why would
backups to an external drive (a mapped "Q" drive) work upon testing but
apparently stop working in production? Other than reviewing the report, is
there anything that I can do to get these backups to work?
Can the database maintenance plans simply not backup to an external drive?
Thanks!
childofthe1980s"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B46F190C-E2CF-4ABD-80D3-7C8A2F6C3AC2@.microsoft.com...
> Hello:
> About three weeks ago, I configured a "Complete Backup" and "Transaction
> Log
> Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN
> files
> to an external drive attached to the server through a USB port. These
> plans
> run between 10 and 11 PM weeknights.
> I tested these two plans before I left the client, that afternoon. The
> backups were successful and I have reports that proved this.
> Now, I reviewed the client's server remotely just today and found that
> only
> the transaction logs backed up that night (10PM). The database backups
> did
> not backup. And, that was the last time that the logs backed up.
> I am going to review the SQL log report in a little while. But, why would
> backups to an external drive (a mapped "Q" drive) work upon testing but
> apparently stop working in production? Other than reviewing the report,
> is
> there anything that I can do to get these backups to work?
I'm confused. Is this an external drive or a mapped drive?
In any case, if it's external, make sure the drive letter hasn't been
changed.
If it's mapped, you're far better off using UNCs.
> Can the database maintenance plans simply not backup to an external drive?
They can be. Bee there, done that.
> Thanks!
> childofthe1980s
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
backing up to an external drive
Hello:
About three weeks ago, I configured a "Complete Backup" and "Transaction Log
Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN files
to an external drive attached to the server through a USB port. These plans
run between 10 and 11 PM weeknights.
I tested these two plans before I left the client, that afternoon. The
backups were successful and I have reports that proved this.
Now, I reviewed the client's server remotely just today and found that only
the transaction logs backed up that night (10PM). The database backups did
not backup. And, that was the last time that the logs backed up.
I am going to review the SQL log report in a little while. But, why would
backups to an external drive (a mapped "Q" drive) work upon testing but
apparently stop working in production? Other than reviewing the report, is
there anything that I can do to get these backups to work?
Can the database maintenance plans simply not backup to an external drive?
Thanks!
childofthe1980s"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B46F190C-E2CF-4ABD-80D3-7C8A2F6C3AC2@.microsoft.com...
> Hello:
> About three weeks ago, I configured a "Complete Backup" and "Transaction
> Log
> Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN
> files
> to an external drive attached to the server through a USB port. These
> plans
> run between 10 and 11 PM weeknights.
> I tested these two plans before I left the client, that afternoon. The
> backups were successful and I have reports that proved this.
> Now, I reviewed the client's server remotely just today and found that
> only
> the transaction logs backed up that night (10PM). The database backups
> did
> not backup. And, that was the last time that the logs backed up.
> I am going to review the SQL log report in a little while. But, why would
> backups to an external drive (a mapped "Q" drive) work upon testing but
> apparently stop working in production? Other than reviewing the report,
> is
> there anything that I can do to get these backups to work?
I'm confused. Is this an external drive or a mapped drive?
In any case, if it's external, make sure the drive letter hasn't been
changed.
If it's mapped, you're far better off using UNCs.
> Can the database maintenance plans simply not backup to an external drive?
They can be. Bee there, done that.
> Thanks!
> childofthe1980s
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
About three weeks ago, I configured a "Complete Backup" and "Transaction Log
Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN files
to an external drive attached to the server through a USB port. These plans
run between 10 and 11 PM weeknights.
I tested these two plans before I left the client, that afternoon. The
backups were successful and I have reports that proved this.
Now, I reviewed the client's server remotely just today and found that only
the transaction logs backed up that night (10PM). The database backups did
not backup. And, that was the last time that the logs backed up.
I am going to review the SQL log report in a little while. But, why would
backups to an external drive (a mapped "Q" drive) work upon testing but
apparently stop working in production? Other than reviewing the report, is
there anything that I can do to get these backups to work?
Can the database maintenance plans simply not backup to an external drive?
Thanks!
childofthe1980s"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:B46F190C-E2CF-4ABD-80D3-7C8A2F6C3AC2@.microsoft.com...
> Hello:
> About three weeks ago, I configured a "Complete Backup" and "Transaction
> Log
> Backup" maintenance plan in SQL Server 2000 to funnel the .BAK and .TRN
> files
> to an external drive attached to the server through a USB port. These
> plans
> run between 10 and 11 PM weeknights.
> I tested these two plans before I left the client, that afternoon. The
> backups were successful and I have reports that proved this.
> Now, I reviewed the client's server remotely just today and found that
> only
> the transaction logs backed up that night (10PM). The database backups
> did
> not backup. And, that was the last time that the logs backed up.
> I am going to review the SQL log report in a little while. But, why would
> backups to an external drive (a mapped "Q" drive) work upon testing but
> apparently stop working in production? Other than reviewing the report,
> is
> there anything that I can do to get these backups to work?
I'm confused. Is this an external drive or a mapped drive?
In any case, if it's external, make sure the drive letter hasn't been
changed.
If it's mapped, you're far better off using UNCs.
> Can the database maintenance plans simply not backup to an external drive?
They can be. Bee there, done that.
> Thanks!
> childofthe1980s
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
Subscribe to:
Posts (Atom)