I lost a whole server (was windows 2000 sp4 with sql server 2000 sp3).
Restored from backup on new server hardware (new idently as far as domain
goes also, did not bring back old server's identity).
Luckily I had a full backup from just the day before. I setup new server
(w2k3 r2 sp2) and installed sql server 2000 sp3. I was using simple recovery
model with just 1 full backup every day (fine for our needs) and so it was a
simple full restore from backup device (file). Completed, no problems. All
user data appears to be there and custom client application seems to be
working fine so far with it today (after updating ODBC config to reflect new
server and refreshing the linked tables in the Access front end mdb file)
1) so from here I'm not sure if I should restore my backups of the system
databases (master, msdb)? In my situation, the front end app just uses one
sql user account (via odbc connection), so recreating and assigning the one
user permissions was no problem (thats what I did). I didn't have any custom
system or user error messages, and wasn't using any linked servers. Users
are already using the system for 1/2 day now without any issues. Also, as
far as msdb, I don't mind creating new backup devices and a new maintenance
plan for this restored database. My backups of these system databases are
about 1 year old. I'm afraid I may cause a problem by restoring these... '
any input on this would be GREATLY appreciated. Just leave it be? is there
something I am overlooking on the need to restore these system databases in
*my* scenario?
2) REPLICATION: also, along the same lines, I'm not sure if I should restore
my distribution database for the merge replication that was on the old
server, or just recreate instead? Again, this backup is about 1 year old.
I'm wondering if it would be simpler/better for me to just recreate from
scratch? In fact it just occurred to me that I need to change to
transactional replication anyway (if I got the term right, its been a while
since I setup replication) because the requirement changed from 2 way
synching to just 1-way recently anyway. I have all the most recent user data
on my end to setup new. Will I have issues with this due to traces of the
old replication in my database? do I need to clean up first? or just create
new?
all in all, as far as I can tell to this point, we have lost zero user data,
which is all my DR plan really set out to do. I planned on having a day of
downtime to rebuild a server if this happened, and as luck would have it, it
happened on a sunday so the company experienced no down time. So what I'm
hoping is that what I've done is fine, and that I don't need to restore the
system databases or distribustion databases, and that instead, I just need
to re-do some configs. yes/no?
sorry so long.David,
You system setup seems very simple. Is this is infact true, by creating the
user account manually and recreating backup/maintenance jobs, you no longer
need to worry about restoring master or MSDB. For future reference, I would
include these DBs in my backup plan though.
"David" <nospam@.nospam.com> wrote in message
news:%23vaaqqNFIHA.1324@.TK2MSFTNGP06.phx.gbl...
>I lost a whole server (was windows 2000 sp4 with sql server 2000 sp3).
>Restored from backup on new server hardware (new idently as far as domain
>goes also, did not bring back old server's identity).
> Luckily I had a full backup from just the day before. I setup new server
> (w2k3 r2 sp2) and installed sql server 2000 sp3. I was using simple
> recovery model with just 1 full backup every day (fine for our needs) and
> so it was a simple full restore from backup device (file). Completed, no
> problems. All user data appears to be there and custom client application
> seems to be working fine so far with it today (after updating ODBC config
> to reflect new server and refreshing the linked tables in the Access front
> end mdb file)
> 1) so from here I'm not sure if I should restore my backups of the system
> databases (master, msdb)? In my situation, the front end app just uses one
> sql user account (via odbc connection), so recreating and assigning the
> one user permissions was no problem (thats what I did). I didn't have any
> custom system or user error messages, and wasn't using any linked servers.
> Users are already using the system for 1/2 day now without any issues.
> Also, as far as msdb, I don't mind creating new backup devices and a new
> maintenance plan for this restored database. My backups of these system
> databases are about 1 year old. I'm afraid I may cause a problem by
> restoring these... ' any input on this would be GREATLY appreciated. Just
> leave it be? is there something I am overlooking on the need to restore
> these system databases in *my* scenario?
>
> 2) REPLICATION: also, along the same lines, I'm not sure if I should
> restore my distribution database for the merge replication that was on the
> old server, or just recreate instead? Again, this backup is about 1 year
> old. I'm wondering if it would be simpler/better for me to just recreate
> from scratch? In fact it just occurred to me that I need to change to
> transactional replication anyway (if I got the term right, its been a
> while since I setup replication) because the requirement changed from 2
> way synching to just 1-way recently anyway. I have all the most recent
> user data on my end to setup new. Will I have issues with this due to
> traces of the old replication in my database? do I need to clean up first?
> or just create new?
> all in all, as far as I can tell to this point, we have lost zero user
> data, which is all my DR plan really set out to do. I planned on having a
> day of downtime to rebuild a server if this happened, and as luck would
> have it, it happened on a sunday so the company experienced no down time.
> So what I'm hoping is that what I've done is fine, and that I don't need
> to restore the system databases or distribustion databases, and that
> instead, I just need to re-do some configs. yes/no?
> sorry so long.
>|||I agree with Dragon: you seem to be fine.
You might want to study the system tables in the system databases on a 2000 install as well as Books
Online. They can give you some extra hints on what information are stored in system databases so you
can pick it up in case you forgot about it (like sp_configure setting as an example).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"David" <nospam@.nospam.com> wrote in message news:%23vaaqqNFIHA.1324@.TK2MSFTNGP06.phx.gbl...
>I lost a whole server (was windows 2000 sp4 with sql server 2000 sp3). Restored from backup on new
>server hardware (new idently as far as domain goes also, did not bring back old server's identity).
> Luckily I had a full backup from just the day before. I setup new server (w2k3 r2 sp2) and
> installed sql server 2000 sp3. I was using simple recovery model with just 1 full backup every day
> (fine for our needs) and so it was a simple full restore from backup device (file). Completed, no
> problems. All user data appears to be there and custom client application seems to be working fine
> so far with it today (after updating ODBC config to reflect new server and refreshing the linked
> tables in the Access front end mdb file)
> 1) so from here I'm not sure if I should restore my backups of the system databases (master,
> msdb)? In my situation, the front end app just uses one sql user account (via odbc connection), so
> recreating and assigning the one user permissions was no problem (thats what I did). I didn't have
> any custom system or user error messages, and wasn't using any linked servers. Users are already
> using the system for 1/2 day now without any issues. Also, as far as msdb, I don't mind creating
> new backup devices and a new maintenance plan for this restored database. My backups of these
> system databases are about 1 year old. I'm afraid I may cause a problem by restoring these... '
> any input on this would be GREATLY appreciated. Just leave it be? is there something I am
> overlooking on the need to restore these system databases in *my* scenario?
>
> 2) REPLICATION: also, along the same lines, I'm not sure if I should restore my distribution
> database for the merge replication that was on the old server, or just recreate instead? Again,
> this backup is about 1 year old. I'm wondering if it would be simpler/better for me to just
> recreate from scratch? In fact it just occurred to me that I need to change to transactional
> replication anyway (if I got the term right, its been a while since I setup replication) because
> the requirement changed from 2 way synching to just 1-way recently anyway. I have all the most
> recent user data on my end to setup new. Will I have issues with this due to traces of the old
> replication in my database? do I need to clean up first? or just create new?
> all in all, as far as I can tell to this point, we have lost zero user data, which is all my DR
> plan really set out to do. I planned on having a day of downtime to rebuild a server if this
> happened, and as luck would have it, it happened on a sunday so the company experienced no down
> time. So what I'm hoping is that what I've done is fine, and that I don't need to restore the
> system databases or distribustion databases, and that instead, I just need to re-do some configs.
> yes/no?
> sorry so long.
>|||thanks. I appreciate it.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:0231D4CD-9B7A-47B1-BF27-131FB29400C0@.microsoft.com...
>I agree with Dragon: you seem to be fine.
> You might want to study the system tables in the system databases on a
> 2000 install as well as Books Online. They can give you some extra hints
> on what information are stored in system databases so you can pick it up
> in case you forgot about it (like sp_configure setting as an example).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "David" <nospam@.nospam.com> wrote in message
> news:%23vaaqqNFIHA.1324@.TK2MSFTNGP06.phx.gbl...
>>I lost a whole server (was windows 2000 sp4 with sql server 2000 sp3).
>>Restored from backup on new server hardware (new idently as far as domain
>>goes also, did not bring back old server's identity).
>> Luckily I had a full backup from just the day before. I setup new server
>> (w2k3 r2 sp2) and installed sql server 2000 sp3. I was using simple
>> recovery model with just 1 full backup every day (fine for our needs) and
>> so it was a simple full restore from backup device (file). Completed, no
>> problems. All user data appears to be there and custom client application
>> seems to be working fine so far with it today (after updating ODBC config
>> to reflect new server and refreshing the linked tables in the Access
>> front end mdb file)
>> 1) so from here I'm not sure if I should restore my backups of the system
>> databases (master, msdb)? In my situation, the front end app just uses
>> one sql user account (via odbc connection), so recreating and assigning
>> the one user permissions was no problem (thats what I did). I didn't have
>> any custom system or user error messages, and wasn't using any linked
>> servers. Users are already using the system for 1/2 day now without any
>> issues. Also, as far as msdb, I don't mind creating new backup devices
>> and a new maintenance plan for this restored database. My backups of
>> these system databases are about 1 year old. I'm afraid I may cause a
>> problem by restoring these... ' any input on this would be GREATLY
>> appreciated. Just leave it be? is there something I am overlooking on the
>> need to restore these system databases in *my* scenario?
>>
>> 2) REPLICATION: also, along the same lines, I'm not sure if I should
>> restore my distribution database for the merge replication that was on
>> the old server, or just recreate instead? Again, this backup is about 1
>> year old. I'm wondering if it would be simpler/better for me to just
>> recreate from scratch? In fact it just occurred to me that I need to
>> change to transactional replication anyway (if I got the term right, its
>> been a while since I setup replication) because the requirement changed
>> from 2 way synching to just 1-way recently anyway. I have all the most
>> recent user data on my end to setup new. Will I have issues with this due
>> to traces of the old replication in my database? do I need to clean up
>> first? or just create new?
>> all in all, as far as I can tell to this point, we have lost zero user
>> data, which is all my DR plan really set out to do. I planned on having a
>> day of downtime to rebuild a server if this happened, and as luck would
>> have it, it happened on a sunday so the company experienced no down time.
>> So what I'm hoping is that what I've done is fine, and that I don't need
>> to restore the system databases or distribustion databases, and that
>> instead, I just need to re-do some configs. yes/no?
>> sorry so long.
>|||thanks. I appreciate it.
"Dragon" <noSpam_baadil@.hotmail.com> wrote in message
news:On$CWTOFIHA.4880@.TK2MSFTNGP03.phx.gbl...
> David,
> You system setup seems very simple. Is this is infact true, by creating
> the user account manually and recreating backup/maintenance jobs, you no
> longer need to worry about restoring master or MSDB. For future reference,
> I would include these DBs in my backup plan though.
>
> "David" <nospam@.nospam.com> wrote in message
> news:%23vaaqqNFIHA.1324@.TK2MSFTNGP06.phx.gbl...
>>I lost a whole server (was windows 2000 sp4 with sql server 2000 sp3).
>>Restored from backup on new server hardware (new idently as far as domain
>>goes also, did not bring back old server's identity).
>> Luckily I had a full backup from just the day before. I setup new server
>> (w2k3 r2 sp2) and installed sql server 2000 sp3. I was using simple
>> recovery model with just 1 full backup every day (fine for our needs) and
>> so it was a simple full restore from backup device (file). Completed, no
>> problems. All user data appears to be there and custom client application
>> seems to be working fine so far with it today (after updating ODBC config
>> to reflect new server and refreshing the linked tables in the Access
>> front end mdb file)
>> 1) so from here I'm not sure if I should restore my backups of the system
>> databases (master, msdb)? In my situation, the front end app just uses
>> one sql user account (via odbc connection), so recreating and assigning
>> the one user permissions was no problem (thats what I did). I didn't have
>> any custom system or user error messages, and wasn't using any linked
>> servers. Users are already using the system for 1/2 day now without any
>> issues. Also, as far as msdb, I don't mind creating new backup devices
>> and a new maintenance plan for this restored database. My backups of
>> these system databases are about 1 year old. I'm afraid I may cause a
>> problem by restoring these... ' any input on this would be GREATLY
>> appreciated. Just leave it be? is there something I am overlooking on the
>> need to restore these system databases in *my* scenario?
>>
>> 2) REPLICATION: also, along the same lines, I'm not sure if I should
>> restore my distribution database for the merge replication that was on
>> the old server, or just recreate instead? Again, this backup is about 1
>> year old. I'm wondering if it would be simpler/better for me to just
>> recreate from scratch? In fact it just occurred to me that I need to
>> change to transactional replication anyway (if I got the term right, its
>> been a while since I setup replication) because the requirement changed
>> from 2 way synching to just 1-way recently anyway. I have all the most
>> recent user data on my end to setup new. Will I have issues with this due
>> to traces of the old replication in my database? do I need to clean up
>> first? or just create new?
>> all in all, as far as I can tell to this point, we have lost zero user
>> data, which is all my DR plan really set out to do. I planned on having a
>> day of downtime to rebuild a server if this happened, and as luck would
>> have it, it happened on a sunday so the company experienced no down time.
>> So what I'm hoping is that what I've done is fine, and that I don't need
>> to restore the system databases or distribustion databases, and that
>> instead, I just need to re-do some configs. yes/no?
>> sorry so long.
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment