Very Computer

by **Mano Nom** » Wed, 10 Jul 2002 12:10:42

Hi All,

I need some help here.
Have two small databases sizes each arond 1.5 GB on an
older cluster. Each node 1GB of RAM.

Curent backup is FULL every 12 hours, every 6 hours a diff
backup and every hour a transactional log backup.

any sugjections of a bether backup schedule for this. The
databases are high critical!!!!

Thanks.......
Mano

by **Uri Diman** » Wed, 10 Jul 2002 13:57:00

Mano
My consider below backup strategy
Full backup at sunday
every day diff backup
an hour backup log file
read this link for more information
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm...
--administaiting best practices

Quote:> Hi All,

> I need some help here.
> Have two small databases sizes each arond 1.5 GB on an
> older cluster. Each node 1GB of RAM.

> Curent backup is FULL every 12 hours, every 6 hours a diff
> backup and every hour a transactional log backup.

> any sugjections of a bether backup schedule for this. The
> databases are high critical!!!!

> Thanks.......
> Mano

by **Mano Nom** » Wed, 10 Jul 2002 13:47:57

hi...

His is nice thank you , but my data gets changed every min.
So if something goes wrong, I have to restore one diff
backup and aprox.12-20 transactional backups!
Is that ok!
I dont know so i ask, is that normal. because my serves
curenly know to time out when the backup is happening...
It it a e-commerce company...

>-----Original Message-----
>Mano
>My consider below backup strategy
>Full backup at sunday
>every day diff backup
>an hour backup log file
>read this link for more information
>http://vyaskn.tripod.com/sql_server_administration_best_pr
actices.htm#Step1
>--administaiting best practices

Quote:>> Hi All,

>> I need some help here.
>> Have two small databases sizes each arond 1.5 GB on an
>> older cluster. Each node 1GB of RAM.

>> Curent backup is FULL every 12 hours, every 6 hours a
diff
>> backup and every hour a transactional log backup.

>> any sugjections of a bether backup schedule for this.
The
>> databases are high critical!!!!

>> Thanks.......
>> Mano

>.

by **Andrew J. Kell** » Wed, 10 Jul 2002 14:15:20

Mano,

If your data is that critical I would suggest more frequent backups.
Possibly this:

Full Daily
Diff Every 2 Hours
Logs Every 15 Minutes

Full backups on a db that small should only take a few minutes and the logs
just a few seconds. If your getting timeouts when you backup then it sounds
like you are backing up to the same drive as the data which is highly
discouraged. Can you change the drive you place the backups on to a
different drive? In either case it sounds like you have disk I/O issues and
you might want to look into that. Perfmon will tell you how much disk
queuing you are experiencing.

--
Andrew J. Kelly SQL MVP
Targitinteractive, Inc.

> hi...

> His is nice thank you , but my data gets changed every min.
> So if something goes wrong, I have to restore one diff
> backup and aprox.12-20 transactional backups!
> Is that ok!
> I dont know so i ask, is that normal. because my serves
> curenly know to time out when the backup is happening...
> It it a e-commerce company...

> >-----Original Message-----
> >Mano
> >My consider below backup strategy
> >Full backup at sunday
> >every day diff backup
> >an hour backup log file
> >read this link for more information
> >http://vyaskn.tripod.com/sql_server_administration_best_pr
> actices.htm#Step1
> >--administaiting best practices

> >> Hi All,

> >> I need some help here.
> >> Have two small databases sizes each arond 1.5 GB on an
> >> older cluster. Each node 1GB of RAM.

> >> Curent backup is FULL every 12 hours, every 6 hours a
> diff
> >> backup and every hour a transactional log backup.

> >> any sugjections of a bether backup schedule for this.
> The
> >> databases are high critical!!!!

> >> Thanks.......
> >> Mano

> >.

by **Uri Diman** » Wed, 10 Jul 2002 15:22:24

Mano, may be i didn' understand properly
Your data where changed every min, so something wrong was happened.
You are trying to restore your database.(this plan is ok)
Why your servers takes time out .you have run the first restore opeation and
trying to restore the may other database ,may be the same ,so the first
restore was not end.
As you decribed your restore plane ,it is ok.

> hi...

> His is nice thank you , but my data gets changed every min.
> So if something goes wrong, I have to restore one diff
> backup and aprox.12-20 transactional backups!
> Is that ok!
> I dont know so i ask, is that normal. because my serves
> curenly know to time out when the backup is happening...
> It it a e-commerce company...

> >-----Original Message-----
> >Mano
> >My consider below backup strategy
> >Full backup at sunday
> >every day diff backup
> >an hour backup log file
> >read this link for more information
> >http://vyaskn.tripod.com/sql_server_administration_best_pr
> actices.htm#Step1
> >--administaiting best practices

> >> Hi All,

> >> I need some help here.
> >> Have two small databases sizes each arond 1.5 GB on an
> >> older cluster. Each node 1GB of RAM.

> >> Curent backup is FULL every 12 hours, every 6 hours a
> diff
> >> backup and every hour a transactional log backup.

> >> any sugjections of a bether backup schedule for this.
> The
> >> databases are high critical!!!!

> >> Thanks.......
> >> Mano

> >.

by **Mano Nom** » Wed, 10 Jul 2002 14:28:43

Thanks :-)

The data is critical. Many updates durin the day, some
times up to 10.000 rows only from my side. without the
shoppers.
The Database backup are located on a different drive where
the data folder is. The MSSQL folder is in G: and the
backups are in in H:.

The database backup files are around 700MB to 1GB size.

It hapens a lockout, timeout, when a transactiona backup
is running and we are updating some data internaly, the
shopper on the other hand sees a huge nice SQL error
message, and the transactional backup fails with a message:
--------------------------
Database xxxxxx: Transaction Log Backup...
Destination: [h:\BACKUP\xxxx\xxxxxxxx.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3023:
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup,
CHECKALLOC, bulk copy, SELECT INTO, and file manipulation
(such as CREATE FILE) operations on a database must be
serialized. Reissue the statement after the current
backup, CHECKALLOC, or file manipulation operation is
completed.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or
restore operation terminating abnormally.
-------------------------------------------------
Somethimes this hapens during night time "the error" and
at that time i have only web shoppers, so only is the web
server accessing the database.
What to do to ensure a good backup plan that will help me
if something bad happens, to restore it quickly as
possible.

Thanks,
Mano

Quote:>-----Original Message-----
>Mano,

>If your data is that critical I would suggest more
frequent backups.
>Possibly this:

>Full Daily
>Diff Every 2 Hours
>Logs Every 15 Minutes

>Full backups on a db that small should only take a few

minutes and the logs

Quote:>just a few seconds. If your getting timeouts when you

backup then it sounds

>like you are backing up to the same drive as the data
which is highly
>discouraged. Can you change the drive you place the
backups on to a
>different drive? In either case it sounds like you have
disk I/O issues and
>you might want to look into that. Perfmon will tell you
how much disk
>queuing you are experiencing.

>--
>Andrew J. Kelly SQL MVP
>Targitinteractive, Inc.

>> hi...

>> His is nice thank you , but my data gets changed every
min.
>> So if something goes wrong, I have to restore one diff
>> backup and aprox.12-20 transactional backups!
>> Is that ok!
>> I dont know so i ask, is that normal. because my serves
>> curenly know to time out when the backup is happening...
>> It it a e-commerce company...

>> >-----Original Message-----
>> >Mano
>> >My consider below backup strategy
>> >Full backup at sunday
>> >every day diff backup
>> >an hour backup log file
>> >read this link for more information

>http://vyaskn.tripod.com/sql_server_administration_best_pr
>> actices.htm#Step1
>> >--administaiting best practices

>> >> Hi All,

>> >> I need some help here.
>> >> Have two small databases sizes each arond 1.5 GB on
an
>> >> older cluster. Each node 1GB of RAM.

>> >> Curent backup is FULL every 12 hours, every 6 hours a
>> diff
>> >> backup and every hour a transactional log backup.

>> >> any sugjections of a bether backup schedule for this.
>> The
>> >> databases are high critical!!!!

>> >> Thanks.......
>> >> Mano

>> >.

>.

by **Tibor Karasz** » Wed, 10 Jul 2002 14:54:54

Quote:> Backup,
> CHECKALLOC, bulk copy, SELECT INTO, and file manipulation
> (such as CREATE FILE) operations on a database must be
> serialized.

The error message really say it all. Which version of SQL Server? There are some operations that
cannot be executed simultaneous, and you have to schedule them so that they are serialized.
There has been quite some improvements here in SQL Server 2000.

--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...

> Thanks :-)

> The data is critical. Many updates durin the day, some
> times up to 10.000 rows only from my side. without the
> shoppers.
> The Database backup are located on a different drive where
> the data folder is. The MSSQL folder is in G: and the
> backups are in in H:.

> The database backup files are around 700MB to 1GB size.

> It hapens a lockout, timeout, when a transactiona backup
> is running and we are updating some data internaly, the
> shopper on the other hand sees a huge nice SQL error
> message, and the transactional backup fails with a message:
> --------------------------
> Database xxxxxx: Transaction Log Backup...
> Destination: [h:\BACKUP\xxxx\xxxxxxxx.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3023:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Backup,
> CHECKALLOC, bulk copy, SELECT INTO, and file manipulation
> (such as CREATE FILE) operations on a database must be
> serialized. Reissue the statement after the current
> backup, CHECKALLOC, or file manipulation operation is
> completed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Backup or
> restore operation terminating abnormally.
> -------------------------------------------------
> Somethimes this hapens during night time "the error" and
> at that time i have only web shoppers, so only is the web
> server accessing the database.
> What to do to ensure a good backup plan that will help me
> if something bad happens, to restore it quickly as
> possible.

> Thanks,
> Mano

> >-----Original Message-----
> >Mano,

> >If your data is that critical I would suggest more
> frequent backups.
> >Possibly this:

> >Full Daily
> >Diff Every 2 Hours
> >Logs Every 15 Minutes

> >Full backups on a db that small should only take a few
> minutes and the logs
> >just a few seconds. If your getting timeouts when you
> backup then it sounds
> >like you are backing up to the same drive as the data
> which is highly
> >discouraged. Can you change the drive you place the
> backups on to a
> >different drive? In either case it sounds like you have
> disk I/O issues and
> >you might want to look into that. Perfmon will tell you
> how much disk
> >queuing you are experiencing.

> >--
> >Andrew J. Kelly SQL MVP
> >Targitinteractive, Inc.

> >> hi...

> >> His is nice thank you , but my data gets changed every
> min.
> >> So if something goes wrong, I have to restore one diff
> >> backup and aprox.12-20 transactional backups!
> >> Is that ok!
> >> I dont know so i ask, is that normal. because my serves
> >> curenly know to time out when the backup is happening...
> >> It it a e-commerce company...

> >> >-----Original Message-----
> >> >Mano
> >> >My consider below backup strategy
> >> >Full backup at sunday
> >> >every day diff backup
> >> >an hour backup log file
> >> >read this link for more information

> >http://vyaskn.tripod.com/sql_server_administration_best_pr
> >> actices.htm#Step1
> >> >--administaiting best practices

> >> >> Hi All,

> >> >> I need some help here.
> >> >> Have two small databases sizes each arond 1.5 GB on
> an
> >> >> older cluster. Each node 1GB of RAM.

> >> >> Curent backup is FULL every 12 hours, every 6 hours a
> >> diff
> >> >> backup and every hour a transactional log backup.

> >> >> any sugjections of a bether backup schedule for this.
> >> The
> >> >> databases are high critical!!!!

> >> >> Thanks.......
> >> >> Mano

> >> >.

> >.

Very Computer

BACKUP HELP URGENT

BACKUP HELP URGENT

BACKUP HELP URGENT

BACKUP HELP URGENT

BACKUP HELP URGENT

BACKUP HELP URGENT

BACKUP HELP URGENT

BACKUP HELP URGENT