Skip to main content

Upgrading to NexentaStor CE 3.1.3

Recently just upgraded my test NexentaStor CE from 3.1.2 to 3.1.3 (r9990). Here are the walkthru of the process upgrade.

nmc@nx:/$ setup appliance upgrade

Cleanup upgrade caches (note: cleanup is generally not required and can be skipped in most cases; if you say Yes, prepare to wait for software upgrade to complete a bit longer) ? Yes  <=answer y

You are about to upgrade the appliance software. Please be advised that by executing this operation you agree to be bound by the terms of the product license available at http://www.nexenta.com/nexentastor-licenses. This operation may take some time to check with the remote appliance's software repository. Proceed?  Yes <=answer y
Checking repository sources. Please wait...

Found new upgrades!
Verifying upgrades...
Trying to gain exclusive access to the appliance.
This operation may take up to 30 seconds to complete. Please wait...
Exclusive access granted.
Initiating appliance upgrade procedure. Please wait...
Success. This upgrade will download approximately 73.30MB
This upgrade will require REBOOT. Proceed? (y/n) y  <= answer y
Downloading upgrades. This may take a few minutes. Please wait...
Upgrade is in progress. Please DO NOT interrupt...
Creating Upgrade Checkpoint...


Now just sit back and enjoy until


* * *
                      SYSTEM NOTICE

     The first phase of upgrade has completed successfully:
       - created Upgrade Checkpoint 'rootfs-nmu-005'
       - the appliance is ready to reboot into this new checkpoint

   +------------------------------------------------------------------+
   |                                                                  |
   |  At this point there are two options:                            |
   |                                                                  |
   |   - You can reboot now and make sure that system is healthy.     |
   |     You will be prompted to activate the newly created           |
   |     checkpoint after the reboot.                                 |
   |                                                                  |
   |   - Or, you can simply continue using the appliance as is and    |
   |     later activate this new checkpoint, and then reboot.         |
   |                                                                  |
   |  See also: 'setup appliance checkpoint'                          |
   |  See also: 'setup appliance reboot'                              |
   |                                                                  |
   +------------------------------------------------------------------+
Would you like to reboot now ? (y/n) y <= answer y
Operation in progress...

After the reboot process is done, login back and this will come up...


* * *
                       SYSTEM NOTICE

  The first phase of safe upgrade has completed successfully.
  The second (and final) phase of software upgrade requires
  activation of 'rootfs-nmu-005' upgrade checkpoint.

Would you like to activate the current checkpoint 'syspool/rootfs-nmu-005' ?  Yes

Checkpoint 'syspool/rootfs-nmu-005' has been activated.
The second phase of activation has completed successfully.
*****************************************************************
*                   Nexenta Management Console                  *
*                       Version 3.1.3 (r9990)                   *
*                                                               *
*  press    TAB-TAB to list and complete available options      *
*                                                               *
*  type     help   for help                                     *
*           exit   to exit local NMC, remote NMC, or group mode *
*           q[uit] or Ctrl-C     exit NMC dialogs               *
*           q[uit] or Ctrl-C     exit NMC text viewer           *
*                                                               *
*           option -h            help on NMC options            *
*           -h     help on any command            *
*           ?      brief summary                  *
*           help keyword [-q]    locate NMC commands            *
*           help -k [-q]         same as above                  *
*           setup usage          combined 'setup' man pages     *
*           show usage           combined 'show' man pages      *
*                                                               *
*  type     help   and press TAB-TAB                            *
*                                                               *
*  Management GUI: http://xxx.xxx.xxx.xxx:2000/                 *
*                                                               *
*****************************************************************

And you're done....


Comments

Popular posts from this blog

Why I Can't Move/Import VM in XenServer.

Ok this is what i found out, the metadata export/import via ' Backup, Restore and Update ' menu in xsconsole OR using ' xe vm-export filename=xxx metadata=true vm= ' will export all vm's metadata eventhough you've specify the vm in the latter, the former is ok because it is backup & restore tool. Problem happens when you want to restore the metadata or import to another xenserver. If you follow the method from 'Backup and Restore' in the reference guide, it should be ok if you're using pool because all pools are using shared storage; and if you don't use pool, your xenserver store all the VMs in the shared storage ONLY, means the Local SR is not use at all. This way, you wont face any problem. But, what if you have a mix of local & shared storage use. 

SQL using partition and connect by clause.

select id, max(ltrim(sys_connect_by_path(gred,' , '),' , ')) as mygred from (select b.KJ19SIJIL||b.KJ19KOD as id, b.KJ19GRED as gred, row_number() over(partition by b.KJ19SIJIL||b.KJ19KOD order by b.KJ19GRED) as myrow from kj19setara b) start with myrow = 1 connect by prior myrow = myrow -1 and prior id = id group by id order by 1;

Use raw disk for Apache Trafficserver in Centos 7

I want to use raw disk for my Trafficserver 5.1.0. I've created a partition at /dev/sda5 and in order to allow trafficserver to use the disk, please follow these steps. 1) Edit/create a file in /etc/udev/rules.d . I named it 50-ats.rules eg. vi /etc/udev/rules.d/50-ats.rules 2) Add these text. SUBSYSTEM=="block", KERNEL=="sda5", GROUP:="trafficserver", OWNER:="nobody" note : - sda5 is the disk/partition I want to use with trafficserver. - OWNER:="nobody" is the default owner when you compile trafficserver.