Unix Technical Forum

Backup Names

This is a discussion on Backup Names within the SQL Server forums, part of the Microsoft SQL Server category; --> Okay, here is a real mellon scratcher. I've got a server I've got semi-automated backups on. A typical backup ...


Go Back   Unix Technical Forum > Database Server Software > Microsoft SQL Server > SQL Server

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-01-2008, 02:54 PM
Utahduck
 
Posts: n/a
Default Backup Names

Okay, here is a real mellon scratcher. I've got a server I've got
semi-automated backups on. A typical backup looks like:

BACKUP DATABASE Master
TO DISK = 'c:\backups\Master20070418.bak'
WITH FORMAT

Then I'll do a log backup if applicable (Not for Master). I then get
some error about the device being offline. But if I run:

BACKUP DATABASE Master
TO DISK = 'c:\backups\Master20070418.log'
WITH FORMAT

then it works fine. The ONLY thing I've changed is the extension on
the backup file. But that is what I wanted to name the log. As a
workaround I have the backups saved as:

Master20070418-bak.log and then name the log files the way they should
be. That works, but I don't like it.

Security is full access to Everyone, so I don't think it is an access/
permissions issue.

Any ideas?

Thanks,
-Utah

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 03-01-2008, 02:54 PM
Erland Sommarskog
 
Posts: n/a
Default Re: Backup Names

Utahduck (Utahduck@hotmail.com) writes:
> Okay, here is a real mellon scratcher. I've got a server I've got
> semi-automated backups on. A typical backup looks like:
>
> BACKUP DATABASE Master
> TO DISK = 'c:\backups\Master20070418.bak'
> WITH FORMAT
>
> Then I'll do a log backup if applicable (Not for Master). I then get
> some error about the device being offline. But if I run:
>
> BACKUP DATABASE Master
> TO DISK = 'c:\backups\Master20070418.log'
> WITH FORMAT
>
> then it works fine. The ONLY thing I've changed is the extension on
> the backup file. But that is what I wanted to name the log. As a
> workaround I have the backups saved as:


I'm not sure that I follow. I think what happens is that you run a
BACKUP LOG statement (which you don't show), and this yields an error
(which you don't show).

Maybe you could clarify by posting the actual command that is
causing you problem and the error message?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 06:36 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com