backup database (sql server backup) and files (nt backup)

Hi!
pls. advise, I need to backup some files on hard drive
using NT backup utility and SQL Server database (using sql
server db backups) to one tape. If I backup first some
folders and files with nt backup utility and then sql
server database, the sql server database cannot be
restored ("not a valid sql server backup"). In the other
case (first backed up sql server db then files using nt
backup) I am getting message "inconsistent media, do not
append to this tape"
How can I solve this?
You must use the SQL Server BACKUP command to create a backup file on disk
(or directly to tape) first. Then you can copy this file to tape. You can
not backup the sql files directly with a native NT backup.
Andrew J. Kelly SQL MVP
"Gabriel" <anonymous@.discussions.microsoft.com> wrote in message
news:12d3001c418b3$612a9610$a001280a@.phx.gbl...
> Hi!
> pls. advise, I need to backup some files on hard drive
> using NT backup utility and SQL Server database (using sql
> server db backups) to one tape. If I backup first some
> folders and files with nt backup utility and then sql
> server database, the sql server database cannot be
> restored ("not a valid sql server backup"). In the other
> case (first backed up sql server db then files using nt
> backup) I am getting message "inconsistent media, do not
> append to this tape"
> How can I solve this?

backup database (sql server backup) and files (nt backup)

Hi!
pls. advise, I need to backup some files on hard drive
using NT backup utility and SQL Server database (using sql
server db backups) to one tape. If I backup first some
folders and files with nt backup utility and then sql
server database, the sql server database cannot be
restored ("not a valid sql server backup"). In the other
case (first backed up sql server db then files using nt
backup) I am getting message "inconsistent media, do not
append to this tape"
How can I solve this?You must use the SQL Server BACKUP command to create a backup file on disk
(or directly to tape) first. Then you can copy this file to tape. You can
not backup the sql files directly with a native NT backup.
Andrew J. Kelly SQL MVP
"Gabriel" <anonymous@.discussions.microsoft.com> wrote in message
news:12d3001c418b3$612a9610$a001280a@.phx
.gbl...
> Hi!
> pls. advise, I need to backup some files on hard drive
> using NT backup utility and SQL Server database (using sql
> server db backups) to one tape. If I backup first some
> folders and files with nt backup utility and then sql
> server database, the sql server database cannot be
> restored ("not a valid sql server backup"). In the other
> case (first backed up sql server db then files using nt
> backup) I am getting message "inconsistent media, do not
> append to this tape"
> How can I solve this?

backup cannot make a copy of the database

I have a client who would like to automate the backup. I have used nti
backup for cd's and microsofts backup utility that came with windows
2000. They both state that the files cannot be backed up because the
files are in use.
any Ideas on how to automate the backup' and bypass the exclusive
holdings of the files'Yes. You have to tell SQL Server to backup the database to a file.
Then you can backup the file using whatever backup utility you like.
The command looks like this:
BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
After the command is executed within SQL Server (HINT: you can schedule a
job to run automatically within the SQL Server Agent) the file will be in
the location specified (the root of the X drive in this example).
Keith Kratochvil
"Mike Ryan" <miker@.centralutahcomputers.com> wrote in message
news:%23IVw6PNhGHA.4104@.TK2MSFTNGP04.phx.gbl...
> I have a client who would like to automate the backup. I have used nti
> backup for cd's and microsofts backup utility that came with windows 2000.
> They both state that the files cannot be backed up because the files are
> in use.
> any Ideas on how to automate the backup' and bypass the exclusive
> holdings of the files'
>|||Keith Kratochvil wrote:
> Yes. You have to tell SQL Server to backup the database to a file.
> Then you can backup the file using whatever backup utility you like.
> The command looks like this:
> BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
> After the command is executed within SQL Server (HINT: you can schedule a
> job to run automatically within the SQL Server Agent) the file will be in
> the location specified (the root of the X drive in this example).
>
Additionally you (or your client) should read up on BACKUP and RESTORE
strategy in Books On Line. It sounds like you aren't very familiar with
SQL backups but there are a few concepts you need to be aware of like
Recovery Model (FULL/SIMPLE), difference between FULL Database backup
and log backup and maybe even more important - RESTORE options.
Regards
Steen Schlter Persson
DBA|||Good point!
Knowing how to backup and restore a database is very important. Books
Online is a great resource and contains good information.
Keith Kratochvil
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:%23LLSG3XhGHA.3572@.TK2MSFTNGP04.phx.gbl...
> Keith Kratochvil wrote:
> Additionally you (or your client) should read up on BACKUP and RESTORE
> strategy in Books On Line. It sounds like you aren't very familiar with
> SQL backups but there are a few concepts you need to be aware of like
> Recovery Model (FULL/SIMPLE), difference between FULL Database backup and
> log backup and maybe even more important - RESTORE options.
> --
> Regards
> Steen Schlter Persson
> DBA

backup cannot make a copy of the database

I have a client who would like to automate the backup. I have used nti
backup for cd's and microsofts backup utility that came with windows
2000. They both state that the files cannot be backed up because the
files are in use.
any Ideas on how to automate the backup' and bypass the exclusive
holdings of the files'Yes. You have to tell SQL Server to backup the database to a file.
Then you can backup the file using whatever backup utility you like.
The command looks like this:
BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
After the command is executed within SQL Server (HINT: you can schedule a
job to run automatically within the SQL Server Agent) the file will be in
the location specified (the root of the X drive in this example).
Keith Kratochvil
"Mike Ryan" <miker@.centralutahcomputers.com> wrote in message
news:%23IVw6PNhGHA.4104@.TK2MSFTNGP04.phx.gbl...
> I have a client who would like to automate the backup. I have used nti
> backup for cd's and microsofts backup utility that came with windows 2000.
> They both state that the files cannot be backed up because the files are
> in use.
> any Ideas on how to automate the backup' and bypass the exclusive
> holdings of the files'
>|||Keith Kratochvil wrote:
> Yes. You have to tell SQL Server to backup the database to a file.
> Then you can backup the file using whatever backup utility you like.
> The command looks like this:
> BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
> After the command is executed within SQL Server (HINT: you can schedule a
> job to run automatically within the SQL Server Agent) the file will be in
> the location specified (the root of the X drive in this example).
>
Additionally you (or your client) should read up on BACKUP and RESTORE
strategy in Books On Line. It sounds like you aren't very familiar with
SQL backups but there are a few concepts you need to be aware of like
Recovery Model (FULL/SIMPLE), difference between FULL Database backup
and log backup and maybe even more important - RESTORE options.
--
Regards
Steen Schlüter Persson
DBA|||Good point!
Knowing how to backup and restore a database is very important. Books
Online is a great resource and contains good information.
--
Keith Kratochvil
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:%23LLSG3XhGHA.3572@.TK2MSFTNGP04.phx.gbl...
> Keith Kratochvil wrote:
>> Yes. You have to tell SQL Server to backup the database to a file.
>> Then you can backup the file using whatever backup utility you like.
>> The command looks like this:
>> BACKUP DATABASE foo TO DISK = 'x:\foo.bak' WITH INIT
>> After the command is executed within SQL Server (HINT: you can schedule a
>> job to run automatically within the SQL Server Agent) the file will be in
>> the location specified (the root of the X drive in this example).
>>
> Additionally you (or your client) should read up on BACKUP and RESTORE
> strategy in Books On Line. It sounds like you aren't very familiar with
> SQL backups but there are a few concepts you need to be aware of like
> Recovery Model (FULL/SIMPLE), difference between FULL Database backup and
> log backup and maybe even more important - RESTORE options.
> --
> Regards
> Steen Schlüter Persson
> DBA

Backing up Transaction log

Is there a way to backup a Transaction log without actually saving with the
backup utility. All I really want to do is dump the log. Thanks.Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
--
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>

Backing up Transaction log

Is there a way to backup a Transaction log without actually saving with the
backup utility. All I really want to do is dump the log. Thanks.
Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>

Backing up Transaction log

Is there a way to backup a Transaction log without actually saving with the
backup utility. All I really want to do is dump the log. Thanks.Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>