Backing up your Content Databases is one of the most critical activities that can be undertaken in order to preserve your data/have a strong Disaster Recovery Plan for SharePoint 2010. In this post we will focus on a simple Maintenance Plan with one “gotcha” I came across. SharePoint 2010 and SQL 2008 R2 offer a host of backup/restore …
Folders provide a single faceted, single point of failure that has limited users and caused inefficiency and risk across Enterprises for years. This is largely due to the nature of a folder. It provides a single source of storage with security options, but once you start nesting folders it creates a single path that may be forgotten or corrupted by improper naming or governance failings. Many organizations complain that their file shares are out of control, and while they may have begun with the best of intentions, the intended use was either not clearly identified or sustained and the end result looks something like the following. How will an organization know where their “real” content is located?
READ FULL POST at blogs.captechconsulting.com
When planning the capacity for your SharePoint 2010 Farm, don’t forget about the size of your Search databases. SharePoint 2010 Search leverages three distinct databases, with very separate roles as follows: Search Administration Database Crawl Database Property Database Per TechNet, the recommendations are as follows: Size estimation recommendation Search requires three databases. Your environment may include multiple Property …
Microsoft has updated their capacity limits with the Service Pack 1 release for SharePoint 2010. Full details of the new limits can be found here: http://technet.microsoft.com/en-us/library/cc262787.aspx This is an update to my previous post found here: https://thebitsthatbyte.com/know-your-limits-capacity-planning-in-sharepoint-2010/ A few key considerations to keep in mind in relation to content database sizing, per TechNet, are as follows: …
Windows 8 is now available as a Developer Preview for those who want to get their hands on this new platform and start developing apps. Bear in mind that this is not a stable version and functionality presented is not necessarily the end release functionality. I highly recommend loading this into a Virtual Machine, unless …
Folders and departmentalization are the enemy of collaboration.
There I said it, straightforward and to the point… and while this is no great
epiphany, it brings to the forefront the constant crusade of Enterprise Content
Management (notice I said Enterprise, not electronic)… What exactly is the point
of sharing?
So many organizations claim they want to “collaborate”, “centralize”, and
make things “easier” but when it comes down to actually putting things in place,
they balk like a little leaguer pitching to a steroid pumped up hitter. WHY?
FEAR… fear of the work it will take, fear of failure, and fear of confronting
organizational inefficiencies/entrenched co-workers and leadership.
So how do you confront these fears and conquer them? Here are a few tips:
Fear #1: ECM takes work and will change the way we think
READ FULL POST at blog.concurrency.com
The update that lifts the Document Set Routing Limit of 50 MB has been posted
as a hotfix. With this fix in place, Document Sets over 50 MB can now be routed
to their destination. Previous to this, users would receive an error such as
follows:
“The <Records Center Display Name> site refused the
submission. You cannot send files larger than 50 MB. To submit this file, you
must upload it directly to the drop off library at the target.”
READ FULL POST at blog.concurrency.com
While a primary focus of Records Management is to determine and maintain records per their retention period, there is always the end state… the day of disposition. When considering Electronic Records Management (ERM), records should be treated the same as any physical record in that the record is retained and then disposed per its legal …
Concurrency has been working closely with Microsoft to lift the limitation on
the routing of Document Sets. Currently, a limit of 50 MB has been set. However,
after investigation and testing of an update to SharePoint, Microsoft will lift
the size limitation and provide a recommended limit of 250 MB.
For those who require routing above the 250 MB recommendation, it is critical
to plan accordingly as performance will be impacted. This will entail an
evaluation of the hardware, specifically memory allocation, to ensure that the
routing operates as intended.
This new functionality is expected in the June Cumulative Update (CU).
Microsoft remains committed to continuously improving SharePoint and working
with industry in this endeavor.
READ FULL POST at blog.concurrency.com
Capacity planning for your Hyper-V Virtual Machines is one of the more critical activities you will undertake in your virtualized server environment. How many CPUs, how much RAM, and how much disk space will largely vary by the server role. In this regard you should treat your Virtual Machine with the same requirements of a …