This section will describe what you need to know in order to protect the SharePoint environment. There is one golden rule when it comes to SharePoint backups – make sure you can restore backups in the timeframe required by the business.
(more…)
Business Continuity is a management process that provides a framework to ensure the resilience of your business to any eventuality, to help ensure continuity of service to your key customers and the protection of your brand and reputation. In defining a SharePoint BCM it provides a basis for planning to ensure your long-term survivability following a disruptive event.
(more…)
If you are planning to install Sharepoint 2010 on Windows 7, here is an excellent article in MSDN, just follow the steps and you will end up successfully installing SharePoint 2010 beta on windows 7.
http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx
TIP: even if you follow the steps, and run the SharePoint Configuration wizard, the wizard might fail.
All you have to do is just to re-run it – it will install. I’ve noticed this seems to take place when you run into low memory issues, and the exception is stating failed provisioning on central administration.
Had a problem today where a content db migrated from a supposedly clean Sharepoint 2007 environment didn’t show up some document libraries or lists when visiting the site.
This left me really puzzled because they were visible in 2007, not 2010!! So, ok, decided to go to the rather cool ‘Review problems and solutions’ first to find out what was going on!
http://CentralAdministration:PORT/Lists/HealthReports Found this: Content databases contain orphaned items. Severity: 1 – Error Category: Availability
Explanation: In some situations, a content database that is used by Microsoft SharePoint Foundation may become corrupted. The corrupted database may contain orphaned items. For example, a document may not have a parent document library or a list may not have a parent Microsoft SharePoint Foundation Web site. Consequently, you may be unable to create new items with the same URL as the orphaned items, and space in the content database will be consumed unnecessarily.
Aha! So I ran the Rule Settings at the bottom, then clicking on RUN now. Accessed the site again, no problems! Wow… Thought I’d look into this one a bit more. Interesting – try going here on the Central Admin: http://CentralAdministration:PORT/Lists/HealthRules/AllItems.aspx Seems I can now do some really ace things in Monitoring; like scheduling when jobs are to occur, enable and disable, and also force a repair! Going to come back soon and blog this more when I get more details!
One thing that you will find installing the Sharepoint 2010 BETA Installation is that things have changed concerning Standalone versus Complete installation.
Standalone build is usually the one to go for when you want a single server developer type environment and also all the SQL permissioning is done for you.
However, Complete installation allows you to finely tune the accounts used in SQL, and I always find that the best route to go personally.
Got a bit of a shock though when at the Specify Configuration Database Settings and filing in the Database Server, Name, Username and Password the following when clicking NEXT:
The specified user MyServerName\MyLocalAccount is a local account. Local accounts should only be used in stand alone mode.
Oh dear, so how to get around that? Time to use another new feature in 2010 – Sharepoint 2010 Management Shell which uses – wow Powershell!! This is availble in the shortcuts for Sharepoint 2010 on Start Programs etc.
Ok, so when running this up, enter the commands as follows:
New-SPConfigurationDatabase
This then brings up the cmdlet for that command. You will need to enter the values for the DatabaseName, Server, Farm Credentials and a Passphrase.
Once these have been entered, please be patient as the config db is created – can take up to 5 minutes!
Once done, all you need to do is rerun the Products Configuration Wizard – you’ll notice straight away that you can join the existing farm based on the the values you entered.
One note. For New-SPConfigurationDatabase to work SQL must be running Service Pack 2 or 3 – also, take a look at this link for more information:
Hope this helps!
