Log shipping TLog dump naming covention

The Tlog dump as part of Log shipping has got me wondering on how the time
portion of the file name is done. So right now I have a file name called
DBName_20071109204000.trn that was taken at 12:40pm on 11/9/2007. Just
looking at the file, how can you tell the time ? I am using SQL 2005. It was
better in SQL 2000.
Thanks
Pls refer
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1773170&SiteID=1
it uses UTC timing convention I believe !
Thanxx
Deepak
"Hassan" wrote:

> The Tlog dump as part of Log shipping has got me wondering on how the time
> portion of the file name is done. So right now I have a file name called
> DBName_20071109204000.trn that was taken at 12:40pm on 11/9/2007. Just
> looking at the file, how can you tell the time ? I am using SQL 2005. It was
> better in SQL 2000.
> Thanks
>
>
>

Log shipping TLog dump naming covention

The Tlog dump as part of Log shipping has got me wondering on how the time
portion of the file name is done. So right now I have a file name called
DBName_20071109204000.trn that was taken at 12:40pm on 11/9/2007. Just
looking at the file, how can you tell the time ? I am using SQL 2005. It was
better in SQL 2000.
ThanksPls refer
http://forums.microsoft.com/MSDN/Sh...773170&SiteID=1
it uses UTC timing convention I believe !
--
Thanxx
Deepak
"Hassan" wrote:

> The Tlog dump as part of Log shipping has got me wondering on how the time
> portion of the file name is done. So right now I have a file name called
> DBName_20071109204000.trn that was taken at 12:40pm on 11/9/2007. Just
> looking at the file, how can you tell the time ? I am using SQL 2005. It w
as
> better in SQL 2000.
> Thanks
>
>
>

Log shipping TLog dump naming covention

The Tlog dump as part of Log shipping has got me wondering on how the time
portion of the file name is done. So right now I have a file name called
DBName_20071109204000.trn that was taken at 12:40pm on 11/9/2007. Just
looking at the file, how can you tell the time ? I am using SQL 2005. It was
better in SQL 2000.
ThanksPls refer
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1773170&SiteID=1
it uses UTC timing convention I believe !
--
Thanxx
Deepak
"Hassan" wrote:
> The Tlog dump as part of Log shipping has got me wondering on how the time
> portion of the file name is done. So right now I have a file name called
> DBName_20071109204000.trn that was taken at 12:40pm on 11/9/2007. Just
> looking at the file, how can you tell the time ? I am using SQL 2005. It was
> better in SQL 2000.
> Thanks
>
>
>

Log Shipping functionality questions

SQL2K sp3
I need to have a basic understanding of LS in order to
answer some Disaster Recovery questions today. I
understand that it takes TLog backups from BoxA(Production
Server in use) and restores them to BoxB(secondary server
that those backups are being sent too) using NoRecovery. I
also understand that if BoxA dies BoxB can perform a Role
Change and become the Production Box. This part Im clear
on.
But what Im not clear on once BoxA is back online what
takes place? Im pretty sure you can do another Role Change
make BoxA the Production Box again. But what actually
takes place here?
Does BoxA go through a Restore process of all its old
backups using NoRecovery, have the latest TLog backups
shipped from BoxB, restore those with Recovery, and then
become Production again? This is what Im guessing would
need to happen in order to accomplish a Role Change from
BoxB to BoxA. But Im not sure and could use some insight.
Of course I JUST found out I need to know this stuff
IMMEDIATELY from the higher ups or else I would just try
testing this out on my own. So sorry for the lazy
questions here.
TIA, ChrisRfull backup of B applied to A. Then apply Trnxn Logs From B To A and A is
"HOT" again.
not sure if that answers your question.
are you planning on using the maintenance plan stuff...aka "Log shipping
Wizard" ?
Greg Jackson
PDX, Oregon|||>full backup of B applied to A. Then apply Trnxn Logs From
B To A and A is
>"HOT" again.
So I actually have to do a full transfer over the line
from B to A? Is this correct? How do companies with large
db's use this as an Enterprise solution? Im not trying to
sound ungrateful for your help, just trying to get a clear
understanding.
>are you planning on using the maintenance plan
stuff...aka "Log shipping
>Wizard" ?
Yes.
>--Original Message--
>full backup of B applied to A. Then apply Trnxn Logs From
B To A and A is
>"HOT" again.
>
>not sure if that answers your question.
>are you planning on using the maintenance plan
stuff...aka "Log shipping
>Wizard" ?
>
>
>Greg Jackson
>PDX, Oregon
>
>.
>|||it aint easy.
moving data of the wire SUX. Especially for large Dbs.
this is really a "Poor Man's Replication" so larger companies probably just
use replication.
I have done tons of this in the past and am doing a huge log shipping
implementation right now.
I recommend NOT using the Wizard Thingy.
Roll your own.
if you need scripts, have questions, etc let me know.
GAJ|||Thanks for the info Jaxon.
>--Original Message--
>it aint easy.
>moving data of the wire SUX. Especially for large Dbs.
>this is really a "Poor Man's Replication" so larger
companies probably just
>use replication.
>I have done tons of this in the past and am doing a huge
log shipping
>implementation right now.
>I recommend NOT using the Wizard Thingy.
>Roll your own.
>if you need scripts, have questions, etc let me know.
>
>GAJ
>
>.
>

Log Shipping functionality questions

SQL2K sp3
I need to have a basic understanding of LS in order to
answer some Disaster Recovery questions today. I
understand that it takes TLog backups from BoxA(Production
Server in use) and restores them to BoxB(secondary server
that those backups are being sent too) using NoRecovery. I
also understand that if BoxA dies BoxB can perform a Role
Change and become the Production Box. This part Im clear
on.
But what Im not clear on once BoxA is back online what
takes place? Im pretty sure you can do another Role Change
make BoxA the Production Box again. But what actually
takes place here?
Does BoxA go through a Restore process of all its old
backups using NoRecovery, have the latest TLog backups
shipped from BoxB, restore those with Recovery, and then
become Production again? This is what Im guessing would
need to happen in order to accomplish a Role Change from
BoxB to BoxA. But Im not sure and could use some insight.
Of course I JUST found out I need to know this stuff
IMMEDIATELY from the higher ups or else I would just try
testing this out on my own. So sorry for the lazy
questions here.
TIA, ChrisRfull backup of B applied to A. Then apply Trnxn Logs From B To A and A is
"HOT" again.
not sure if that answers your question.
are you planning on using the maintenance plan stuff...aka "Log shipping
Wizard" ?
Greg Jackson
PDX, Oregon|||>full backup of B applied to A. Then apply Trnxn Logs From
B To A and A is
>"HOT" again.
So I actually have to do a full transfer over the line
from B to A? Is this correct? How do companies with large
db's use this as an Enterprise solution? Im not trying to
sound ungrateful for your help, just trying to get a clear
understanding.

>are you planning on using the maintenance plan
stuff...aka "Log shipping
>Wizard" ?
Yes.

>--Original Message--
>full backup of B applied to A. Then apply Trnxn Logs From
B To A and A is
>"HOT" again.
>
>not sure if that answers your question.
>are you planning on using the maintenance plan
stuff...aka "Log shipping
>Wizard" ?
>
>
>Greg Jackson
>PDX, Oregon
>
>.
>|||it aint easy.
moving data of the wire SUX. Especially for large Dbs.
this is really a "Poor Man's Replication" so larger companies probably just
use replication.
I have done tons of this in the past and am doing a huge log shipping
implementation right now.
I recommend NOT using the Wizard Thingy.
Roll your own.
if you need scripts, have questions, etc let me know.
GAJ|||Thanks for the info Jaxon.

>--Original Message--
>it aint easy.
>moving data of the wire SUX. Especially for large Dbs.
>this is really a "Poor Man's Replication" so larger
companies probably just
>use replication.
>I have done tons of this in the past and am doing a huge
log shipping
>implementation right now.
>I recommend NOT using the Wizard Thingy.
>Roll your own.
>if you need scripts, have questions, etc let me know.
>
>GAJ
>
>.
>

Log Shipping functionality questions

SQL2K sp3
I need to have a basic understanding of LS in order to
answer some Disaster Recovery questions today. I
understand that it takes TLog backups from BoxA(Production
Server in use) and restores them to BoxB(secondary server
that those backups are being sent too) using NoRecovery. I
also understand that if BoxA dies BoxB can perform a Role
Change and become the Production Box. This part Im clear
on.
But what Im not clear on once BoxA is back online what
takes place? Im pretty sure you can do another Role Change
make BoxA the Production Box again. But what actually
takes place here?
Does BoxA go through a Restore process of all its old
backups using NoRecovery, have the latest TLog backups
shipped from BoxB, restore those with Recovery, and then
become Production again? This is what Im guessing would
need to happen in order to accomplish a Role Change from
BoxB to BoxA. But Im not sure and could use some insight.
Of course I JUST found out I need to know this stuff
IMMEDIATELY from the higher ups or else I would just try
testing this out on my own. So sorry for the lazy
questions here.
TIA, ChrisR
full backup of B applied to A. Then apply Trnxn Logs From B To A and A is
"HOT" again.
not sure if that answers your question.
are you planning on using the maintenance plan stuff...aka "Log shipping
Wizard" ?
Greg Jackson
PDX, Oregon
|||>full backup of B applied to A. Then apply Trnxn Logs From
B To A and A is
>"HOT" again.
So I actually have to do a full transfer over the line
from B to A? Is this correct? How do companies with large
db's use this as an Enterprise solution? Im not trying to
sound ungrateful for your help, just trying to get a clear
understanding.

>are you planning on using the maintenance plan
stuff...aka "Log shipping
>Wizard" ?
Yes.

>--Original Message--
>full backup of B applied to A. Then apply Trnxn Logs From
B To A and A is
>"HOT" again.
>
>not sure if that answers your question.
>are you planning on using the maintenance plan
stuff...aka "Log shipping
>Wizard" ?
>
>
>Greg Jackson
>PDX, Oregon
>
>.
>
|||it aint easy.
moving data of the wire SUX. Especially for large Dbs.
this is really a "Poor Man's Replication" so larger companies probably just
use replication.
I have done tons of this in the past and am doing a huge log shipping
implementation right now.
I recommend NOT using the Wizard Thingy.
Roll your own.
if you need scripts, have questions, etc let me know.
GAJ
|||Thanks for the info Jaxon.

>--Original Message--
>it aint easy.
>moving data of the wire SUX. Especially for large Dbs.
>this is really a "Poor Man's Replication" so larger
companies probably just
>use replication.
>I have done tons of this in the past and am doing a huge
log shipping
>implementation right now.
>I recommend NOT using the Wizard Thingy.
>Roll your own.
>if you need scripts, have questions, etc let me know.
>
>GAJ
>
>.
>

log shipping barfing

sql2k sp2
Log Shipping gets set up successfully. The db gets created
on the secondary box. All the TLog backups get transferred
to the secondary box. But then after some time it gets out
of sync. In the reporting file there is the message:
(snippet)
(SQL Server does not exist or access is denied)
How could this be since it was able to intialize the new
db? If it never did that and I got this message it would
make more sense than creating the db but not baing able to
connect after that.
TIA, ChrisChris,
Which job is failing? Sounds like the restore job on the secondary. Are you
sure SQL Agent on the secondary can connect to the secondary SQL Server?
Ron
--
Ron Talmage
SQL Server MVP
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:05e001c3a4ca$1a848f70$a301280a@.phx.gbl...
> sql2k sp2
> Log Shipping gets set up successfully. The db gets created
> on the secondary box. All the TLog backups get transferred
> to the secondary box. But then after some time it gets out
> of sync. In the reporting file there is the message:
> (snippet)
> (SQL Server does not exist or access is denied)
> How could this be since it was able to intialize the new
> db? If it never did that and I got this message it would
> make more sense than creating the db but not baing able to
> connect after that.
> TIA, Chris
>|||Are you
>sure SQL Agent on the secondary can connect to the
secondary SQL Server?
Not sure Im following on this one.
>--Original Message--
>Chris,
>Which job is failing? Sounds like the restore job on the
secondary. Are you
>sure SQL Agent on the secondary can connect to the
secondary SQL Server?
>Ron
>--
>Ron Talmage
>SQL Server MVP
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
>news:05e001c3a4ca$1a848f70$a301280a@.phx.gbl...
>> sql2k sp2
>> Log Shipping gets set up successfully. The db gets
created
>> on the secondary box. All the TLog backups get
transferred
>> to the secondary box. But then after some time it gets
out
>> of sync. In the reporting file there is the message:
>> (snippet)
>> (SQL Server does not exist or access is denied)
>> How could this be since it was able to intialize the new
>> db? If it never did that and I got this message it would
>> make more sense than creating the db but not baing able
to
>> connect after that.
>> TIA, Chris
>
>.
>