Lesson 1 Part 2 - Data Protection (continued)

00:04

All right. Welcome to part two of the lesson one for data protection

00:09

in this section, we're gonna talk about the the Sphere, data protection, appliance

00:14

and some of its components.

00:16

So,

00:17

like all applying says, this is a pre configured VM with all the

00:22

software installed ready to use.

00:25

This is Agent Lis.

00:28

As we talked about some of the disadvantages of traditional backup where you have a backup agent on your host, there's no agent required to use

00:35

the, uh

00:36

these are data protection

00:38

and it is Web based. So everything you're doing is through a browser which makes

00:43

life a lot easier.

00:45

It's not having to deal with dedicated clients.

00:49

This uses a patented technology for D duplication, as we talked about in the previous section. D duplication

00:57

allows you to identify duplicate blocks of data in your backup storage area so that you don't have to back them up

01:03

more than one time

01:07

so we can back up the entire VM if you remember the VM.

01:11

Typically, all the files are contained in one folder,

01:15

so we can we can back up the VM bite by effectively backing up that folder or, as I mentioned earlier We can mount

01:23

the virtual disk for the VM directly to the backup server

01:29

in some cases and do the backups that way.

01:30

We also can support file level restores

01:36

and GDP is included in all versions of these fair except for the essentials version.

01:42

So it's already something you you have included. You don't have to pay extra for it unless you have essentials that you have to buy this as a separate license.

01:51

So it's very scalable. I can have up to 100 v EMS, pervy DP appliance

01:56

and up to 10 VP appliances per be center instance.

02:00

So right there you can do 1000.

02:04

Be EMS

02:05

for one. Be center instance. That's pretty pretty generous.

02:09

There's two terabytes of de duplicated storage

02:13

are up to two terabytes. You can configure it with half a terabyte, one terabyte or two terabytes.

02:21

And because of the change, block tracking and D duplication, we have much more efficient backups than our traditional backup method would provide.

02:30

There's ah,

02:31

variable length segments,

02:35

which helps with your

02:38

writing to disk, meaning I'm not writing a ah block of data for every single object it's. It decides how much storage to actually allocate. So you used your storage more efficiently

02:49

and then the duty D duplication happens across all the VM is there in the data store. They're all analyzed by VP by the VP appliance

02:58

to decide where the duplicate duplicate blocks might exist so that they can be avoided

03:04

in backing them up a second time.

03:07

And we even have the future of this scuzzy hot ad

03:12

which allows the appliance to only copy that information which needs to be copied instead of copying the entire V M. D K file across the network, which would

03:22

take a lot of band with and would use a lot of other resource is

03:28

Okay, so let's have a look at the components.

03:30

We've got V sphere of minimum version for here. The center running as an appliance, which is the way it is for the labs,

03:38

has to be at least version 5.1.

03:42

I can have my BDP appliance all running within this environment

03:46

with my D duplication stores.

03:49

These are all the V M p K files that I mentioned

03:51

that are being analyzed for duplicate blocks so that those could be

03:54

more efficiently dealt with.

03:57

Ah, the appliance itself is in a over B a package,

04:00

which means that it's very easy to deploy.

04:03

If you wanted to have more than one of them around, you just deploy another O V a appliance. Very simple. It does require four virtual CPU is and four gigabytes of RAM. So it does have a fair, high, fairly high resource requirement

04:18

that you're host must be able to satisfy. So be aware of that.

04:25

You can configure the appliance in three different sizes. 850 gig, 1.6 terabytes, or 3.1 terabytes.

04:31

It runs a Susie Enterprise, Lennox's version 11 64 bit.

04:36

And as I mentioned earlier, it's managed through the Web client

04:42

so very easy to deal with, getting into the Web client for V sphere in general and then just looking at the V D. P.

04:49

Portion of GDP tab.

04:54

So there's a tab with N V P for doing backups and restores.

04:59

Once you select a backup tab, you can just select an individual BM or multiple the EMS

05:04

and right click and indicate them for backups or select the backup option.

05:10

We can also back up data centers, clusters hosts

05:14

resource pools and folders.

05:15

So this is a nice feature to be able to, uh,

05:19

breaker backups into smaller chunks. If you don't want to deal with a bunch of separate PM's, you can do them by the folder or grab Ahold Data Store are sorry, a whole data center all once back that up as it exists.

05:32

And, of course, you get your typical daily, weekly and monthly scheduling for your backup window

05:40

for doing a restore. When you select the restore tab of the VP

05:44

and then we wave. Simply look at the list of the EMS that are available and pick a restore point that that matches your requirements.

05:53

That's a gang leverages the

05:55

the

05:57

change block tracking.

05:58

So we're on Lee restoring those things that are different

06:01

from when the last backup was performed.

06:04

So I saved a lot of time and energy by operating the backups that restores that way.

06:12

So a couple things here for the B center and your host

06:15

for the center back up, you have to pick a solution that makes sense for your environment.

06:19

In this case, I'm showing the center as an appliance, but it could just as easily be a physical server.

06:27

So whatever makes the most sense to get that initial backup is what you should do.

06:31

However, before you do that back up, you have to stop the V Central Server Service,

06:36

the act of director database service V. A V, C, M S, D. S

06:42

and the database service.

06:44

We don't want any of these running

06:46

while a backup is happening, because that means that data will still be changing

06:50

and it's going to make the back of larger and more difficult to deal with. So it's

06:56

best practice to stop those first.

06:58

Then you can do a full backup of your V Center server.

07:02

Then you would back up the V Center database

07:05

if your databases embedded than the center's server would include the database. But if you have a separate like an oracle or D B two database, and you have to do that back up separately,

07:16

we also want to make sure that we back up our SSL certificates and

07:21

the V p x d

07:24

dot config. File.

07:26

If you don't get these last two, when you do your restore, you're going to have some problems with the configuration and with your

07:32

your access authentication,

07:34

so make sure you don't forget to do this. Certificates and

07:38

the CONFIG file

07:41

as far as the host itself. When you build your E S X I host

07:45

best practices indicate that you should do a backup

07:48

of the configuration at that first point when the when the system was first built.

07:56

Then you would do additional backups every time you make some changes to the configuration or possibly if you're upgrading the host,

08:03

there's a special last command that you can run from the V. C L. I called v eye config dash config backup

08:11

That makes life a lot easier. And you can run that interactively to explore the different options available for performing the backup.

08:22

Okay, that concludes Lesson one for modulate for data protection.