SOLVED

Copy SharePoint 2013 Prod environment to Dev.

%3CLINGO-SUB%20id%3D%22lingo-sub-1195184%22%20slang%3D%22en-US%22%3ECopy%20SharePoint%202013%20Prod%20environment%20to%20Dev.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1195184%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Friends%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20no%20Dev%20environment%20in%20our%20Org%2C%20only%20Production%20SharePoint%202013%20Farm%20is%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20I%20need%20to%20prepare%20the%20Development%20SharePoint%20Farm%20(Single%20server%20farm)%20from%20scratch%20and%20then%20need%20to%20keep%20the%20same%20as%20Prod%20is.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20could%20you%20please%20guide%3A%3C%2FP%3E%3CP%3E*%20What%20else%20I%20need%20to%20copy%20from%20Prod%20like%20Site%20Collection%20content%20Database%3F%3C%2FP%3E%3CP%3E*%20Should%20I%20also%20copy%20the%20services%20database%20like%20search%2C%20my%20profile%2C%20etc..%20or%20anything%20else%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20guide%20the%20best%20practise%20and%20time-saving%20steps...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1195184%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1195281%22%20slang%3D%22en-US%22%3ERe%3A%20Copy%20SharePoint%202013%20Prod%20environment%20to%20Dev.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1195281%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F133114%22%20target%3D%22_blank%22%3E%40Anand%20Prakash%20Singh%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wouldn't%20recommend%20copying%20PROD%20to%20Dev.%20For%20data%20security%20this%20is%20not%20a%20good%20idea.%20It%20would%20also%20be%20difficult%20to%20do(I%20have%20heard%20some%20talk%20of%20the%20odd%20company%20doing%20this)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20recommendation%20would%20be%20to%20get%20any%20custom%20solutions%20built%20in%20Dev%2C%20tested%20on%20a%20Test%20environment%20and%20then%20deployed%20to%20PROD.%20Test%20should%20match%20PROD%20as%20mush%20as%20possible%20whereas%20Dev%20will%20get%20messy%20if%20you%20are%20doing%20Dev%20on%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198162%22%20slang%3D%22en-US%22%3ERe%3A%20Copy%20SharePoint%202013%20Prod%20environment%20to%20Dev.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198162%22%20slang%3D%22en-US%22%3EHello%20Andrew%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20very%20much%20for%20the%20guidance%2C%20that%20make%20sense.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20if%20i%20prepare%20test%20farm%20like%20Prod%2C%20so%20could%20you%20please%20guide%20%2C%20when%20need%20to%20copy%20from%20Prod%20servers.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198202%22%20slang%3D%22en-US%22%3ERe%3A%20Copy%20SharePoint%202013%20Prod%20environment%20to%20Dev.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198202%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F133114%22%20target%3D%22_blank%22%3E%40Anand%20Prakash%20Singh%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20applies%2C%20I%20wouldn't%20recommend%20copying%20PROD%20to%20TEST.%20I%20would%20recommend%20installing%20any%20custom%20solutions%20on%20Test%2C%20testing%20them%20and%20then%20deploying%20to%20PROD.%20That%20gives%20you%20a%20route%20to%20PROD%20for%20custom%20code%20and%20satisfies%20a%20basic%20Software%20Life%20Cycle%20management.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBy%20all%20means%20have%20some%20test%20content%20on%20Test%20but%20copying%20the%20whole%20DB%20is%20rarely%20actually%20required%20and%20isn't%20a%20good%20idea%20as%20I%20mentioned%20for%20data%20security%20etc.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1199094%22%20slang%3D%22en-US%22%3ERe%3A%20Copy%20SharePoint%202013%20Prod%20environment%20to%20Dev.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1199094%22%20slang%3D%22en-US%22%3EOK%2C%20you%20mean%20to%20prepare%20the%20Dev%20or%20Test%20environment%20from%20scratch%20and%20configure%20the%20required%20services%20manually%20and%20use%20accordingly..%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20yes%2C%20It's%20best%20option%20to%20keep%20in%20mind%20the%20data%20security%20part.%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20very%20much%2C%20I%20hope%20this%20will%20help%20others%20also%20to%20follow%20this%20as%20a%20best%20practice.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello Friends,

 

Currently no Dev environment in our Org, only Production SharePoint 2013 Farm is there.

 

Now, I need to prepare the Development SharePoint Farm (Single server farm) from scratch and then need to keep the same as Prod is.

 

So could you please guide:

* What else I need to copy from Prod like Site Collection content Database?

* Should I also copy the services database like search, my profile, etc.. or anything else?

 

Please guide the best practise and time-saving steps...

4 Replies
Highlighted

@Anand Prakash Singh 

 

I wouldn't recommend copying PROD to Dev. For data security this is not a good idea. It would also be difficult to do(I have heard some talk of the odd company doing this)

 

My recommendation would be to get any custom solutions built in Dev, tested on a Test environment and then deployed to PROD. Test should match PROD as mush as possible whereas Dev will get messy if you are doing Dev on it. 

Highlighted
Hello Andrew,

Thank you very much for the guidance, that make sense.

So if i prepare test farm like Prod, so could you please guide , when need to copy from Prod servers.
Highlighted
Best Response confirmed by Anand Prakash Singh (Occasional Contributor)
Solution

@Anand Prakash Singh

 

Same applies, I wouldn't recommend copying PROD to TEST. I would recommend installing any custom solutions on Test, testing them and then deploying to PROD. That gives you a route to PROD for custom code and satisfies a basic Software Life Cycle management.

 

By all means have some test content on Test but copying the whole DB is rarely actually required and isn't a good idea as I mentioned for data security etc.  

Highlighted
OK, you mean to prepare the Dev or Test environment from scratch and configure the required services manually and use accordingly..

I think yes, It's best option to keep in mind the data security part.

Thank you very much, I hope this will help others also to follow this as a best practice.