Display date: recovery

显示标签为“recovery”的博文。显示所有博文

2012年3月22日星期四

Disester Recovery

Hi,
I'm using SQL Server 2000 Standard Edition and now I want to create a
Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
edition? For info, I'm running a Financial Software, which means data
transection rate is very high. Another thing is that, for my remote users
what would be the minimum bandwidth required to connect to SQL Server as well
as DR Site?
Please let me know..
regards,
Mahmud
Hi,
You can wither use
1. Logshipping
2. TRansactional Replication
But all depends up on the network speed between your location to DR site. If
you have a dedicated network connectivity
then you can setup a Transactional replication.
Regarding the bandwidth -- Depends up on the transacgtion and amount of
users connecting to your system. I recommend that you should
have identical network band width for both production and DR site
Thanks
Hari
SQL Server MVP
"Mahmud" <Mahmud@.discussions.microsoft.com> wrote in message
news:B6058E06-B1F7-45B7-A8E2-1ED6D83B6022@.microsoft.com...
> Hi,
> I'm using SQL Server 2000 Standard Edition and now I want to create a
> Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
> edition? For info, I'm running a Financial Software, which means data
> transection rate is very high. Another thing is that, for my remote users
> what would be the minimum bandwidth required to connect to SQL Server as
> well
> as DR Site?
> Please let me know..
> regards,
> Mahmud
|||Hi
Thanks for the info. Can you please provide me some technical doc links, so
that I can get a better idea & can able to create/manage DR site.
Thanks once again.
"Hari Prasad" wrote:

> Hi,
> You can wither use
> 1. Logshipping
> 2. TRansactional Replication
> But all depends up on the network speed between your location to DR site. If
> you have a dedicated network connectivity
> then you can setup a Transactional replication.
> Regarding the bandwidth -- Depends up on the transacgtion and amount of
> users connecting to your system. I recommend that you should
> have identical network band width for both production and DR site
> Thanks
> Hari
> SQL Server MVP
> "Mahmud" <Mahmud@.discussions.microsoft.com> wrote in message
> news:B6058E06-B1F7-45B7-A8E2-1ED6D83B6022@.microsoft.com...
>
>

Disester Recovery

Hi,
I'm using SQL Server 2000 Standard Edition and now I want to create a
Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
edition? For info, I'm running a Financial Software, which means data
transection rate is very high. Another thing is that, for my remote users
what would be the minimum bandwidth required to connect to SQL Server as well
as DR Site?
Please let me know..
regards,
MahmudHi,
You can wither use
1. Logshipping
2. TRansactional Replication
But all depends up on the network speed between your location to DR site. If
you have a dedicated network connectivity
then you can setup a Transactional replication.
Regarding the bandwidth -- Depends up on the transacgtion and amount of
users connecting to your system. I recommend that you should
have identical network band width for both production and DR site
Thanks
Hari
SQL Server MVP
"Mahmud" <Mahmud@.discussions.microsoft.com> wrote in message
news:B6058E06-B1F7-45B7-A8E2-1ED6D83B6022@.microsoft.com...
> Hi,
> I'm using SQL Server 2000 Standard Edition and now I want to create a
> Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
> edition? For info, I'm running a Financial Software, which means data
> transection rate is very high. Another thing is that, for my remote users
> what would be the minimum bandwidth required to connect to SQL Server as
> well
> as DR Site?
> Please let me know..
> regards,
> Mahmud|||Hi
Thanks for the info. Can you please provide me some technical doc links, so
that I can get a better idea & can able to create/manage DR site.
Thanks once again.
"Hari Prasad" wrote:
> Hi,
> You can wither use
> 1. Logshipping
> 2. TRansactional Replication
> But all depends up on the network speed between your location to DR site. If
> you have a dedicated network connectivity
> then you can setup a Transactional replication.
> Regarding the bandwidth -- Depends up on the transacgtion and amount of
> users connecting to your system. I recommend that you should
> have identical network band width for both production and DR site
> Thanks
> Hari
> SQL Server MVP
> "Mahmud" <Mahmud@.discussions.microsoft.com> wrote in message
> news:B6058E06-B1F7-45B7-A8E2-1ED6D83B6022@.microsoft.com...
> > Hi,
> >
> > I'm using SQL Server 2000 Standard Edition and now I want to create a
> > Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
> > edition? For info, I'm running a Financial Software, which means data
> > transection rate is very high. Another thing is that, for my remote users
> > what would be the minimum bandwidth required to connect to SQL Server as
> > well
> > as DR Site?
> >
> > Please let me know..
> >
> > regards,
> >
> > Mahmud
>
>

Disester Recovery

Hi,
I'm using SQL Server 2000 Standard Edition and now I want to create a
Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
edition? For info, I'm running a Financial Software, which means data
transection rate is very high. Another thing is that, for my remote users
what would be the minimum bandwidth required to connect to SQL Server as wel
l
as DR Site?
Please let me know..
regards,
MahmudHi,
You can wither use
1. Logshipping
2. TRansactional Replication
But all depends up on the network speed between your location to DR site. If
you have a dedicated network connectivity
then you can setup a Transactional replication.
Regarding the bandwidth -- Depends up on the transacgtion and amount of
users connecting to your system. I recommend that you should
have identical network band width for both production and DR site
Thanks
Hari
SQL Server MVP
"Mahmud" <Mahmud@.discussions.microsoft.com> wrote in message
news:B6058E06-B1F7-45B7-A8E2-1ED6D83B6022@.microsoft.com...
> Hi,
> I'm using SQL Server 2000 Standard Edition and now I want to create a
> Disester Recovery Site. Can I do that using that SQL Server 2000 Standard
> edition? For info, I'm running a Financial Software, which means data
> transection rate is very high. Another thing is that, for my remote users
> what would be the minimum bandwidth required to connect to SQL Server as
> well
> as DR Site?
> Please let me know..
> regards,
> Mahmud|||Hi
Thanks for the info. Can you please provide me some technical doc links, so
that I can get a better idea & can able to create/manage DR site.
Thanks once again.
"Hari Prasad" wrote:

> Hi,
> You can wither use
> 1. Logshipping
> 2. TRansactional Replication
> But all depends up on the network speed between your location to DR site.
If
> you have a dedicated network connectivity
> then you can setup a Transactional replication.
> Regarding the bandwidth -- Depends up on the transacgtion and amount of
> users connecting to your system. I recommend that you should
> have identical network band width for both production and DR site
> Thanks
> Hari
> SQL Server MVP
> "Mahmud" <Mahmud@.discussions.microsoft.com> wrote in message
> news:B6058E06-B1F7-45B7-A8E2-1ED6D83B6022@.microsoft.com...
>
>

2012年3月20日星期二

Disconnected Mirror / In Recovery

Hello,

I'm having a problem with two mirrored databases, using SQL Server 2005 SP2, that autmatically failed over last night for unknown reasons. I was trying to fail them back over to the primary SQL server because it says the mirror is disconnected and out of sync. Other databases failed over too, but I was able to fail those back over without a problem. It's just these two. I removed the mirror from the secondary server thinking that this would allow me to restore the database back on the primary server, but that didn't help.

These two databases show a status of (Principal, Disconnected / In Recovery) and I still cannot do anything with the two databases on the primary server. When I try to pull up the properties for them, I get the following error:

"Database <Name> is enabled for Database Mirroring, but neither the partner nor the witness server instances are available: the database cannot be opened.(Microsoft SQL Server, Error: 955)"

I cannot delete, detach, Alter or do anything with the databases. If I could just delete them that would be fine so I can just do a restore, but I can't seem to do anything.

Does anyone know what I can do to resolve this problem.

Thanks in advance!

-Jay

I was finally able to get the two databases to come back up online. I was trying so many different things, I 'm not sure which one, or combination, fixed it. But I checked the processes and there was one process running on one of the databases so I killed it. It seemed to come back right away, but after that, I was able to detach the DB. I reattached it and both of the databases came up with an online status.

I hope this helps.

-Jay

|||

This sounds similar to problems I have had (see my post below on split brain). I too had to kill connections to the principal in order to do anything to fix it, it went into recovery when I tried to remove mirroring and all users were disconnected.

I think this is very undesirable. There is no way both nodes should ever be the principal. If failover happens, it should either complete or not, there should be no half way, whatever the mode of failure.

|||

Sound like it, also mention what kind of configuration mode you are using for DB Mirroring.

As suggested referring to witness server log will helps a bit to see what is going on.

2012年3月19日星期一

Disater Recovery Solution using SQL

Hello,
For my DR soluion I am using an XP1024(Hitachi) array to sync data from
production site to DR site. My SQL servers take up a lot of bandwidth during
high business times with other applications. What is another way I can sync
the data from site A to site B? Is replication the answer?
Replication isn't recommended as a disaster recovery solution, all though it
can be used as such.
The main reasons are
1) not automatic failover
2) you have to reconfigure your apps to point to the new server
3) no system objects are replicated
4) not complete support for changing schemas - i.e. you can't change a pk
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Lontae Jones" <LontaeJones@.discussions.microsoft.com> wrote in message
news:98B3CFB8-27DF-40A3-B21C-B48C7BE4EF26@.microsoft.com...
> Hello,
> For my DR soluion I am using an XP1024(Hitachi) array to sync data from
> production site to DR site. My SQL servers take up a lot of bandwidth
during
> high business times with other applications. What is another way I can
sync
> the data from site A to site B? Is replication the answer?
>

2012年3月11日星期日

Disaster/recovery techniques

I have recently installed SQL Server 2000 on a newly acquired Windows
2003 server. The network admins also got Brightstor Agent for SQL
Server to interface with Brightstor ARCserve Backup for Windows
running on our backup server. I think I have a pretty good handle on
how to setup the SQL Server backups using a combination of
full/differential/transaction log backups to handle any recovery
required for the SQL Server databases.
What are the alternatives for backing up the Server itself for use in
recovery? Two approaches come to mind.
The first is not worry about backing up the server, in which case for
a recovery, I would have to reinstall all the software and service
packs to rebuild the environment. This would certainly require that I
have fully documented what applications (Windows 2003 server, SQL
Server, Outlook, Brightstor Agent, etc) and the install options that
were chosen. The rebuild process for this could take some time, and
there may be some issues that I haven't considered.
The second is to fully backup the server including the registry. If
everything were installed to the "C:\" drive, I could maybe get by
with just backing up the "C:\" drive and the registry. I do have a
weekend window where I could down the server to perform this task on a
weekly basis. Then for recovery I could just install an operating
system, restore from the backup of the "C:\" drive and registry and
proceed to my SQL Server recovery. Are there any problems with this
approach?
Finally, are there other techniques that I should consider? Any
websites or newsgroup threads on this topic would be greatly
appreciated.
Thanks Much, Lane LesperanceI prefere the first approach. it's the databases you should back up, not the
server.
Part of a good recovery plan is to document everything, so you can put the
server back to its original configuration before applying your backup files.
you can use the 2nd one, but to me it will take longer, and you need to
really test it on a test box to make sure you can recover your data that
way.
Steve Lin
MCDBA
"Lane Lesperance" <llesperance@.cooperpower.com> wrote in message
news:66feb5c.0404051118.e0472bf@.posting.google.com...
> I have recently installed SQL Server 2000 on a newly acquired Windows
> 2003 server. The network admins also got Brightstor Agent for SQL
> Server to interface with Brightstor ARCserve Backup for Windows
> running on our backup server. I think I have a pretty good handle on
> how to setup the SQL Server backups using a combination of
> full/differential/transaction log backups to handle any recovery
> required for the SQL Server databases.
> What are the alternatives for backing up the Server itself for use in
> recovery? Two approaches come to mind.
> The first is not worry about backing up the server, in which case for
> a recovery, I would have to reinstall all the software and service
> packs to rebuild the environment. This would certainly require that I
> have fully documented what applications (Windows 2003 server, SQL
> Server, Outlook, Brightstor Agent, etc) and the install options that
> were chosen. The rebuild process for this could take some time, and
> there may be some issues that I haven't considered.
> The second is to fully backup the server including the registry. If
> everything were installed to the "C:\" drive, I could maybe get by
> with just backing up the "C:\" drive and the registry. I do have a
> weekend window where I could down the server to perform this task on a
> weekly basis. Then for recovery I could just install an operating
> system, restore from the backup of the "C:\" drive and registry and
> proceed to my SQL Server recovery. Are there any problems with this
> approach?
> Finally, are there other techniques that I should consider? Any
> websites or newsgroup threads on this topic would be greatly
> appreciated.
> Thanks Much, Lane Lesperance

Disaster Recovery: SQL Server 2000 on Win 2000 Server.

This past Monday, our Raid 5 array failed on our SQL 2000 server (standard edition). Long story short, we were able to get the data back, mostly. In SQL server Ent. Mgr., I had to restore 4 databases that were 'Suspect' and "greyed out". No problems there... I was able to restore them.

What was interesting was that the SQL Server Agent would not start. As it turned out, a few files were either corrupt or missing after we got the machine back up. We had to restore a few files from tape backup and now the SQL Server Agent starts... but now I have a new problem.

For some reason, my default SQL Server Agent "Job" that is scheduled to run once per day fails. It appears that all of the databases get backed up, but for some reason, the msdbdata.mdf database is NOT being backed up.

I have a few questions. Could my msdbdata.mdf be corrupt? I have a successful backup of the msdbdata.mdf table from 9/10/2007. Can I just restore from that? Will there be any repercussions to any of the other database tables if I do?

Furthermore, should I just restore the msdbdata.mdf, master.mdf and the model.mdf? I really have no idea what these tables do and the repercussions of modifying them. I am not a DBA (obviously) and I just don't want to make an mistakes.

Thanks, CFDev.
Can you pls provide the details of the job history if any ? I guess you mean to say that msdb database backup fails if i interpret it correctly and Yes you can go ahead and restore the msdb.bak dated 9/10/2007 and check........the only issue is that all the jobs,dts packages created since 9/10 will not be available if you restore it.........I don't think its needed its enough if you restore msdb no need to restore master or model dbs..........
|||The "Job" is part of the databases default "maintenance plan". It consists of four parts:
1. DB backup
2. Integrity checks
3. Optimizations
4. Transaction Log Backup

This should be familiar to you, no? Anyway, would be okay to restore the msdb database then? How about the model and master databases? No tables, stored procedures, dts packages or anything has been changed. I just want peace of mind that if I were to restore any of these database tables, it would not effect any of my website's database tables. Make sense?

|||

Yes i am familiar with it if you feel there is no change done in msdb after 9/10 you can go ahead and restore msdb. Master stores all the login information and model acts as
template for other dbs so just restore msdb as it contains all the jobs and dts packages....I dont think restoring msdb would affect your db tables.......

|||

It would also be a good idea to run checkdb on all databases to make sure that they're clean.

You haven't made changes since 9/10, but you'd really rather not trip across hidden problems later.

Disaster Recovery: SQL Server 2000 on Win 2000 Server.

|||

It would also be a good idea to run checkdb on all databases to make sure that they're clean.

You haven't made changes since 9/10, but you'd really rather not trip across hidden problems later.

Disaster Recovery With SQL 8.0

Hi,
We are trialling a disaster recovery for a new customer who has been assured
his SQL is being backed up and can be recovered with the minimum of fuss. I
immediately found that his Master and Model were not being backed up, not
the end of the world but not what they were expecting either. Anyway, their
SQL is backed up a coupld of times per day via a Maintenance Plan. I have
completely restored his server to a new box and everything, apart from SQL,
is up and running. The situation is, I have the databases in *.bak format,
but because the Master and Model are missing, I cannot start SQL to
re-attach the databases. I have since copied a backup of Master and Model
taken since the original backup, copied them into place and tried to start
the service. No joy. No error. No nothing.
I've hunted high and low to find some documentation for my current scenario,
but not found any. Can somebody please point me in the right direction.
Many thanks
Hi
You can not attach a *.bak file. It's a backup you need to restore it. As
you say you don't need the master and model. However if you have a lot of
individual users with standard accounts it might take a while to get the
master up to date.
Here are some links to a lot of articles about moving/restoring databases to
another server. they should help you understand and resolve your issues.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission Issues
When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf http://www.support.microsoft.com/?id=307775 Disaster
Recovery Articles for SQL Server
Good Luck
John
|||By the way when i said you don't need to master and model database I did of
course mean you don't need to original. You definately need a master and
model database.
|||"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:AB7C8416-35B2-4233-8D4B-FE39CC2CCC9F@.microsoft.com...
> Hi
> You can not attach a *.bak file. It's a backup you need to restore it. As
> you say you don't need the master and model. However if you have a lot of
> individual users with standard accounts it might take a while to get the
> master up to date.
> Here are some links to a lot of articles about moving/restoring databases
> to
> another server. they should help you understand and resolve your issues.
> http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to
> a
> New Location with Detach/Attach
> http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
> Restore http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
> Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues
> When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scri...p?scriptid=599
> Restoring a .mdf http://www.support.microsoft.com/?id=307775 Disaster
> Recovery Articles for SQL Server
> Good Luck
> John
Thanks for the reply. A quick look through these, and they all rely on the
SQL server actually starting. My problem is, I can't start it! I've tried
rebuilding the Master but I get a message telling me there are no suitable
instances of SQL available..
|||Hi
I dont have access to your server and i don't know how you restored it, so I
can not comment on those issues. However from my experiences it is very hard
to restore a server including SQL Server files and then get it to work.
You would find it a lot easier to install SQL Server from scratch and then
restore your databases.
What tends to happen when you restore the entire Server is that SQL Server
does not respond well. (As you have found out). Usual reason is that the
backup software cannot backup in-use files. So you have things missing, most
significantly the .mdf and .ldf files.
With copies of the Master and Model and MSDB from another server and a good
bit of hacking into the register you may be able to bring it up, but what
state it would be in I don't know. Not a good one I'm sure.
I would advise you to rebuild the server, Install the operating system and
SQL Server and then follow the articles I first posted. Trying to proceed
from your current position is not going to work.
Regards
John
|||"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:31C3562B-D4B3-44FA-96AA-C6E8856FFDE3@.microsoft.com...
> Hi
> I dont have access to your server and i don't know how you restored it, so
> I
> can not comment on those issues. However from my experiences it is very
> hard
> to restore a server including SQL Server files and then get it to work.
> You would find it a lot easier to install SQL Server from scratch and then
> restore your databases.
> What tends to happen when you restore the entire Server is that SQL Server
> does not respond well. (As you have found out). Usual reason is that the
> backup software cannot backup in-use files. So you have things missing,
> most
> significantly the .mdf and .ldf files.
> With copies of the Master and Model and MSDB from another server and a
> good
> bit of hacking into the register you may be able to bring it up, but what
> state it would be in I don't know. Not a good one I'm sure.
> I would advise you to rebuild the server, Install the operating system and
> SQL Server and then follow the articles I first posted. Trying to proceed
> from your current position is not going to work.
> Regards
> John
Done it. Managed to get rebuildm.exe working after all kinds of traumas, and
once I had master back in place, it was as easy as I was hoping it would be!
Thanks for you help.
Matt

Disaster Recovery With SQL 8.0

Hi,
We are trialling a disaster recovery for a new customer who has been assured
his SQL is being backed up and can be recovered with the minimum of fuss. I
immediately found that his Master and Model were not being backed up, not
the end of the world but not what they were expecting either. Anyway, their
SQL is backed up a coupld of times per day via a Maintenance Plan. I have
completely restored his server to a new box and everything, apart from SQL,
is up and running. The situation is, I have the databases in *.bak format,
but because the Master and Model are missing, I cannot start SQL to
re-attach the databases. I have since copied a backup of Master and Model
taken since the original backup, copied them into place and tried to start
the service. No joy. No error. No nothing.
I've hunted high and low to find some documentation for my current scenario,
but not found any. Can somebody please point me in the right direction.
Many thanksHi
You can not attach a *.bak file. It's a backup you need to restore it. As
you say you don't need the master and model. However if you have a lot of
individual users with standard accounts it might take a while to get the
master up to date.
Here are some links to a lot of articles about moving/restoring databases to
another server. they should help you understand and resolve your issues.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission Issues
When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf http://www.support.microsoft.com/?id=307775 Disaster
Recovery Articles for SQL Server
Good Luck
John|||By the way when i said you don't need to master and model database I did of
course mean you don't need to original. You definately need a master and
model database.|||"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:AB7C8416-35B2-4233-8D4B-FE39CC2CCC9F@.microsoft.com...
> Hi
> You can not attach a *.bak file. It's a backup you need to restore it. As
> you say you don't need the master and model. However if you have a lot of
> individual users with standard accounts it might take a while to get the
> master up to date.
> Here are some links to a lot of articles about moving/restoring databases
> to
> another server. they should help you understand and resolve your issues.
> http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases to
> a
> New Location with Detach/Attach
> http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
> Restore http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
> Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues
> When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
> Restoring a .mdf http://www.support.microsoft.com/?id=307775 Disaster
> Recovery Articles for SQL Server
> Good Luck
> John
Thanks for the reply. A quick look through these, and they all rely on the
SQL server actually starting. My problem is, I can't start it! I've tried
rebuilding the Master but I get a message telling me there are no suitable
instances of SQL available..|||Hi
I dont have access to your server and i don't know how you restored it, so I
can not comment on those issues. However from my experiences it is very hard
to restore a server including SQL Server files and then get it to work.
You would find it a lot easier to install SQL Server from scratch and then
restore your databases.
What tends to happen when you restore the entire Server is that SQL Server
does not respond well. (As you have found out). Usual reason is that the
backup software cannot backup in-use files. So you have things missing, most
significantly the .mdf and .ldf files.
With copies of the Master and Model and MSDB from another server and a good
bit of hacking into the register you may be able to bring it up, but what
state it would be in I don't know. Not a good one I'm sure.
I would advise you to rebuild the server, Install the operating system and
SQL Server and then follow the articles I first posted. Trying to proceed
from your current position is not going to work.
Regards
John|||"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:31C3562B-D4B3-44FA-96AA-C6E8856FFDE3@.microsoft.com...
> Hi
> I dont have access to your server and i don't know how you restored it, so
> I
> can not comment on those issues. However from my experiences it is very
> hard
> to restore a server including SQL Server files and then get it to work.
> You would find it a lot easier to install SQL Server from scratch and then
> restore your databases.
> What tends to happen when you restore the entire Server is that SQL Server
> does not respond well. (As you have found out). Usual reason is that the
> backup software cannot backup in-use files. So you have things missing,
> most
> significantly the .mdf and .ldf files.
> With copies of the Master and Model and MSDB from another server and a
> good
> bit of hacking into the register you may be able to bring it up, but what
> state it would be in I don't know. Not a good one I'm sure.
> I would advise you to rebuild the server, Install the operating system and
> SQL Server and then follow the articles I first posted. Trying to proceed
> from your current position is not going to work.
> Regards
> John
Done it. Managed to get rebuildm.exe working after all kinds of traumas, and
once I had master back in place, it was as easy as I was hoping it would be!
Thanks for you help.
Matt

Disaster recovery through log file alone?

A collegue (really not me ;) has accidentally emptied a table in one of his
databases by making a simple typing error in a query, only to notice after
it happened that he had forgotten to create a backup schedule for that
database.
He has full recovery enabled the log has never been shrunk, so all his data
should still be present there.
Is there any way to use that log file to get his data back up to the point
where he emptied the table?
Automatic recovery would restore everything including the deletion, so what
we need is something like the 'STOPAT' option from RESTORE LOG, except that
there's no backup so RESTORE LOG is out of the question.
Or isn't it?
hi,
"Lucvdv" <replace_name@.null.net> ha scritto nel messaggio
news:v8ads0pkece7kjeelaalribkgt6dtec1b2@.4ax.com
> A collegue (really not me ;) has accidentally emptied a table in one
> of his databases by making a simple typing error in a query, only to
> notice after it happened that he had forgotten to create a backup
> schedule for that database.
> He has full recovery enabled the log has never been shrunk, so all
> his data should still be present there.
> Is there any way to use that log file to get his data back up to the
> point where he emptied the table?
> Automatic recovery would restore everything including the deletion,
> so what we need is something like the 'STOPAT' option from RESTORE
> LOG, except that there's no backup so RESTORE LOG is out of the
> question.
> Or isn't it?
as you do not have a backup to restore from, you are aout of luck with
standard SQL Server tools... but..
but Lumigent has a tool, Log Explorer,
http://www.lumigent.com/products/le_sql.html, which can be of interest..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Mon, 20 Dec 2004 13:23:50 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

> as you do not have a backup to restore from, you are aout of luck with
> standard SQL Server tools... but..
> but Lumigent has a tool, Log Explorer,
> http://www.lumigent.com/products/le_sql.html, which can be of interest..
Thanks.
I passed it on, but I wonder if his data are going to be worth the $1850
price tag of the product ;)
|||"Lucvdv" <replace_name@.null.net> ha scritto nel messaggio
news:bsnds0to23e1rm8p2lndi1nepcq97idvej@.4ax.com
> On Mon, 20 Dec 2004 13:23:50 +0100, "Andrea Montanari"
> <andrea.sqlDMO@.virgilio.it> wrote:
>
> Thanks.
> I passed it on, but I wonder if his data are going to be worth the
> $1850 price tag of the product ;)
:D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Disaster Recovery Tests

Currently we use Log shipping between our active site and our DR site. The
question I have is when we do DR testing at the DR site to test
recoverability, we have to recover all those Log shipped databases which
means we are exposed until our DR tests are completed.
How does one go about ensuring we do not get exposed and continue to keep
data current and yet be able to test. Does that mean I have to log ship to 2
instances ? We have so many databases with TBs of storage and now I have to
double the storage and maintenance..
Anyways, are there other ways of doing so than Log shipping ?
We are on the SAN.When you say "exposed," what do you mean? What we do is we have DNS
settings that we manually change (IP address changes, that is) during DR
tests. This in itself will prevent anybody from accessing the production
servers, unless they know the server and instance names and access the
servers directly. After DR tests, we revert to the original IP addresses of
the production servers configured on our DNS settings.
"Hassan" <hassan@.hotmail.com> wrote in message
news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
> Currently we use Log shipping between our active site and our DR site. The
> question I have is when we do DR testing at the DR site to test
> recoverability, we have to recover all those Log shipped databases which
> means we are exposed until our DR tests are completed.
> How does one go about ensuring we do not get exposed and continue to keep
> data current and yet be able to test. Does that mean I have to log ship to
> 2 instances ? We have so many databases with TBs of storage and now I have
> to double the storage and maintenance..
> Anyways, are there other ways of doing so than Log shipping ?
> We are on the SAN.
>|||I meant exposed at the DR site by not receiving logs and being current as
the log ship databases would be recovered for DR testing..
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u7im1C7AIHA.4476@.TK2MSFTNGP06.phx.gbl...
> When you say "exposed," what do you mean? What we do is we have DNS
> settings that we manually change (IP address changes, that is) during DR
> tests. This in itself will prevent anybody from accessing the production
> servers, unless they know the server and instance names and access the
> servers directly. After DR tests, we revert to the original IP addresses
> of the production servers configured on our DNS settings.
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
>> Currently we use Log shipping between our active site and our DR site.
>> The question I have is when we do DR testing at the DR site to test
>> recoverability, we have to recover all those Log shipped databases which
>> means we are exposed until our DR tests are completed.
>> How does one go about ensuring we do not get exposed and continue to keep
>> data current and yet be able to test. Does that mean I have to log ship
>> to 2 instances ? We have so many databases with TBs of storage and now I
>> have to double the storage and maintenance..
>> Anyways, are there other ways of doing so than Log shipping ?
>> We are on the SAN.
>|||Hassan
RESTORE DATABASE database_name WITH RECOVERY
"Hassan" <hassan@.hotmail.com> wrote in message
news:%23MvD1r7AIHA.2268@.TK2MSFTNGP04.phx.gbl...
>I meant exposed at the DR site by not receiving logs and being current as
>the log ship databases would be recovered for DR testing..
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:u7im1C7AIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> When you say "exposed," what do you mean? What we do is we have DNS
>> settings that we manually change (IP address changes, that is) during DR
>> tests. This in itself will prevent anybody from accessing the production
>> servers, unless they know the server and instance names and access the
>> servers directly. After DR tests, we revert to the original IP addresses
>> of the production servers configured on our DNS settings.
>>
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:%23TgJzy4AIHA.5160@.TK2MSFTNGP05.phx.gbl...
>> Currently we use Log shipping between our active site and our DR site.
>> The question I have is when we do DR testing at the DR site to test
>> recoverability, we have to recover all those Log shipped databases which
>> means we are exposed until our DR tests are completed.
>> How does one go about ensuring we do not get exposed and continue to
>> keep data current and yet be able to test. Does that mean I have to log
>> ship to 2 instances ? We have so many databases with TBs of storage and
>> now I have to double the storage and maintenance..
>> Anyways, are there other ways of doing so than Log shipping ?
>> We are on the SAN.
>>
>

Disaster Recovery Site Setup

All,
We are planning to setup disaster recovery in Vegas, actual one is in
SanFrancisco.
We have to synchronize the databases from SanFrancisco to Vegas.Ours is
24 X 7 ecommerce site.
Requirement for Disaster recovery is automatic failover and fail back
from one site to another site with minimum manual intervention.
Please advise if anybody has setup the disaster recovery.
Is Transactional Replication is good for two way replication?
Log shipping is good for just one way synchronization, and our log backups
will be 30 gb per day.
Has anybody has used wansync or goldengate softwares for the disaster
recovery setup?
Thanks.Hi,
SQL Server 2005 - Database Mirroring is the most suggested mechanism for
you. Database mirroring with a
Witness instance supported will do a automatic failover if the Primary
instance is down.
See the below URL on the article on setup of database mirroring.
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
Thanks
Hari
SQL Server MVP
"DKRReddy" <dkrreddy@.hotmail.com> wrote in message
news:%23rbl0R7wGHA.1484@.TK2MSFTNGP04.phx.gbl...
> All,
> We are planning to setup disaster recovery in Vegas, actual one is in
> SanFrancisco.
> We have to synchronize the databases from SanFrancisco to Vegas.Ours
> is
> 24 X 7 ecommerce site.
> Requirement for Disaster recovery is automatic failover and fail back
> from one site to another site with minimum manual intervention.
> Please advise if anybody has setup the disaster recovery.
> Is Transactional Replication is good for two way replication?
> Log shipping is good for just one way synchronization, and our log backups
> will be 30 gb per day.
> Has anybody has used wansync or goldengate softwares for the disaster
> recovery setup?
>
> Thanks.
>|||You mention that you are a 24 x 7 ecommerce site. Besides the
databases, what are you doing to protect your web servers? If you host
your web servers in SanFrancisco and you lose the whole site, do you
have an automated means of redirecting the web traffic to the DR site
in Vegas?
In regards to your database solution, SQL Server 2005 - Database
Mirroring is fine for some things, however when running in the
automatic failover mode, you must use syncronous replication.
Syncronous replication across a WAN is going to kill the performance of
your primary database because it must wait for the write to commit on
the secondary server before it can commit on the primary server.
The other issue with SQL Server 2005 replication with automatic
failover is the placement of the witness server. This setup only truly
works if you have the witness server in a third location with seperate
communication paths to the primary and secondary data center.
Otherwise, with the witness server in the primary data center you will
not failover if you have a site loss (witness server is also gone).
With the witness server in the secondary data center you will have
false failovers if the WAN link goes down, because the witness server
and the secondary server will think the primary is unavailable.
If you go with SQL Server 2005 Database Mirroring, then I would forget
about the automatic failover mode and go with asyncronous replication
and a manual failover. Your other option is to go with a third party
solution such as LifeKeeper for SQL Server or one of the other ones you
mentioned.
David A. Bermingham, MCSE, MCSA:Messaging
Systems Engineer
www.steeleye.com
Hari Prasad wrote:
> Hi,
> SQL Server 2005 - Database Mirroring is the most suggested mechanism for
> you. Database mirroring with a
> Witness instance supported will do a automatic failover if the Primary
> instance is down.
> See the below URL on the article on setup of database mirroring.
> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
> Thanks
> Hari
> SQL Server MVP
>
> "DKRReddy" <dkrreddy@.hotmail.com> wrote in message
> news:%23rbl0R7wGHA.1484@.TK2MSFTNGP04.phx.gbl...
> > All,
> > We are planning to setup disaster recovery in Vegas, actual one is in
> > SanFrancisco.
> > We have to synchronize the databases from SanFrancisco to Vegas.Ours
> > is
> > 24 X 7 ecommerce site.
> > Requirement for Disaster recovery is automatic failover and fail back
> > from one site to another site with minimum manual intervention.
> >
> > Please advise if anybody has setup the disaster recovery.
> >
> > Is Transactional Replication is good for two way replication?
> > Log shipping is good for just one way synchronization, and our log backups
> > will be 30 gb per day.
> >
> > Has anybody has used wansync or goldengate softwares for the disaster
> > recovery setup?
> >
> >
> > Thanks.
> >
> >

Disaster Recovery Site Setup

All,
We are planning to setup disaster recovery in Vegas, actual one is in
SanFrancisco.
We have to synchronize the databases from SanFrancisco to Vegas.Ours is
24 X 7 ecommerce site.
Requirement for Disaster recovery is automatic failover and fail back
from one site to another site with minimum manual intervention.
Please advise if anybody has setup the disaster recovery.
Is Transactional Replication is good for two way replication?
Log shipping is good for just one way synchronization, and our log backups
will be 30 gb per day.
Has anybody has used wansync or goldengate softwares for the disaster
recovery setup?
Thanks.Hi,
SQL Server 2005 - Database Mirroring is the most suggested mechanism for
you. Database mirroring with a
Witness instance supported will do a automatic failover if the Primary
instance is down.
See the below URL on the article on setup of database mirroring.
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
Thanks
Hari
SQL Server MVP
"DKRReddy" <dkrreddy@.hotmail.com> wrote in message
news:%23rbl0R7wGHA.1484@.TK2MSFTNGP04.phx.gbl...
> All,
> We are planning to setup disaster recovery in Vegas, actual one is in
> SanFrancisco.
> We have to synchronize the databases from SanFrancisco to Vegas.Ours
> is
> 24 X 7 ecommerce site.
> Requirement for Disaster recovery is automatic failover and fail back
> from one site to another site with minimum manual intervention.
> Please advise if anybody has setup the disaster recovery.
> Is Transactional Replication is good for two way replication?
> Log shipping is good for just one way synchronization, and our log backups
> will be 30 gb per day.
> Has anybody has used wansync or goldengate softwares for the disaster
> recovery setup?
>
> Thanks.
>|||You mention that you are a 24 x 7 ecommerce site. Besides the
databases, what are you doing to protect your web servers? If you host
your web servers in SanFrancisco and you lose the whole site, do you
have an automated means of redirecting the web traffic to the DR site
in Vegas?
In regards to your database solution, SQL Server 2005 - Database
Mirroring is fine for some things, however when running in the
automatic failover mode, you must use syncronous replication.
Syncronous replication across a WAN is going to kill the performance of
your primary database because it must wait for the write to commit on
the secondary server before it can commit on the primary server.
The other issue with SQL Server 2005 replication with automatic
failover is the placement of the witness server. This setup only truly
works if you have the witness server in a third location with seperate
communication paths to the primary and secondary data center.
Otherwise, with the witness server in the primary data center you will
not failover if you have a site loss (witness server is also gone).
With the witness server in the secondary data center you will have
false failovers if the WAN link goes down, because the witness server
and the secondary server will think the primary is unavailable.
If you go with SQL Server 2005 Database Mirroring, then I would forget
about the automatic failover mode and go with asyncronous replication
and a manual failover. Your other option is to go with a third party
solution such as LifeKeeper for SQL Server or one of the other ones you
mentioned.
David A. Bermingham, MCSE, MCSA:Messaging
Systems Engineer
www.steeleye.com
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> SQL Server 2005 - Database Mirroring is the most suggested mechanism for
> you. Database mirroring with a
> Witness instance supported will do a automatic failover if the Primary
> instance is down.
> See the below URL on the article on setup of database mirroring.
> http://www.microsoft.com/technet/pr...5/dbmirror.mspx
> Thanks
> Hari
> SQL Server MVP
>
> "DKRReddy" <dkrreddy@.hotmail.com> wrote in message
> news:%23rbl0R7wGHA.1484@.TK2MSFTNGP04.phx.gbl...

Disaster Recovery Scenarios for Analysis Services

I am trying to find disaster recovery scenarios for Analysis Services which seems to be lacking. Is there anything documented.

Thanks

Steve -

I am not aware of any disaster recovery document that talks specifically about Analysis Services.

The bits and pieces of disaster recovery information are scattered in Books Online: you might look in Backup/Restore, Failover Clustering, server sync… But I don’t see any one topic in BOL that brings it all together.

I asked members of the Analysis Services team and they said the same thing.

Thanks,

Don

|||I thought as much. Thanks for asking.|||Which version of Analysis Services?

Disaster Recovery rehearsal

Hi,
I am performing a disaster recovery reharsal for SQL
Server with various test cases on a Test Server. I want to
corrupt the Master Database( without deleting the .ldf)
Manually and then try to recover. Which is the best way to
do this? . also Any resources on Disaster Recovery
reharsals on SQL Servers are appreciated.
Regards
ChipHi
check out following articles about disaster recovery
http://www.sqljunkies.com/HowTo/F30B1E5F-F50F-40A8-96F2-476CEAD46C79.scuk
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;307775
Regards,
MD
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> Hi,
> I am performing a disaster recovery reharsal for SQL
> Server with various test cases on a Test Server. I want to
> corrupt the Master Database( without deleting the .ldf)
> Manually and then try to recover. Which is the best way to
> do this? . also Any resources on Disaster Recovery
> reharsals on SQL Servers are appreciated.
> Regards
> Chip|||Do you want it to go suspect or just cause a corruption in the master
database?
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> Hi,
> I am performing a disaster recovery reharsal for SQL
> Server with various test cases on a Test Server. I want to
> corrupt the Master Database( without deleting the .ldf)
> Manually and then try to recover. Which is the best way to
> do this? . also Any resources on Disaster Recovery
> reharsals on SQL Servers are appreciated.
> Regards
> Chip|||hi Tibor,
Thanks for the response. what should i do to go it to
suspect(without deleting .ldf) and how to cause a
corruption. Please suggest both ways so that I can have
two test cases in hand. :-)
Sincere Regards
Chip.
>--Original Message--
>Do you want it to go suspect or just cause a corruption
in the master
>database?
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Chip" <anonymous@.discussions.microsoft.com> wrote in
message
>news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
>> Hi,
>> I am performing a disaster recovery reharsal for SQL
>> Server with various test cases on a Test Server. I want
to
>> corrupt the Master Database( without deleting the .ldf)
>> Manually and then try to recover. Which is the best way
to
>> do this? . also Any resources on Disaster Recovery
>> reharsals on SQL Servers are appreciated.
>> Regards
>> Chip
>
>.
>|||Chip,
To make it corrupt, you can create a table and for the table hack some value
in the sysindexes table (IAM column, for instance). You need to figure out
how to do modifications against the systems tables as I don't want to put
that information in a public place.
As for suspect, read the source code for sp_resetstatus and reverse what it
does. It should work on the master database...
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
> hi Tibor,
> Thanks for the response. what should i do to go it to
> suspect(without deleting .ldf) and how to cause a
> corruption. Please suggest both ways so that I can have
> two test cases in hand. :-)
> Sincere Regards
> Chip.
> >--Original Message--
> >Do you want it to go suspect or just cause a corruption
> in the master
> >database?
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> I am performing a disaster recovery reharsal for SQL
> >> Server with various test cases on a Test Server. I want
> to
> >> corrupt the Master Database( without deleting the .ldf)
> >> Manually and then try to recover. Which is the best way
> to
> >> do this? . also Any resources on Disaster Recovery
> >> reharsals on SQL Servers are appreciated.
> >>
> >> Regards
> >>
> >> Chip
> >
> >
> >.
> >|||Poor me.
Not a expert dba to hack and crack :-(. If it is possible
to mail the procedure, I will be greatful. I need to
perform this at any cost and send the details to my boss
with step-by-step procedure :-(. Any resources pointing to
achieve this are highly appreciated.
Chip
chipsin007@.NOSPAM.yahoo.com
>--Original Message--
>Chip,
>To make it corrupt, you can create a table and for the
table hack some value
>in the sysindexes table (IAM column, for instance). You
need to figure out
>how to do modifications against the systems tables as I
don't want to put
>that information in a public place.
>As for suspect, read the source code for sp_resetstatus
and reverse what it
>does. It should work on the master database...
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Chip" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
>> hi Tibor,
>> Thanks for the response. what should i do to go it to
>> suspect(without deleting .ldf) and how to cause a
>> corruption. Please suggest both ways so that I can have
>> two test cases in hand. :-)
>> Sincere Regards
>> Chip.
>> >--Original Message--
>> >Do you want it to go suspect or just cause a corruption
>> in the master
>> >database?
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >Archive at:
>> >http://groups.google.com/groups?
>> oi=djq&as_ugroup=microsoft.public.sqlserver
>> >
>> >
>> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
>> >> Hi,
>> >>
>> >> I am performing a disaster recovery reharsal for SQL
>> >> Server with various test cases on a Test Server. I
want
>> to
>> >> corrupt the Master Database( without deleting
the .ldf)
>> >> Manually and then try to recover. Which is the best
way
>> to
>> >> do this? . also Any resources on Disaster Recovery
>> >> reharsals on SQL Servers are appreciated.
>> >>
>> >> Regards
>> >>
>> >> Chip
>> >
>> >
>> >.
>> >
>
>.
>|||You won't, to my knowledge, find any such resources. And I don't have any
ready-made scripts as I always do them as I go along. On top for the first
one is sp_configure and the "allow updates" option. As for the second one,
you need to read the source code of sp_resetstatus and make appropriate
changes (the suspect status is in the status column if
master..sysdatabases). If this makes no sense to you, you really need to
bring someone in to do these things... :-)
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:e9d401c3f15c$1898d3e0$a301280a@.phx.gbl...
> Poor me.
> Not a expert dba to hack and crack :-(. If it is possible
> to mail the procedure, I will be greatful. I need to
> perform this at any cost and send the details to my boss
> with step-by-step procedure :-(. Any resources pointing to
> achieve this are highly appreciated.
> Chip
> chipsin007@.NOSPAM.yahoo.com
> >--Original Message--
> >Chip,
> >
> >To make it corrupt, you can create a table and for the
> table hack some value
> >in the sysindexes table (IAM column, for instance). You
> need to figure out
> >how to do modifications against the systems tables as I
> don't want to put
> >that information in a public place.
> >As for suspect, read the source code for sp_resetstatus
> and reverse what it
> >does. It should work on the master database...
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
> >> hi Tibor,
> >>
> >> Thanks for the response. what should i do to go it to
> >> suspect(without deleting .ldf) and how to cause a
> >> corruption. Please suggest both ways so that I can have
> >> two test cases in hand. :-)
> >>
> >> Sincere Regards
> >>
> >> Chip.
> >> >--Original Message--
> >> >Do you want it to go suspect or just cause a corruption
> >> in the master
> >> >database?
> >> >
> >> >--
> >> >Tibor Karaszi, SQL Server MVP
> >> >Archive at:
> >> >http://groups.google.com/groups?
> >> oi=djq&as_ugroup=microsoft.public.sqlserver
> >> >
> >> >
> >> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> >> message
> >> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> I am performing a disaster recovery reharsal for SQL
> >> >> Server with various test cases on a Test Server. I
> want
> >> to
> >> >> corrupt the Master Database( without deleting
> the .ldf)
> >> >> Manually and then try to recover. Which is the best
> way
> >> to
> >> >> do this? . also Any resources on Disaster Recovery
> >> >> reharsals on SQL Servers are appreciated.
> >> >>
> >> >> Regards
> >> >>
> >> >> Chip
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||You can always change where SQL looks for the master.mdf file. That will
put you in a DR situation when you restart it. SQL will attempt to come
online and will not be able to start. It is also fixable by changing the
regkey back. I'd practice on a lab server until you are comfortable. USE
AT YOUR OWN RISK.
Christian Smith
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:e98501c3f154$c22ad640$a301280a@.phx.gbl...
> hi Tibor,
> Thanks for the response. what should i do to go it to
> suspect(without deleting .ldf) and how to cause a
> corruption. Please suggest both ways so that I can have
> two test cases in hand. :-)
> Sincere Regards
> Chip.
> >--Original Message--
> >Do you want it to go suspect or just cause a corruption
> in the master
> >database?
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Chip" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:f22a01c3f111$bfee2820$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> I am performing a disaster recovery reharsal for SQL
> >> Server with various test cases on a Test Server. I want
> to
> >> corrupt the Master Database( without deleting the .ldf)
> >> Manually and then try to recover. Which is the best way
> to
> >> do this? . also Any resources on Disaster Recovery
> >> reharsals on SQL Servers are appreciated.
> >>
> >> Regards
> >>
> >> Chip
> >
> >
> >.
> >

Disaster Recovery rehearsal

Disaster Recovery question

Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
--
sql2k sp3
TIA, ChrisRYou can restore master to another box. Just keep in mind that if you don't
have your app DB's in the exact same folders, you will have a bunch of
suspect DB's. Here, you can do one of two things:
1) Drop the suspect DB's and simply restore from backup. IOW, you've
restored master and the other DB's don't even exist (physically) on your
server yet. When master is restored, it thinks they're there (since they're
in the sysdatabases table) and it then marks them as suspect. Dropping them
sets the record straight and you can just restore them at that point.
2) Restore the app databases first. Make sure they are in the exact same
folders as on your original server. Now, restore master and everything is
in synch.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
Ive been doing a bit of digging lately about Restoring the Master db to a
box with another name and Im a bit confused. Near as I can tell this action
isn't supported. At least not by people in these types of forums. My
Disaster Recovery pobbibilities are very limited @. the moment. I don't have
a spare server. Probably won't have one anytime soon. Yes, yes, Ive brought
this up to everyone but got nowhere. The reply I got was if the server dies
we would resotre from backup over to the Reporting box. So now my question.
I take backups of the Master, MSDB, and user db's regularly. They are put
onto tape. But, since Master cant be restored to a box with another name,
what good is the backup of it for someone like in my scenario? That being
said, how would I ever get back my logins/ passwords, etc. I know I can get
the jobs from MSDB, but not the logins. All ideas appreciated.
sql2k sp3
TIA, ChrisR|||Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>|||That's odd. The only thing I'd be doing with respect to the name is
sp_dropserver <old name> and sp_addserver <new name., 'local'.
Can you post the SQL Server error log of the dysfunctional server? Have you
tried starting the SQL Server service from the command prompt? Check out
sqlservr.exe in the BOL for the details.
BTW, I've had no problems in DR rehearsals restoring master to another box.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
Tom I appreciate your reply. To clarify, you are referring to a box with
another name, correct? Ive made several attempts at this and have yet to do
it successfully. I restore it fine, but then the service doesnt start and
doesnt report an error either. Says it can be an internal Windows problem.
All the KB articles I can find on moving db's makes no reference to whether
or not the box has the same name.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> You can restore master to another box. Just keep in mind that if you
don't
> have your app DB's in the exact same folders, you will have a bunch of
> suspect DB's. Here, you can do one of two things:
> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
> restored master and the other DB's don't even exist (physically) on your
> server yet. When master is restored, it thinks they're there (since
they're
> in the sysdatabases table) and it then marks them as suspect. Dropping
them
> sets the record straight and you can just restore them at that point.
> 2) Restore the app databases first. Make sure they are in the exact
same
> folders as on your original server. Now, restore master and everything is
> in synch.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> Ive been doing a bit of digging lately about Restoring the Master db to a
> box with another name and Im a bit confused. Near as I can tell this
action
> isn't supported. At least not by people in these types of forums. My
> Disaster Recovery pobbibilities are very limited @. the moment. I don't
have
> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
brought
> this up to everyone but got nowhere. The reply I got was if the server
dies
> we would resotre from backup over to the Reporting box. So now my
question.
> I take backups of the Master, MSDB, and user db's regularly. They are put
> onto tape. But, since Master cant be restored to a box with another name,
> what good is the backup of it for someone like in my scenario? That being
> said, how would I ever get back my logins/ passwords, etc. I know I can
get
> the jobs from MSDB, but not the logins. All ideas appreciated.
>
> --
> sql2k sp3
> TIA, ChrisR
>|||The name does not prevent SQL Server from starting. Having a different path does, though. Hunt for
error messages in the error log file and in the event log. This will show you the root of the
problem(s).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.NoEmails.com> wrote in message news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
> Tom I appreciate your reply. To clarify, you are referring to a box with
> another name, correct? Ive made several attempts at this and have yet to do
> it successfully. I restore it fine, but then the service doesnt start and
> doesnt report an error either. Says it can be an internal Windows problem.
> All the KB articles I can find on moving db's makes no reference to whether
> or not the box has the same name.
>
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
>> You can restore master to another box. Just keep in mind that if you
> don't
>> have your app DB's in the exact same folders, you will have a bunch of
>> suspect DB's. Here, you can do one of two things:
>> 1) Drop the suspect DB's and simply restore from backup. IOW, you've
>> restored master and the other DB's don't even exist (physically) on your
>> server yet. When master is restored, it thinks they're there (since
> they're
>> in the sysdatabases table) and it then marks them as suspect. Dropping
> them
>> sets the record straight and you can just restore them at that point.
>> 2) Restore the app databases first. Make sure they are in the exact
> same
>> folders as on your original server. Now, restore master and everything is
>> in synch.
>> --
>> Tom
>> ---
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinnaclepublishing.com
>>
>> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
>> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
>> Ive been doing a bit of digging lately about Restoring the Master db to a
>> box with another name and Im a bit confused. Near as I can tell this
> action
>> isn't supported. At least not by people in these types of forums. My
>> Disaster Recovery pobbibilities are very limited @. the moment. I don't
> have
>> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
> brought
>> this up to everyone but got nowhere. The reply I got was if the server
> dies
>> we would resotre from backup over to the Reporting box. So now my
> question.
>> I take backups of the Master, MSDB, and user db's regularly. They are put
>> onto tape. But, since Master cant be restored to a box with another name,
>> what good is the backup of it for someone like in my scenario? That being
>> said, how would I ever get back my logins/ passwords, etc. I know I can
> get
>> the jobs from MSDB, but not the logins. All ideas appreciated.
>>
>> --
>> sql2k sp3
>> TIA, ChrisR
>>
>|||> The name does not prevent SQL Server from starting. Having a different
path does, though
Bingo! The Master, Model, and MSDB files must all be in the same path as
they were on the original Server. That was the problem.
Tom and Tibor, thank you both!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e0HZ#J3uEHA.1264@.TK2MSFTNGP12.phx.gbl...
> The name does not prevent SQL Server from starting. Having a different
path does, though. Hunt for
> error messages in the error log file and in the event log. This will show
you the root of the
> problem(s).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
news:%23gEtx72uEHA.1448@.TK2MSFTNGP10.phx.gbl...
> > Tom I appreciate your reply. To clarify, you are referring to a box with
> > another name, correct? Ive made several attempts at this and have yet to
do
> > it successfully. I restore it fine, but then the service doesnt start
and
> > doesnt report an error either. Says it can be an internal Windows
problem.
> > All the KB articles I can find on moving db's makes no reference to
whether
> > or not the box has the same name.
> >
> >
> >
> >
> > "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> > news:OSDMax2uEHA.200@.TK2MSFTNGP11.phx.gbl...
> >> You can restore master to another box. Just keep in mind that if you
> > don't
> >> have your app DB's in the exact same folders, you will have a bunch of
> >> suspect DB's. Here, you can do one of two things:
> >>
> >> 1) Drop the suspect DB's and simply restore from backup. IOW,
you've
> >> restored master and the other DB's don't even exist (physically) on
your
> >> server yet. When master is restored, it thinks they're there (since
> > they're
> >> in the sysdatabases table) and it then marks them as suspect. Dropping
> > them
> >> sets the record straight and you can just restore them at that point.
> >>
> >> 2) Restore the app databases first. Make sure they are in the exact
> > same
> >> folders as on your original server. Now, restore master and everything
is
> >> in synch.
> >>
> >> --
> >> Tom
> >>
> >> ---
> >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> >> SQL Server MVP
> >> Columnist, SQL Server Professional
> >> Toronto, ON Canada
> >> www.pinnaclepublishing.com
> >>
> >>
> >> "ChrisR" <ChrisR@.NoEmails.com> wrote in message
> >> news:eRF8sr2uEHA.228@.TK2MSFTNGP10.phx.gbl...
> >> Ive been doing a bit of digging lately about Restoring the Master db to
a
> >> box with another name and Im a bit confused. Near as I can tell this
> > action
> >> isn't supported. At least not by people in these types of forums. My
> >> Disaster Recovery pobbibilities are very limited @. the moment. I don't
> > have
> >> a spare server. Probably won't have one anytime soon. Yes, yes, Ive
> > brought
> >> this up to everyone but got nowhere. The reply I got was if the server
> > dies
> >> we would resotre from backup over to the Reporting box. So now my
> > question.
> >> I take backups of the Master, MSDB, and user db's regularly. They are
put
> >> onto tape. But, since Master cant be restored to a box with another
name,
> >> what good is the backup of it for someone like in my scenario? That
being
> >> said, how would I ever get back my logins/ passwords, etc. I know I can
> > get
> >> the jobs from MSDB, but not the logins. All ideas appreciated.
> >>
> >>
> >> --
> >> sql2k sp3
> >>
> >> TIA, ChrisR
> >>
> >>
> >
> >
>

Disaster Recovery Question

Have cluster running on two servers; suppose I lost both of them, but have a tape backup of the cluster. Does anyone have some thorough directions on restoring the cluster on different servers? We've had no luck in completely making the restore function.
Have you tried this:
http://support.microsoft.com/default...b;en-us;286422
What happened when you tried before?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Sue" <Sue@.discussions.microsoft.com> wrote in message
news:6C013ECA-FA78-4A11-ACCF-1E14CBAAFF48@.microsoft.com...
> Have cluster running on two servers; suppose I lost both of them, but have
a tape backup of the cluster. Does anyone have some thorough directions on
restoring the cluster on different servers? We've had no luck in completely
making the restore function.
|||One thing the cluster service wouldn't start.
We had people tell us that the drives weren't in the wrong order.
"Rodney R. Fournier [MVP]" wrote:

> Have you tried this:
> http://support.microsoft.com/default...b;en-us;286422
> What happened when you tried before?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "Sue" <Sue@.discussions.microsoft.com> wrote in message
> news:6C013ECA-FA78-4A11-ACCF-1E14CBAAFF48@.microsoft.com...
> a tape backup of the cluster. Does anyone have some thorough directions on
> restoring the cluster on different servers? We've had no luck in completely
> making the restore function.
>
>
|||One thing the cluster service wouldn't start.
We had people tell us that the drives weren't in the wrong order.
"Rodney R. Fournier [MVP]" wrote:

> Have you tried this:
> http://support.microsoft.com/default...b;en-us;286422
> What happened when you tried before?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "Sue" <Sue@.discussions.microsoft.com> wrote in message
> news:6C013ECA-FA78-4A11-ACCF-1E14CBAAFF48@.microsoft.com...
> a tape backup of the cluster. Does anyone have some thorough directions on
> restoring the cluster on different servers? We've had no luck in completely
> making the restore function.
>
>

Disaster Recovery question

What's the best method for preparing for a SQL Server2K disaster? Is backing
up master, msdb and model as well as the logins and user databases enough?
Is it better to restore master and msdb or re-create the logins and jobs
(assuming they were scripted out).
Looking for other perspectives.
Thanks
Ron
Ron hi,
Check this article and you will find some ideas
http://support.microsoft.com/default...b;en-us;307775
HTH
Andreas
"Ron" wrote:

> What's the best method for preparing for a SQL Server2K disaster? Is backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>
|||Thanks - that shows good "How to" for the details. However I was looking for
more of an overview, bigger picture for DR.
Thanks.
Ron
"Andreas Mavrogenis" wrote:
[vbcol=seagreen]
> Ron hi,
> Check this article and you will find some ideas
> http://support.microsoft.com/default...b;en-us;307775
> HTH
> Andreas
> "Ron" wrote:
|||MASTER, MSDB and user database backup if fine.. this include most of the
things.. other then this, keep on taking registry backup of server nad
doucment your configuration setting of SQL Server.
You should do some dummy test for restoration of databases and validate what
backup policy you have for point in time recovery of user databases.
"Ron" wrote:
[vbcol=seagreen]
> Thanks - that shows good "How to" for the details. However I was looking for
> more of an overview, bigger picture for DR.
> Thanks.
> Ron
> "Andreas Mavrogenis" wrote:
|||If a brand new box is to replace the fail server, prepare the disk drive
mappings, processor, RAM, etc.
Other things include SQL server configuration, startup parameters, memory
configuration, scripted replications, and more.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
> What's the best method for preparing for a SQL Server2K disaster? Is
> backing
> up master, msdb and model as well as the logins and user databases enough?
> Is it better to restore master and msdb or re-create the logins and jobs
> (assuming they were scripted out).
> Looking for other perspectives.
> Thanks
> Ron
>
|||Hi,
As writen, you must have a documented disaster recovery plan, in order to
perform these actions step-by-step, avoiding to forget something.
Also, if you have another machine, the ideal is to have it on another site
if applicable with all nesecary network routes.
A disaster plan is a subject to discuss because you have many-many option
according to your needs.
Following, for a well designed and documented DRP, in SQL 2000, consider
having a new machine, with SQL 2000 and try to enable log shipping
http://support.microsoft.com/default...b;en-us;323135
Finally, you can check this article for common FAQs on log shipping
http://support.microsoft.com/default...b;en-us;314515
HTH
Andreas
"Richard Ding" wrote:

> If a brand new box is to replace the fail server, prepare the disk drive
> mappings, processor, RAM, etc.
> Other things include SQL server configuration, startup parameters, memory
> configuration, scripted replications, and more.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:584D6A0B-A59B-4B0E-90FC-F601950641B8@.microsoft.com...
>
>

订阅：博文 (Atom)

2012年3月22日星期四

Disester Recovery

Disester Recovery

Disester Recovery

2012年3月20日星期二

Disconnected Mirror / In Recovery

2012年3月19日星期一

Disater Recovery Solution using SQL

2012年3月11日星期日

Disaster/recovery techniques

Disaster Recovery: SQL Server 2000 on Win 2000 Server.

Disaster Recovery: SQL Server 2000 on Win 2000 Server.

Disaster Recovery With SQL 8.0

Disaster Recovery With SQL 8.0

Disaster recovery through log file alone?

Disaster Recovery Tests

Disaster Recovery Site Setup

Disaster Recovery Site Setup

Disaster Recovery Scenarios for Analysis Services

Disaster Recovery rehearsal

Disaster Recovery rehearsal

Disaster Recovery question

Disaster Recovery Question

Disaster Recovery question

Display date

Blog Archive

About Me