Sponsored Content
Operating Systems Solaris Sun cluster and Veritas cluster question. Post 302482185 by sparcguy on Monday 20th of December 2010 07:28:58 PM
Old 12-20-2010
Sun cluster and Veritas cluster question.

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 existing production servers which are connected to both HDS and EMC storage. configure the suncluster to use emc disk whilst vcs is still attached to HDS storage.

Once suncluster+EMC and all filesystems are created and working properly get a downtime copy data over from old vcs setup. then test with the application in the sun cluster.

My questions as follows:
1) Does anybody forsee any problems if vcs and suncluster cluster setups co-exist side by side?

2) Anybody done any similar cluster migrations in the past?
 

10 More Discussions You Might Find Interesting

1. Solaris

veritas cluster

Hi I want to install VCS 5 on solaris 10 the product states it needs 3 nic cards. how to install it if I have 2 cards only (this is just for demo)? thank you for your help. (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

2. High Performance Computing

SUN Cluster Vs Veritas Cluster

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

3. Solaris

scconf crash: registering a Veritas local disk on Sun Cluster (localonly=true)

Hi all, I want to put a local disk on a Sun Cluster node but scconf command explodes :eek: My system: * two node cluster on two VMWare virtual machines * Solaris 10 SunOS 5.10 Generic_141415-05 i86pc i386 i86pc * Sun Cluster 3.2 u2 * Veritas Volume manager The situation... (2 Replies)
Discussion started by: gxmsgx
2 Replies

4. Solaris

Sun cluster setup question

I have 2 sun blade 1500 with Qlogic card and T3 storedge. I can connect to the T3 storedge through my boxes. Now I want to setup cluster, in order to setup I need to buy a Fiber Channel switch. Can I buy any fiber channel switch? Can you recommend some old switches? I can get it from ebay. ... (4 Replies)
Discussion started by: mokkan
4 Replies

5. Solaris

Veritas Cluster Server Question

Is it possible to configure veritas cluster server using 2 Ldoms on same host? I just want to test and learn VCS. We can do a cluster (sun cluster3.2 ) in a box using 2 Ldoms but i 'm not sure if thats possible with veritas cluster or not ? (1 Reply)
Discussion started by: fugitive
1 Replies

6. Solaris

Veritas Cluster

How to create your cluster members routes and manual nat, and proxy. (2 Replies)
Discussion started by: padmaja@tech
2 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

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

8. Solaris

Sun Cluster question

Hello everyone I've inherited an Oracle Solaris system holding ASE Sybase databases. The system consists of two nodes inside a Sun Cluster. Each of the nodes is hosting 2 Sybase database instances, where one of the nodes is active and other is standing by. The scenario at hand is that when any of... (3 Replies)
Discussion started by: abohmeed
3 Replies

9. Solaris

Sun Cluster/Storage question

Hi Bros, I am a newbie to this cluster environment...my workplace is a mess of Sun solaris server, oracle database, Cisco switch, router, MS Server, Windows PC..so and so..now my boss ask me to come out with a procedure for maintenance of storage array in our sun cluster environment..I read few... (12 Replies)
Discussion started by: xavierantony
12 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
PKGKDE-VCS(1)						  Debian KDE packaging VCS helper					     PKGKDE-VCS(1)

NAME
pkgkde-vcs - a helper tool for Debian pkg-kde VCS repositories. SYNOPSIS
pkgkde-vcs [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ] pkgkde-git [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ] DESCRIPTION
pkgkde-vcs is a helper tool which aims to simplify a couple of routine tasks associated with packaging management in version control system (VCS) repositories. pkgkde-vcs transparently supports VCSes used by Debian Qt/KDE maintainer groups wrapping various VCS related command sequences into a convenient CLI interface. Please note that this helper enforces the best practises and packaging conventions adopted by Debian Qt/KDE maintainer groups and therefore it should not be considered as a general purpose packaging helper. pkgkde-vcs should be run from the fully checked out packaging repository of the package it is supposed to act upon. Firstly, it attempts to detect a VCS in use for the particular packaging in the working directory. Please note, that the detection might fail if underlying VCS utilities are not installed. If you want or have to force a specific VCS type, run the command as pkgkde-$vcs, for example pkgkde-git. If detection is successful, pkgkde-vcs will perform tasks as defined for the specified subcommand (e.g. tag). Different set of subcommands might be defined for each VCS and each of them might accept a different set of SUBCOMMAND OPTIONS (see below). All locally unrecognized subcommand options (or the ones specified as EXTERNAL TOOL OPTIONS after --) will be passed to the external VCS tool(s) which pkgkde-vcs executes to do the job. pkgkde-vcs accepts a couple of common options which apply to the helper as whole or are common for all VCSes it supports. They should be passed before subcommand in order to be recognized. Even if pkgkde-vcs does extensive sanity checks before doing anything, an underlying command it executes might still fail. Then pkgkde-vcs will terminate immediately possibly leaving repository in an inconsistent state. It is up to a user to recover from such a failure. At the moment, pkgkde-vcs supports only Git VCS. OPTIONS
Common options -y By default, execution of the first external command that makes changes to the repository has to be explicitly confirmed by user. However, if this option is specified, the first command will be run without confirmation. -n Do not run any external commands that make changes to the repository. Useful with -v to see what commands with what options would be run. -v Be more verbose (e.g. show external commands as they are executed). -- EXTERNAL TOOL OPTIONS Pass additional EXTERNAL TOOL OPTIONS to the external commands pkgkde-vcs executes to accomplish the task. See documentations of the specific subcommand for more details. SUPPORTED VERSION CONTROL SYSTEMS AND SUBCOMMANDS
Git In order to use pkgkde-vcs with Git, git(1) must be available in PATH. Bare Git repositories are not supported and Git repository should be in the fully checked out state (except clone). The following subcommands for Git repositories are supported at the moment: clone Clone the specified pkg-kde git repository. This subcommand should be specified by forcing VCS to git, i.e. by running pkgkde-git command rather than pkgkde-vcs. Repository should be specified relatively to the root of the official pkg-kde repository tree. Once operation is complete, the cloned repository will be put at the same relative location on the local filesystem and update-config (see below) will be executed on it. For example, in order to clone kde4libs repository from kde-sc, akonadi repository from kde-req and pkg-kde-tools repository from the root tree, execute: $ pkgkde-git clone kde-sc/kde4libs $ pkgkde-git clone kde-req/akonadi $ pkgkde-git clone pkg-kde-tools tag Tag current packaging state (HEAD) as upload to Debian archive. Repository working tree must be clean before executing this subcom- mand. Current package version and target distribution are automatically determined from debian/changelog. Distribution must be a valid Debian suite in order to avoid tagging of unfinished (aka UNRELEASED) revisions. The subcommand will create an annotated Git tag under "debian/" namespace. The subcommand itself does not accept any additional options. All EXTERNAL TOOL OPTIONS (if specified) and will be passed to git tag invocation. It is recommended to sign tags by speci- fying -s option. The tag created by pkgkde-vcs tag will meet the following requirements: o The tag will named as "debian/<version>" where <version> is a full debian package version without epoch. All occurrences of the ~ character in <version> will be replaced with the - character because Git does not support ~ character in tag names. o The tag will be assigned the message with content like <version>/<distribution>" where <version> is a full debian version of the package (without any modifications including epoch) and <distribution> is the distribution this package is uploaded. For example, a standard pkgkde-vcs tag will execute the following under the hood (assuming version is 1:2.3.4-5 and distribution is experimental): $ git tag debian/2.3.4-5 -m "1:2.3.4-5/experimental" update-config Do some common configuration on the checked out packaging repository. At the moment, the subcommand performs the following: o Set up master branch and debian tags for pushing. -f option may be specified to force update of the pushing configuration even if some pushing configuration already exists. o Set repository user name and email address to the values of the DEBFULLNAME and DEBEMAIL environment variables respectively. -f option may be specified to override the values even if the repository has some specified already. LICENSE
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. AUTHORS
Modestas Vainius <modax@debian.org> 0.15 2012-05-27 PKGKDE-VCS(1)
All times are GMT -4. The time now is 02:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy