Thanks Kevin,
Z Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:[email protected] Cell:401-639-3505 From: Kevin Lundy [mailto:[email protected]] Sent: Friday, April 15, 2011 9:39 AM To: NT System Admin Issues Subject: Re: Sharepoint 2010 Specifications and questions Inline On Fri, Apr 15, 2011 at 7:52 AM, Ziots, Edward <[email protected]> wrote: To the list and the Sharepoint Guru's out there a few questions. I have been asked to spec hardware for a Sharepoint 2010 site for internal IS. (Note: I am a sharepoint N00b, so forgive my trivial questions) 1) Are folks out there storing there documents in Sharepoint in BLOB ( Binary Large Objects within SQL or are they using the Filestream parameter within SQL 2008/SQL 2008 R2 to store the documents in file-stores? yes. To both. Older installations are solely BLOB. New installation by default are BLOB. In my opinion, it's not a simple binary decision. You need to factor the average size of your documents, how many, how often opened, etc. 2) How many Web servers are folks using for a small site ( less than 1K in users) and what roles are they putting on which servers? Also any gotchas using Windows 2008 R2 and IIS 7.5 vs Windows 2008 and IIS 7.0 for the web-front end. Sharepoint or Sharepoint Foundation? Extensive workflow? Event receivers? Large lists with custom filtering? Indexing file shares? Again, no simple answer. If using Foundation, fairly much out of the box, 2 front ends should handle the load. Both MS and VMware have some good whitepapers on virtualizing Sharepoint, I would start with them. 3) Also what are folks using to backup sharepoint so that documents within the sharepoint site back be retrieved ( Avepoint? Just native SQL backup? Windows Backup? There are 2 configurable recycle bins - one on each site, and one for admins. So between those, and PowerShell many people don't need much else. SQL backup, while important, will only allow you to restore a site collection - painful if you just need a document. It really gets down to your requirements, users, and SLA. As an example, on one of our farms we use only native tools. On another farm, we use Avepoint due to our SLA. Any guidance would be helpful, There are several good books. MS has some online labs. I suggest you spend some time there and that will help you then plan your infrastructure. Sincerely, EZ Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:[email protected] <mailto:email%[email protected]> Cell:401-639-3505 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
