Is it possible to recover a dropped table?

Hi All,
Accidentally I have dropped a table and that is the main table for my application.
I dont have a backup of it. Is there any way to recover it.Please help me guys.
Thanks,
Kumar.With no backups you have to hope the data is recoverable from the transaction logs with a tool likewww.lumigent.com offers, but even this does not offer 100% certainty of recovering the table.

Is it possible to make a backup from MSDE ? (Y/N)

Hi all;

Is it possible to make a backup from MSDE ?? (Y/N)

The problem: I am going to develop an application for a small company and it don't like to spend more $$ rather than some $$ for the App.

So, I don't know if it is possible to do a backup from MSDE or not?

BTW: How much MS SQL Sever200 will cost per a PC? (any idea even approx.)??

Thanks in advanced!

~~CS4Ever~~there's the T-SQL BACKUP DATABASE statement :

BACKUP DATABASE { database_name | @.database_name_var }
TO < backup_device > [ ,...n ]
[ WITH
 [ BLOCKSIZE = { blocksize | @.blocksize_variable } ]
 [ [ , ] DESCRIPTION = { 'text' | @.text_variable } ]
 [ [ , ] DIFFERENTIAL ]
 [ [ , ] EXPIREDATE = { date | @.date_var }
 | RETAINDAYS = { days | @.days_var } ]
 [ [ , ] PASSWORD = { password | @.password_variable } ]
 [ [ , ] FORMAT | NOFORMAT ]
 [ [ , ] { INIT | NOINIT } ]
 [ [ , ] MEDIADESCRIPTION = { 'text' | @.text_variable } ]
 [ [ , ] MEDIANAME = { media_name | @.media_name_variable } ]
 [ [ , ] MEDIAPASSWORD = { mediapassword | @.mediapassword_variable } ]
 [ [ , ] NAME = { backup_set_name | @.backup_set_name_var } ]
 [ [ , ] { NOSKIP | SKIP } ]
 [ [ , ] { NOREWIND | REWIND } ]
 [ [ , ] { NOUNLOAD | UNLOAD } ]
 [ [ , ] RESTART ]
 [ [ , ] STATS [ = percentage ] ]
]

> How much MS SQL Sever200 will cost per a PC?

Given that it's 1800 years out of date, probably pretty cheap ;-)

(joke!) - have a lookhere|||And once backed up is it possible to restore the database?

Is it possible to import a backup

Had sql database on a dual boot machine... backed up the sql database ...
now put sql on the windows 2003 server... not sure how to import the databas
e to the new sql server... any suggestions or links would be appreciated."Vincent Keller" <anonymous@.discussions.microsoft.com> wrote in message
news:E69894D4-2385-4242-A34A-016B2AA94462@.microsoft.com...
> Had sql database on a dual boot machine... backed up the sql database
... now put sql on the windows 2003 server... not sure how to import the
database to the new sql server... any suggestions or links would be
appreciated.
>
RESTORE DATABASE dbname
FROM wherever
WITH MOVE logical_name TO 'C:\data\whatever.mdf'
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.647 / Virus Database: 414 - Release Date: 29/03/2004sql

Is it possiable to restore a DB ...

Hi,

I've written a M.plan in my client place which is scheduled to occur
weekly once.But 4 days gone from the last backup taken , there is a
problem in the server which does not start loading windows .The only
way is entering via SAFE-MODE.In the safe mode the E.Manage does not
connected(is it due to safe-mode).

They told they going to format the system . Since the E.M is not
connected, I just copied only my DB(.mdf) and the log file(.ldf).After
that i come accross that all the system databases should be backed up
along with the User DB then only possible for Restoration.

My request is

Is it not possiable to restore my copied DB(.MDF) (not backed up)
After reinstallation of Sql server.

With Heartfull thanks
Raghu"Raghuraman" <raghuraman_ace@.rediffmail.com> wrote in message
news:66c7bef8.0311260443.3adb69db@.posting.google.c om...
> Hi,
>
> I've written a M.plan in my client place which is scheduled to occur
> weekly once.But 4 days gone from the last backup taken , there is a
> problem in the server which does not start loading windows .The only
> way is entering via SAFE-MODE.In the safe mode the E.Manage does not
> connected(is it due to safe-mode).
>
> They told they going to format the system . Since the E.M is not
> connected, I just copied only my DB(.mdf) and the log file(.ldf).After
> that i come accross that all the system databases should be backed up
> along with the User DB then only possible for Restoration.
> My request is
> Is it not possiable to restore my copied DB(.MDF) (not backed up)
> After reinstallation of Sql server.
> With Heartfull thanks
> Raghu

I saw something already written in this newgroup today that may help.

Subject: attach db file copied previously

Comand: sp_attach_single_file_db|||"Raghuraman" <raghuraman_ace@.rediffmail.com> wrote in message
news:66c7bef8.0311260443.3adb69db@.posting.google.c om...
> Hi,
>
> I've written a M.plan in my client place which is scheduled to occur
> weekly once.But 4 days gone from the last backup taken , there is a
> problem in the server which does not start loading windows .The only
> way is entering via SAFE-MODE.In the safe mode the E.Manage does not
> connected(is it due to safe-mode).
>
> They told they going to format the system . Since the E.M is not
> connected, I just copied only my DB(.mdf) and the log file(.ldf).After
> that i come accross that all the system databases should be backed up
> along with the User DB then only possible for Restoration.

If possible you want to backup all the system DBs, especially the MSDB or
you risk losing jobs, etc.

So, if you can grab copies of the MDF and LDF of that to, that will help.

> My request is
> Is it not possiable to restore my copied DB(.MDF) (not backed up)

If you have the MDF and LDF then sp_attach_db is your best bet. If you have
only the .MDF, you MAY be able to use sp_attach_single_file_db, but
generally that will NOT work unless you used sp_detach_db in the first
place.

However, if you have just the MDF and can't attach it, contact Microsoft
Server Support. They may be able to help you, but your DB is likely to be
in an inconsistent state.

Note: If you're doing full backups only weekly, I highly recommend
differential or transactional backups on a daily basis (or even more often.)

> After reinstallation of Sql server.
> With Heartfull thanks
> Raghu

Is it OK to Copy Database Backups to Tape Using Compression?

Hi, I back up SQL Server 2000 and SQL server 2005 databases to hard disk using the SQL Server Backup Wizard and maintenance plans. Then, I copy the resulting backups to tape using third party tape backup software and compression by the backup software and hardware. I do not use the SQL Server Agent available for the third party backup software. Is this acceptable, or does the compression performed by the third party backup system introduce opportunities for database corruption or other negative effects?

Thanks

Hello,

This is completely acceptable - provided of course that the software you are using is reputable and that you have tested restoration succesfully.

Cheers
Rob

Is it necessary to exclude the \data folder when using NetBackup?

I am not a big fan of paying 3rd party backup vendors for
agents, but I need to make sure that we are not risking
corrupting the database files. I have setup maintenance
plans to do the fulls and log backups to disk. We are just
beginning to roll out NetBackup 5.0 in production, and
without the SQL agent installed, it appears as though it
can backup all the data files without error. Should I
exclude the "hot files" in NetBackup, and rely on the bak
and trn files if I need to restore the whole server?
Meaning, if my prod server died, and I needed to restore
from tape to a hotspare, is it possible to restore the
database(s) if the mssql\data\*.mdf and ldf files are not
restored?
If this is a lame question, I apologize, as I am not a
DBA, but a storage guy, and we have no official SQL DBA's
in house yet.
Thanks for any and all help!
DaveYes, you want to avoid trying to back up the mdf and ldf files and instead
just back up the native SQL backup files (trn/bak) to tape. You would use
these to restore the database. BOL has plenty of detail on backup and
restore in the Administering SQL Server>Backing Up and Restoring Databases
section
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
> I am not a big fan of paying 3rd party backup vendors for
> agents, but I need to make sure that we are not risking
> corrupting the database files. I have setup maintenance
> plans to do the fulls and log backups to disk. We are just
> beginning to roll out NetBackup 5.0 in production, and
> without the SQL agent installed, it appears as though it
> can backup all the data files without error. Should I
> exclude the "hot files" in NetBackup, and rely on the bak
> and trn files if I need to restore the whole server?
> Meaning, if my prod server died, and I needed to restore
> from tape to a hotspare, is it possible to restore the
> database(s) if the mssql\data\*.mdf and ldf files are not
> restored?
> If this is a lame question, I apologize, as I am not a
> DBA, but a storage guy, and we have no official SQL DBA's
> in house yet.
> Thanks for any and all help!
> Dave
>
>|||Yes, I was planning on keeping the maintenance plan. I was
not sure if it is possible to restore the trn\bak files if
real SQL server datafiles were not restored (ie excluding
the \data\*.* in NetBackup policy). Is there some command
line you can run to start SQL enough to restore the files?
I've looked in the online help, but I must be missing the
obvious. What is BOL?
thanks!

>--Original Message--
>Yes, you want to avoid trying to back up the mdf and ldf
files and instead
>just back up the native SQL backup files (trn/bak) to
tape. You would use
>these to restore the database. BOL has plenty of detail
on backup and
>restore in the Administering SQL Server>Backing Up and
Restoring Databases
>section
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Dave" <anonymous@.discussions.microsoft.com> wrote in
message
>news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
for
just
bak
not
DBA's
>
>.
>|||> Is there some command
> line you can run to start SQL enough to restore the files?
?
When you do a RESTORE in SQL Server, the database is created, if it doesn't
exists. If a system database is broken, you need to use REBUILDM.EXE to
create new system databases so that you can start SQL Server and then do the
restore. If the whole installation is toast, you need to install SQL Server
first instead. :-)
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:2ad501c3fcb0$61c267c0$a001280a@.phx.gbl...
> Yes, I was planning on keeping the maintenance plan. I was
> not sure if it is possible to restore the trn\bak files if
> real SQL server datafiles were not restored (ie excluding
> the \data\*.* in NetBackup policy). Is there some command
> line you can run to start SQL enough to restore the files?
> I've looked in the online help, but I must be missing the
> obvious. What is BOL?
> thanks!
>
> files and instead
> tape. You would use
> on backup and
> Restoring Databases
> message
> for
> just
> bak
> not
> DBA's

Is it necessary to exclude the \data folder when using NetBackup?

I am not a big fan of paying 3rd party backup vendors for
agents, but I need to make sure that we are not risking
corrupting the database files. I have setup maintenance
plans to do the fulls and log backups to disk. We are just
beginning to roll out NetBackup 5.0 in production, and
without the SQL agent installed, it appears as though it
can backup all the data files without error. Should I
exclude the "hot files" in NetBackup, and rely on the bak
and trn files if I need to restore the whole server?
Meaning, if my prod server died, and I needed to restore
from tape to a hotspare, is it possible to restore the
database(s) if the mssql\data\*.mdf and ldf files are not
restored?
If this is a lame question, I apologize, as I am not a
DBA, but a storage guy, and we have no official SQL DBA's
in house yet.
Thanks for any and all help!
DaveYou must do sql backups using maintenance plan or using
SQL Agent. Make sure to backup bak and trn files on tape
if you use maintenance plan. You should not rely on "hot
files" backup in NebBackup because it doesn't always work
in case of sql files. SQL backups (through a maintenance
plan or NetBackup sql agent) is the only reliable way to
restore sql databases.
I would advise against doing backup of \data folder,
specially if backup window is limited.
hth.
>--Original Message--
>I am not a big fan of paying 3rd party backup vendors for
>agents, but I need to make sure that we are not risking
>corrupting the database files. I have setup maintenance
>plans to do the fulls and log backups to disk. We are
just
>beginning to roll out NetBackup 5.0 in production, and
>without the SQL agent installed, it appears as though it
>can backup all the data files without error. Should I
>exclude the "hot files" in NetBackup, and rely on the bak
>and trn files if I need to restore the whole server?
>Meaning, if my prod server died, and I needed to restore
>from tape to a hotspare, is it possible to restore the
>database(s) if the mssql\data\*.mdf and ldf files are not
>restored?
>If this is a lame question, I apologize, as I am not a
>DBA, but a storage guy, and we have no official SQL DBA's
>in house yet.
>Thanks for any and all help!
>Dave
>
>.
>|||Yes, you want to avoid trying to back up the mdf and ldf files and instead
just back up the native SQL backup files (trn/bak) to tape. You would use
these to restore the database. BOL has plenty of detail on backup and
restore in the Administering SQL Server>Backing Up and Restoring Databases
section
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
> I am not a big fan of paying 3rd party backup vendors for
> agents, but I need to make sure that we are not risking
> corrupting the database files. I have setup maintenance
> plans to do the fulls and log backups to disk. We are just
> beginning to roll out NetBackup 5.0 in production, and
> without the SQL agent installed, it appears as though it
> can backup all the data files without error. Should I
> exclude the "hot files" in NetBackup, and rely on the bak
> and trn files if I need to restore the whole server?
> Meaning, if my prod server died, and I needed to restore
> from tape to a hotspare, is it possible to restore the
> database(s) if the mssql\data\*.mdf and ldf files are not
> restored?
> If this is a lame question, I apologize, as I am not a
> DBA, but a storage guy, and we have no official SQL DBA's
> in house yet.
> Thanks for any and all help!
> Dave
>
>|||Yes, I was planning on keeping the maintenance plan. I was
not sure if it is possible to restore the trn\bak files if
real SQL server datafiles were not restored (ie excluding
the \data\*.* in NetBackup policy). Is there some command
line you can run to start SQL enough to restore the files?
I've looked in the online help, but I must be missing the
obvious. What is BOL?
thanks!
>--Original Message--
>Yes, you want to avoid trying to back up the mdf and ldf
files and instead
>just back up the native SQL backup files (trn/bak) to
tape. You would use
>these to restore the database. BOL has plenty of detail
on backup and
>restore in the Administering SQL Server>Backing Up and
Restoring Databases
>section
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Dave" <anonymous@.discussions.microsoft.com> wrote in
message
>news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
>> I am not a big fan of paying 3rd party backup vendors
for
>> agents, but I need to make sure that we are not risking
>> corrupting the database files. I have setup maintenance
>> plans to do the fulls and log backups to disk. We are
just
>> beginning to roll out NetBackup 5.0 in production, and
>> without the SQL agent installed, it appears as though it
>> can backup all the data files without error. Should I
>> exclude the "hot files" in NetBackup, and rely on the
bak
>> and trn files if I need to restore the whole server?
>> Meaning, if my prod server died, and I needed to restore
>> from tape to a hotspare, is it possible to restore the
>> database(s) if the mssql\data\*.mdf and ldf files are
not
>> restored?
>> If this is a lame question, I apologize, as I am not a
>> DBA, but a storage guy, and we have no official SQL
DBA's
>> in house yet.
>> Thanks for any and all help!
>> Dave
>>
>
>.
>|||> Is there some command
> line you can run to start SQL enough to restore the files?
?
When you do a RESTORE in SQL Server, the database is created, if it doesn't
exists. If a system database is broken, you need to use REBUILDM.EXE to
create new system databases so that you can start SQL Server and then do the
restore. If the whole installation is toast, you need to install SQL Server
first instead. :-)
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:2ad501c3fcb0$61c267c0$a001280a@.phx.gbl...
> Yes, I was planning on keeping the maintenance plan. I was
> not sure if it is possible to restore the trn\bak files if
> real SQL server datafiles were not restored (ie excluding
> the \data\*.* in NetBackup policy). Is there some command
> line you can run to start SQL enough to restore the files?
> I've looked in the online help, but I must be missing the
> obvious. What is BOL?
> thanks!
> >--Original Message--
> >Yes, you want to avoid trying to back up the mdf and ldf
> files and instead
> >just back up the native SQL backup files (trn/bak) to
> tape. You would use
> >these to restore the database. BOL has plenty of detail
> on backup and
> >restore in the Administering SQL Server>Backing Up and
> Restoring Databases
> >section
> >
> >--
> >HTH
> >
> >Jasper Smith (SQL Server MVP)
> >
> >I support PASS - the definitive, global
> >community for SQL Server professionals -
> >http://www.sqlpass.org
> >
> >
> >"Dave" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:288a01c3fc84$cf4b5850$a101280a@.phx.gbl...
> >> I am not a big fan of paying 3rd party backup vendors
> for
> >> agents, but I need to make sure that we are not risking
> >> corrupting the database files. I have setup maintenance
> >> plans to do the fulls and log backups to disk. We are
> just
> >> beginning to roll out NetBackup 5.0 in production, and
> >> without the SQL agent installed, it appears as though it
> >> can backup all the data files without error. Should I
> >> exclude the "hot files" in NetBackup, and rely on the
> bak
> >> and trn files if I need to restore the whole server?
> >> Meaning, if my prod server died, and I needed to restore
> >> from tape to a hotspare, is it possible to restore the
> >> database(s) if the mssql\data\*.mdf and ldf files are
> not
> >> restored?
> >> If this is a lame question, I apologize, as I am not a
> >> DBA, but a storage guy, and we have no official SQL
> DBA's
> >> in house yet.
> >> Thanks for any and all help!
> >>
> >> Dave
> >>
> >>
> >>
> >
> >
> >.
> >

is it a good practice to do integrity check before perform backup?

On maintenance plan, there is a check box on integrity tab page, is it a good
way to do that first? if there is error found, will the backup stop? thanks
Hi
It depends on what error it will find. Actually, you can checkbox but make
sure that you uncheck Attempt to repair... option.
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:06E26A1F-4F08-4D81-9502-07E9DB0F5041@.microsoft.com...
> On maintenance plan, there is a check box on integrity tab page, is it a
> good
> way to do that first? if there is error found, will the backup stop?
> thanks
|||My approach is that if you have plenty of maintenance window for doing the
integraity checks (i.e. DBCC checks), do them by all means. And if you are
running into integrity issues, you may want to perform the DBCC checks more
regularly. It becomes a more difficult question when you are dealing with a
large amount of data and when you are struggling to contain your maintenance
jobs inside a limited maintenance window. In that case, you may have to forgo
the DBCC checks or do them very selectively.
Linchi
"tulip" wrote:

> On maintenance plan, there is a check box on integrity tab page, is it a good
> way to do that first? if there is error found, will the backup stop? thanks

is it a good practice to do integrity check before perform backup?

On maintenance plan, there is a check box on integrity tab page, is it a good
way to do that first? if there is error found, will the backup stop? thanksHi
It depends on what error it will find. Actually, you can checkbox but make
sure that you uncheck Attempt to repair... option.
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:06E26A1F-4F08-4D81-9502-07E9DB0F5041@.microsoft.com...
> On maintenance plan, there is a check box on integrity tab page, is it a
> good
> way to do that first? if there is error found, will the backup stop?
> thanks|||My approach is that if you have plenty of maintenance window for doing the
integraity checks (i.e. DBCC checks), do them by all means. And if you are
running into integrity issues, you may want to perform the DBCC checks more
regularly. It becomes a more difficult question when you are dealing with a
large amount of data and when you are struggling to contain your maintenance
jobs inside a limited maintenance window. In that case, you may have to forgo
the DBCC checks or do them very selectively.
Linchi
"tulip" wrote:
> On maintenance plan, there is a check box on integrity tab page, is it a good
> way to do that first? if there is error found, will the backup stop? thanks

Is it a bug of SQL Server 2000 SP4?

Database backup file:
http://www.keepmyfile.com/download/c58b2a565144
Environment:
SQL Server 2000 SP4
Problem:
The following two statements returns different number of records:
Exec GenPeriodical1 102, null, '20050601', '20050630', null, null, 0
SELECT *
FROM dbo.OtherFee (null, '20050601', '20050630', null, null, 0)
WHERE flow_id = 102
This problem wasn't found in SQL Server 2000 original version and SQL Server
2005.
Any help is appreciated!Well, seems like a bug.
You can fix it by rearranginf the FROM clause in the function in the
following manner.
FROM action_room_req2 arr
JOIN flow_action fa ON arr.flow_id = fa.flow_id
JOIN cust_action ca ON ca.valid = 0 AND fa.action_id = ca.id
JOIN action_room ar ON ar.action_id = ca.id AND ar.code = 0
JOIN customer c ON ca.customer_id = c.id
LEFT JOIN turn_rule tr ON arr.req_type = 'Mall' and arr.ref_id = tr.id
Regards
Roji. P. Thomas
http://toponewithties.blogspot.com
"hghua" <hghua@.discussions.microsoft.com> wrote in message
news:A9FB112B-AD45-463A-A167-CFAF77E20B5D@.microsoft.com...
> Database backup file:
> http://www.keepmyfile.com/download/c58b2a565144
> Environment:
> SQL Server 2000 SP4
> Problem:
> The following two statements returns different number of records:
> Exec GenPeriodical1 102, null, '20050601', '20050630', null, null, 0
> SELECT *
> FROM dbo.OtherFee (null, '20050601', '20050630', null, null, 0)
> WHERE flow_id = 102
> This problem wasn't found in SQL Server 2000 original version and SQL
> Server
> 2005.
> Any help is appreciated!|||Thanks a lot! That works!
Hope Microsoft will solve the problem.
"Roji. P. Thomas" wrote:

> Well, seems like a bug.
> You can fix it by rearranginf the FROM clause in the function in the
> following manner.
> FROM action_room_req2 arr
> JOIN flow_action fa ON arr.flow_id = fa.flow_id
> JOIN cust_action ca ON ca.valid = 0 AND fa.action_id = ca.id
> JOIN action_room ar ON ar.action_id = ca.id AND ar.code = 0
> JOIN customer c ON ca.customer_id = c.id
> LEFT JOIN turn_rule tr ON arr.req_type = 'Mall' and arr.ref_id = tr.id
> --
> Regards
> Roji. P. Thomas
> http://toponewithties.blogspot.com
> "hghua" <hghua@.discussions.microsoft.com> wrote in message
> news:A9FB112B-AD45-463A-A167-CFAF77E20B5D@.microsoft.com...
>
>

Is it a bug of SQL Server 2000 SP4?

Database backup file: 
http://www.keepmyfile.com/download/c58b2a565144

Environment:
SQL Server 2000 SP4

Problem:
The following two statements returns different number of records:
Exec GenPeriodical1 102, null, '20050601', '20050630', null, null, 0 

SELECT *
FROM dbo.OtherFee (null, '20050601', '20050630', null, null, 0)
WHERE flow_id = 102

This problem wasn't found in SQL Server 2000 original version and SQL Server 
2005.
Any help is appreciated!

Is it possible to see text for dbo.OtherFee and GenPeriodical1?|||

Thanks for your reply!

I've got the answer from the newsgroup. The replyer said it seems a bug of SP4 and gave a work-around. If you are interested in this issue, you can download the backup file, it's just 1.18MB.

The store proc and function call other functions, thus not convenient to paste them here.

Is copy of database and log file enough for backup?

Hello,

i would like to copy the SQL Server Express database .mdf and .ldf files for backup. Is this ok?
Autoclose = true and recovery model = simple.

Must i detach the database before copy the 2 files or can i copy the 2 files without detach at any time? When connections are open (also remote connections).
Can i copy at any time even when transactions are active?

I would like to write a copy programm which copies the 2 files every 30 minuutes. Only 30 minutes of work could be lost.

This would be enough for me and i don't have to care for the the BACKUP and RESTORE stuff. In the past i used BACKUP and when i needed this BACKUP it did not run. Returns some error message..

Is copy ok? When is it possible? At any time or must all transactions be comitted? Must all connections (remotes too) be closed? Must the database be detached?

Is this enough to have a valid backup? Backup would be an attach of the .mdf file.

Or must i use the BACKUP and RESTORE stuff? Why?
If so, for what reason is the AUTO CLOSE property there?

Regards,

Markus

And in my opinion attach a database should be enough. ít is the users, the owners, wish to get the data stored in the database.

In the past, as i tried to use RESTORE stuff, i get an error message. From the sql server system point of view this was ok because something of the restore file did not match the STRICT criteria for restore. But i lost the data.

Therefore a attach should do it, to fullfill the wishes of the owner. To show him the data of that .mdf file. Even it this .mdf file does not meet the critierias of the current version. SQL Server should inform the owner of that, and ask if it is allowed to try to converte the file to the current format. If OK, it should do everything to save as much data as possible.

Sorry, if it sounds a bit curious, but i would like a way to do the obvious things without force the owner to take any learning effort.

Read in a blog:
http://www.sqlserver2005.de/SQLServer2005/MyBlog/tabid/56/Default.aspx
This schould not be the case..

Markus

|||

I personaly would use the back up and restore options, this is what they are designed for. You can run these from the Management studio (Express Version) or from a raw query. If you need to schedule it you can either use the normal scheduler that is in windows or use a custom one. For one of my clients I created a windows service that copied the function on the unix cron system but on a windows machine.

The only time that I have used the attach and detach functions is when I need to move a database quickly. I have seen some people use it to install the database when the program is installed, but for this I prefer to code a solution that creates the database from scripts. Doing it this way I know that the structure and data is clean at the time of install.

|||

Thank you Glenn.

But the question was, is copy enough? And under what conditions?

In my opinion, if Sql Server Express should be a common datastore, it should be easy to backup.

Without knowing Sql Server Books online, without knowing what "scripts" are. This is stuff for a few freaks, who likes things like that. But most of the people don't like to read such stuff. Most people hate this stuff.

What is if someone use a Sql Server database (any older version) and want to sell his computer. He copies the .mdf and .ldf file to a cd. He buys a new computer. Installs a new download of Sql Server. Tries to attach the copied files. This should be the only thing he should know. And Sql Server should be the best it can do and not show an error message.

Or what is if someone send's the .mdf and .ldf file via email to another person. Who knows which version of Sql Server he is running`?

What i mean, if Sql Server want to be a datastore of everyone it should meet the needs of everyone. Don*t kow and don't need to know what BOL is or what scripts are. Perform the needs of the owners autmatically and explain him in a few simple sentences.

I think today the normal person is a bit confused.

Best regards,

Markus

|||

When you do use the attach and detach system you do not have to copy the ldf file as this is only the transaction log file, In that should only be open transactions... If you are copying the file to a new location you will need to make sure that al transactions are commited to the database. This is why I prefer to use the backup option as this makes sure that at the time of the backup all of the data is stored. If you do use the attach and detach method there are chances of loosing data.

|||

Hello Glenn,

you wrote:
> The only time that I have used the attach and detach functions is when I need to
> move a database quickly. I have seen some people use it to install the database
> when the program is installed, but for this I prefer to code a solution that creates
> the database from scripts. Doing it this way I know that the structure and data is
> clean at the time of install.

This is what i want to do when my program is installed. Install SQL Server Express with a named instance. Copy the database files and attach them. Because there ist allready data in the database files. What do you think is the risk of that way? Have you ever heard that his fails?

> When you do use the attach and detach system you do not have to copy the ldf
> file as this is only the transaction log file, In that should only be open transactions...

If i use attach and have only the .mdf file, is the .ldf file then new created?

> If you are copying the file to a new location you will need to make sure that al
> transactions are commited to the database.

Is this the case when i use Detach? When does a detach fail?

> This is why I prefer to use the backup option as this makes sure that at the time of
> the backup all of the data is stored. If you do use the attach and detach method
> there are chances of loosing data.

Are there limitations of restore and backup? When will a restore fail? What is of different version ofs sql server, differences betwen the system where the database was backed up and where it is to be restored? Is there allways compatibility or what must the user care for, that the restore will run?

Regards,
Markus

|||

>This is what i want to do when my program is installed. Install SQL Server Express with a named instance. Copy the database files and attach them. Because there ist allready data in the database files. What do you think is the risk of that way? Have you ever heard that his fails?

Well there are certain things that are not stored in the database itself. Logins, for example.

I have had problems doing exactly what you described in SQL 2000, especially when my original database had any users other than dbo.I've had problems with restore as well.

If you are shipping initial data with your product I would recommend that you do it all in code.INFORMATION_SCHEMA is your friend.I've done things using batch scripts and the command line tools.These work but are not flexible enough and don't provide sufficient error detection.

|||

>Well there are certain things that are not stored in the
>database itself. Logins, for example.
>I have had problems doing exactly what you described
>in SQL 2000, especially when my original database had
>any users other than dbo. I've had problems with
>restore as well.

But when you install a seperate named instance for your application? Do you see this problems in this case too?

|||

Yes you do see the same problems, a Named Instance is just like a completly new server install...

Is backup log truncate inactive part of logs?

Also,what is steps needed for online backup?
backup database and then
backup logs
or reverse?
Thanks a lot,ZvonimirTo answer your subject line, the backup log command does nothing with the INACTIVE part of the log. It only truncates the active part, it does not shrink the logfile if that is what you are asking. A full backup does not truncate or shrink the log file so it depends on what your needs are in regards to doing a log backup before or after a full backup.

HTH|||rhigdon,

The active portion of the log can never be truncated. The active part represents transactions in progress. It is the inactive part that is truncated.

blindman|||"Active portion" may not have been the right term to use, you are right in saying Active TRANSACTIONS are transactions that have not been committed. So, not sure if we can call any PORTION of the log active, and would we call the remainder INACTIVE? Meaning the empty space of the footprint plus the transactions not checkpointed?

My definition of the active portion of the tran log in the context of this thread was the transactions that have not been checkpointed and sent to the database yet but were still in the tran log (and of course would show up in any query). Wheras (again, my definition) the inactive portion was the percentage not being used in the tran log.

Soo, not sure if active or inactive are the right terms but what I meant to relay was that if my tran log is 50mb with 20mb used, a backup or truncate log command would clear that 20mb but still leave the footprint or shell of 50mb until it was shrunk or grew more.

Thanks for pointing that out :)|||You are also right that active trans can not be truncated , forgot to add that.|||Thanks for Your answers.I believe i wasn't exact enough.
My experience with DB2 and Oracle tell me that for RDBMS common feature is "online backup",that is during backup my users can work with database.But,for recovery of database,only database online backup isn't enough,because of uncommited transactions in "active part of logs".So,for online backup I MUST do BACKUP LOG.
My qestions are:
1) How i force database to do online backup?Is this any reserved word for online backup telling "it is online backup" or SQL by "status of database" recognize online ( or offline) backup?

2) What is better:
a) BACKUP DATABASE
BACKUP LOG (with truncate,not shrink)
or
b) BACKUP LOG
BACKUP DATABASE?

Thanks a lot for Your answers,Zvonimir

Is Arcserve 2000 backing up my SQL server properly?

I recently installed arcserve small business version for a client who
is running SQL server. It seems that at the beginning of the backup
cycle the files are skipped due to a sharing violation (I mean the
database files). Later during the part when the SQL agent backs up
files it seems to back up fine. Is this normal or is something wrong
here. Below is a log...sorry if it is a little long. Thanks so much
for youe help.
20030701 010009 16 Run Backup Job Scheduled for 7/01/03 at 1:00 AM.
20030701 010009 16 Start Backup Operation. (QUEUE=1, JOB=2)
20030701 010010 16 Overwrite media Monthly2, ID DBA9, sequence #1
20030701 010037 TAPE Tape Engine finished formatting media.(new name:
Monthly2, old name: Monthly2)
20030701 010037 Begin cleaning database.
20030701 010044 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=1, RECS=18130)
20030701 010047 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=2, RECS=11705)
20030701 010048 TAPE Format Successful!
20030701 010048 16 Use media Monthly2, ID 2542, sequence #1
20030701 010054 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=3, RECS=27896)
20030701 010129 16 Source Directory: C:
20030701 010129 16 Back up Session 1 on Media Monthly2
20030701 010129 16 Backed up volume disk quota.
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=4, RECS=151242)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=5, RECS=7)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=6, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=7, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=8, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=9, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=10, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=11, RECS=12)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=12, RECS=13291)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=13, RECS=225)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=14, RECS=123)
20030701 010159 End cleaning database. (CLEANED=222691)
20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\qmgr0.dat, EC=SHARING VIOLATION)
20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\qmgr1.dat, EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSDat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSLog.ldf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Dat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Log.ldf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWODat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWOLog.ldf,
EC=SHARING VIOLATION)
20030701 010601 16 Catalog File Backed Up
20030701 010601 16 Registry Files Backed Up
20030701 010601 16 1,049 Directories 17,088 Files (1,404.55 MB) Backed
Up to Media.
20030701 010601 16 8 Directories/Files Skipped.
20030701 010601 16 1,463.31 MB Written to Media.
20030701 010601 16 Elapsed Time: 4m 30s
20030701 010601 16 Average Throughput: 325.17 MB/min
20030701 010601 16 Number of Errors/Warnings: 0/8
20030701 010611 16 Source Directory: E:
20030701 010611 16 Back up Session 2 on Media Monthly2
20030701 010611 16 Backed up volume disk quota.
20030701 011115 16 Catalog File Backed Up
20030701 011115 16 563 Directories 11,142 Files (1,254.87 MB) Backed
Up to Media.
20030701 011115 16 1,292.68 MB Written to Media.
20030701 011115 16 Elapsed Time: 5m 0s
20030701 011115 16 Average Throughput: 258.53 MB/min
20030701 011201 16 Source Directory: F:
20030701 011201 16 Back up Session 3 on Media Monthly2
20030701 011201 16 Backed up volume disk quota.
20030701 012213 16 Catalog File Backed Up
20030701 012213 16 4,665 Directories 23,262 Files (3,229.25 MB) Backed
Up to Media.
20030701 012213 16 3,320.18 MB Written to Media.
20030701 012213 16 Elapsed Time: 10m 9s
20030701 012213 16 Average Throughput: 327.11 MB/min
20030701 012213 16 Source Directory: Registry
20030701 012213 16 Back up Session 4 on Media Monthly2
20030701 012244 16 Registry Files Backed Up
20030701 012244 16 54,946 Directories 96,295 Files (21.42 MB) Backed
Up to Media.
20030701 012244 16 404.87 MB Written to Media.
20030701 012244 16 Elapsed Time: 28s
20030701 012244 16 Average Throughput: 867.58 MB/min
20030701 012244 16 Source Directory: dbaexchis\First Storage Group
20030701 012244 16 Back up Session 5 on Media Monthly2
20030701 012301 16 1 Databases/Transaction Logs (103.04 MB) Backed Up
to Media.
20030701 012301 16 103.12 MB Written to Media.
20030701 012301 16 Elapsed Time: 15s
20030701 012301 16 Average Throughput: 412.50 MB/min
20030701 012302 16 Source Directory: dbasql@.MSGPSBM\TWO
20030701 012302 16 Back up Session 6 on Media Monthly2
20030701 012311 16 1 Databases/Transaction Logs (90.07 MB) Backed Up
to Media.
20030701 012311 16 90.18 MB Written to Media.
20030701 012311 16 Elapsed Time: 7s
20030701 012311 16 Average Throughput: 773.03 MB/min
20030701 012311 16 Source Directory: dbasql@.MSGPSBM\SBM01
20030701 012311 16 Back up Session 7 on Media Monthly2
20030701 012355 16 1 Databases/Transaction Logs (548.07 MB) Backed Up
to Media.
20030701 012355 16 548.37 MB Written to Media.
20030701 012355 16 Elapsed Time: 42s
20030701 012355 16 Average Throughput: 783.39 MB/min
20030701 012355 16 Source Directory: dbasql@.MSGPSBM\msdb
20030701 012355 16 Back up Session 8 on Media Monthly2
20030701 012357 16 1 Databases/Transaction Logs (2.32 MB) Backed Up to
Media.
20030701 012357 16 2.37 MB Written to Media.
20030701 012357 16 Elapsed Time: 1s
20030701 012357 16 Average Throughput: 142.50 MB/min
20030701 012357 16 Source Directory: dbasql@.MSGPSBM\model
20030701 012357 16 Back up Session 9 on Media Monthly2
20030701 012400 16 1 Databases/Transaction Logs (721 KB) Backed Up to
Media.
20030701 012400 16 768 KB Written to Media.
20030701 012400 16 Elapsed Time: 1s
20030701 012400 16 Average Throughput: 45.00 MB/min
20030701 012400 16 Source Directory: dbasql@.MSGPSBM\master
20030701 012400 16 Back up Session 10 on Media Monthly2
20030701 012407 16 1 Databases/Transaction Logs (10.51 MB) Backed Up
to Media.
20030701 012407 16 10.56 MB Written to Media.
20030701 012407 16 Elapsed Time: 0s
20030701 012407 16 Average Throughput: 633.75 MB/min
20030701 012407 16 Source Directory: dbasql@.MSGPSBM\DYNAMICS
20030701 012407 16 Back up Session 11 on Media Monthly2
20030701 012412 16 1 Databases/Transaction Logs (29.95 MB) Backed Up
to Media.
20030701 012412 16 30.00 MB Written to Media.
20030701 012412 16 Elapsed Time: 3s
20030701 012412 16 Average Throughput: 600.00 MB/min
20030701 012413 16 Source Directory: System State
20030701 012413 16 Back up Session 12 on Media Monthly2
20030701 012413 16 Backing Up Files : Boot and System Protected Files
20030701 012445 16 Backing Up Files : Active Directory
20030701 012448 16 Backing Up Files : SysVol
20030701 012448 16 Backing Up Files : COM+ Class Registration Database
20030701 012448 16 Backing Up Files : Registry
20030701 012455 16 Registry Files Backed Up
20030701 012455 16 91 Directories 1,963 Files (287.99 MB) Backed Up to
Media.
20030701 012455 16 294.56 MB Written to Media.
20030701 012455 16 Elapsed Time: 39s
20030701 012455 16 Average Throughput: 453.17 MB/min
20030701 012455 16 Source Directory: dbaxchg2
20030701 012455 16 Back up Session 13 on Media Monthly2
20030701 012516 16 11 Databases/Transaction Logs (40.19 MB) Backed Up
to Media.
20030701 012516 16 40.50 MB Written to Media.
20030701 012516 16 Elapsed Time: 19s
20030701 012516 16 Average Throughput: 127.89 MB/min
20030701 012516 16 ** Summary for My Computer **
20030701 012516 16 13 Sessions.
20030701 012516 16 61,314 Directories 149,750 Files (6,198.15 MB)
Backed Up to Media.
20030701 012516 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
to Media.
20030701 012516 16 8 Directories/Files Skipped.
20030701 012516 16 7,601.50 MB Written to Media.
20030701 012516 16 Elapsed Time: 22m 14s
20030701 012516 16 Average Throughput: 341.89 MB/min
20030701 012516 16 Number of Errors/Warnings: 0/8
20030701 012519 16 Backup ARCserve Database...
20030701 012520 16 Source Directory: C:\Program
Files\ComputerAssociates\ARCserve\DATABASE
20030701 012520 16 Back up Session 14 on Media Monthly2
20030701 012529 16 Catalog File Backed Up
20030701 012529 16 1 Directories 118 Files (104.17 MB) Backed Up to
Media.
20030701 012529 16 104.62 MB Written to Media.
20030701 012529 16 Elapsed Time: 7s
20030701 012529 16 Average Throughput: 896.78 MB/min
20030701 012529 16 ARCServe Database Backed Up
20030701 012538 [CAT] Monthly2 [ID:2542,SESSION:1] is
merged.(files=17088)
20030701 012542 [CAT] Monthly2 [ID:2542,SESSION:2] is
merged.(files=11142)
20030701 012555 [CAT] Monthly2 [ID:2542,SESSION:3] is
merged.(files=23262)
20030701 012631 16 ** Summary for Job **
20030701 012631 16 14 Sessions.
20030701 012631 16 61,315 Directories 149,868 Files (6,302.33 MB)
Backed Up to Media.
20030701 012631 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
to Media.
20030701 012631 16 8 Directories/Files Skipped.
20030701 012631 16 7,706.12 MB Written to Media.
20030701 012631 16 Elapsed Time: 22m 21s
20030701 012631 16 Average Throughput: 344.79 MB/min
20030701 012631 16 Number of Errors/Warnings: 0/8
20030701 012631 16 Backup Operation Incomplete.
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:4] is
merged.(files=96295)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:5] is merged.(files=5)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:6] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:7] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:8] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:9] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:10] is
merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:11] is
merged.(files=3)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:12] is
merged.(files=1963)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:13] is
merged.(files=110)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:14] is
merged.(files=118)
20030701 012709 16 Reschedule Backup Job for 7/02/03 at 1:00 AM.You can't normally backup the database files with ArcServe since they are
always in use. I believe they have a way to bypass that but then what good
is backing up a file that is constantly changing. You can't restore the db
using these backups made from Arcserve since they are not consistent. What
you can do is basically one of 2 things. Either use the SQL Server plug-in
for ArcServe to have it issue the equivalent of a sql server backup or don't
even attempt to backup the database files with Arcserve and have it backup
the files generated by the SQL Server backup.
--
Andrew J. Kelly
SQL Server MVP
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307021902.4a418a32@.posting.google.com...
> I recently installed arcserve small business version for a client who
> is running SQL server. It seems that at the beginning of the backup
> cycle the files are skipped due to a sharing violation (I mean the
> database files). Later during the part when the SQL agent backs up
> files it seems to back up fine. Is this normal or is something wrong
> here. Below is a log...sorry if it is a little long. Thanks so much
> for youe help.
>
> 20030701 010009 16 Run Backup Job Scheduled for 7/01/03 at 1:00 AM.
> 20030701 010009 16 Start Backup Operation. (QUEUE=1, JOB=2)
> 20030701 010010 16 Overwrite media Monthly2, ID DBA9, sequence #1
> 20030701 010037 TAPE Tape Engine finished formatting media.(new name:
> Monthly2, old name: Monthly2)
> 20030701 010037 Begin cleaning database.
> 20030701 010044 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=1, RECS=18130)
> 20030701 010047 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=2, RECS=11705)
> 20030701 010048 TAPE Format Successful!
> 20030701 010048 16 Use media Monthly2, ID 2542, sequence #1
> 20030701 010054 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=3, RECS=27896)
> 20030701 010129 16 Source Directory: C:
> 20030701 010129 16 Back up Session 1 on Media Monthly2
> 20030701 010129 16 Backed up volume disk quota.
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=4, RECS=151242)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=5, RECS=7)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=6, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=7, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=8, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=9, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=10, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=11, RECS=12)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=12, RECS=13291)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=13, RECS=225)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=14, RECS=123)
> 20030701 010159 End cleaning database. (CLEANED=222691)
> 20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
> Settings\All Users\Application
> Data\Microsoft\Network\Downloader\qmgr0.dat, EC=SHARING VIOLATION)
> 20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
> Settings\All Users\Application
> Data\Microsoft\Network\Downloader\qmgr1.dat, EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSDat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSLog.ldf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Dat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Log.ldf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWODat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWOLog.ldf,
> EC=SHARING VIOLATION)
> 20030701 010601 16 Catalog File Backed Up
> 20030701 010601 16 Registry Files Backed Up
> 20030701 010601 16 1,049 Directories 17,088 Files (1,404.55 MB) Backed
> Up to Media.
> 20030701 010601 16 8 Directories/Files Skipped.
> 20030701 010601 16 1,463.31 MB Written to Media.
> 20030701 010601 16 Elapsed Time: 4m 30s
> 20030701 010601 16 Average Throughput: 325.17 MB/min
> 20030701 010601 16 Number of Errors/Warnings: 0/8
> 20030701 010611 16 Source Directory: E:
> 20030701 010611 16 Back up Session 2 on Media Monthly2
> 20030701 010611 16 Backed up volume disk quota.
> 20030701 011115 16 Catalog File Backed Up
> 20030701 011115 16 563 Directories 11,142 Files (1,254.87 MB) Backed
> Up to Media.
> 20030701 011115 16 1,292.68 MB Written to Media.
> 20030701 011115 16 Elapsed Time: 5m 0s
> 20030701 011115 16 Average Throughput: 258.53 MB/min
> 20030701 011201 16 Source Directory: F:
> 20030701 011201 16 Back up Session 3 on Media Monthly2
> 20030701 011201 16 Backed up volume disk quota.
> 20030701 012213 16 Catalog File Backed Up
> 20030701 012213 16 4,665 Directories 23,262 Files (3,229.25 MB) Backed
> Up to Media.
> 20030701 012213 16 3,320.18 MB Written to Media.
> 20030701 012213 16 Elapsed Time: 10m 9s
> 20030701 012213 16 Average Throughput: 327.11 MB/min
> 20030701 012213 16 Source Directory: Registry
> 20030701 012213 16 Back up Session 4 on Media Monthly2
> 20030701 012244 16 Registry Files Backed Up
> 20030701 012244 16 54,946 Directories 96,295 Files (21.42 MB) Backed
> Up to Media.
> 20030701 012244 16 404.87 MB Written to Media.
> 20030701 012244 16 Elapsed Time: 28s
> 20030701 012244 16 Average Throughput: 867.58 MB/min
> 20030701 012244 16 Source Directory: dbaexchis\First Storage Group
> 20030701 012244 16 Back up Session 5 on Media Monthly2
> 20030701 012301 16 1 Databases/Transaction Logs (103.04 MB) Backed Up
> to Media.
> 20030701 012301 16 103.12 MB Written to Media.
> 20030701 012301 16 Elapsed Time: 15s
> 20030701 012301 16 Average Throughput: 412.50 MB/min
> 20030701 012302 16 Source Directory: dbasql@.MSGPSBM\TWO
> 20030701 012302 16 Back up Session 6 on Media Monthly2
> 20030701 012311 16 1 Databases/Transaction Logs (90.07 MB) Backed Up
> to Media.
> 20030701 012311 16 90.18 MB Written to Media.
> 20030701 012311 16 Elapsed Time: 7s
> 20030701 012311 16 Average Throughput: 773.03 MB/min
> 20030701 012311 16 Source Directory: dbasql@.MSGPSBM\SBM01
> 20030701 012311 16 Back up Session 7 on Media Monthly2
> 20030701 012355 16 1 Databases/Transaction Logs (548.07 MB) Backed Up
> to Media.
> 20030701 012355 16 548.37 MB Written to Media.
> 20030701 012355 16 Elapsed Time: 42s
> 20030701 012355 16 Average Throughput: 783.39 MB/min
> 20030701 012355 16 Source Directory: dbasql@.MSGPSBM\msdb
> 20030701 012355 16 Back up Session 8 on Media Monthly2
> 20030701 012357 16 1 Databases/Transaction Logs (2.32 MB) Backed Up to
> Media.
> 20030701 012357 16 2.37 MB Written to Media.
> 20030701 012357 16 Elapsed Time: 1s
> 20030701 012357 16 Average Throughput: 142.50 MB/min
> 20030701 012357 16 Source Directory: dbasql@.MSGPSBM\model
> 20030701 012357 16 Back up Session 9 on Media Monthly2
> 20030701 012400 16 1 Databases/Transaction Logs (721 KB) Backed Up to
> Media.
> 20030701 012400 16 768 KB Written to Media.
> 20030701 012400 16 Elapsed Time: 1s
> 20030701 012400 16 Average Throughput: 45.00 MB/min
> 20030701 012400 16 Source Directory: dbasql@.MSGPSBM\master
> 20030701 012400 16 Back up Session 10 on Media Monthly2
> 20030701 012407 16 1 Databases/Transaction Logs (10.51 MB) Backed Up
> to Media.
> 20030701 012407 16 10.56 MB Written to Media.
> 20030701 012407 16 Elapsed Time: 0s
> 20030701 012407 16 Average Throughput: 633.75 MB/min
> 20030701 012407 16 Source Directory: dbasql@.MSGPSBM\DYNAMICS
> 20030701 012407 16 Back up Session 11 on Media Monthly2
> 20030701 012412 16 1 Databases/Transaction Logs (29.95 MB) Backed Up
> to Media.
> 20030701 012412 16 30.00 MB Written to Media.
> 20030701 012412 16 Elapsed Time: 3s
> 20030701 012412 16 Average Throughput: 600.00 MB/min
> 20030701 012413 16 Source Directory: System State
> 20030701 012413 16 Back up Session 12 on Media Monthly2
> 20030701 012413 16 Backing Up Files : Boot and System Protected Files
> 20030701 012445 16 Backing Up Files : Active Directory
> 20030701 012448 16 Backing Up Files : SysVol
> 20030701 012448 16 Backing Up Files : COM+ Class Registration Database
> 20030701 012448 16 Backing Up Files : Registry
> 20030701 012455 16 Registry Files Backed Up
> 20030701 012455 16 91 Directories 1,963 Files (287.99 MB) Backed Up to
> Media.
> 20030701 012455 16 294.56 MB Written to Media.
> 20030701 012455 16 Elapsed Time: 39s
> 20030701 012455 16 Average Throughput: 453.17 MB/min
> 20030701 012455 16 Source Directory: dbaxchg2
> 20030701 012455 16 Back up Session 13 on Media Monthly2
> 20030701 012516 16 11 Databases/Transaction Logs (40.19 MB) Backed Up
> to Media.
> 20030701 012516 16 40.50 MB Written to Media.
> 20030701 012516 16 Elapsed Time: 19s
> 20030701 012516 16 Average Throughput: 127.89 MB/min
> 20030701 012516 16 ** Summary for My Computer **
> 20030701 012516 16 13 Sessions.
> 20030701 012516 16 61,314 Directories 149,750 Files (6,198.15 MB)
> Backed Up to Media.
> 20030701 012516 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
> to Media.
> 20030701 012516 16 8 Directories/Files Skipped.
> 20030701 012516 16 7,601.50 MB Written to Media.
> 20030701 012516 16 Elapsed Time: 22m 14s
> 20030701 012516 16 Average Throughput: 341.89 MB/min
> 20030701 012516 16 Number of Errors/Warnings: 0/8
> 20030701 012519 16 Backup ARCserve Database...
> 20030701 012520 16 Source Directory: C:\Program
> Files\ComputerAssociates\ARCserve\DATABASE
> 20030701 012520 16 Back up Session 14 on Media Monthly2
> 20030701 012529 16 Catalog File Backed Up
> 20030701 012529 16 1 Directories 118 Files (104.17 MB) Backed Up to
> Media.
> 20030701 012529 16 104.62 MB Written to Media.
> 20030701 012529 16 Elapsed Time: 7s
> 20030701 012529 16 Average Throughput: 896.78 MB/min
> 20030701 012529 16 ARCServe Database Backed Up
> 20030701 012538 [CAT] Monthly2 [ID:2542,SESSION:1] is
> merged.(files=17088)
> 20030701 012542 [CAT] Monthly2 [ID:2542,SESSION:2] is
> merged.(files=11142)
> 20030701 012555 [CAT] Monthly2 [ID:2542,SESSION:3] is
> merged.(files=23262)
> 20030701 012631 16 ** Summary for Job **
> 20030701 012631 16 14 Sessions.
> 20030701 012631 16 61,315 Directories 149,868 Files (6,302.33 MB)
> Backed Up to Media.
> 20030701 012631 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
> to Media.
> 20030701 012631 16 8 Directories/Files Skipped.
> 20030701 012631 16 7,706.12 MB Written to Media.
> 20030701 012631 16 Elapsed Time: 22m 21s
> 20030701 012631 16 Average Throughput: 344.79 MB/min
> 20030701 012631 16 Number of Errors/Warnings: 0/8
> 20030701 012631 16 Backup Operation Incomplete.
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:4] is
> merged.(files=96295)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:5] is merged.(files=5)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:6] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:7] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:8] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:9] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:10] is
> merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:11] is
> merged.(files=3)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:12] is
> merged.(files=1963)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:13] is
> merged.(files=110)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:14] is
> merged.(files=118)
> 20030701 012709 16 Reschedule Backup Job for 7/02/03 at 1:00 AM.|||Hello,
Arcserver has an Open File Agent, as do most of these large backup software
products. This is supposed to allow the backing up of files that Andrew
says are always in use. It is my experience that this can be a hit and miss
affair and is one that I am not comfortable with. Yes I have been bitten by
it. I always now backup using SQL Server to a .bak file and have Arcserve.*
back that file up.
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
: You can't normally backup the database files with ArcServe since they are
: always in use. I believe they have a way to bypass that but then what
good
: is backing up a file that is constantly changing. You can't restore the
db
: using these backups made from Arcserve since they are not consistent.
What
: you can do is basically one of 2 things. Either use the SQL Server
plug-in
: for ArcServe to have it issue the equivalent of a sql server backup or
don't
: even attempt to backup the database files with Arcserve and have it backup
: the files generated by the SQL Server backup.
-- Microsoft Outlook Express 6.00.2800.1158|||Yes that is what I meant by bypass. Poor choice of word but it will allow
it to backup up the file anyway. That does no one any good since it is in
an inconsistent state database wise.
--
Andrew J. Kelly
SQL Server MVP
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OK7gauSQDHA.2852@.tk2msftngp13.phx.gbl...
> Hello,
> Arcserver has an Open File Agent, as do most of these large backup
software
> products. This is supposed to allow the backing up of files that Andrew
> says are always in use. It is my experience that this can be a hit and
miss
> affair and is one that I am not comfortable with. Yes I have been bitten
by
> it. I always now backup using SQL Server to a .bak file and have
Arcserve.*
> back that file up.
>
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> : You can't normally backup the database files with ArcServe since they
are
> : always in use. I believe they have a way to bypass that but then what
> good
> : is backing up a file that is constantly changing. You can't restore the
> db
> : using these backups made from Arcserve since they are not consistent.
> What
> : you can do is basically one of 2 things. Either use the SQL Server
> plug-in
> : for ArcServe to have it issue the equivalent of a sql server backup or
> don't
> : even attempt to backup the database files with Arcserve and have it
backup
> : the files generated by the SQL Server backup.
> -- Microsoft Outlook Express 6.00.2800.1158
>|||it might behoove you to test the viability of your recovery resources.
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307031210.57474c7@.posting.google.com...
> From what I think:
> 1) The error messages during the beginning are because Arcserve is
> trying to backup the files on C:. These particular files are skipped
> doe to them being open and in use.
> 2) Later on during the backup I -think- Arcserve is backing up the
> database using the SQL agent which I installed. I can see that in the
> log.
>
> I was just wondering if this looks normal. Has anyone else used
> Arcserve? Is it normal to have the files skipped during the C: but
> then (it looks like) backed up during the SQL agent runs?
> Thanks|||I agree with that assessment but like I said, why bother to have it attempt
to backup those files (in the beginning) if you know they will only fail and
are useless anyway? And as nttp states, it wouldn't be a bad idea to
restore your backups somewhere to see if it's really doing what you hope it
is.
--
Andrew J. Kelly
SQL Server MVP
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307031210.57474c7@.posting.google.com...
> From what I think:
> 1) The error messages during the beginning are because Arcserve is
> trying to backup the files on C:. These particular files are skipped
> doe to them being open and in use.
> 2) Later on during the backup I -think- Arcserve is backing up the
> database using the SQL agent which I installed. I can see that in the
> log.
>
> I was just wondering if this looks normal. Has anyone else used
> Arcserve? Is it normal to have the files skipped during the C: but
> then (it looks like) backed up during the SQL agent runs?
> Thanks