Migrating a Sun Cluster Running Oracle to New Hardware

Has anyone attempted this? Essentially we are moving a Sun Cluster from one location to hardware at another location while maintaining the same node names. From what I can tell, I need to (on an install lan):
1) Load the OS
2) Configure the IPs
3) Install Sun Cluster
4) Install Oracle Parallel Server/RAC
5) Restore the data on a per node basis
6) Restore the shared data
7) Adjust, tweak, and run
Are there any pitfalls or suggestions on the approach? The shop is relatively new to clustering much less oracle clustering and the original cluster was installed by admins gone bye.

I would say that Apple should be able to update your 36-months maintenance agreement with a OSXS 10.4 serial number.
As far as I know, the structure of 10.3 and 10.4 serial numbers is different (wasn't the case between 10.2 and 10.3) so I'm short of a technical answer here.
Maybe you could try :
/System/Library/ServerSetup/serversetup -setServerSerialNumber xxxx-xxx-xxx-x-xxx-xxx-xxx-xxx-xxx-xxx-x
in a Terminal window on the server. It's theorically the same as using Server Admin but maybe this could help.

Similar Messages

  • Migration from SCVMM 2012 SP1 to R2 - New Hardware

    We want to migrate our existing SCVMM 2012 SP1 to new hardware and then bump it to SCVMM 2012 R2. Our database is on a separate SQL 2008 R2 server. This is what we envision doing to get there:
    Uninstall SCVMM 2012 SP1 on existing server and retaining the database
    Backup and restore the SCVMM database to a new SQL 2012 server
    Install SCVMM 2012 R2 on new hardware and connect to existing database on SQL 2012 server
    Does this sound doable? Will we lose anything in the move? Maybe our existing libraries?
    Orange County District Attorney

    Using your steps outlined above may NOT be supported.
    Please see here:
    http://technet.microsoft.com/en-us/library/dn469607.aspx
    Upgrading on a remote computer
    Upgrading from VMM in System Center 2012 SP1 on one computer to VMM in System Center 2012 R2 on a different computer is not supported when data is retained from the original installation, and the following configurations apply:
    The original installation uses Windows DPAPI. This is the default setting if you did not configure distributed key management during setup.
    The VMM management server is configured to use any of the following encrypted values or settings:
    Application settings (encrypted value)
    Service setting (encrypted value)
    SQL Server deployment (product key)
    Web deploy package (encryption password)
    "Personally" and this is a pain, I would:
    Uninstall VMM SP1 and retain the DB.
    Re-install the exisiting hardware with Server 2012
    Re-install VMM SP1 and reconnect to existing DB
    Upgrade to VMM 2012 R2
    Uninstall and retain the DB
    Restore the DB on new SQL 2012 server
    Reinstall VMM 2012 R2 on new Server and reconnect to existing DB
    Note that you will probably get access denied messages once running on the new VMM server due to the SID change.  You will need to re-associate hosts and libraries.
    I'm still not saying this is a supported method, but it's likely it's more supported as it's essentially following DR principals.
    My System Center Blog

  • Encountered ora-29701 during Sun Cluster for Oracle RAC 9.2.0.7 startup (UR

    Hi all,
    Need some help from all out there
    In our Sun Cluster 3.1 Data Service for Oracle RAC 9.2.0.7 (Solaris 9) configuration, my team had encountered
    ora-29701 *Unable to connect to Cluster Manager*
    during the startup of the Oracle RAC database instances on the Oracle RAC Server resources.
    We tried the attached workaround by Oracle. This workaround works well for the 1^st time but it doesn’t work anymore when the server is rebooted.
    Kindly help me to check whether anyone encounter the same problem as the above and able to resolve. Thanks.
    Bug No. 4262155
    Filed 25-MAR-2005 Updated 11-APR-2005
    Product Oracle Server - Enterprise Edition Product Version 9.2.0.6.0
    Platform Linux x86
    Platform Version 2.4.21-9.0.1
    Database Version 9.2.0.6.0
    Affects Platforms Port-Specific
    Severity Severe Loss of Service
    Status Not a Bug. To Filer
    Base Bug N/A
    Fixed in Product Version No Data
    Problem statement:
    ORA-29701 DURING DATABASE CREATION AFTER APPLYING 9.2.0.6 PATCHSET
    *** 03/25/05 07:32 am ***
    TAR:
    PROBLEM:
    Customer applied 9.2.0.6 patchset over 9.2.0.4 patchset.
    While creating the database, customer receives following error:
         ORA-29701: unable to connect to Cluster Manager
    However, if customer goes from 9.2.0.4 -> 9.2.0.5 -> 9.2.0.6, the problem does not occur.
    DIAGNOSTIC ANALYSIS:
    It seems that the problem is with libskgxn9.so shared library.
    For 9.2.0.4 -> 9.2.0.5 -> 9.2.0.6, the install log shows the following:
    installActions2005-03-22_03-44-42PM.log:,
    [libskgxn9.so->%ORACLE_HOME%/lib/libskgxn9.so 7933 plats=1=>[46]langs=1=> en,fr,ar,bn,pt_BR,bg,fr_CA,ca,hr,cs,da,nl,ar_EG,en_GB,et,fi,de,el,iw,hu,is,in, it,ja,ko,es,lv,lt,ms,es_MX,no,pl,pt,ro,ru,zh_CN,sk,sl,es_ES,sv,th,zh_TW, tr,uk,vi]]
    installActions2005-03-22_04-13-03PM.log:, [libcmdll.so ->%ORACLE_HOME%/lib/libskgxn9.so 64274 plats=1=>[46] langs=-554696704=>[en]]
    For 9.2.0.4 -> 9.2.0.6, install log shows:
    installActions2005-03-22_04-13-03PM.log:, [libcmdll.so ->%ORACLE_HOME%/lib/libskgxn9.so 64274 plats=1=>[46] langs=-554696704=>[en]] does not exist.
    This means that while patching from 9.2.0.4 -> 9.2.0.5, Installer copies the libcmdll.so library into libskgxn9.so, while patching from 9.2.0.4 -> 9.2.0.6 does not.
    ORACM is located in /app/oracle/ORACM which is different than ORACLE_HOME in customer's environment.
    WORKAROUND:
    Customer is using the following workaround:
    cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk rac_on ioracle ipc_udp
    RELATED BUGS:
    Bug 4169291

    Check if following MOS note helps.
    Series of ORA-7445 Errors After Applying 9.2.0.7.0 Patchset to 9.2.0.6.0 Database (Doc ID 373375.1)

  • Sun cluster and oracle RAC

    my client is insisting on putting oracle RAC on top of sun cluster, the thing is i don't know what is the benifit of creating such an architecture, i tries to search on the internet but couldn't understand the benifits nor the advantage, Kindly if some one has implemented such an architecture to let us know the use and the benifits

    Hi,
    Here on my environment, there is SUNCluster only for single instances. The Clusterware Oracle is complete providing high availability and load balance for your database, you don't need sun cluster with this case, no advantages gained. The only thing controlled by SUNCluster on my RAC environment is QFS (Cluster file system from SUN).
    If search on this forum, there are many discussion by this topic (suncluster X RAC) like this post Re: Sun Cluster.. Why?
    Regards,
    Rodrigo Mufalani

  • RAC: using Sun cluster or Oracle clusterware?

    Going to build RAC on SUN machine (Solaris 10) and Sun SAN storage, couldn't decide how to build the foundation-----use Sun cluster 3.1 or Oracle clusterware?
    Any idea? Thanks.

    Starting with 10g Release 2, Oracle provides its own and indipendient cluster management, i.e., Clusterware which can be used as replacement for the OS specific cluster software.
    You can still use the OS level cluster, in this case, Oracle Clusterware depends on OS cluster for the node information.
    If you are on 10g, you can safely, go with Oracle Clusterware.
    Jaffar

  • Migrate user data from SLES10sp3 OES2sp3 to new hardware

    Hi,
    I am trying to migrate user data on a nss volume from a SLES10sp3 and
    OES2sp3 server to new hardware already setup with SLES10sp3 and OES2sp3.
    Authentication and configuration of the data selection is sorted. After
    starting the data transfer I get a message saying the migration failed.
    Below is the error from the log file:
    FATAL -FILESYSTEM:migfiles:Fatal: Cannot migrate source path
    /media/nss/DATA/Users/JohnG/: nbackup: Failed to open dataset
    /media/nss/DATA/Users/JohnG/ for backup
    WARNING - FILESYSTEM:migfiles:Warning: Going to next data set
    ERROR - FILESYSTEM:migfiles:Error: nbackup: (libtsafs.so 6.50.0 291) An
    invalid path was used.
    Regards
    John

    Hi kjhurni,
    I have not setup to get update from the Novell channel as I have an issue
    with connecting to the update channel but I will deal with that later.
    I tried to run a miggui to migrate my data to the new server with SLES10sp3
    and OES2sp3. Below is the entire log file, I have highlighted the error at
    the end of the log file. (Names and addresses have been changed to protect
    the innocent)
    Regards
    John
    2012-01-12 11:15:17,394 INFO - Migration
    Framework:getSourceServerConfigDetails():Finding Source Server eDirectory
    Tree Name using command: ndsstat -h SERVER1
    2012-01-12 11:15:17,474 INFO - MigUtil:ResolvIP:Resolving IP address from
    hostname SERVER1
    2012-01-12 11:15:17,539 INFO - Migration Framework:Getting Source Server
    certificate:Using 10.1.3.1 to retrieve Source Server certificate
    2012-01-12 11:15:17,539 INFO - Migration Framework:Getting Source Server
    certificate:executing command: LC_ALL=en_US.UTF-8 /usr/bin/ruby
    /opt/novell/migration/sbin/getServerCert.rb --server-ip "10.1.3.1"
    --ldap-port 636 --file /opt/novell/migration/plugin/conf/SourceServerCert
    2012-01-12 11:15:20,795 INFO - Migration Framework:Getting Source tree
    certificate:using getSSCert command
    2012-01-12 11:15:20,801 INFO - Migration Framework:Getting Source tree
    certificate:Using 10.1.3.1 to retrieve Source tree certificate
    2012-01-12 11:15:20,801 INFO - Migration Framework:Getting Source tree
    certificate:executing command: LC_ALL=en_US.UTF-8
    /opt/novell/oes-install/util/getSSCert -a "10.1.3.1" -t "TREE_NAME" -u
    "admin.b"
    2012-01-12 11:15:21,087 INFO - Migration
    Framework:MigController:getSourceServerTreeCert(): :Copied certificate to
    /opt/novell/migration/plugin/conf/SourceCert.der
    2012-01-12 11:15:21,127 INFO - Migration
    Framework:importSourceTreeCert():Using 10.1.3.1 to import Source Tree
    certificate
    2012-01-12 11:15:21,127 INFO - Migration Framework:Importing Source Tree
    certificate:Importing certificate to Java keystore
    (/opt/novell/migration/plugin/conf/novellStore.keystore)
    2012-01-12 11:15:21,911 INFO - Migration
    Framework:importSourceTreeCert()eleting existing source tree certificate
    using command: /usr/bin/keytool -delete -noprompt -alias 10.1.3.1 -keystore
    /opt/novell/migration/plugin/conf/novellStore.keystore
    2012-01-12 11:15:21,911 INFO - Migration Framework:importSourceTreeCert():
    command: /usr/bin/keytool -import -alias 10.1.3.1 -file
    /opt/novell/migration/plugin/conf/SourceCert.der -noprompt -keystore
    /opt/novell/migration/plugin/conf/novellStore.keystore
    2012-01-12 11:15:22,577 INFO - Migration Framework:SourceServer
    Authentication:Attempting to Connect to Source with the parameters
    2012-01-12 11:15:22,587 INFO - Migration Framework:SourceServer
    Authentication:Authenticating using LDAP(secure)
    2012-01-12 11:15:23,263 INFO - Migration Framework:SourceServer
    Authentication:Authenticating to the Source Server returned true
    2012-01-12 11:15:23,270 INFO - Migration Framework:SourceServer
    Authenticationetecting the source server version
    2012-01-12 11:15:23,315 INFO - Migration Framework:Authentication:Using SMS
    to validate root password for server 10.1.3.1
    2012-01-12 11:15:23,315 INFO - MigUtils:Authentication:Executing
    command:/opt/novell/sms/bin/nbackup -U root -R 10.1.3.1 -cf
    /var/opt/novell/migration/NewProj5/migsrc.sidf /etc/SuSE-release
    2012-01-12 11:15:37,876 INFO - Migration
    Framework:getTargetServerConfigDetails():Finding Target Server eDirectoty
    Tree Name using command: ndsstat -h 10.1.3.2
    2012-01-12 11:15:37,930 INFO - Migration Framework:Getting Target Server
    certificate:Using 10.1.3.2 to retrieve Target Server certificate
    2012-01-12 11:15:37,930 INFO - Migration Framework:Getting Target Server
    certificate:executing command: LC_ALL=en_US.UTF-8 /usr/bin/ruby
    /opt/novell/migration/sbin/getServerCert.rb --server-ip "10.1.3.2"
    --ldap-port 636 --file /opt/novell/migration/plugin/conf/TargetServerCert
    2012-01-12 11:15:40,115 INFO - Migration
    Framework:getTargetTreeCertificate():Attempting to connect to Target with
    the parameters
    2012-01-12 11:15:40,116 INFO - Migration
    Framework:getTargetTreeCertificate():Copy certificate to
    /opt/novell/migration/plugin/conf/TargetCert.der for CLI usage
    2012-01-12 11:15:40,122 INFO - Migration Framework:Importing Target Tree
    certificate:Attempting to connect to Target with the parameters
    2012-01-12 11:15:40,122 INFO - Migration Framework:Importing Target Tree
    certificate:Importing certificate to Java keystore
    (/opt/novell/migration/plugin/conf/novellStore.keystore)
    2012-01-12 11:15:40,122 INFO - Migration
    Framework:importTargetTreeCert():keytool delete command to be executed to
    delete target tree certificate
    2012-01-12 11:15:40,122 INFO - Migration
    Framework:importTargetTreeCert():Executing command : /usr/bin/keytool
    -delete -noprompt -alias 10.1.3.2 -keystore
    /opt/novell/migration/plugin/conf/novellStore.keystore
    2012-01-12 11:15:40,788 INFO - Migration
    Framework:importTargetTreeCert():Using keytool to delete existing
    alias10.1.3.2
    2012-01-12 11:15:40,789 INFO - Migration
    Framework:importTargetTreeCert():keytool command to be executed to store
    target tree certificate
    2012-01-12 11:15:41,486 INFO - Migration
    Framework:importTargetTreeCert():Return Value true
    2012-01-12 11:15:41,486 INFO - Migration Framework:TargetServer
    Authentication:Attempting to connect to Target with the parameters
    2012-01-12 11:15:41,487 INFO - Migration Framework:TargetServer
    Authentication:Authenticating to the Target Server(secure)
    2012-01-12 11:15:41,550 INFO - Migration Framework:Authentication:Using SMS
    to validate root password for server 10.1.3.2
    2012-01-12 11:15:41,550 INFO - MigUtils:Authentication:Executing
    command:/opt/novell/sms/bin/nbackup -U root -l /etc/SuSE-release
    2012-01-12 11:16:35,254 INFO - FILESYSTEM:migfiles:Validating data from
    source path(s) to target path(s) using migfiles
    2012-01-12 11:16:35,254 INFO - FILESYSTEM:migfiles:Executing command:
    /opt/novell/migration/sbin/migfiles --source-server 10.1.3.1 --verbose
    --source-path "@/var/opt/novell/migration/NewProj5/fs/sourcepaths.in"
    --destination-full-path
    "@/var/opt/novell/migration/NewProj5/fs/targetpaths.in" --precheck
    --progress --progress-interval 1 --source-ldap-port 636
    --delete-file-on-restore-error
    2012-01-12 11:16:35,618 INFO - FILESYSTEM:migfiles:Enter the username (e.g
    cn=admin,o=mycompany)
    2012-01-12 11:16:35,618 INFO - FILESYSTEM:migfiles:for the server 10.1.3.1:
    Enter cn=admin,o=b password:
    2012-01-12 11:16:35,618 INFO - FILESYSTEM:migfiles:Enter the username (e.g
    root)
    2012-01-12 11:16:35,619 INFO - FILESYSTEM:migfiles:for the server 10.1.3.2:
    Enter root password:
    2012-01-12 11:16:39,225 INFO - FILESYSTEM:migfiles:Information: Validation
    for migfiles is done successfully
    2012-01-12 11:16:39,230 INFO - FILESYSTEM:migfiles:
    2012-01-12 11:16:39,230 INFO - FILESYSTEM:migfiles:Successfully validated
    data
    2012-01-12 11:16:39,245 INFO -
    FILESYSTEM:Information:****************Migrating files and/or
    trustees****************
    2012-01-12 11:16:39,246 INFO - FILESYSTEM:migfiles:Migrating data from
    source path(s) to target path(s) using migfiles
    2012-01-12 11:16:39,246 INFO - FILESYSTEM:migfiles:Executing command:
    /opt/novell/migration/sbin/migfiles --source-server 10.1.3.1 --verbose
    --source-path "@/var/opt/novell/migration/NewProj5/fs/sourcepaths.in"
    --destination-full-path
    "@/var/opt/novell/migration/NewProj5/fs/targetpaths.in" --session-file
    "/var/opt/novell/migration/NewProj5/fs/migfiles.session" --progress
    --progress-interval 1 --source-ldap-port 636
    --delete-file-on-restore-error
    2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:Enter the username (e.g
    cn=admin,o=mycompany)
    2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:for the server 10.1.3.1:
    Enter cn=admin,o=b password:
    2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:Enter the username (e.g
    root)
    2012-01-12 11:16:39,534 INFO - FILESYSTEM:migfiles:for the server 10.1.3.2:
    Enter root password:
    2012-01-12 11:16:45,078 INFO - FILESYSTEM:migfiles:Information: nbackup:
    precomputing for displaying progress...
    2012-01-12 11:16:45,157 FATAL - FILESYSTEM:migfiles:Fatal: Cannot migrate
    source path /media/nss/DATA/Users/JohnG/: nbackup: Failed to open dataset
    /media/nss/DATA/Users/JohnG/ for backup
    2012-01-12 11:16:45,167 WARN - FILESYSTEM:migfiles:Warning: Going to next
    data set
    2012-01-12 11:16:45,168 ERROR - FILESYSTEM:migfiles:Error: nbackup:
    (libtsafs.so 6.50.0 291) An invalid path was used.
    2012-01-12 11:16:45,242 FATAL - FILESYSTEM:migfiles:Fatal: nbackup command
    failed to complete
    2012-01-12 11:16:45,246 INFO - FILESYSTEM:migfiles:
    2012-01-12 11:16:45,247 ERROR - FILESYSTEM:migfiles:migfiles command
    failed!
    2012-01-12 11:16:45,247 INFO -
    FILESYSTEM:Information:****************End******** ********

  • Sun Cluster, ZFS, Oracle

    Hi, I'm planning an installation of a Solaris Cluster 3.2 with 2 nodes and a Sun storage array 6140: can I use ZFS with Oracle? It's supported? Which is the best solution for soring datafiles? Do I have to install Volume Manager too?
    thanks
    Lorenzo

    Ron,
    I may have misunderstood your question so I'll answer with perhaps more.
    - You will need to use the resource type SUNW.HAStoragePlus to automate/manage the failover of the ZFS zpool between cluster nodes. Refer to the SUNW.HAStoragePlus man page for more info.
    - The HA-Oracle data service will need to have a resource_dependency against the SUNW.HAStoragePlus resource you created earlier for the ZFS Zpool. Refer to the r_properties man page.
    - When creating (or updating) the HA-Oracle data service the VALIDATE method will run on all cluster nodes, however because a SUNW.HAStoragepPlus resource is managing a failover (Zpool) file system, the validation on the cluster node where the Zpool in not imported will be ignored. Consequently, the validation will be successful.
    The combined effect is that if the Oracle alert log is located within the Zpool then it will be available before the HA-Oracle data service attempts to start the Oracle database.
    Regards
    Neil

  • Sun Cluster with Oracle Dataguard

    When I use the logical hostname in the dataguard configuration and go and enable it I get
    ORA-16596: site is not a member of the Data Guard configuration
    I use the physical hostname works ok.
    Has any one got around this

    You may find further informations here:
    <span style="text-decoration: none"><font color="#0000FF">www.oracle-10g.de</font></span></font></strong></span></p>
    <p><span class="bibliotext"><strong>
    <font size="2" face="Arial">

  • Migrate WSUS server from 2003x86 to 2008x64, new hardware, use same name and IP address?

    Searching through the WSUS forums and reading the TechNET migration documentation, I have bits and pieces of information to make this a smooth transition...I think. I have a plan in mind but
    would like the communities input on what I am thinking before moving forward and having it blowup in my face :). <o:p></o:p>
    I have the following currently:<o:p></o:p>
    A single WSUS 3.0 SP2 server, running on Server Win2003x86, using the default WID (susdb.mdf) on the same server. I have SQL 2005 Express installed on this server as well for other services
    but this has no bearing on the WID correct?<o:p></o:p>
    What I would like to do:<o:p></o:p>
    I have a new server (a much better one) that I would like to move WSUS on to, that will be running Server Win2008x64 (I have to setup first). <o:p></o:p>
    Steps that I would like to follow:<o:p></o:p>
    1. I will go through and setup this new server with all M$ updates etc... under a new name (ex. wsusnew) and DHCP acquired IP address and then power it down. <o:p></o:p>
    2. Get on my current WSUS server and backup all current WSUS settings, groups, DB etc... to a network location for temporary storage. Then power it down.<o:p></o:p>
    3. Delete the current WSUS server computer object in AD, DNS entry I will leave because my intension is to give the same IP address to the new WSUS server.<o:p></o:p>
    4. Start the new server, static assign the IP address from the old WSUS server to this new server and then change the name of (wsusnew) to the old servers name, which should be ok sense I deleted
    the AD object in step 3.<o:p></o:p>
    5. After the obvious restart, the new server will have the same name and IP address as the old server. <o:p></o:p>
    6. Now that the new server is up (with same settings name/IP as old server), I will then go through and install the WSUS role on the server and restore my WSUS information.<o:p></o:p>
    Questions:<o:p></o:p>
    1. Step 2 above, is it possible to do this, without making replica servers? I kept reading about this as I was researching doing this, I would rather just copy the DB and folders and simply
    put them in-place on the new server.<o:p></o:p>
    2. Step 6 above, restoring of the data, what is the proper way to do this in the scenarioI described? <o:p></o:p>
    Thank you to anyone who can provide me some information.
    Jeff

    Thank you for the reply, I will follow and let you know. Proabably be next week sometime before I'm able to try though. So look for a reponse then. Thank you again.
    Jeff
    OR...
    You can use the much more simple, much more reliable, and much more proven method of:
    Install new server as a replica of the old.
    Replicate.
    Configure new server as upstream server.
    Point clients to new server.
    Turn off old server after all clients have redirected to the new server.
    For everybody that has tried the backup/restore the database procedure described above, they have encounted complications of one form or another.
    WSUS has a built-in and fully supported comprehensive replication capbility. use it! :-)
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • Migrate user data from SLES10sp3 OES2sp3 to new hardware (again)

    Hi,
    I am running SLES10sp3_64 with OES2sp3_64 and need to migrate the user data
    to a new server running the same OS. I have also updated the SLES & OES to
    the maintenance pack of November 2011.
    The miggui authenticates and I can select the folders for migration. Below
    is an extract of the log file error:
    FATAL -FILESYSTEM:migfiles:Fatal: Cannot migrate source path
    /media/nss/DATA/Users/JohnG/: nbackup: Failed to open dataset
    /media/nss/DATA/Users/JohnG/ for backup
    WARN - FILESYSTEM:migfiles:Warning: Going to next data set
    ERROR - FILESYSTEM:migfiles:Error: nbackup: (libtsafs.so 6.50.0 291) An
    invalid path was used.
    FATAL - FILESYSTEM:migfiles:Fatal: nbackup command failed to complete
    INFO - FILESYSTEM:migfiles:
    ERROR - FILESYSTEM:migfiles command failed!
    Regards
    John

    Hi,
    The log is from /var/opt/novell/migration of the miggui. The begining of the log is about the connection and the authentication to the servers. Which is 100%
    I then also ran the "nbackup" command from a terminal with the same result. I don't think it matters, but I am migrating from-and-to NSS volumes.
    I have looked at the tid and have checked all relevent points and again, no issues. Perhaps this is a "NCP" issue rather than a "miggui" issue.
    Thanks again.
    John
    Originally Posted by kjhurni
    Which log file is this from? Looks like the filesystem log?
    I think there's a migration log and a debug log as well that may show some additional info.
    Have you looked at this TID (slightly old, but I think most of it still applies)
    Troubleshooting data migration issues with miggui

  • Migrate user data from SLES10sp4 OES2sp3 to new hardware

    Hi,
    Running SLES10sp4 with OES2sp3. I just updated all patches on both the
    source and destination servers.
    The command "cat /etc/*release" returns the following info:
    SUSE Linux Enterprise Server 10 (x86_64)
    VERSION = 10
    PATCH LEVEL = 4
    LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64
    Novell Open Enterprise Server 2.0.3 (x86_64)
    VERSION =2.0.3
    PATCHLEVEL = 3
    BUILD
    I then ran "miggui" and connected to both servers and authenticated. I then
    selected "consolidate" and selected the folders to migrate. After clicking
    "start", the system runs for a few second and then fails with the following
    error:
    FATAL - FILESYSTEM:migfiles:Fatal: Cannot migrate source path
    /media/nss/DATA/Users/: nbackup: Failed to open dataset
    /media/nss/DATA/Users/ for backup
    Regards
    John

    ...mmmh, so applying a million patches, updates and rebooting a zillion times, still no success.
    SOLUTION: rsync the two data volumes,
    edited each user and group rights
    Using iManager or Console1 ispretty slow, so I used NwAdmin (old netware management tool, still the fastest)
    (found some interesting rights allocations, fixed them)
    changed login script
    and all is good .... erm, watch this space

  • Is oracle 9.2.0.8 compatible with Sun Cluster 3.3 5/11 and 3.3 3/13?

    Is oracle 9.2.0.8 compatible with Sun Cluster 3.3 5/11 and 3.3 3/13?
    Where can I check compatibility matrix?

    matthew_morris wrote:
    This forum is about Oracle professional certifications (i.e. "Oracle Database 12c Administrator Certified Professional"), not about certifying product compatibility.
    I concur with Matthew.  The release notes for sun cluster and oracle for solaris might tell you.  oracle 9.2.0.8 is out of support on solaris and I recall needing a number of patches to get it to a fit state ... and that is without considering sun cluster.  Extended support for 9.2.0.8 ended about 4 years ago ... this is not a combination I would currently be touching with a bargepole!  You are best to seek on MOS.

  • SBS 2008 - SBS Console and AD errors after migration to new hardware

    Hi there,
    I'm trying to work out how to fix some of the errors and random behaviour I'm experiencing with the SBS 2008 console and AD related matters since I had to quickly migrate SBS 2008 to new hardware using Windows Server Backup after a failure of the old server.
    In my haste to get our email and ftp services back up and running (which use Smartermail and Filezilla respectively instead of Exchange etc) I overlooked the fact that the new server had 3 NICs installed and not one and so restored SBS 2008 and loaded up new
    drivers for those and other hardware that had changed (such as the graphics card and mobo. I have since removed the two additional NICs by disabling them on the mobo).
    Whilst I got the server up and running again with email and ftp services, even though I currently don't use any AD related stuff directly I have since noted that if I try to say view a list of users that I had previously created via the SBS console, more often
    than not it will show no users, and then randomly it will (but when you do see them you can't edit or delete them. I'm aware that I have probably broken a number of golden rules in doing this 'migration' but having a metaphorical gun to my head meant that
    I rushed things out of desperation. 
    Common errors that I experience generally will say things like 'Current security connect is not associated with an Active Directory domain or forest' if I try to list users, or DC not found for domain "xyz.local' etc. I have been searching the net and
    trying out some things to fix this but I'm like a dog chasing its tail as I'm not so clued up on server related issues as I am with workstation problems, so if anyone could at least point me in the right direction I would be very grateful. If you require any
    info from me (eg diag logs etc) I will be happy to provide them!
    Regards,
    Dave

    Hi Dave,
    Based on current situation, please run SBS BPA and fix all that it can find, then monitor the result. For more details, please refer to the following KB.
    Windows SBS Best Practices Analyzer (BPA)
    Meanwhile, please refer to the following article and repair SBS console.
    Repair the Windows SBS 2008 Console
    By the way, I noticed that you had got some error messages (such as: “DC not found for domain” and so on). Would you please let me know complete error messages? In addition, when you migrate SBS 2008 to the new hardware, had you done any preparation for
    that Source Server? For more details, please refer to the following article.
    Migrate Windows Small Business Server 2008 to New Hardware
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Dependency between Sun Cluster 2.2 and Sun hardware ?

    I am evaluating Sun Cluster 2.2 for the usage as clustering software within our project.
    Can anybody say me, if there is a dependency between Sun Cluster 2.2 and Sun hardware ?
    Can I use Sun Cluster 2.2 with other hardware platforms running Sun Solaris 7 and Veritas Volume Manager ?

    I have had this discussion with fellow cluster admins, and we think a port of cluster 2.2 could be done to Intel running Solaris. And here is the BUT, BUT SUN does not support anything except a SPARC based cluster. So currently there is definately a depedancy bewteen the 2.2 software and the hardware.
    Hope this helps
    Heath

  • Apply one non-kernel Solaris10 patch at Sun Cluster ***Beginner Question***

    Dear Sir/Madam,
    Our two Solaris 10 servers are running Sun Cluster 3.3. One server "cluster-1" has one online running zone "classical". Another server
    "cluster-2" has two online running zones, namely "romantic" and "modern". We are tying to install a regular non-kernel patch #145200-03 at cluster-1 LIVE which doesn't have prerequisite and no need to reboot afterwards. Our goal is to install this patch at the global zone,
    three local zones, i.e., classical, romantic and modern at both cluster servers, cluster-1 and cluster02.
    Unfortunately, when we began our patching at cluster-1, it could patch the running zone "classical" but we were getting the following errors which prevent it from continuing with patching at zones, i.e., "romantic" and "modern" which are running on cluster-2. And when we try to patch cluster-2, we are getting similiar patching error about failing to boot non-global zone "classical" which is in cluster-1.
    Any idea how I could resolve this ? Do we have to shut down the cluster in order to apply this patch ? I would prefer to apply this
    patch with the Sun Cluster running. If not, what's the preferred way to apply simple non-reboot patch at all the zones at both nodes in the Sun Cluster ?
    Like to hear from folks who have experience in dealing with patching in Sun Cluster.
    Thanks, Mr. Channey
    p.s. Below are output form the patch #145200-03 run, zoneadm and clrg
    outputs at cluster-1
    root@cluster-1# patchadd 145200-03
    Validating patches...
    Loading patches installed on the system...
    Done!
    Loading patches requested to install.
    Done!
    Checking patches that you specified for installation.
    Done!
    Approved patches will be installed in this order:
    145200-03
    Preparing checklist for non-global zone check...
    Checking non-global zones...
    Failed to boot non-global zone romantic
    exiting
    root@cluster-1# zoneadm list -iv
    ID NAME STATUS PATH BRAND IP
    0 global running / native shared
    15 classical running /zone-classical native shared
    - romantic installed /zone-romantic native shared
    - modern installed /zone-modern native shared
    root@cluster-1# clrg status
    === Cluster Resource Groups ===
    Group Name Node Name Suspended Status
    classical cluster-1 No Online
    cluster-2 No Offline
    romantic cluster-1 No Offline
    cluster-2 No Online
    modern cluster-1 No Offline
    cluster-2 No Online

    Hi Hartmut,
    I kind of got the idea. Just want to make sure. The zones 'romantic' and 'modern' show "installed" as the current status at cluster-1. These 2 zones are in fact running and online at cluster-2. So I will issue your commands below at cluster-2 to detach these zones to "configured" status :
    cluster-2 # zoneadm -z romantic detach
    cluster-2 # zoneadm -z modern detach
    Afterwards, I apply the Solaris patch at cluster-2. Then, I go to cluster-1 and apply the same Solaris patch. Once I am done patching both cluster-1 and cluster-2, I will
    go back to cluster-2 and run the following commands to force these zones back to "installed" status :
    cluster-2 # zoneadm -z romantic attach -f
    cluster-2 # zoneadm -z modern attach -f
    CORRECT ?? Please let me know if I am wrong or if there's any step missing. Thanks much, Humphrey
    root@cluster-1# zoneadm list -iv
    ID NAME STATUS PATH BRAND IP
    0 global running / native shared
    15 classical running /zone-classical native shared
    - romantic installed /zone-romantic native shared
    - modern installed /zone-modern native shared

Maybe you are looking for