Ø Having now tried several tests through UI (and received only errors) and
STSADM (and seen the hell that breaks loose afterwards) Ive gone down
Uzmas path of only backing up individual sites and restoring to dev as
required for testing and development. Hardly ideal
What Errors? Did you deploy the existing features to the new environment,
ensure all DLLs are in the right spot/place, etc?
Ø With publishing sites (and quite possibly WSS w/ publishing enabled) this
still requires running custom STSADM commands and other fixes to correct
page layout paths (break page settings), CQWP queries, hundreds of
hard-coded links within web part fields or pages (because MOSS wouldnt
allow a relative URL!) and more. And lets not forget about the lack of
support for tasks and workflows.
Sounds more like a issue of someone has instead of using relative paths,
used hard paths, Hardly a fault of MOSS. Could you give an example of where
MOSS has a hardcoded URL? As I know that this is something they wish to
address in upcoming versions.
Ø I cannot get over the sheer amount of hard paths and absolute URLs that
MOSS uses. That simple environment variables or tokens for {siteroot},
{site}, {_layout} etc., are not used simply amazes me.
~Site, ~SiteCollction, /_layouts (accessible from any path or folder in the
URL, i.e. ~Site/_layouts/page.aspx)
Ø Its insulting enough to pay this much for a product and then be left
with a command line tool for all these operations, but to the have this many
problems with something as simple as a backup and restore operation...
Backup & Restore is not as simple as just export and import, it relies on
DLLs, features and solution dependencies. If a dependency is invalid or
missing, it will not restore (imo it makes sense).
Ø Why would it have be so hard to create a web-based GUI for theses (and
other) essential daily tasks that allowed a bit more control over the
various parameters and managed syntax while also providing a Test mode for
the less brazen?
Central Admin under Backup/Restore? Or Item level backup/restore level with
DPM? Or even batch script with use of STSADM to run on a schedule.
STSADM could of been made to support item level backup/.restore, but the
amount of effort/overhead involved in this via a CLI is pretty large, Should
the UI have supported it? Yes It should have.
Happy to Help,
DB
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Paul Noone
Sent: Wednesday, 19 November 2008 9:41 AM
To: [email protected]
Subject: RE: [OzMOSS] RE: create SharePoint development same as production
site
Having now tried several tests through UI (and received only errors) and
STSADM (and seen the hell that breaks loose afterwards) Ive gone down
Uzmas path of only backing up individual sites and restoring to dev as
required for testing and development. Hardly ideal.
With publishing sites (and quite possibly WSS w/ publishing enabled) this
still requires running custom STSADM commands and other fixes to correct
page layout paths (break page settings), CQWP queries, hundreds of
hard-coded links within web part fields or pages (because MOSS wouldnt
allow a relative URL!) and more. And lets not forget about the lack of
support for tasks and workflows.
I cannot get over the sheer amount of hard paths and absolute URLs that MOSS
uses. That simple environment variables or tokens for {siteroot}, {site},
{_layout} etc., are not used simply amazes me.
Its insulting enough to pay this much for a product and then be left with a
command line tool for all these operations, but to the have this many
problems with something as simple as a backup and restore operation...
Why would it have be so hard to create a web-based GUI for theses (and
other) essential daily tasks that allowed a bit more control over the
various parameters and managed syntax while also providing a Test mode for
the less brazen?
Thank God for the generous and talented souls out there who have filled this
black hole of omissions with their own tools and scripts.
[Sorry, Ishai, if I beat you to todays rant. ;)]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Nemtsev
Sent: Wednesday, 19 November 2008 8:06 AM
To: [email protected]
Subject: RE: [OzMOSS] RE: create SharePoint development same as production
site
You will find those errors during backup/restore. So, it will be clear if
OOTB backup works or not.
I would not recommend using STSADM o export/import till you have no
problems with UI tools
There are no issues with export/import command, but its very error-proned
approach, and you should know how to do it correctly.
Michael Nemtsev | WSS MCTS, MS MVP
Readify
B: <http://msmvps.com/blogs/laflour/> http://msmvps.com/blogs/laflour/ T:
+61 424 184 978 E: <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ajay
Sent: Wednesday, November 19, 2008 5:45 AM
To: [email protected]
Subject: Re: [OzMOSS] RE: create SharePoint development same as production
site
My worry is that will deploying with backup/restore make it unsupported as
Stefan post says.
I will be finishing with the client soon, don't want him to get problems
with MS Support later in case anything happens
On Tue, Nov 18, 2008 at 11:14 PM, Michael Nemtsev
<[EMAIL PROTECTED]> wrote:
I never had issues which Stefan described.
I believe it will be fixed with the SP2
Michael Nemtsev | WSS MCTS, MS MVP
Readify
B: <http://msmvps.com/blogs/laflour/> http://msmvps.com/blogs/laflour/ T:
+61 424 184 978 E: <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ajay
Sent: Tuesday, November 18, 2008 8:53 PM
To: [email protected]
Subject: Re: [OzMOSS] RE: create SharePoint development same as production
site
I have been using backup/restore for deployment between different
environments and then I found this....
Be aware that backup/restore of MOSS content databases between server farms
are not fully supported! Official documentation of this support limitation
is currently in the works. The supported way to transfer content between
server farms is to use STSADM -o export/import or content deployment.
Backup/restore is only supported for the same server farm
http://blogs.technet.com/stefan_gossner/archive/2008/03/12/common-error-situ
ation-with-when-using-backup-restore-to-transfer-a-database-to-a-new-farm-on
-moss-2007.aspx
Though I haven't had the error in the above post so far and have deployed
about 15 web applications so far...
On Tue, Nov 18, 2008 at 9:09 PM, Michael Nemtsev
<[EMAIL PROTECTED]> wrote:
There is no issues if you restore you farm backup to single SharePoint
instance. It will work fine. It's common scenario when you design you
Disaster Recovery (DR) box, and you don't need farm there only single
instance. So you restore your backup there and set up SQL mirroring.
There is no OOTB way to backup content selectively and omit some files.
What you can try to do is to copy your content into new content DB and
remove content of doc libraries there
Michael Nemtsev | WSS MCTS, MS MVP
Readify
B: <http://msmvps.com/blogs/laflour/> http://msmvps.com/blogs/laflour/ T:
+61 424 184 978 E: <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Paul Noone
Sent: Tuesday, November 18, 2008 10:40 AM
To: [email protected]
Subject: [OzMOSS] RE: create SharePoint development same as production site
Hi Michael,
Sorry to pick up an old thread but I'm just getting ready to backup/restore
our production environment to development in order to have a current version
to work with.
Is the GUI-based Farm backup in Central Administration smart enough to
recognise different farm topology, configurations, paths, domains, ports
etc., and update them? Having not gone down this road before I'm finding the
unknown more than a little frightening.
Also, does anyone know of a method to selectively backup content i.e.
_without_ the content in document libraries?
Regards,
Paul
Online Developer, ICT
CEO Sydney
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Nemtsev
Sent: Saturday, 11 October 2008 11:04 AM
To: [email protected]
Subject: [OzMOSS] RE: create SharePoint development same as production site
What's the reason for this, why u need to copy the whole environment?
Because usually you are doing it vice versa, from development to production
Just make a whole farm backup on production box and restore on your box via
OOTB backup/restore
Michael Nemtsev | WSS MCTS, MS MVP
Readify
B: <http://msmvps.com/blogs/laflour/> http://msmvps.com/blogs/laflour/ T:
+61 424 184 978 E: <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ken Zheng
Sent: Friday, October 10, 2008 3:26 PM
To: [email protected]
Subject: [OzMOSS] create SharePoint development same as production site
Hi All:
Just want to find out what you guys do to copy the production site to the
development machine, is backup/restore or import/export site or some other
better way.
Cheers
Ken
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com <http://mailenable.com/>
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com <http://mailenable.com/>
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com <http://mailenable.com/>
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com <http://mailenable.com/>
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com
-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject.
Powered by mailenable.com
------------------------------------------------------------------- OzMOSS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered by mailenable.com
