Part 1 of 3 in the SharePoint Server 2013 Advanced Solutions (70-332) series. This series focuses on the planning and implementing phases of all aspects of SharePoint 2013. This course is intended for advanced users who are looking to gain knowledge for the 70-332 exam. We will start with a bare bones environment, and begin to build and plan through SQL, SharePoint, and the Services, until our entire environment is configured; based on our demo company, Globomantics, requests.
SharePoint Server 2013 Advanced Solutions (70-332) Hi, and welcome to the SharePoint Server 2013 Advanced Solutions course, where we're going to go over for the exam 70-332. My name is Jeff, and I want to say thank you very much for joining me. SharePoint is one of my favorite products, and I'm going to love digging into this with you. So before we jump in and start digging our hands into the product, I want to take a couple moments for an introduction. I just want to look over what we're going to be doing, how we're going to be doing it, and what we hope to achieve by doing all of this. So let's jump right into our introduction.
SQL High Availability: Mirroring, Clusters, and Always On Hi. Jeff here, and thanks for joining me for another lesson. Today's lesson we're going to go over SQL High Availability, Mirroring, Clustering, and Always On. So, we're going to go look at those three in a moment. But before we jump in there I want to take a second and I want to talk about SQL High Availability. We talk about SQL High Availability, most people look at it going, well, thats just making sure we can access the data. And that is accurate, but we also need to look at it in the real world in two parts. One is accessing the data, making sure that we can always get to it. But the other one is, maintaining the data. Making sure that the data is always available and that its as close to updated as possible. So, as we go forward I want you to think about those two pieces. Accessing the data, and maintaining the data. So lets go forward and talk about Mirroring for a moment.
SQL Disaster Recovery Hi, Jeff here. In this lesson, we're going to go over a couple things that are above and beyond what we talked about in the last lesson. We're going to start looking at things like log shipping. You know, what is storage redundancy? Things along those lines. And then we're going to jump into our scenario, and from there we're going to go right into the servers, and get our hands dirty right away. So without further adieu let's jump over, and I want to go over some of these definitions, and have a discussion about them just for a couple moments. I promise, we'll get right in the server as fast as we can.
SharePoint Server and Services Distribution Hi, Jeff here and thanks for joining me for SharePoint Server and Services Distribution. Today we're actually going to be talking about how do we distribute these. Where do we put our SharePoint servers? What type are we going to be utilizing, and how do we distribute our services across them to get the most effectiveness out of them? Now, a lot of the last lessons we've done, we looked over some slides to talk about some things. In this one, what we're going to do, is we're going to walk and click. That means while we're going through it, we're going to be talking about each piece. So we're going to stay away from slides this time. All we're going to do is we're going to go to a scenario. We're going to find out what globomantics requires of us and then we're going to go in and we're going to walk and click. So without further adieu, let's go right to our scenario. Let's see what they. . .
Network Load Balancing and Redundancy Hi, Jeff here, and thanks for joining me for Network Load Balancing and Redundancy lesson. What we're going to be doing in this lesson is we're actually going to be looking over the NLB, the Network Load Balancer for our two frontends. Now remember, we've got our frontends done, we've got our application server done, we've got our search server done, we've even got SQL, so we've got all three layers. Remember our three layers. We've got a web layer, we've got our application layer, and we've got our data layer, so we have all three of these set. So we have our three tiers already there, and we're ready to go, but, without having the NLB in place it's not going to work so well. We're also going to talk a little bit about redundancy. But before we talk about redundancy, we're going to have to go and see exactly what Globomantics wants from us this time. So in this lesson, we're going to do what we did before, we're going to do what's called click and talk, so we're going to go check out the scenario, and we're going to go straight from the scenario, and we're going to go jump right into those servers, okay?
Plan Backup and Restore - SharePoint Hi, Jeff here and welcome to Plan Backup and Restore. This is going to be the SharePoint portion of this. We are going to talk about the SQL portion in a future lesson, but right now we're going to specifically look at SharePoint itself. Now a lot of us when we think about, you know, planning our backup and restore, we only think about SQL. You know, we back up the DBs, we restore the DBs, this is what we do, and this is what we've always done in SharePoint. Now in 2010, we got some capabilities to be able to do some backups inside, but we didn't pay a lot of attention, now some people did. So if you're one of the ones that did pay attention, this is going to be a real easy lesson for you, because only a couple small things have changed. In fact, really only one has changed, and I'll get to that in a moment as well. So, what we're going to do is we're going to go forward and we're going to talk about what can SharePoint back up. What can it do without having to do SQL backups? So let's go take a quick look at what capabilities SharePoint actually has and what it can back up.
Plan Backup and Restore - SQL Hi, Jeff here, and welcome to Plan Backup and Restore. This time we're going to be looking at SQL to see what it's able to back up, and we're going to check to see what Globomantics requires of us in regards to SQL specifically. So, in the last one, we talked about doing SharePoint backups and we saw we can get pretty fine-grained on them. SQL is a little bit of a different story. Let's go see what we can actually back up in regards to SQL itself. So SQL Server backups, they give us the ability to back up the following objects. We can back up the database. In fact, we can back up all databases. We can back up files. We can back up filegroups. Now, I'm going to stop there for a moment because we've seen a lot of the other stuff as we've gone through SQL together, but what we haven't talked about is filegroups. And it's actually pretty simple. It's exactly what the name states. This is a group of files that we have combined together to make it easy to back up. That way if I need something from here, and over there, and over there, and there, I can create a group that contains all of it. No matter what changes are made to those, those are still part of my filegroup, and I can back that up to make it real easy for myself. And last but not least, we've got logs. And you'll notice in the first one, when we did our backup, when we were doing mirroring, we went and we did a backup but then we turned around and we also did a backup of our logs. Now that's kind of silly, since we took the database. One thing to know about SQL backups is, we don't take our data and our logs and have them together in the same backups. It just doesn't occur. It doesn't occur because that option is really not there and available for us. If we back up the database, we always need to back up our logs as well. So that's something to remember as we go forward. Now we're going to talk a little bit more about that as we go along, but for right now, I want to start and get right into that scenario, just because I'm curious to see what they're asking for today.
Evaluate Content and Customizations for Upgrade Welcome back. Today we're going to go over the lesson, Evaluate Content and Customizations for Upgrade. My name is Jeff and I'm glad to have you here for this lesson. Now, this is one of those ones that we have to go through every single time we look at an upgrade. Not only that, every exam, all the way up from 2007, 2010, all of the exams that talked about it made sure to ask you about the upgrade, what can we do for the upgrade? And one of the things we've got to look at right off the bat when we're going to do an upgrade is evaluating the content and customizations. 'Cause if we don't know what we're upgrading and we just decide we're going to upgrade it, throw it over there and see what happens, well, that can be a dangerous mixture, not really something that we want to try. We can of course, I just don't think it would work so well, you'd have to cross your fingers on that one, so let's jump in this lesson and let's talk about how we evaluate the content and customizations, and some of the things we've got available that we can use.
Plan an Upgrade Process Well, welcome back. In this lesson we're going to go over a Plan and Upgrade Process. My name's Jeff and I'm glad to have you here. So without further ado, what we're going to is we're going to jump in and we're going to go talk about this upgrade process, what some of the stages are, some of the steps, and what we're going to do when we plan all of this. Now, like every lesson, we still have to get our hands dirty so as much as I say plan, please remember, whatever we talk about, we're going to go do. So let's go check out some of these pieces.
The Upgrade Process Hey, welcome back. In today's lesson, we're actually going to go over the upgrade process. In this one, we're going to actually look over some of the upgrade stages that we've seen in the previous lesson, and we're going to talk about actually going through it. We're going to talk about what we can upgrade, and then we're going to go check out what Globomantics would like us to upgrade. Remember, our entire process here is upgrading from SharePoint 2010 to 2013. As we saw in the last lesson, just to remind you on this, there is no more in-place upgrade. Hence, we have to bring the DBs over, we have to upgrade them onto the 2013 farm, which, luckily, we've already set up. We've got our farm set up, we've got our services set, we've got server distribution, we've got a ton of things already there, waiting for us in the SharePoint 2013 farm, but what we don't have is the actual 2010 data. Before we continue on to all of that, what we're going to do is we're going to take a moment and we're going to talk about the upgrade stages.
Upgrade Site Collections Welcome back. In this lesson we're going to go over upgrade site collections. Now, I know in the last one I kind of left off with a bit of a cliffhanger, but we're actually going to go and take a peek at what they look like in just a couple of moments. Just like every lesson, we're going to go through a couple slides first and then we're going to go jump in. Now, we've upgraded the service applications, we've upgraded the content DB, and that's great, but we're still in the position where if we allow it to just be as is, every single site collection administrator can go forward and click a button and upgrade their site. So, good in some ways, if that's what we want, but there are other things we have to think about. What if we had a 1, 000 sites and everybody went and clicked the button and went, I want to upgrade now. Well, what happens? What happen to our servers? What type of throttling can we put in place? You know, these are things we have to think about. Especially when we're talking about larger environments. Smaller ones, maybe not as much, but it really depends on how many web objects they've got inside their site collection, tons of little things like that. So, let's go forward and take a quick look at upgrading the site collections.