Backing Up Issue

My transaction log is growing really big few hundred MB.
However before I do transaction log backup, I read that I
need to do a full database backup at least once. Also
clearing the transaction log before you backup the
database results in a smaller backup of the full database
I should have done earlier when the log was small.
My question is : Does it mean that I have no other way
except to back up the database with the full transaction
log.. ?
After the full database backup, I will then do a
transaction log backupYou could truncate the log and immediately perform a full database backup.
Given that you're never performed a full database backup anyway, this should
be fine in your situation.
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
followed by DBCC SHRINKFILE .. command for the log file.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:39bd01c47f48$57251f40$a301280a@.phx.gbl...
> My transaction log is growing really big few hundred MB.
> However before I do transaction log backup, I read that I
> need to do a full database backup at least once. Also
> clearing the transaction log before you backup the
> database results in a smaller backup of the full database
> I should have done earlier when the log was small.
> My question is : Does it mean that I have no other way
> except to back up the database with the full transaction
> log.. ?
> After the full database backup, I will then do a
> transaction log backup
>|||When the database is in FULL recovery mode, the log will automatically
truncate until you do the first full db backup, because it has no value
until then...So your log should not be growing if you haven't made the first
db backup...
Peter's response is one of your options...
Long term, if you need to be able to recover all of the data.
Start scheduling a regular full database backup, followed by regular log
backups as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:39bd01c47f48$57251f40$a301280a@.phx.gbl...
> My transaction log is growing really big few hundred MB.
> However before I do transaction log backup, I read that I
> need to do a full database backup at least once. Also
> clearing the transaction log before you backup the
> database results in a smaller backup of the full database
> I should have done earlier when the log was small.
> My question is : Does it mean that I have no other way
> except to back up the database with the full transaction
> log.. ?
> After the full database backup, I will then do a
> transaction log backup
>|||Thanks for the advice..
So even though I've not done even one full database
backup before, I can still safely 1) Backup the log with
truncate only, followed by 2) DBCC Shrinkfile for the log
3) Then do a full database backup...
Can I say it is safe to NOT do at least one full database
backup before doing a log ?|||> So even though I've not done even one full database
> backup before, I can still safely 1) Backup the log with
> truncate only, followed by 2) DBCC Shrinkfile for the log
> 3) Then do a full database backup...
Yes, since the log is useless without a full database backup. I believe SQL
Server makes this check too i.e. prevents you from making a trx log backup
if no full backup has ever been done.

> Can I say it is safe to NOT do at least one full database
> backup before doing a log ?
What do you mean by 'doing a log'?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:49aa01c4803a$aa694260$a501280a@.phx.gbl...
> Thanks for the advice..
> So even though I've not done even one full database
> backup before, I can still safely 1) Backup the log with
> truncate only, followed by 2) DBCC Shrinkfile for the log
> 3) Then do a full database backup...
> Can I say it is safe to NOT do at least one full database
> backup before doing a log ?
>
>|||Hi Peter,
Thanks for you reply to the first part of my question..

database[vbcol=seagreen]
>What do you mean by 'doing a log'?
I mean 'doing a transaction log backup' Please excuse me
for my type error.|||If you change from Simple to Full or Bulk-logged recovery, or if you are
intializing log shipping, you must take a full database backup before
starting transaction log backups. The database annot be in the Simple
recovery model if you want to take transaction log backups.
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:564501c4810b$02640830$a501280a@.phx.gbl...
> Hi Peter,
> Thanks for you reply to the first part of my question..
>
> database
> I mean 'doing a transaction log backup' Please excuse me
> for my type error.
>

Backing Up Issue

My transaction log is growing really big few hundred MB.
However before I do transaction log backup, I read that I
need to do a full database backup at least once. Also
clearing the transaction log before you backup the
database results in a smaller backup of the full database
I should have done earlier when the log was small.
My question is : Does it mean that I have no other way
except to back up the database with the full transaction
log.. ?
After the full database backup, I will then do a
transaction log backup
You could truncate the log and immediately perform a full database backup.
Given that you're never performed a full database backup anyway, this should
be fine in your situation.
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
followed by DBCC SHRINKFILE .. command for the log file.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:39bd01c47f48$57251f40$a301280a@.phx.gbl...
> My transaction log is growing really big few hundred MB.
> However before I do transaction log backup, I read that I
> need to do a full database backup at least once. Also
> clearing the transaction log before you backup the
> database results in a smaller backup of the full database
> I should have done earlier when the log was small.
> My question is : Does it mean that I have no other way
> except to back up the database with the full transaction
> log.. ?
> After the full database backup, I will then do a
> transaction log backup
>
|||When the database is in FULL recovery mode, the log will automatically
truncate until you do the first full db backup, because it has no value
until then...So your log should not be growing if you haven't made the first
db backup...
Peter's response is one of your options...
Long term, if you need to be able to recover all of the data.
Start scheduling a regular full database backup, followed by regular log
backups as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:39bd01c47f48$57251f40$a301280a@.phx.gbl...
> My transaction log is growing really big few hundred MB.
> However before I do transaction log backup, I read that I
> need to do a full database backup at least once. Also
> clearing the transaction log before you backup the
> database results in a smaller backup of the full database
> I should have done earlier when the log was small.
> My question is : Does it mean that I have no other way
> except to back up the database with the full transaction
> log.. ?
> After the full database backup, I will then do a
> transaction log backup
>
|||Thanks for the advice..
So even though I've not done even one full database
backup before, I can still safely 1) Backup the log with
truncate only, followed by 2) DBCC Shrinkfile for the log
3) Then do a full database backup...
Can I say it is safe to NOT do at least one full database
backup before doing a log ?
|||> So even though I've not done even one full database
> backup before, I can still safely 1) Backup the log with
> truncate only, followed by 2) DBCC Shrinkfile for the log
> 3) Then do a full database backup...
Yes, since the log is useless without a full database backup. I believe SQL
Server makes this check too i.e. prevents you from making a trx log backup
if no full backup has ever been done.

> Can I say it is safe to NOT do at least one full database
> backup before doing a log ?
What do you mean by 'doing a log'?
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:49aa01c4803a$aa694260$a501280a@.phx.gbl...
> Thanks for the advice..
> So even though I've not done even one full database
> backup before, I can still safely 1) Backup the log with
> truncate only, followed by 2) DBCC Shrinkfile for the log
> 3) Then do a full database backup...
> Can I say it is safe to NOT do at least one full database
> backup before doing a log ?
>
>
|||Hi Peter,
Thanks for you reply to the first part of my question..
[vbcol=seagreen]
database
>What do you mean by 'doing a log'?
I mean 'doing a transaction log backup' Please excuse me
for my type error.
|||If you change from Simple to Full or Bulk-logged recovery, or if you are
intializing log shipping, you must take a full database backup before
starting transaction log backups. The database annot be in the Simple
recovery model if you want to take transaction log backups.
Hope this helps,
Ron
Ron Talmage
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:564501c4810b$02640830$a501280a@.phx.gbl...
> Hi Peter,
> Thanks for you reply to the first part of my question..
> database
> I mean 'doing a transaction log backup' Please excuse me
> for my type error.
>

Backing Up Issue

My transaction log is growing really big few hundred MB.
However before I do transaction log backup, I read that I
need to do a full database backup at least once. Also
clearing the transaction log before you backup the
database results in a smaller backup of the full database
I should have done earlier when the log was small.
My question is : Does it mean that I have no other way
except to back up the database with the full transaction
log.. ?
After the full database backup, I will then do a
transaction log backupYou could truncate the log and immediately perform a full database backup.
Given that you're never performed a full database backup anyway, this should
be fine in your situation.
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
followed by DBCC SHRINKFILE .. command for the log file.
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:39bd01c47f48$57251f40$a301280a@.phx.gbl...
> My transaction log is growing really big few hundred MB.
> However before I do transaction log backup, I read that I
> need to do a full database backup at least once. Also
> clearing the transaction log before you backup the
> database results in a smaller backup of the full database
> I should have done earlier when the log was small.
> My question is : Does it mean that I have no other way
> except to back up the database with the full transaction
> log.. ?
> After the full database backup, I will then do a
> transaction log backup
>|||When the database is in FULL recovery mode, the log will automatically
truncate until you do the first full db backup, because it has no value
until then...So your log should not be growing if you haven't made the first
db backup...
Peter's response is one of your options...
Long term, if you need to be able to recover all of the data.
Start scheduling a regular full database backup, followed by regular log
backups as well...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:39bd01c47f48$57251f40$a301280a@.phx.gbl...
> My transaction log is growing really big few hundred MB.
> However before I do transaction log backup, I read that I
> need to do a full database backup at least once. Also
> clearing the transaction log before you backup the
> database results in a smaller backup of the full database
> I should have done earlier when the log was small.
> My question is : Does it mean that I have no other way
> except to back up the database with the full transaction
> log.. ?
> After the full database backup, I will then do a
> transaction log backup
>|||Thanks for the advice..
So even though I've not done even one full database
backup before, I can still safely 1) Backup the log with
truncate only, followed by 2) DBCC Shrinkfile for the log
3) Then do a full database backup...
Can I say it is safe to NOT do at least one full database
backup before doing a log ?|||> So even though I've not done even one full database
> backup before, I can still safely 1) Backup the log with
> truncate only, followed by 2) DBCC Shrinkfile for the log
> 3) Then do a full database backup...
Yes, since the log is useless without a full database backup. I believe SQL
Server makes this check too i.e. prevents you from making a trx log backup
if no full backup has ever been done.
> Can I say it is safe to NOT do at least one full database
> backup before doing a log ?
What do you mean by 'doing a log'?
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:49aa01c4803a$aa694260$a501280a@.phx.gbl...
> Thanks for the advice..
> So even though I've not done even one full database
> backup before, I can still safely 1) Backup the log with
> truncate only, followed by 2) DBCC Shrinkfile for the log
> 3) Then do a full database backup...
> Can I say it is safe to NOT do at least one full database
> backup before doing a log ?
>
>|||Hi Peter,
Thanks for you reply to the first part of my question..
>> Can I say it is safe to NOT do at least one full
database
>> backup before doing a log ?
>What do you mean by 'doing a log'?
I mean 'doing a transaction log backup' Please excuse me
for my type error.|||If you change from Simple to Full or Bulk-logged recovery, or if you are
intializing log shipping, you must take a full database backup before
starting transaction log backups. The database annot be in the Simple
recovery model if you want to take transaction log backups.
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:564501c4810b$02640830$a501280a@.phx.gbl...
> Hi Peter,
> Thanks for you reply to the first part of my question..
> >> Can I say it is safe to NOT do at least one full
> database
> >> backup before doing a log ?
> >
> >What do you mean by 'doing a log'?
> I mean 'doing a transaction log backup' Please excuse me
> for my type error.
>

Backing up and ever growing database

Dear Sirs,
I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
what is the best to back it up. All the data is critical to be
preserved.
Any method would be apreciated.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!Elie
.htm#Step1" target="_blank">http://vyaskn.tripod.com/ sql_serve...r />
.htm#Step1
--administaiting
best practices
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hi,
I suggest you to do below backup strategy:-
1. Sunday - Full database Backup
2. Every day night - Differential backup
3. Every 30 minutes or 1 hour Transaction log backup.
have a look into the details of above strategies:-
http://techrepublic.com.com/5100-6268-1043671-3.html
Thanks
Hari
MCDBA
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hari
Each Diff backup will be grown so on Saturday you will have a pretty big
file and look,if you want to restore database you will need to restore FULL
backup and then a bigger (last) DIFF backup which will consume more time
and resourse.
In my opinion he can do it every night FULL backup of the database and then
every 30 min or an hour LOG file.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I suggest you to do below backup strategy:-
> 1. Sunday - Full database Backup
> 2. Every day night - Differential backup
> 3. Every 30 minutes or 1 hour Transaction log backup.
> have a look into the details of above strategies:-
> http://techrepublic.com.com/5100-6268-1043671-3.html
>
> --
> Thanks
> Hari
> MCDBA
> "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>|||thxs for those suggestions
In fact the data is so important that we are doing a transaction log
back up every 5 minutes, i was thinking maybe another backup server with
data synchronized continuesly like replication or something, or maybe
mdf files synchronization.
any suggestion from someone with such experience would be much
apreciated
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||If you are worried about losing data in that 5 minute window, the easiest
solution would be to use RAID 1,5, or 10 for your data files and log files.
For heavy duty real-time synchronisation, you would be looking at
implementing remote mirroring on a SAN.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:e7N%23I9rUEHA.4088@.TK2MSFTNGP09.phx.gbl...
>
> thxs for those suggestions
> In fact the data is so important that we are doing a transaction log
> back up every 5 minutes, i was thinking maybe another backup server with
> data synchronized continuesly like replication or something, or maybe
> mdf files synchronization.
> any suggestion from someone with such experience would be much
> apreciated
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Elie
You can set up LOG_SHIPPING.
http://www.sql-server-performance.c...og_shipping.asp
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:e7N%23I9rUEHA.4088@.TK2MSFTNGP09.phx.gbl...
>
> thxs for those suggestions
> In fact the data is so important that we are doing a transaction log
> back up every 5 minutes, i was thinking maybe another backup server with
> data synchronized continuesly like replication or something, or maybe
> mdf files synchronization.
> any suggestion from someone with such experience would be much
> apreciated
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hi Uri,
I agree with you 90%, rest 10% I disagree because if the database size grows
above 50Gb, it is always
advised to do a differential during week days. This will save your backup
time as well as reduce the IO used for backup operations.
Do you agree with me or
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> Hari
> Each Diff backup will be grown so on Saturday you will have a pretty big
> file and look,if you want to restore database you will need to restore
FULL
> backup and then a bigger (last) DIFF backup which will consume more time
> and resourse.
> In my opinion he can do it every night FULL backup of the database and
then
> every 30 min or an hour LOG file.
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
>|||Well
What is about restoring ?
I'd use DIFF backup if amount of time spent in recovering the database by
applying all the transaction logs is not acceptable.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> Hi Uri,
> I agree with you 90%, rest 10% I disagree because if the database size
grows
> above 50Gb, it is always
> advised to do a differential during week days. This will save your backup
> time as well as reduce the IO used for backup operations.
> Do you agree with me or
>
> --
> Thanks
> Hari
> MCDBA
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> FULL
time[vbcol=seagreen]
> then
week,[vbcol=seagreen]
>|||Hi,
OK I Agree, Both areas got it own demerits. But still if you have a huge
database (1 TB) the full database
backup is not a feasible solution because it will take a long time even in a
SAN .
Restore?
In case of Restore, I will restore the Differential backup taken last night
and start applying the Transaction log one by one till last file.
Please explain me if you have a better approach.
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urcN7nsUEHA.4064@.TK2MSFTNGP11.phx.gbl...
> Well
> What is about restoring ?
> I'd use DIFF backup if amount of time spent in recovering the database by
> applying all the transaction logs is not acceptable.
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> grows
backup[vbcol=seagreen]
big[vbcol=seagreen]
> time
> week,
>sql

Backing up and ever growing database

Dear Sirs,
I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
what is the best to back it up. All the data is critical to be
preserved.
Any method would be apreciated.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
Elie
http://vyaskn.tripod.com/sql_server_...ices.htm#Step1 --administaiting
best practices
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi,
I suggest you to do below backup strategy:-
1. Sunday - Full database Backup
2. Every day night - Differential backup
3. Every 30 minutes or 1 hour Transaction log backup.
have a look into the details of above strategies:-
http://techrepublic.com.com/5100-6268-1043671-3.html
Thanks
Hari
MCDBA
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hari
Each Diff backup will be grown so on Saturday you will have a pretty big
file and look,if you want to restore database you will need to restore FULL
backup and then a bigger (last) DIFF backup which will consume more time
and resourse.
In my opinion he can do it every night FULL backup of the database and then
every 30 min or an hour LOG file.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I suggest you to do below backup strategy:-
> 1. Sunday - Full database Backup
> 2. Every day night - Differential backup
> 3. Every 30 minutes or 1 hour Transaction log backup.
> have a look into the details of above strategies:-
> http://techrepublic.com.com/5100-6268-1043671-3.html
>
> --
> Thanks
> Hari
> MCDBA
> "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
|||thxs for those suggestions
In fact the data is so important that we are doing a transaction log
back up every 5 minutes, i was thinking maybe another backup server with
data synchronized continuesly like replication or something, or maybe
mdf files synchronization.
any suggestion from someone with such experience would be much
apreciated
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||If you are worried about losing data in that 5 minute window, the easiest
solution would be to use RAID 1,5, or 10 for your data files and log files.
For heavy duty real-time synchronisation, you would be looking at
implementing remote mirroring on a SAN.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:e7N%23I9rUEHA.4088@.TK2MSFTNGP09.phx.gbl...
>
> thxs for those suggestions
> In fact the data is so important that we are doing a transaction log
> back up every 5 minutes, i was thinking maybe another backup server with
> data synchronized continuesly like replication or something, or maybe
> mdf files synchronization.
> any suggestion from someone with such experience would be much
> apreciated
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
|||Elie
You can set up LOG_SHIPPING.
http://www.sql-server-performance.co...g_shipping.asp
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:e7N%23I9rUEHA.4088@.TK2MSFTNGP09.phx.gbl...
>
> thxs for those suggestions
> In fact the data is so important that we are doing a transaction log
> back up every 5 minutes, i was thinking maybe another backup server with
> data synchronized continuesly like replication or something, or maybe
> mdf files synchronization.
> any suggestion from someone with such experience would be much
> apreciated
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi Uri,
I agree with you 90%, rest 10% I disagree because if the database size grows
above 50Gb, it is always
advised to do a differential during week days. This will save your backup
time as well as reduce the IO used for backup operations.
Do you agree with me or
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> Hari
> Each Diff backup will be grown so on Saturday you will have a pretty big
> file and look,if you want to restore database you will need to restore
FULL
> backup and then a bigger (last) DIFF backup which will consume more time
> and resourse.
> In my opinion he can do it every night FULL backup of the database and
then
> every 30 min or an hour LOG file.
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
>
|||Well
What is about restoring ?
I'd use DIFF backup if amount of time spent in recovering the database by
applying all the transaction logs is not acceptable.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> Hi Uri,
> I agree with you 90%, rest 10% I disagree because if the database size
grows[vbcol=seagreen]
> above 50Gb, it is always
> advised to do a differential during week days. This will save your backup
> time as well as reduce the IO used for backup operations.
> Do you agree with me or
>
> --
> Thanks
> Hari
> MCDBA
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> FULL
time[vbcol=seagreen]
> then
week,
>
|||Hi,
OK I Agree, Both areas got it own demerits. But still if you have a huge
database (1 TB) the full database
backup is not a feasible solution because it will take a long time even in a
SAN .
Restore?
In case of Restore, I will restore the Differential backup taken last night
and start applying the Transaction log one by one till last file.
Please explain me if you have a better approach.
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urcN7nsUEHA.4064@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Well
> What is about restoring ?
> I'd use DIFF backup if amount of time spent in recovering the database by
> applying all the transaction logs is not acceptable.
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> grows
backup[vbcol=seagreen]
big
> time
> week,
>

Backing up and ever growing database

Dear Sirs,
I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
what is the best to back it up. All the data is critical to be
preserved.
Any method would be apreciated.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!Elie
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1 --administaiting
best practices
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hi,
I suggest you to do below backup strategy:-
1. Sunday - Full database Backup
2. Every day night - Differential backup
3. Every 30 minutes or 1 hour Transaction log backup.
have a look into the details of above strategies:-
http://techrepublic.com.com/5100-6268-1043671-3.html
Thanks
Hari
MCDBA
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hari
Each Diff backup will be grown so on Saturday you will have a pretty big
file and look,if you want to restore database you will need to restore FULL
backup and then a bigger (last) DIFF backup which will consume more time
and resourse.
In my opinion he can do it every night FULL backup of the database and then
every 30 min or an hour LOG file.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I suggest you to do below backup strategy:-
> 1. Sunday - Full database Backup
> 2. Every day night - Differential backup
> 3. Every 30 minutes or 1 hour Transaction log backup.
> have a look into the details of above strategies:-
> http://techrepublic.com.com/5100-6268-1043671-3.html
>
> --
> Thanks
> Hari
> MCDBA
> "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> >
> >
> > Dear Sirs,
> >
> > I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> > what is the best to back it up. All the data is critical to be
> > preserved.
> >
> > Any method would be apreciated.
> >
> > *** Sent via Devdex http://www.devdex.com ***
> > Don't just participate in USENET...get rewarded for it!
>|||Well
What is about restoring ?
I'd use DIFF backup if amount of time spent in recovering the database by
applying all the transaction logs is not acceptable.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> Hi Uri,
> I agree with you 90%, rest 10% I disagree because if the database size
grows
> above 50Gb, it is always
> advised to do a differential during week days. This will save your backup
> time as well as reduce the IO used for backup operations.
> Do you agree with me or :)
>
> --
> Thanks
> Hari
> MCDBA
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> > Hari
> > Each Diff backup will be grown so on Saturday you will have a pretty big
> > file and look,if you want to restore database you will need to restore
> FULL
> > backup and then a bigger (last) DIFF backup which will consume more
time
> > and resourse.
> > In my opinion he can do it every night FULL backup of the database and
> then
> > every 30 min or an hour LOG file.
> >
> >
> > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> > > Hi,
> > >
> > > I suggest you to do below backup strategy:-
> > >
> > > 1. Sunday - Full database Backup
> > > 2. Every day night - Differential backup
> > > 3. Every 30 minutes or 1 hour Transaction log backup.
> > >
> > > have a look into the details of above strategies:-
> > >
> > > http://techrepublic.com.com/5100-6268-1043671-3.html
> > >
> > >
> > > --
> > > Thanks
> > > Hari
> > > MCDBA
> > > "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> > > news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> > > >
> > > >
> > > > Dear Sirs,
> > > >
> > > > I have an sql 2000 ever growing databse, 24 hours a day 7 days a
week,
> > > > what is the best to back it up. All the data is critical to be
> > > > preserved.
> > > >
> > > > Any method would be apreciated.
> > > >
> > > > *** Sent via Devdex http://www.devdex.com ***
> > > > Don't just participate in USENET...get rewarded for it!
> > >
> > >
> >
> >
>|||Hi,
OK I Agree, Both areas got it own demerits. But still if you have a huge
database (1 TB) the full database
backup is not a feasible solution because it will take a long time even in a
SAN .
Restore?
In case of Restore, I will restore the Differential backup taken last night
and start applying the Transaction log one by one till last file.
Please explain me if you have a better approach.
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:urcN7nsUEHA.4064@.TK2MSFTNGP11.phx.gbl...
> Well
> What is about restoring ?
> I'd use DIFF backup if amount of time spent in recovering the database by
> applying all the transaction logs is not acceptable.
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> > Hi Uri,
> >
> > I agree with you 90%, rest 10% I disagree because if the database size
> grows
> > above 50Gb, it is always
> > advised to do a differential during week days. This will save your
backup
> > time as well as reduce the IO used for backup operations.
> >
> > Do you agree with me or :)
> >
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> > > Hari
> > > Each Diff backup will be grown so on Saturday you will have a pretty
big
> > > file and look,if you want to restore database you will need to restore
> > FULL
> > > backup and then a bigger (last) DIFF backup which will consume more
> time
> > > and resourse.
> > > In my opinion he can do it every night FULL backup of the database and
> > then
> > > every 30 min or an hour LOG file.
> > >
> > >
> > > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > > news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> > > > Hi,
> > > >
> > > > I suggest you to do below backup strategy:-
> > > >
> > > > 1. Sunday - Full database Backup
> > > > 2. Every day night - Differential backup
> > > > 3. Every 30 minutes or 1 hour Transaction log backup.
> > > >
> > > > have a look into the details of above strategies:-
> > > >
> > > > http://techrepublic.com.com/5100-6268-1043671-3.html
> > > >
> > > >
> > > > --
> > > > Thanks
> > > > Hari
> > > > MCDBA
> > > > "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> > > > news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> > > > >
> > > > >
> > > > > Dear Sirs,
> > > > >
> > > > > I have an sql 2000 ever growing databse, 24 hours a day 7 days a
> week,
> > > > > what is the best to back it up. All the data is critical to be
> > > > > preserved.
> > > > >
> > > > > Any method would be apreciated.
> > > > >
> > > > > *** Sent via Devdex http://www.devdex.com ***
> > > > > Don't just participate in USENET...get rewarded for it!
> > > >
> > > >
> > >
> > >
> >
> >
>|||In addition to the other comments... Good data placement will be a
requirement for up to the minute recovery..
1. Keep log away from database data ( different physical drive)
2. Keep database data away from master( Different physical drive).
3. Mirror the log
Doing so with good backup practices ( including doing your dbcc checkdb)
will get you up-to the minute recovery under most conditions.
The risk area is the time between log backups... If the Server simply
explodes, what you have lost is the changes since the last log backup...
Doing log backups frequently reduce this potential ( and probably rare)
opportunity for data loss.
Neither Log Shipping nor clustering will improve your recoverability.
Clustering increases availability - nothing more.
Hope this helps...
But congratulations to you... You are doing the right things, and thinking
the right way... This forum is the perfect place to have such a
discussion...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
>
> Dear Sirs,
> I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> what is the best to back it up. All the data is critical to be
> preserved.
> Any method would be apreciated.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hari
> In case of Restore, I will restore the Differential backup taken last
night
> and start applying the Transaction log one by one till last file.
But do not forget restore FULL backup database before it (1T):)
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:umQy62sUEHA.2564@.TK2MSFTNGP11.phx.gbl...
> Hi,
> OK I Agree, Both areas got it own demerits. But still if you have a huge
> database (1 TB) the full database
> backup is not a feasible solution because it will take a long time even in
a
> SAN .
> Restore?
> In case of Restore, I will restore the Differential backup taken last
night
> and start applying the Transaction log one by one till last file.
> Please explain me if you have a better approach.
>
> --
> Thanks
> Hari
> MCDBA
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:urcN7nsUEHA.4064@.TK2MSFTNGP11.phx.gbl...
> > Well
> > What is about restoring ?
> > I'd use DIFF backup if amount of time spent in recovering the database
by
> > applying all the transaction logs is not acceptable.
> >
> > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> > > Hi Uri,
> > >
> > > I agree with you 90%, rest 10% I disagree because if the database size
> > grows
> > > above 50Gb, it is always
> > > advised to do a differential during week days. This will save your
> backup
> > > time as well as reduce the IO used for backup operations.
> > >
> > > Do you agree with me or :)
> > >
> > >
> > > --
> > > Thanks
> > > Hari
> > > MCDBA
> > > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > > news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> > > > Hari
> > > > Each Diff backup will be grown so on Saturday you will have a pretty
> big
> > > > file and look,if you want to restore database you will need to
restore
> > > FULL
> > > > backup and then a bigger (last) DIFF backup which will consume more
> > time
> > > > and resourse.
> > > > In my opinion he can do it every night FULL backup of the database
and
> > > then
> > > > every 30 min or an hour LOG file.
> > > >
> > > >
> > > > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > > > news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> > > > > Hi,
> > > > >
> > > > > I suggest you to do below backup strategy:-
> > > > >
> > > > > 1. Sunday - Full database Backup
> > > > > 2. Every day night - Differential backup
> > > > > 3. Every 30 minutes or 1 hour Transaction log backup.
> > > > >
> > > > > have a look into the details of above strategies:-
> > > > >
> > > > > http://techrepublic.com.com/5100-6268-1043671-3.html
> > > > >
> > > > >
> > > > > --
> > > > > Thanks
> > > > > Hari
> > > > > MCDBA
> > > > > "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> > > > > news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> > > > > >
> > > > > >
> > > > > > Dear Sirs,
> > > > > >
> > > > > > I have an sql 2000 ever growing databse, 24 hours a day 7 days a
> > week,
> > > > > > what is the best to back it up. All the data is critical to be
> > > > > > preserved.
> > > > > >
> > > > > > Any method would be apreciated.
> > > > > >
> > > > > > *** Sent via Devdex http://www.devdex.com ***
> > > > > > Don't just participate in USENET...get rewarded for it!
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Hi Uri,
I agree with you 90%, rest 10% I disagree because if the database size grows
above 50Gb, it is always
advised to do a differential during week days. This will save your backup
time as well as reduce the IO used for backup operations.
Do you agree with me or :)
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> Hari
> Each Diff backup will be grown so on Saturday you will have a pretty big
> file and look,if you want to restore database you will need to restore
FULL
> backup and then a bigger (last) DIFF backup which will consume more time
> and resourse.
> In my opinion he can do it every night FULL backup of the database and
then
> every 30 min or an hour LOG file.
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> > Hi,
> >
> > I suggest you to do below backup strategy:-
> >
> > 1. Sunday - Full database Backup
> > 2. Every day night - Differential backup
> > 3. Every 30 minutes or 1 hour Transaction log backup.
> >
> > have a look into the details of above strategies:-
> >
> > http://techrepublic.com.com/5100-6268-1043671-3.html
> >
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> > "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> > news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> > >
> > >
> > > Dear Sirs,
> > >
> > > I have an sql 2000 ever growing databse, 24 hours a day 7 days a week,
> > > what is the best to back it up. All the data is critical to be
> > > preserved.
> > >
> > > Any method would be apreciated.
> > >
> > > *** Sent via Devdex http://www.devdex.com ***
> > > Don't just participate in USENET...get rewarded for it!
> >
> >
>|||Not to detract what has already been said, but if the data
is that critical then you have a case for clustering or
having a warm standby. Both of these option should give
you near enough immediate recovery without data loss.
J
>--Original Message--
>
>Dear Sirs,
>I have an sql 2000 ever growing databse, 24 hours a day 7
days a week,
>what is the best to back it up. All the data is critical
to be
>preserved.
>Any method would be apreciated.
>*** Sent via Devdex http://www.devdex.com ***
>Don't just participate in USENET...get rewarded for it!
>.
>|||Hi Uri,
Thanks for poiting out. I accept that.
--
Thanks
Hari
MCDBA
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OYALqEtUEHA.2484@.TK2MSFTNGP11.phx.gbl...
> Hari
> > In case of Restore, I will restore the Differential backup taken last
> night
> > and start applying the Transaction log one by one till last file.
> But do not forget restore FULL backup database before it (1T):)
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:umQy62sUEHA.2564@.TK2MSFTNGP11.phx.gbl...
> > Hi,
> >
> > OK I Agree, Both areas got it own demerits. But still if you have a huge
> > database (1 TB) the full database
> > backup is not a feasible solution because it will take a long time even
in
> a
> > SAN .
> >
> > Restore?
> >
> > In case of Restore, I will restore the Differential backup taken last
> night
> > and start applying the Transaction log one by one till last file.
> >
> > Please explain me if you have a better approach.
> >
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:urcN7nsUEHA.4064@.TK2MSFTNGP11.phx.gbl...
> > > Well
> > > What is about restoring ?
> > > I'd use DIFF backup if amount of time spent in recovering the database
> by
> > > applying all the transaction logs is not acceptable.
> > >
> > > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > > news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> > > > Hi Uri,
> > > >
> > > > I agree with you 90%, rest 10% I disagree because if the database
size
> > > grows
> > > > above 50Gb, it is always
> > > > advised to do a differential during week days. This will save your
> > backup
> > > > time as well as reduce the IO used for backup operations.
> > > >
> > > > Do you agree with me or :)
> > > >
> > > >
> > > > --
> > > > Thanks
> > > > Hari
> > > > MCDBA
> > > > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > > > news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> > > > > Hari
> > > > > Each Diff backup will be grown so on Saturday you will have a
pretty
> > big
> > > > > file and look,if you want to restore database you will need to
> restore
> > > > FULL
> > > > > backup and then a bigger (last) DIFF backup which will consume
more
> > > time
> > > > > and resourse.
> > > > > In my opinion he can do it every night FULL backup of the database
> and
> > > > then
> > > > > every 30 min or an hour LOG file.
> > > > >
> > > > >
> > > > > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > > > > news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> > > > > > Hi,
> > > > > >
> > > > > > I suggest you to do below backup strategy:-
> > > > > >
> > > > > > 1. Sunday - Full database Backup
> > > > > > 2. Every day night - Differential backup
> > > > > > 3. Every 30 minutes or 1 hour Transaction log backup.
> > > > > >
> > > > > > have a look into the details of above strategies:-
> > > > > >
> > > > > > http://techrepublic.com.com/5100-6268-1043671-3.html
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Thanks
> > > > > > Hari
> > > > > > MCDBA
> > > > > > "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> > > > > > news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> > > > > > >
> > > > > > >
> > > > > > > Dear Sirs,
> > > > > > >
> > > > > > > I have an sql 2000 ever growing databse, 24 hours a day 7 days
a
> > > week,
> > > > > > > what is the best to back it up. All the data is critical to be
> > > > > > > preserved.
> > > > > > >
> > > > > > > Any method would be apreciated.
> > > > > > >
> > > > > > > *** Sent via Devdex http://www.devdex.com ***
> > > > > > > Don't just participate in USENET...get rewarded for it!
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||What if you get a corrupt log backup?
Diff backups give a bit more security.
"Uri Dimant" wrote:
> Well
> What is about restoring ?
> I'd use DIFF backup if amount of time spent in recovering the database by
> applying all the transaction logs is not acceptable.
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:OpHxsgsUEHA.3944@.TK2MSFTNGP12.phx.gbl...
> > Hi Uri,
> >
> > I agree with you 90%, rest 10% I disagree because if the database size
> grows
> > above 50Gb, it is always
> > advised to do a differential during week days. This will save your backup
> > time as well as reduce the IO used for backup operations.
> >
> > Do you agree with me or :)
> >
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:ukTnZprUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> > > Hari
> > > Each Diff backup will be grown so on Saturday you will have a pretty big
> > > file and look,if you want to restore database you will need to restore
> > FULL
> > > backup and then a bigger (last) DIFF backup which will consume more
> time
> > > and resourse.
> > > In my opinion he can do it every night FULL backup of the database and
> > then
> > > every 30 min or an hour LOG file.
> > >
> > >
> > > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > > news:%23SfnEVrUEHA.1020@.TK2MSFTNGP11.phx.gbl...
> > > > Hi,
> > > >
> > > > I suggest you to do below backup strategy:-
> > > >
> > > > 1. Sunday - Full database Backup
> > > > 2. Every day night - Differential backup
> > > > 3. Every 30 minutes or 1 hour Transaction log backup.
> > > >
> > > > have a look into the details of above strategies:-
> > > >
> > > > http://techrepublic.com.com/5100-6268-1043671-3.html
> > > >
> > > >
> > > > --
> > > > Thanks
> > > > Hari
> > > > MCDBA
> > > > "elie chucrallah" <eliechucrallah@.hotmail.com> wrote in message
> > > > news:eYA8V5qUEHA.808@.tk2msftngp13.phx.gbl...
> > > > >
> > > > >
> > > > > Dear Sirs,
> > > > >
> > > > > I have an sql 2000 ever growing databse, 24 hours a day 7 days a
> week,
> > > > > what is the best to back it up. All the data is critical to be
> > > > > preserved.
> > > > >
> > > > > Any method would be apreciated.
> > > > >
> > > > > *** Sent via Devdex http://www.devdex.com ***
> > > > > Don't just participate in USENET...get rewarded for it!
> > > >
> > > >
> > >
> > >
> >
> >
>
>