Boot.ini file: backup

Showing posts with label backup. Show all posts

Sunday, March 11, 2012

Bug in Task

Hi all,
I have a job that run 3 task. The first one do a backup, the second one copy those backup files from one drive to another drive, the third one supposed to delete the backup from the first drive. What is happening is as soon as the second task start the third task also start for some reason, it does not wait for all the backup files to be moved, so i end up with one backup file being copied on the second drive (locking the backup file) but all the other backup get deleted except for the lock file. Has anyone encounter the same problem? is there a way i can set up the third task not to start until the second is completed?

axel_2005 wrote:
Hi all,
I have a job that run 3 task. The first one do a backup, the second one copy those backup files from one drive to another drive, the third one supposed to delete the backup from the first drive. What is happening is as soon as the second task start the third task also start for some reason, it does not wait for all the backup files to be moved, so i end up with one backup file being copied on the second drive (locking the backup file) but all the other backup get deleted except for the lock file. Has anyone encounter the same problem? is there a way i can set up the third task not to start until the second is completed?

Do you have any precedence constraints (i.e. blue, red or green lines) between your tasks?

-Jamie

|||the tasks are link by the green arrow|||That's weird. Have you messed with the precedence constraints? When you draw a green arrow between task, by default a 'upon success' precedence is created. Just to make sure, check the options of the precedence constrains by double clicking the green arrow between the 2nd a 3rd task.|||I found a work around. Apparently when the task copy files from one place to another, it somehow return a success even though it did not copy all the files (i would say as soon as it copy the first file) so I removed the maintenance clean up and added another step to delete the files in task 3, that way only when the first step is done it will go to the next step. Thanks for your help.

Saturday, February 25, 2012

Buffer Latch error

I have a backup database job that failed with the following error on sql server 2005

Executed as user: TestUSer. Time-out occurred while waiting for buffer latch type 3 for page (1:10541989), database ID 8. [SQLSTATE 42000] (Error 845) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

Does anyone know why this happened? Is it the server or the array?

Any help is appreciated.

Thanks

Check your database storage for hardware errors (disk failures, fibre connection, I/O errors, etc) This was a bug on SQL 2000 and 7.0, solved with a service pack. But i guess this is not the answer here. So, please check your equipment 1st.

Sunday, February 19, 2012

British Summer Time stopping SQL backup routine

Hi All
I have set up several DB Maintenance Plans in my SQL 2000 installation to
backup 3 sep DBs to a designated 'day' folder (ie 7 different folders to
cover Mon - Sun) on the same HD every day at 1am. This was working fine
everyday until the clocks moved forward by 1 hour to accommodate BST
(British Summer Time) and then the backups stopped backing up.
Now my PC Server being a good SBS 2000 installation auto-changed it's clock
to 1 hour forward, but the backups have just stopped working.
To correct this, I simply went into each DB Maintenance plan , opened up the
schedule, unticked a day, ticked it again and then saved it (ala what I call
a refresh) and everything started working again.
I know I could put these backups into 1 folder so I didn't have to update 21
or so individual plans, but I need to put it into these day folders to make
it easier for the day-to-day monitor-er of these backups.
I also know this problem only appears to happen twice a year (day when the
clocks go back and day when the clocks go forward), but because it is such
an unnecessary procedure, I just wanted to ask you if there was any fix for
it.
Many thanks.
Rgds
RobbieThere's not really a "fix", as there isn't really a problem, at least not
with SQL Server. 1:00 AM doesn't exist on the day you go to summer time, as
the clock moves from 00:59:59 GMT to 02:00:00 BST. On the other side, you
would have 1:00 AM twice when the clocks go back.
The best practice, if you want to avoid these little irritations, is not to
schedule anything within this period, and instead start your backup at 00:59
AM.
--
Jacco Schalkwijk
SQL Server MVP
"Astra" <info@.noemail.com> wrote in message
news:emGph0QNFHA.3000@.TK2MSFTNGP10.phx.gbl...
> Hi All
> I have set up several DB Maintenance Plans in my SQL 2000 installation to
> backup 3 sep DBs to a designated 'day' folder (ie 7 different folders to
> cover Mon - Sun) on the same HD every day at 1am. This was working fine
> everyday until the clocks moved forward by 1 hour to accommodate BST
> (British Summer Time) and then the backups stopped backing up.
> Now my PC Server being a good SBS 2000 installation auto-changed it's
> clock
> to 1 hour forward, but the backups have just stopped working.
> To correct this, I simply went into each DB Maintenance plan , opened up
> the
> schedule, unticked a day, ticked it again and then saved it (ala what I
> call
> a refresh) and everything started working again.
> I know I could put these backups into 1 folder so I didn't have to update
> 21
> or so individual plans, but I need to put it into these day folders to
> make
> it easier for the day-to-day monitor-er of these backups.
> I also know this problem only appears to happen twice a year (day when the
> clocks go back and day when the clocks go forward), but because it is such
> an unnecessary procedure, I just wanted to ask you if there was any fix
> for
> it.
> Many thanks.
> Rgds
> Robbie
>|||Dohhh!!!
Many thanks Jacco
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:ue9SDFRNFHA.3156@.TK2MSFTNGP15.phx.gbl...
There's not really a "fix", as there isn't really a problem, at least not
with SQL Server. 1:00 AM doesn't exist on the day you go to summer time, as
the clock moves from 00:59:59 GMT to 02:00:00 BST. On the other side, you
would have 1:00 AM twice when the clocks go back.
The best practice, if you want to avoid these little irritations, is not to
schedule anything within this period, and instead start your backup at 00:59
AM.
--
Jacco Schalkwijk
SQL Server MVP
"Astra" <info@.noemail.com> wrote in message
news:emGph0QNFHA.3000@.TK2MSFTNGP10.phx.gbl...
> Hi All
> I have set up several DB Maintenance Plans in my SQL 2000 installation to
> backup 3 sep DBs to a designated 'day' folder (ie 7 different folders to
> cover Mon - Sun) on the same HD every day at 1am. This was working fine
> everyday until the clocks moved forward by 1 hour to accommodate BST
> (British Summer Time) and then the backups stopped backing up.
> Now my PC Server being a good SBS 2000 installation auto-changed it's
> clock
> to 1 hour forward, but the backups have just stopped working.
> To correct this, I simply went into each DB Maintenance plan , opened up
> the
> schedule, unticked a day, ticked it again and then saved it (ala what I
> call
> a refresh) and everything started working again.
> I know I could put these backups into 1 folder so I didn't have to update
> 21
> or so individual plans, but I need to put it into these day folders to
> make
> it easier for the day-to-day monitor-er of these backups.
> I also know this problem only appears to happen twice a year (day when the
> clocks go back and day when the clocks go forward), but because it is such
> an unnecessary procedure, I just wanted to ask you if there was any fix
> for
> it.
> Many thanks.
> Rgds
> Robbie
>

Thursday, February 16, 2012

Bring up the standby server in sql 2k

Hi,
How do I bring up the standby server online in sql2k by restoring the last
log backup(backed up with noinit).
This log file has been restored with standby clause. can I restore again
with recovery?
Thanks,Hi
Yes.
RESTORE <dbname> WITH RECOVERY
will bring the DB into a usable state.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uAtveOg9FHA.2264@.tk2msftngp13.phx.gbl...
> Hi,
> How do I bring up the standby server online in sql2k by restoring the last
> log backup(backed up with noinit).
> This log file has been restored with standby clause. can I restore again
> with recovery?
> Thanks,
>|||Thanks,
But when I doing restore with recovery give me error says Server: Msg 4326,
Level 16, State 1, Line 11
The log in this backup set terminates at LSN 6791000023918900001, which is
too early to apply to the database. A more recent log backup that includes
LSN 6794000015810000001 can be restored.
I don't know why?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:um6tXTg9FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hi
> Yes.
> RESTORE <dbname> WITH RECOVERY
> will bring the DB into a usable state.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:uAtveOg9FHA.2264@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > How do I bring up the standby server online in sql2k by restoring the
last
> > log backup(backed up with noinit).
> > This log file has been restored with standby clause. can I restore again
> > with recovery?
> >
> > Thanks,
> >
> >
>|||Can you post that exact RESTORE command you are executing?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:u4ki7ag9FHA.1332@.tk2msftngp13.phx.gbl...
> Thanks,
> But when I doing restore with recovery give me error says Server: Msg 4326,
> Level 16, State 1, Line 11
> The log in this backup set terminates at LSN 6791000023918900001, which is
> too early to apply to the database. A more recent log backup that includes
> LSN 6794000015810000001 can be restored.
> I don't know why?
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:um6tXTg9FHA.252@.TK2MSFTNGP15.phx.gbl...
>> Hi
>> Yes.
>> RESTORE <dbname> WITH RECOVERY
>> will bring the DB into a usable state.
>> --
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "mecn" <mecn2002@.yahoo.com> wrote in message
>> news:uAtveOg9FHA.2264@.tk2msftngp13.phx.gbl...
>> > Hi,
>> >
>> > How do I bring up the standby server online in sql2k by restoring the
> last
>> > log backup(backed up with noinit).
>> > This log file has been restored with standby clause. can I restore again
>> > with recovery?
>> >
>> > Thanks,
>> >
>> >
>>
>|||This is the script I excuted with error.
restore log LDNPROD from disk = 'path.bak' with recovery
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ObMuJOn9FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Can you post that exact RESTORE command you are executing?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
news:u4ki7ag9FHA.1332@.tk2msftngp13.phx.gbl...
> > Thanks,
> > But when I doing restore with recovery give me error says Server: Msg
4326,
> > Level 16, State 1, Line 11
> > The log in this backup set terminates at LSN 6791000023918900001, which
is
> > too early to apply to the database. A more recent log backup that
includes
> > LSN 6794000015810000001 can be restored.
> >
> > I don't know why?
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:um6tXTg9FHA.252@.TK2MSFTNGP15.phx.gbl...
> >> Hi
> >>
> >> Yes.
> >>
> >> RESTORE <dbname> WITH RECOVERY
> >> will bring the DB into a usable state.
> >>
> >> --
> >> --
> >> Mike Epprecht, Microsoft SQL Server MVP
> >> Zurich, Switzerland
> >>
> >> IM: mike@.epprecht.net
> >>
> >> MVP Program: http://www.microsoft.com/mvp
> >>
> >> Blog: http://www.msmvps.com/epprecht/
> >>
> >> "mecn" <mecn2002@.yahoo.com> wrote in message
> >> news:uAtveOg9FHA.2264@.tk2msftngp13.phx.gbl...
> >> > Hi,
> >> >
> >> > How do I bring up the standby server online in sql2k by restoring the
> > last
> >> > log backup(backed up with noinit).
> >> > This log file has been restored with standby clause. can I restore
again
> >> > with recovery?
> >> >
> >> > Thanks,
> >> >
> >> >
> >>
> >>
> >
> >|||If you just want to make the database accessible (fail over), try executing (as suggested by Mike):
RESTORE DATABASE LDNPROD WITH RECOVERY
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:eRuvPeo9FHA.1224@.TK2MSFTNGP12.phx.gbl...
> This is the script I excuted with error.
> restore log LDNPROD from disk = 'path.bak' with recovery
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:ObMuJOn9FHA.3660@.TK2MSFTNGP09.phx.gbl...
>> Can you post that exact RESTORE command you are executing?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:u4ki7ag9FHA.1332@.tk2msftngp13.phx.gbl...
>> > Thanks,
>> > But when I doing restore with recovery give me error says Server: Msg
> 4326,
>> > Level 16, State 1, Line 11
>> > The log in this backup set terminates at LSN 6791000023918900001, which
> is
>> > too early to apply to the database. A more recent log backup that
> includes
>> > LSN 6794000015810000001 can be restored.
>> >
>> > I don't know why?
>> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> > news:um6tXTg9FHA.252@.TK2MSFTNGP15.phx.gbl...
>> >> Hi
>> >>
>> >> Yes.
>> >>
>> >> RESTORE <dbname> WITH RECOVERY
>> >> will bring the DB into a usable state.
>> >>
>> >> --
>> >> --
>> >> Mike Epprecht, Microsoft SQL Server MVP
>> >> Zurich, Switzerland
>> >>
>> >> IM: mike@.epprecht.net
>> >>
>> >> MVP Program: http://www.microsoft.com/mvp
>> >>
>> >> Blog: http://www.msmvps.com/epprecht/
>> >>
>> >> "mecn" <mecn2002@.yahoo.com> wrote in message
>> >> news:uAtveOg9FHA.2264@.tk2msftngp13.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > How do I bring up the standby server online in sql2k by restoring the
>> > last
>> >> > log backup(backed up with noinit).
>> >> > This log file has been restored with standby clause. can I restore
> again
>> >> > with recovery?
>> >> >
>> >> > Thanks,
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>

Breaking up sql server backups into smaller files

Hey guys,

I'm wondering how most people manage very very large backups. What is the best approach to breaking up the backup files if you're restricted to a drive size (450gig in my case). I unix, you can pipe the backup to gzip and split, I'm not sure how the same thing could be accomplished in windows.

Thanks,
-KilkaHave you looked into backing up filegroups or doing differential backups?|||Hey Thrasymachus,

I had a look and neither of those two would solve the problem. In order to accomplish either of the two, you do need a full backup to recover from scratch. However, after a little investigation, I found out that you can split a full backup into a set of files, I previously never knew you could do this.

Check this out:
restore database warehouse_test FROM
disk = 'X:\warehouse_test1.bak',disk = 'X:\warehouse_test2.bak'

Peace,
-Kilka

Sunday, February 12, 2012

Bottleneck - Backup Server

I am trying to analyze/identify the bottleneck on our new backup
server. I was wondering if someone could recommend some performance
counters to watch.
Right now I am watching "% Write Time" I am averaging around
"500" for this measure while copying a 50GB database file. It is
taking almost twice as long to copy the file to a different server as
opposed to a different direct attached array. The % disk write counter
is similar on both servers. Am I wrong to assume that the physical
disks are the bottleneck (due to high performance counter ratings)?
Does anyone know some general guide lines on real world throughput on
the following? What kinds of things should I be looking at and/or
asking our IT department?
Gigabit dedicated network
Perc4 (I read on Dells site that it is 320MB/s which translates to
1.1TB / hour)
Raid 5 using 6 - 300MB disks (10,000 RPM)
Other bottleneck candidate?
Server Configuration
Windows Server 2003
Dell PowerEdge 2850
Perc4 - Raid 5
PowerVault 200s
Gigabit networkDave,
Look at the current or average disk queue length. It will tell you if the OS
is waiting for the disks. Also look at the network interface / Bytes
Receive/sec. to determine how fast the data is being moved across your
network. The network is usually the slowest in the mix and it is common for
a server to server copy to take more time than a disk to disk copy on the
same server.
Also, you will have additional overhead writing to a raid 5 because of
writing the parity information.
-- Bill
"Dave" <daveg.01@.gmail.com> wrote in message
news:1168620575.775759.196740@.i15g2000cwa.googlegroups.com...
>I am trying to analyze/identify the bottleneck on our new backup
> server. I was wondering if someone could recommend some performance
> counters to watch.
> Right now I am watching "% Write Time" I am averaging around
> "500" for this measure while copying a 50GB database file. It is
> taking almost twice as long to copy the file to a different server as
> opposed to a different direct attached array. The % disk write counter
> is similar on both servers. Am I wrong to assume that the physical
> disks are the bottleneck (due to high performance counter ratings)?
>
> Does anyone know some general guide lines on real world throughput on
> the following? What kinds of things should I be looking at and/or
> asking our IT department?
>
> Gigabit dedicated network
> Perc4 (I read on Dells site that it is 320MB/s which translates to
> 1.1TB / hour)
> Raid 5 using 6 - 300MB disks (10,000 RPM)
> Other bottleneck candidate?
>
> Server Configuration
> Windows Server 2003
> Dell PowerEdge 2850
> Perc4 - Raid 5
> PowerVault 200s
> Gigabit network
>

Bottleneck - Backup Server

I am trying to analyze/identify the bottleneck on our new backup
server. I was wondering if someone could recommend some performance
counters to watch.
Right now I am watching "% Write Time" I am averaging around
"500" for this measure while copying a 50GB database file. It is
taking almost twice as long to copy the file to a different server as
opposed to a different direct attached array. The % disk write counter
is similar on both servers. Am I wrong to assume that the physical
disks are the bottleneck (due to high performance counter ratings)?
Does anyone know some general guide lines on real world throughput on
the following? What kinds of things should I be looking at and/or
asking our IT department?
Gigabit dedicated network
Perc4 (I read on Dells site that it is 320MB/s which translates to
1.1TB / hour)
Raid 5 using 6 - 300MB disks (10,000 RPM)
Other bottleneck candidate?
Server Configuration
Windows Server 2003
Dell PowerEdge 2850
Perc4 - Raid 5
PowerVault 200s
Gigabit network
Dave,
Look at the current or average disk queue length. It will tell you if the OS
is waiting for the disks. Also look at the network interface / Bytes
Receive/sec. to determine how fast the data is being moved across your
network. The network is usually the slowest in the mix and it is common for
a server to server copy to take more time than a disk to disk copy on the
same server.
Also, you will have additional overhead writing to a raid 5 because of
writing the parity information.
-- Bill
"Dave" <daveg.01@.gmail.com> wrote in message
news:1168620575.775759.196740@.i15g2000cwa.googlegr oups.com...
>I am trying to analyze/identify the bottleneck on our new backup
> server. I was wondering if someone could recommend some performance
> counters to watch.
> Right now I am watching "% Write Time" I am averaging around
> "500" for this measure while copying a 50GB database file. It is
> taking almost twice as long to copy the file to a different server as
> opposed to a different direct attached array. The % disk write counter
> is similar on both servers. Am I wrong to assume that the physical
> disks are the bottleneck (due to high performance counter ratings)?
>
> Does anyone know some general guide lines on real world throughput on
> the following? What kinds of things should I be looking at and/or
> asking our IT department?
>
> Gigabit dedicated network
> Perc4 (I read on Dells site that it is 320MB/s which translates to
> 1.1TB / hour)
> Raid 5 using 6 - 300MB disks (10,000 RPM)
> Other bottleneck candidate?
>
> Server Configuration
> Windows Server 2003
> Dell PowerEdge 2850
> Perc4 - Raid 5
> PowerVault 200s
> Gigabit network
>

Sunday, March 11, 2012

Bug in Task

Saturday, February 25, 2012

Buffer Latch error

Sunday, February 19, 2012

British Summer Time stopping SQL backup routine

Thursday, February 16, 2012

Bring up the standby server in sql 2k

Bring up the standby server in sql 2k

Bring up the standby server in sql 2k

Breaking up sql server backups into smaller files

Sunday, February 12, 2012

Bottleneck - Backup Server

Bottleneck - Backup Server

Bottleneck - Backup Server

Boot.ini file

Blog Archive

About Me