8 More Discussions You Might Find Interesting
1. Solaris
Hello Guys,
I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me.
The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade?
1. before creating the new boot environment? or
2. after creating... (1 Reply)
Discussion started by: cjashu
1 Replies
2. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
3. Emergency UNIX and Linux Support
I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade.
OS DVD is mounted on /mnt
Boot environments are Solaris9old (Active now)... (2 Replies)
Discussion started by: solaris_1977
2 Replies
4. Solaris
I want to basically update an ABE that someone created a few months back.
I'm sure stuff has changed since it was made, and I was going to delete it and create a new one.
But from what I'm looking at, the lumake appears like it would be a faster approach.
I want to use live upgrade to... (0 Replies)
Discussion started by: BG_JrAdmin
0 Replies
5. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
6. Solaris
Hi,
I currently have one BE and would like to create an ABE.
# lustatus
BE_name Complete Active ActiveOnReboot CopyStatus
------------------------------------------------------------------------
coolthreads yes yes yes - But... (3 Replies)
Discussion started by: pgarousi
3 Replies
7. Solaris
Hi,
I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7 (0 Replies)
Discussion started by: fugitive
0 Replies
8. High Performance Computing
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
LEARN ABOUT DEBIAN
pg_upgradecluster
PG_UPGRADECLUSTER(8) Debian PostgreSQL infrastructure PG_UPGRADECLUSTER(8)
NAME
pg_upgradecluster - upgrade an existing PostgreSQL cluster to a new major version.
SYNOPSIS
pg_upgradecluster [-v newversion] version name [newdatadir]
DESCRIPTION
pg_upgradecluster upgrades an existing PostgreSQL server cluster (i. e. a collection of databases served by a postmaster instance) to a new
version specified by newversion (default: latest available version). The configuration files of the old version are copied to the new
cluster.
The cluster of the old version will be configured to use a previously unused port since the upgraded one will use the original port. The
old cluster is not automatically removed. After upgrading, please verify that the new cluster indeed works as expected; if so, you should
remove the old cluster with pg_dropcluster(8). Please note that the old cluster is set to "manual" startup mode, in order to avoid
inadvertently changing it; this means that it will not be started automatically on system boot, and you have to use pg_ctlcluster(8) to
start/stop it. See section "STARTUP CONTROL" in pg_createcluster(8) for details.
The newdatadir argument can be used to specify a non-default data directory of the upgraded cluster. It is passed to pg_createcluster. If
not specified, this defaults to /var/lib/postgresql/version/name.
Please note that this program cannot upgrade clusters which use tablespaces. If you use those, you have to upgrade manually.
OPTIONS
-v newversion
Set the version to upgrade to (default: latest available).
--logfile filel
Set a custom log file path for the upgraded database cluster.
--locale=locale
Set the default locale for the upgraded database cluster. If this option is not specified, the locale is inherited from the old
cluster.
--lc-collate=locale
--lc-ctype=locale
--lc-messages=locale
--lc-monetary=locale
--lc-numeric=locale
--lc-time=locale
Like --locale, but only sets the locale in the specified category.
HOOK SCRIPTS
Some PostgreSQL extensions like PostGIS need metadata in auxiliary tables which must not be upgraded from the old version, but rather
initialized for the new version before copying the table data. For this purpose, extensions (as well as administrators, of course) can drop
upgrade hook scripts into /etc/postgresql-common/pg_upgradecluster.d/. Script file names must consist entirely of upper and lower case
letters, digits, underscores, and hyphens; in particular, dots (i. e. file extensions) are not allowed.
Scripts in that directory will be called with the following arguments:
<old version> <cluster name> <new version> <phase>
Phases:
init
A virgin cluster of version new version has been created, i. e. this new cluster will already have template1, but no user databases.
Please note that you should not create tables in this phase, since they will be overwritten by the dump/restore operation.
finish
All data from the old version cluster has been dumped/reloaded into the new one. The old cluster still exists.
The scripts are called as the user who owns the database.
SEE ALSO
pg_createcluster(8), pg_dropcluster(8), pg_lsclusters(1), pg_wrapper(1)
AUTHOR
Martin Pitt <mpitt@debian.org>
Debian 2012-10-08 PG_UPGRADECLUSTER(8)