Re: Restore problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: STH (STH_at_discussions.microsoft.com)
Date: 01/26/05 

Date: Wed, 26 Jan 2005 07:43:03 -0800

Thanks for the suggestions Bill. here are the ones I can answer

1) They are not. The production config contains a farm and the dev does
not. I was hoping this wouldn't be a problem....

2) I am not trying to restore the configDB. Only what backed up with
SPSbackup (which I believe doesn't backup the config)

3) I don't understand this one. Could you explain what you mean?

4) If I understand you correctly, you can only restore back to the same URL
that you backed up? If that's the case then the answer is no they are not
the same. I'm trying to make a backup of our development portal and restore
it to our production server and both servers have different URLs. This isn't
possible?

5) The DB names are the same as the original. Isn't that normal since it's
a backup of the original?

Thanks again for your help. As you can tell, I'm new to the Portal world.

"Bill English [MVP]" wrote:

> Ummm.....I've seen this once and am trying to remember what it was. Check
> the following:
>
> 1. Your dev and production farm configurations are the same
> 2. You're not trying to restore the configdb
> 3. You're restoring to restored copies of your virtual servers
> 4. The URL you're restoring to is the same
> 5. That you're not using the same DB name in the restore process as the
> original DB name or the backup file DB name
>
> Lemme know how it goes. I'm curious as to what is causing this.
>
> --
>
> Bill English
> www.mindsharp.com
> www.mindsharpblogs.com
> sharepointdiscussions@yahoogroups.com
>
>
> "STH" <STH@discussions.microsoft.com> wrote in message
> news:789FC595-CF6B-43F9-90ED-5EB585A6F04F@microsoft.com...
> > I'm trying to migrate our completed development portal to our completely
> > empty production portal. I did a backup using spsbackup on the dev portal
> > but when I try to do the restore on the production server it won't let me
> > check the SITEDBS restore option because the status says the following:
> >
> > Portal site existed at backup time but no longer exists
> >
> > I've even repeated the backup on the dev server to ensure everything went
> > correctly but the error still persists.
> >
> > Any help is appreciated.
>
>
>

Relevant Pages

  • Re: Disaster recover
    ... full backup every night. ... workgroup, restore the system state, reboot, installexchangewith the ... and push button recovery of Exchange. ... downtime in your production environment. ...
    (microsoft.public.exchange.admin)
  • Re: taking db offline for batch processing
    ... Maybe I need to be sure everyone's disconnected, make a backup, detatch so nobody can make changes and then restore my backup to a test db. ... I'm trying to find out what exactly taking the db offline does. ... Restore the production backup to teh test db ...
    (microsoft.public.sqlserver.programming)
  • Disaster Recovery
    ... I've been trying to restore a backup for the last coulpe of days without ... Am i right in assuming that in this situation, i cannot restore the config ... a single top level site, with multiple departmental sites created below it. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Restore failed: database schema too old
    ... Production Serverand Test ServerConfiguration: ... Windows Server 2003 with SP1 ... Backup is taken every day and we try to restore the same every day ...
    (microsoft.public.sharepoint.portalserver)
  • RE: Portal Site Restore
    ... Create a new Virual server,map to C:\MyTest. ... Use spsbackup.exe to restore portal. ... and then copy the above 2 files from production to my machine. ... 3.successfull backup and restore using tools should do that job. ...
    (microsoft.public.sharepoint.portalserver)