Before you do a routine upgrade of
the PI Server, we suggest you do a backup. Now this is just
common sense IT, you know, good practices.
We always want to have a good backup just in case, for whatever
reason, the upgrade fails, or if,
for example, you would like to go back to the previous version.
Obviously it's not be design, but sometimes we see customers
who upgrade and then there are certain features they were counting
on that the behavior changes. And, obviously,
we, we try to avoid those, but it is, it's sometimes
just a sad fact of development that,
you know, changes you make to improve may actually end up hurting
some customers. So, in any event, it's a really
good idea to have a good backup. Just to let you know, there is
no downgrade procedure so, in fact,
when you do have to restore to a
previous version, you are basically going to be deleting PI
and then reinstalling it and restoring the backup. So,
the first step to an upgrade is to do a backup.
We suggest you first stop PI
before you do your upgrade. Then do the upgrade
and then start up PI, and, and
that should work fine. Of course, we say upgrade from the CD.
Now most people are downloading PI from,
you know, Pi from a, a,
a website, so it's probably not going to be on
a physical media that you do this. So let's take a look at,
let's take a look at this computer. I will do a quick upgrade.
First think I would like to do is just make sure that
PI is, in fact, shut down, and
I would do that my going into the PI-adm directory
and doing a pisrvstop.
Do pisrvstop, that should normally
stop the PI System -- one of the few times you are going to be stopping it
without actually long... -- you know, aside from
when you shut down the Operating System. Now, once
you are finished doing that, next thing you should do is do a
net start command just to verify that
everything has, in fact, shut down. So, take a
look at what happens when I do this. I do net start. This is a Windows
command, and without passing
any parameters, the net start has the effect of listing
all the services that are currently running. If I scroll
up, you can see -- oh, that's, interesting. PI Network
Manager. I had just stopped PI, so why is this still running?
Well, in this case, and this is not too unusual to happen,
I may have, say for example, shut
down PI and then I just launched ProcessBook
briefly to take a look at something on the, on a different
server, for example. The effect of starting up
a Local Client is that it will start up
PI Network Manager and it will start up
this -- well, some other things as well, some other PI --
the PI Message Sub-system, for example, is sometimes
started up. Now this is just a normal client
service so you do not have to shut that down
before backing up or before doing an upgrade.
So, in any case, at this point I would like to shut
this down, PI Network Manager. And
there's a couple of ways to do this. Probably the,
well, the most convenient right here would be to
use the DOS prompt commands, and let me
demonstrate that. I would do a net stop
and then the name of the service, pi network
manager. That would work just fine.
Now the other things you could do --
let's see if can demonstrate this. I
do not know if you can see -- there you go, you can see this now. If you
run the Services Applet within Windows,
services.msc.
You can also stop PI Net Manager
using that service manager. Let me bring this on
to the screen here, and if we look at
all the Pi-related Services, you should find
PI Network Manager, and you should
see that it's actually currently started. So,
we could stop it either way. I could stop PI Network Manager --
... here go, PI Network
Manager -- it's just currently started. I could just stop it like that.
Or, as I said, I could, I could do it this
kind of old-school way from the DOS prompt.
Net stop is a command that will
normally stop a service. So, I will go ahead and stop
PI Network Manager before I do my upgrade.
And, as you can see, if I refresh my screen
now -- there we go -- it is now
stopped. So,
at this point, with all the PI processes stopped,
I am ready to do the upgrade. I am going to go
ahead and close out of these, and
as we said in our slides here, again, first step stop PI.
Second is to go ahead and just actually do the upgrade.
I am going to do the upgrade by running
my upgrade executable.
I tend to -- and we, we, we have told people this
for years, for System Managers -- it's not a bad idea to keep all your
installations in one place. Just keep them locally.
We traditionally have called that PI Source. But that's just kind of
a recommendation that we have had within Tech
Support and Training for a while. It's certainly nothing official.
So, I, I have put my upgrade executable
in the PI Source Directory, and I am ready to go ahead
and upgrade PI. So I will go ahead and double-click on this. You will notice
this is precisely the same file
that you would use to do a fresh install. So the
install script is smart enough to detect whether this is an
upgrade or a, or a new install.
Now, while that's unzipping, what I would like to do is
bring up the DOS prompt again and just show you what
I am, in fact, upgrading. So, let me show you --
I am going to type cmd to launch the Command Window.
I will bring this up onto the screen,
and I will change directories to pi-adm.
And, if you look at piversion -v,
you can see this is the
3.4.364 version. We are going to upgrade to the
365 version .38 I believe.
So that's the upgrade that we are involved with at this
point right here. Now let's
take a look at where our upgrade is. It's still
unzipping. There we go. It looks like everything was unzipped successfully.
And now the upgrade will
proceed. There we being
advised all these things will be
installed or upgraded.
And I will just go ahead and take the defaults for just about
everything in here. You will notice there are very few things
really to respond to while doing a,
an upgrade. I will take the default on
that. Of course, good practice is to exit all Windows
Programs.
Now, at this point, I am being reminded about the License
File. Now those
of you who have not upgraded, well, for quite a while since
the 3.3 release, I believe, this may be new to
you. And if you do not have a License File on your system,
you are going to have to contact -- as we say right here, we are going to have to contact
Tech Support. Tech Support would be glad to
supply this. They will just check your license, make sure you have got the License File.
Currently, what we are doing is, we are just,
we are basically checking to make sure that you are licensed
for those applications that are running.
And, it's going to go, go ahead and look for that. If it cannot
it, it's going to give you the opportunity to browse for it.
And, in this case, it does not find a
License File. So, I am going to go ahead and browse for it
and place it in the right directory.
Now this should not be a problem for me
because, if I switch over to
my installed copy of PI, I will find the License
File right there. So, I will go up to
the Root Directory which is where we normally install PI.
Go into the dat directory and we will find the PI License.dat.
So we are being prompted, where is that License
File? That's where the License File is in this case.
So, I will go ahead and choose Next. And now, we are ready to
answer the rest of the prompts. As
we have said during the install, if you are not familiar with your
Serial Number, your actual Server
Number, just in a zero there.
And I would like this to be used by anybody.
And it's going to go ahead and
take the Default Directory which, in this case, is
where the existing PI Server is. I will just --
you know, I kept it in the original default. And now,
just as we have been prompted during
the install, you have the choice -- do you want this to be
auto-started? Actually, in this case, I have, I am using this as
a demo on a test machine. I do not want this to be started automatically
every time I reboot the Operating System. But, I warn you.
Do not do this at home. This is -- normally you would want
PI to be started every time you start the Operating
System unless you are doing some kind of a test system or a staging
system. So, in this case, I am going to
turn that off, but you definitely -- well, in, in most cases, you
would not want to do that on a production system.
I will go ahead and choose Next, and
at this point we are being prompted for -- or reminded
about changes to our Backup System.
Now, we put this kind of a
roadblock here, just to make sure that everybody
understands, everybody upgrading understands that their current
backups, backups, will probably fail
since we have changed the backup procedure. However,
this does not mean that you cannot do the backups
the same way you have always done them. If you do not have
this Microsoft Volume Shadow Services, this VSS,
then there are mechanisms
that you can use. There, there's options you have for
setting it up to do just the traditional backup that you have, you have always
done. So, in order to know, learn
more about that, we have to refer you over to a
section of the Server System Management
Introduction. Let me show you where that is.
If you go to our Tech Support Site, and you --
this is just simply techsupport.osisoft.com --
if you simply say let's go to download some User Manuals,
and, in this case, what we are going to be looking for
-- let's just look for all of the
User Manuals for the,
the PI Server that have the word system management
in it. This is taking a little bit of time.
Okay,
there we go. And if I simply
switch to -- let's go with a PI3 Enterprise Server.
And we are going to look for the file name, System
Management. Actually,
you did not have to choose the product there.
And what we should find
is this Introduction. The Introduction to
System Management is a PDF File.
There it is, Introduction. And once you download this --
well, you will see something like this. Let me open up the file.
Yeah, if you go to Section 7.6,
there's a section there on setting automatic backups. So,
we simply have changed the mechanism, so we do
exploit the Visual -- or the VSS
technology if it does exist. If it's not,
we do still support doing backups the way you have always done it.
It's just that there are some changes you have to make, and those
changes are described here.
So, what we have asked people to do is, just go ahead and acknowledge
that, that there is a new backup, and then
you can go read that chapter on how to set the backups
up the way you'd, you'd like to have them run.
And, of course,
as a good practice, we always warn people, do you have
a good pack... backup? And I will go ahead and say yes, I
do have a good backup here.
And, at that point, the system should go ahead and
start doing the upgrade.
This message is telling me that the machine I am
currently upgrading has a 1.2 version of PI AF, the
Analysis Framework. The 1.3
version is the version that is associated with
this particular release. Now this is the
PR1 Release. Actually, we have an even
more recent one that is just about ready to be released:
the, the PI AF2.x. So, depending
on what version you are upgrading, you may get this message or a
slightly different message. Now currently, that upgrade to
PI AF is not part of the upgrade of PI.
That is something you can download from our, our website,
or contact Tech Support if you need that
shipped to you.