Re: Moving SMS Primary to new hardware



Hi Mike, Great questions, I'll cover them in-line.

ST
"Mike Soloway" <MikeSoloway@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:45D6BF88-EDCC-4D53-BDEE-AA042467DE86@xxxxxxxxxxxxxxxx
Currently getting ready to move my SMS Primary Site to new hardware and I
a
couple questions
Regarding the SMS site recovery process. First my SMS hierarchy consists
of
a SMS Primary site with a number of SMS Secondary sites.

1. From reading the documentation, my understanding is that I need to
isolate my Secondary sites from the Primary during the recovery process.
The
best way to do this is to shutdown the SMS Executive and SMS Component
Manager services on the Secondary site Is this the best course of action
or
is there an Alternative?

Yes, stop ALL SMS services on the secondary sites while performing your
migration.

2. As an extension of the first question, I have a number of workstations
that report to Primary site (for various reasons) rather than to a SMS
Secondary site. Is it necessary for me to be concerned about isolating
them
from the Primary SMS site during the recovery process?

No -- they'll try to talk to their sites management point, and will not hear
back. It's really not a problem.

My thought was that
turning off the client agents (Hardware Inventory, Software Inventory,
etc)
would reduce any communication by the clients. Does this seem the correct
course of action?

Don't worry about it... leave them alone :)

3. Final question, if I tell the SMS site backup to back up the SMS
database
as part of its process, does it back up the other SQL databases as well,
like
the Master database? Or do they need to be backed up separately? Do the
logins for SQL Server get backed up as well?

The SMS backup task only backs up the sms db, which is the only database you
need for this operation.

Depending on whether you are running Standard or Advanced security mode the
site recovery wizard will provide the appropriate instructions.

Thanks for any information or direction that you can provide on these
questions.

Follow the SMS site recovery wizard instructions EXACTLY and you should be
fine.


.



Relevant Pages

  • Re: Primary vs Secondary
    ... I personally would tend to go with a primary site unless I have a good ... Check out the SMS Technical FAQ: ... Aside from the sql and server license. ... Advanced Clients cannot be assigned to Secondary Sites. ...
    (microsoft.public.sms.admin)
  • Re: Secondary Sites
    ... I don't have to create secondary sites? ... Can the advanced client talk to the existing primary site server if ... your SMS sites tend to correlate with your Active ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... We are belatedly upgrading from SMS 2.0 to SMS 2003. ... the Primary Site Server hardware as it is old and under spec. ... secondary sites as some of them are throwing errors under SMS 2.0. ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ...
    (microsoft.public.sms.admin)
  • Re: Confused About Proxy Management Points
    ... Can I expect to see any issues as primary site is running server 2003 ... with sms 2003 and secondary sites will be running windows 2000 server ... DRW was ran on the primary site with no warnings just errors (after the ...
    (microsoft.public.sms.admin)
  • Re: new sms installation
    ... other clients over WAN ... I am brand new to SMS and still trying to grasp it. ... Secondary sites do not require a database, ... hosted on the same sql server.. ...
    (microsoft.public.sms.setup)