Backup DB on compressed folder

Hi I have a very strange case here.
Currently our db server is short of space and as a temp solution database is backed up to a compressed folder. OS is W2K advanced Edition and SQL is Enterprise version. Database is 62GB now. every time Db backup fails after backup running for 2hrs and hal
f. the error msg says that "18210 :
BackupMedium::ReportIoError: write failure on backup device 'd:\mssql\backup\DataDMP01.BAK'. Operating system error 33(The process cannot access the file because another process has locked a portion of the file.)."
we have tried another file name or rebooting the server, but none helps.
I doubt that compressed fold causes the problem or exceeds the file size limit, but can not find any clue on it.
Pls help.
thanks for reply.
George
Compressed drives are not supported for sql server databases and to the best
of my knowledge backups either. If you are low on disk space I would
suggest using a product such as SQL LiteSpeed.
Andrew J. Kelly SQL MVP
"george" <georgey@.cryptologic.com> wrote in message
news:D916C3F2-92F3-405C-9951-39D3E1D095CC@.microsoft.com...
> Hi I have a very strange case here.
> Currently our db server is short of space and as a temp solution database
is backed up to a compressed folder. OS is W2K advanced Edition and SQL is
Enterprise version. Database is 62GB now. every time Db backup fails after
backup running for 2hrs and half. the error msg says that "18210 :
> BackupMedium::ReportIoError: write failure on backup device
'd:\mssql\backup\DataDMP01.BAK'. Operating system error 33(The process
cannot access the file because another process has locked a portion of the
file.)."
> we have tried another file name or rebooting the server, but none helps.
> I doubt that compressed fold causes the problem or exceeds the file size
limit, but can not find any clue on it.
> Pls help.
> thanks for reply.
> George

Backup DB on compressed folder

Hi I have a very strange case here.
Currently our db server is short of space and as a temp solution database is
backed up to a compressed folder. OS is W2K advanced Edition and SQL is Ent
erprise version. Database is 62GB now. every time Db backup fails after back
up running for 2hrs and hal
f. the error msg says that "18210 :
BackupMedium::ReportIoError: write failure on backup device 'd:\mssql\backup
\DataDMP01.BAK'. Operating system error 33(The process cannot access the fil
e because another process has locked a portion of the file.)."
we have tried another file name or rebooting the server, but none helps.
I doubt that compressed fold causes the problem or exceeds the file size lim
it, but can not find any clue on it.
Pls help.
thanks for reply.
GeorgeCompressed drives are not supported for sql server databases and to the best
of my knowledge backups either. If you are low on disk space I would
suggest using a product such as SQL LiteSpeed.
Andrew J. Kelly SQL MVP
"george" <georgey@.cryptologic.com> wrote in message
news:D916C3F2-92F3-405C-9951-39D3E1D095CC@.microsoft.com...
> Hi I have a very strange case here.
> Currently our db server is short of space and as a temp solution database
is backed up to a compressed folder. OS is W2K advanced Edition and SQL is
Enterprise version. Database is 62GB now. every time Db backup fails after
backup running for 2hrs and half. the error msg says that "18210 :
> BackupMedium::ReportIoError: write failure on backup device
'd:\mssql\backup\DataDMP01.BAK'. Operating system error 33(The process
cannot access the file because another process has locked a portion of the
file.)."
> we have tried another file name or rebooting the server, but none helps.
> I doubt that compressed fold causes the problem or exceeds the file size
limit, but can not find any clue on it.
> Pls help.
> thanks for reply.
> George

Backup and restore just part of the backup,

Hi All,
I got a question from my users. When I backup a Database from MS SQL I back
up the whole database. My question is. In case I want to restore just one or
two tables from the backup, it is possible.
Thanks in advance
RobertoNo, you can not natively restore tables from a backup file, your users might
be asking this to find out if you had to do a restore if you would have to
bring the entire database down. You typically would restore the backup to a
second test database and then transfer over the tables that you need from
the test to the production database.
If you use a third part tool like Lumigent Log Explorer I believe you could
selectively recover the tables but I've always had a question on how it
recovers the data held within those tables if time has elapsed to a point
where the previously referenced pages have been overwritten.
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Julio Gonzalez" <jcquijada@.hotmail.com> wrote in message
news:e0sGl0$aDHA.2572@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> I got a question from my users. When I backup a Database from MS SQL I
back
> up the whole database. My question is. In case I want to restore just one
or
> two tables from the backup, it is possible.
> Thanks in advance
> Roberto
>

Backup and Restore issue

I have a strange case. I do a full backup this morning. The size of
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?
Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:

> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>
|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.

Backup and Restore issue

I have a strange case. I do a full backup this morning. The size of
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.|||Thats good to know...
Thanks
Hari
<akkha1234@.gmail.com> wrote in message
news:1170369045.337711.234660@.l53g2000cwa.googlegroups.com...
> Dear Hari,
> You are absolutely correct. Learn one more thing on MSSQL again.
>

Backup and Restore issue

I have a strange case. I do a full backup this morning. The size of
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:

> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.|||Thats good to know...
Thanks
Hari
<akkha1234@.gmail.com> wrote in message
news:1170369045.337711.234660@.l53g2000cwa.googlegroups.com...
> Dear Hari,
> You are absolutely correct. Learn one more thing on MSSQL again.
>

Backup ?

I am setting up some sort of a backup server in the case our main production
server fails. A few questions.
When setting up a standby server do I do the following:
run full backup of the primary server. Then during the day do transaction
log backups and then apply those trans log backups to the standby server. I
currently have a differential db backup running every hour. I am guessing
that I don't need to do that. I just run the trans log backup and apply it
to my standby server at intervals during the day.
Does log shipping do the same thing. full backup in the morning then do log
shipping during the day? Any one better than the other. Do I need to have a
monitor server to monitor log shipping.
Try this
http://msdn.microsoft.com/library/de...erver_8elj.asp
and
http://msdn.microsoft.com/library/de...ackpt_3r21.asp
Jeff Duncan
MCDBA, MCSE+I
"JC" <striderguy56@.hotmail.com> wrote in message
news:O4Kph4UMEHA.3872@.TK2MSFTNGP12.phx.gbl...
> I am setting up some sort of a backup server in the case our main
production
> server fails. A few questions.
> When setting up a standby server do I do the following:
> run full backup of the primary server. Then during the day do transaction
> log backups and then apply those trans log backups to the standby server.
I
> currently have a differential db backup running every hour. I am guessing
> that I don't need to do that. I just run the trans log backup and apply it
> to my standby server at intervals during the day.
> Does log shipping do the same thing. full backup in the morning then do
log
> shipping during the day? Any one better than the other. Do I need to have
a
> monitor server to monitor log shipping.
>
>
|||Built in Log Shipping does a nice job of keeping things in sync and has a
built in monitoring tool.
Jeff Duncan
MCDBA, MCSE+I
"Jeff Duncan" <jduncan@.gtefcu.org> wrote in message
news:%23I5GRJVMEHA.1272@.tk2msftngp13.phx.gbl...
> Try this
>
http://msdn.microsoft.com/library/de...erver_8elj.asp
> and
>
http://msdn.microsoft.com/library/de...ackpt_3r21.asp[vbcol=seagreen]
>
> --
> Jeff Duncan
> MCDBA, MCSE+I
> "JC" <striderguy56@.hotmail.com> wrote in message
> news:O4Kph4UMEHA.3872@.TK2MSFTNGP12.phx.gbl...
> production
transaction[vbcol=seagreen]
server.[vbcol=seagreen]
> I
guessing[vbcol=seagreen]
it[vbcol=seagreen]
> log
have
> a
>

Backup ?

I am setting up some sort of a backup server in the case our main production
server fails. A few questions.
When setting up a standby server do I do the following:
run full backup of the primary server. Then during the day do transaction
log backups and then apply those trans log backups to the standby server. I
currently have a differential db backup running every hour. I am guessing
that I don't need to do that. I just run the trans log backup and apply it
to my standby server at intervals during the day.
Does log shipping do the same thing. full backup in the morning then do log
shipping during the day? Any one better than the other. Do I need to have a
monitor server to monitor log shipping.Try this
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_8elj.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_7_backpt_3r21.asp
Jeff Duncan
MCDBA, MCSE+I
"JC" <striderguy56@.hotmail.com> wrote in message
news:O4Kph4UMEHA.3872@.TK2MSFTNGP12.phx.gbl...
> I am setting up some sort of a backup server in the case our main
production
> server fails. A few questions.
> When setting up a standby server do I do the following:
> run full backup of the primary server. Then during the day do transaction
> log backups and then apply those trans log backups to the standby server.
I
> currently have a differential db backup running every hour. I am guessing
> that I don't need to do that. I just run the trans log backup and apply it
> to my standby server at intervals during the day.
> Does log shipping do the same thing. full backup in the morning then do
log
> shipping during the day? Any one better than the other. Do I need to have
a
> monitor server to monitor log shipping.
>
>|||Built in Log Shipping does a nice job of keeping things in sync and has a
built in monitoring tool.
--
Jeff Duncan
MCDBA, MCSE+I
"Jeff Duncan" <jduncan@.gtefcu.org> wrote in message
news:%23I5GRJVMEHA.1272@.tk2msftngp13.phx.gbl...
> Try this
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_8elj.asp
> and
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_7_backpt_3r21.asp
>
> --
> Jeff Duncan
> MCDBA, MCSE+I
> "JC" <striderguy56@.hotmail.com> wrote in message
> news:O4Kph4UMEHA.3872@.TK2MSFTNGP12.phx.gbl...
> > I am setting up some sort of a backup server in the case our main
> production
> > server fails. A few questions.
> >
> > When setting up a standby server do I do the following:
> >
> > run full backup of the primary server. Then during the day do
transaction
> > log backups and then apply those trans log backups to the standby
server.
> I
> > currently have a differential db backup running every hour. I am
guessing
> > that I don't need to do that. I just run the trans log backup and apply
it
> > to my standby server at intervals during the day.
> >
> > Does log shipping do the same thing. full backup in the morning then do
> log
> > shipping during the day? Any one better than the other. Do I need to
have
> a
> > monitor server to monitor log shipping.
> >
> >
> >
>

Backup ?

I am setting up some sort of a backup server in the case our main production
server fails. A few questions.
When setting up a standby server do I do the following:
run full backup of the primary server. Then during the day do transaction
log backups and then apply those trans log backups to the standby server. I
currently have a differential db backup running every hour. I am guessing
that I don't need to do that. I just run the trans log backup and apply it
to my standby server at intervals during the day.
Does log shipping do the same thing. full backup in the morning then do log
shipping during the day? Any one better than the other. Do I need to have a
monitor server to monitor log shipping.Try this
http://msdn.microsoft.com/library/d...>
ver_8elj.asp
and
http://msdn.microsoft.com/library/d...>
kpt_3r21.asp
Jeff Duncan
MCDBA, MCSE+I
"JC" <striderguy56@.hotmail.com> wrote in message
news:O4Kph4UMEHA.3872@.TK2MSFTNGP12.phx.gbl...
> I am setting up some sort of a backup server in the case our main
production
> server fails. A few questions.
> When setting up a standby server do I do the following:
> run full backup of the primary server. Then during the day do transaction
> log backups and then apply those trans log backups to the standby server.
I
> currently have a differential db backup running every hour. I am guessing
> that I don't need to do that. I just run the trans log backup and apply it
> to my standby server at intervals during the day.
> Does log shipping do the same thing. full backup in the morning then do
log
> shipping during the day? Any one better than the other. Do I need to have
a
> monitor server to monitor log shipping.
>
>|||Built in Log Shipping does a nice job of keeping things in sync and has a
built in monitoring tool.
Jeff Duncan
MCDBA, MCSE+I
"Jeff Duncan" <jduncan@.gtefcu.org> wrote in message
news:%23I5GRJVMEHA.1272@.tk2msftngp13.phx.gbl...
> Try this
>
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_8elj.asp[/ur
l]
> and
>
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_7_backpt_3r21.asp[/ur
l]
>
> --
> Jeff Duncan
> MCDBA, MCSE+I
> "JC" <striderguy56@.hotmail.com> wrote in message
> news:O4Kph4UMEHA.3872@.TK2MSFTNGP12.phx.gbl...
> production
transaction[vbcol=seagreen]
server.[vbcol=seagreen]
> I
guessing[vbcol=seagreen]
it[vbcol=seagreen]
> log
have[vbcol=seagreen]
> a
>

Backup

I'm not sure if I'm doing this correctly to ensure recovery in case of a
disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
attached to it. What I'm doing is during the night I run a backup through a
maintenance job in enterprise manager to the BACKUP directory in the SQL file
structure. On another server that has a tape drive I'm backing up this
BACKUP directory to tape. Should I be backing up anything else to ensure
disaster recovery.In summary, ensure that you are backing-up the system databases (there is an
option in the maintenance plan wizard to do this) as well as your user
databases. Make the maintenance plan for the system databases separate from
your plans for the user databases. Also ensure that if you are doing tran log
backups on the databases that have full recovery model, that you have the
backups for the simple model databases in a different plan or you will get an
error in the tran log backup job (even though the tran log backups will
succeed).
If you can backup to a remote server using UNC paths if your mssqlserver
service uses a service account (that has the necessary rights to the file
system on the remote server), that would be preferable. If you cannot
however, then your current backup strategy is adequate.
AndyP,
Sr. Database Administrator,
MCDBA 2003
"George Schneider" wrote:
> I'm not sure if I'm doing this correctly to ensure recovery in case of a
> disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> attached to it. What I'm doing is during the night I run a backup through a
> maintenance job in enterprise manager to the BACKUP directory in the SQL file
> structure. On another server that has a tape drive I'm backing up this
> BACKUP directory to tape. Should I be backing up anything else to ensure
> disaster recovery.
>|||I currently have all databses under on Maintenance plan. Why is it
neccessary to seperate the system and user db's into two?
"AndyP" wrote:
> In summary, ensure that you are backing-up the system databases (there is an
> option in the maintenance plan wizard to do this) as well as your user
> databases. Make the maintenance plan for the system databases separate from
> your plans for the user databases. Also ensure that if you are doing tran log
> backups on the databases that have full recovery model, that you have the
> backups for the simple model databases in a different plan or you will get an
> error in the tran log backup job (even though the tran log backups will
> succeed).
> If you can backup to a remote server using UNC paths if your mssqlserver
> service uses a service account (that has the necessary rights to the file
> system on the remote server), that would be preferable. If you cannot
> however, then your current backup strategy is adequate.
>
> --
> AndyP,
> Sr. Database Administrator,
> MCDBA 2003
>
> "George Schneider" wrote:
> > I'm not sure if I'm doing this correctly to ensure recovery in case of a
> > disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> > attached to it. What I'm doing is during the night I run a backup through a
> > maintenance job in enterprise manager to the BACKUP directory in the SQL file
> > structure. On another server that has a tape drive I'm backing up this
> > BACKUP directory to tape. Should I be backing up anything else to ensure
> > disaster recovery.
> >
> >|||Your plans will fail in an ungraceful manner if you have database in both full and simple recovery
mode and you try to do log backups in such a plan.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:0C3B4830-8855-45BF-8CC4-84C27E5EF174@.microsoft.com...
>I currently have all databses under on Maintenance plan. Why is it
> neccessary to seperate the system and user db's into two?
> "AndyP" wrote:
>> In summary, ensure that you are backing-up the system databases (there is an
>> option in the maintenance plan wizard to do this) as well as your user
>> databases. Make the maintenance plan for the system databases separate from
>> your plans for the user databases. Also ensure that if you are doing tran log
>> backups on the databases that have full recovery model, that you have the
>> backups for the simple model databases in a different plan or you will get an
>> error in the tran log backup job (even though the tran log backups will
>> succeed).
>> If you can backup to a remote server using UNC paths if your mssqlserver
>> service uses a service account (that has the necessary rights to the file
>> system on the remote server), that would be preferable. If you cannot
>> however, then your current backup strategy is adequate.
>>
>> --
>> AndyP,
>> Sr. Database Administrator,
>> MCDBA 2003
>>
>> "George Schneider" wrote:
>> > I'm not sure if I'm doing this correctly to ensure recovery in case of a
>> > disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
>> > attached to it. What I'm doing is during the night I run a backup through a
>> > maintenance job in enterprise manager to the BACKUP directory in the SQL file
>> > structure. On another server that has a tape drive I'm backing up this
>> > BACKUP directory to tape. Should I be backing up anything else to ensure
>> > disaster recovery.
>> >
>> >

Backup

I'm not sure if I'm doing this correctly to ensure recovery in case of a
disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
attached to it. What I'm doing is during the night I run a backup through
a
maintenance job in enterprise manager to the BACKUP directory in the SQL fil
e
structure. On another server that has a tape drive I'm backing up this
BACKUP directory to tape. Should I be backing up anything else to ensure
disaster recovery.In summary, ensure that you are backing-up the system databases (there is an
option in the maintenance plan wizard to do this) as well as your user
databases. Make the maintenance plan for the system databases separate from
your plans for the user databases. Also ensure that if you are doing tran lo
g
backups on the databases that have full recovery model, that you have the
backups for the simple model databases in a different plan or you will get a
n
error in the tran log backup job (even though the tran log backups will
succeed).
If you can backup to a remote server using UNC paths if your mssqlserver
service uses a service account (that has the necessary rights to the file
system on the remote server), that would be preferable. If you cannot
however, then your current backup strategy is adequate.
AndyP,
Sr. Database Administrator,
MCDBA 2003
"George Schneider" wrote:

> I'm not sure if I'm doing this correctly to ensure recovery in case of a
> disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> attached to it. What I'm doing is during the night I run a backup throug
h a
> maintenance job in enterprise manager to the BACKUP directory in the SQL f
ile
> structure. On another server that has a tape drive I'm backing up this
> BACKUP directory to tape. Should I be backing up anything else to ensure
> disaster recovery.
>|||I currently have all databses under on Maintenance plan. Why is it
neccessary to seperate the system and user db's into two?
"AndyP" wrote:
[vbcol=seagreen]
> In summary, ensure that you are backing-up the system databases (there is
an
> option in the maintenance plan wizard to do this) as well as your user
> databases. Make the maintenance plan for the system databases separate fro
m
> your plans for the user databases. Also ensure that if you are doing tran
log
> backups on the databases that have full recovery model, that you have the
> backups for the simple model databases in a different plan or you will get
an
> error in the tran log backup job (even though the tran log backups will
> succeed).
> If you can backup to a remote server using UNC paths if your mssqlserver
> service uses a service account (that has the necessary rights to the file
> system on the remote server), that would be preferable. If you cannot
> however, then your current backup strategy is adequate.
>
> --
> AndyP,
> Sr. Database Administrator,
> MCDBA 2003
>
> "George Schneider" wrote:
>|||Your plans will fail in an ungraceful manner if you have database in both fu
ll and simple recovery
mode and you try to do log backups in such a plan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:0C3B4830-8855-45BF-8CC4-84C27E5EF174@.microsoft.com...[vbcol=seagreen]
>I currently have all databses under on Maintenance plan. Why is it
> neccessary to seperate the system and user db's into two?
> "AndyP" wrote:
>

Backup

I'm not sure if I'm doing this correctly to ensure recovery in case of a
disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
attached to it. What I'm doing is during the night I run a backup through a
maintenance job in enterprise manager to the BACKUP directory in the SQL file
structure. On another server that has a tape drive I'm backing up this
BACKUP directory to tape. Should I be backing up anything else to ensure
disaster recovery.
In summary, ensure that you are backing-up the system databases (there is an
option in the maintenance plan wizard to do this) as well as your user
databases. Make the maintenance plan for the system databases separate from
your plans for the user databases. Also ensure that if you are doing tran log
backups on the databases that have full recovery model, that you have the
backups for the simple model databases in a different plan or you will get an
error in the tran log backup job (even though the tran log backups will
succeed).
If you can backup to a remote server using UNC paths if your mssqlserver
service uses a service account (that has the necessary rights to the file
system on the remote server), that would be preferable. If you cannot
however, then your current backup strategy is adequate.
AndyP,
Sr. Database Administrator,
MCDBA 2003
"George Schneider" wrote:

> I'm not sure if I'm doing this correctly to ensure recovery in case of a
> disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> attached to it. What I'm doing is during the night I run a backup through a
> maintenance job in enterprise manager to the BACKUP directory in the SQL file
> structure. On another server that has a tape drive I'm backing up this
> BACKUP directory to tape. Should I be backing up anything else to ensure
> disaster recovery.
>
|||I currently have all databses under on Maintenance plan. Why is it
neccessary to seperate the system and user db's into two?
"AndyP" wrote:
[vbcol=seagreen]
> In summary, ensure that you are backing-up the system databases (there is an
> option in the maintenance plan wizard to do this) as well as your user
> databases. Make the maintenance plan for the system databases separate from
> your plans for the user databases. Also ensure that if you are doing tran log
> backups on the databases that have full recovery model, that you have the
> backups for the simple model databases in a different plan or you will get an
> error in the tran log backup job (even though the tran log backups will
> succeed).
> If you can backup to a remote server using UNC paths if your mssqlserver
> service uses a service account (that has the necessary rights to the file
> system on the remote server), that would be preferable. If you cannot
> however, then your current backup strategy is adequate.
>
> --
> AndyP,
> Sr. Database Administrator,
> MCDBA 2003
>
> "George Schneider" wrote:
|||Your plans will fail in an ungraceful manner if you have database in both full and simple recovery
mode and you try to do log backups in such a plan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:0C3B4830-8855-45BF-8CC4-84C27E5EF174@.microsoft.com...[vbcol=seagreen]
>I currently have all databses under on Maintenance plan. Why is it
> neccessary to seperate the system and user db's into two?
> "AndyP" wrote: