No - The problem is that I will need to take the original server down before
I start up the new server with the same name. I did do a publish to the new
server with a different name, but all the links were recalculated with the
new server name - plus that is where I had the most difficulties with the
permissions.
Once I changed the name to the old name - it did do a recalculation and
restored all the old links to the old name - but my original problem with the
permissions were still there.
The only way I could access the webs with FrontPage was on the server
itself. I could not from my workstation. (I have full domain admin priv).
The only way that I could access from my workstation was to give "everyone"
full permissions to the webs.
I am thinking about restoring from a backup - then removing the FP
extensions - then reapplying them - then re-applying permissions.
Is there a prolem wit this type of plan?
Thanks,
Tom C
"MD Websunlimited" wrote:
> Hi Tom,
>
> If the new server is also FP extended then why not just publish from one to the other?
>
>
> --
> Mike -- FrontPage MVP '97-'02
> J-Bots 2004 102 Components For FP
> http://www.websunlimited.com
> FrontPage Add-ins Since '97 FP 2003 / 2002 / 2000 Compatible
>
> "Tom Conklin" <(E-Mail Removed)> wrote in message news:6B1FA184-3692-46E2-A202-(E-Mail Removed)...
> >I have many FrontPage 2000 webs on a single server (Main site - then many
> > subwebs).
> > I need to move the webs on to a new server. In all - there are about 200,000
> > documents.
> > I have been backing up this server (wwwroot and all subfolders) with NT
> > backup.
> >
> > Is it possible to restore from a backup to the new server?
> > The new server will have the same name as the old one - the old one will be
> > taken off-line - I will rename the new server with the old server name.
> >
> >
> > Or - is there a better way to do this? I can't seem to find good disaster
> > recovery docs on FrontPage webs -While it is not the case - what if my server
> > died?
> >
> > I have tried to set the webs up on a new server with a different name.
> > I did the publish function, but ran into permissions problems. (I was going
> > to just use the host header for client requests to the web server - this is
> > for a Intranet).
> > Additionally and unfortunately - Some of the hyperlinks point to file paths
> > - that is why I am now going to just rename the new server to the old server
> > name.
> >
> > Thanks,
> > Tom C
> >
> >
> >
> >
> >
>
>
>