Disaster Recovery Scripts for Managed Server MSI Startup

I am trying to get some custom start scripts created for each of my managed servers in the event the admin console is down or server gets hosed. We use nodemanager to start the managed servers in a Windows environment. I have about 8 managed servers and they all use the same nodemanager classpath but all have different server start arguments (different memory settings, etc....) so I need to make different custom scripts for each.
Verbose Garbage Collection to Determine Heap Size .....this thread by Jay has been very helpful but so far I am just getting kicked back to the syntax screen like something is wrong in my script. Attached is the script and the output when I run it. Any help would be appreciated...thanks.
startManagedFPCE1.cmd contents
java.exe -Xms400m -Xmx400m -classpath $CLASSPATH -Dweblogic.Name=FPCE1 -Dbea.home="C:\Oracle\Middleware" -Dweblogic.management.username=beaadmin -Dweblogic.management.password=beaadminxxx -Dweblogic.management.server=http://sitportal1:8098 -Djava.library.path=c:\Oracle\Middleware\wlserver_10.3\server\bin -Dweblogic.ext.dirs=C:\Oracle\Middleware\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_wlp1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_oepe1111\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\wlportal_10.3\p13n\lib\system;C:\Oracle\Middleware\wlportal_10.3\light-portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\lib\system;C:\Oracle\Middleware\wlportal_10.3\analytics\lib\system;C:\Oracle\Middleware\wlportal_10.3\apps\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\deprecated\lib\system;C:\Oracle\Middleware\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\Oracle\Middleware\wlportal_10.3\portal\lib\security
Results of running above script:
C:\Oracle\Middleware\user_projects\domains\SIT11\servers\FPCE1>java.exe -Xms400m -Xmx400m -classpath $CLASSPATH -Dweblogic.Name=FPCE1 -Dbea.home="C:\Oracle\Middleware" -Dweblogic.management.username=b
eaadmin -Dweblogic.management.password=beaadminsit11 -Dweblogic.management.server=http://sitportal1:8098 -Djava.library.path=c:\Oracle\Middleware\wlserver_10.3\server\bin -Dweblogic.ext.dirs=C:\Oracle
\Middleware\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_wlp1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_oepe1111\profiles\default\
sysext_manifest_classpath;C:\Oracle\Middleware\wlportal_10.3\p13n\lib\system;C:\Oracle\Middleware\wlportal_10.3\light-portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\portal\lib\system;C:\Oracle\M
iddleware\wlportal_10.3\info-mgmt\lib\system;C:\Oracle\Middleware\wlportal_10.3\analytics\lib\system;C:\Oracle\Middleware\wlportal_10.3\apps\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\dep
recated\lib\system;C:\Oracle\Middleware\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\Oracle\Middleware\wlportal_10.3\portal\lib\security
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-server to select the "server" VM
-hotspot is a synonym for the "server" VM [deprecated]
The default VM is server.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options

"bharat nagwani" <[email protected]> wrote:
>
Hi,
Configuration: Weblogic 8.1SP2 on Windows 2000, 1 admin server and 14
managed
servers
whats the right way from these 2 scenarious to create a domain on managed
server
1. create domain on managed server using configuration wizard. Then point
to this
domain from administration server remote start tab(root directory). This
is what
we do so far.This is the best way to create managed servers for your domain.
>
2. Just enter user_projects/domains folder/$domain name$ in remote start
tab(root
directory)
on admin server console and when you start the managed server from
admin console
the domain folder and files will be created.
Yes, the managed server is started in this case at the root directory you specified.
The difference is in the
1. first case we see all scripts like startManagedWeblogic, setenv, boot.properties
etc
this may help(we still dont know) if one wants to bring up managed
server
manually using
startManagedServer.bat without using node manager.Yes, that is correct. You will need to edit the startManagedServer.bat to include
the admin server URL, username and paswword..
>
2. second case only 2-3 files get created like msi-config.xml and SerializedSystemIni.dat
Basically first case is superset of second case.
What is the experience of people in this regard?
thanks much
bharat

Similar Messages

  • Disaster Recovery Plan for BW Production db

    Hello Experts,
    We at IP are trying to evaluate and institute a sound and
    cost-effective disaster recovery plan for the BW production system.
    In this regard, we would like to hear from you(or from your infrastructure folks) about the experience(s) at
    client sites of such scenarios for BW.
    We are specifically interested in knowing answers to:
    0. Customer Name
    1. Do you have currently have Disaster Recovery Plan for BW Production?.
    2. How large is your BW production database?
    3. Is the alternate server being replicated real time or using tapes or ......?
    4. What are your target service levels?
    5. Location specifics or any other pertinent info.
    Any input is highly appreciated.
    Thanks in advance,
    Kumar Gudiseva.

    I don't think people will give this information out - especially the customer name will certainly not be published in a public forum.
    For DR plans check http://service.sap.com/ha
    Markus

  • Disaster Recovery Plan for BW Production

    Hello Experts,
    We at IP are trying to evaluate and institute a sound and
    cost-effective disaster recovery plan for the BW production system.
    In this regard, we would like to hear from you(or from your infrastructure folks) about the experience(s) at
    client sites of such scenarios for BW.
    We are specifically interested in knowing answers to:
    1. Do you have currently have Disaster Recovery Plan for BW Production?.
    2. How large is your BW production database?
    3. Is the alternate server being replicated real time or using tapes or ......?
    4. What are your target service levels?
    5. Location specifics or any other pertinent info.
    Any input is highly appreciated.
    Thanks in advance,
    Kumar Gudiseva.
    Edited by: Kumar Gudiseva on Jan 9, 2008 3:35 PM

    Hi,
    The disaster recovery strategy should include a backup and restore plan that determines which data should be backed up and the procedures that will be used to recover it.
    Please check these links:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/001ef297-9bbf-2910-bbaa-babedc1b01ca
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6efca1a6-0301-0010-6f9d-82cf87340e45
    /people/nicholas.holshouser/blog/2006/09/07/the-square-root-of-an-it-disaster-is-recovery
    Hope it helps.
    Regards,
    Mona

  • Planning Disaster Recovery Site for SAP ERP ECC 6.0

    Dear All,
    I am planning for DR ( Disaster Recovery ) Site. Our current environment is
    Production Site
    OS        : AIX 5.3
    DB        : IBM DB2      version 8.2
    SAP      : SAP ERP 6.0 ECC 6
    Disaster Recovery Site
    OS        : AIX 6.1
    DB        : IBM DB2      version 9.5
    SAP      : SAP ERP 6.0 ECC 6
    I have following confusion in planning the solution.
    1 - If I export the data at db level from production site and import that data in DR Site ...  than DR Site will be equivalent to Production Site or not.
    2 - if answer of point 1 is yes then for SAP DR ...  HADR is the best solution or there is any other better solution exist.
    regards
    Syed Saifuddin

    Hello Syed,
    If you export from the prod db and import into the disastor recover db then they will be the same provided that SAP environment is all the same. I would recommend that you update the prod side to the same db2 release and fixpack level as soon as possible though as 9.5 (or even better 9.7) has some advanced features that make administration alot easier and save much space.
    HADR would be the best setup for disaster recovery in db6 environment.
    Check the following documentation which should answer most of your queries.
    SAP Note 960843 # DB6:Installation SA MP
    "High Availability and Disaster Recovery Options for DB2 on Linux, UNIX,
    and Windows"
    http://www.redbooks.ibm.com/redbooks/pdfs/sg247363.pdf
    "Data Recovery and High Availability Guide and Reference"
    http://publibfp.boulder.ibm.com/epubs/pdf/c1042280.pdf
    Please update if questions remain unanswered.
    Regards,
    Paul

  • Best Way to setup a disaster Recovery site for a logical standby database

    I have a logical standby DB (L1DB) as a reporting db on the same machine as the primary (P1DB). We are planning on building a disaster recovery site with similar hardware and potentially have disk mirroring of atleast the redo log files.
    The DR site can hold an additional physical standby (S1DB) for the primary (P1DB). I am trying to understand what would be the best way to setup the Disaster Recovery site for the L1DB logical stdby. Ideally, when the disaster happens, and I no longer have P1DB and L1DB, I should be able to switch to S1DB as the new primary. But how do I setup to have a L2DB that takes the place of L1DB and has its contents and can be setup as a logical standby of S1DB?

    If you already setup one logical standby, then you know how it works, so not sure what question you are asking ?
    Personally I would setup L2DB as a standby of the original primary P1DB. Having downstream standby databases complicates things, and adds additional lag between primary transaction time and L2DB apply.

  • Disaster Recovery Plan for SAP BW

    Dear All,
    We are planning for robust Disaster Recovery Site for BW . We have similar  R3 & BIW  servers at DR site at different location and data is being copied every 3 Hrs.
    R3 & BIW at DR site is exact replica of primary site. When primary site is down DR site will act as a primary. In that case we might face data loading issue from DR R3 to DR BW because of source system change. If we change the source system then we loose data consistency and might need initialisation. We are looking for the solution which will involve less efforts to up the system.
    Does anyone has done this or overcome this situation ?
    Regards,
    Manish

    Hi Raman,
    We are doing disaster recovery test for both ECC and BW systems so whole PR system switched to DR system for some time and then back to PR system. so in that case what precautions we need to take from BW side?
    Thanks
    Bhavin

  • Install window services for managed server

    hi all, i wanted to install window services for managed server. Can anyone advice me how to do it? My weblogic version is 10. Thanks in advance.

    Hi,
    Please refer to the following link....it might be helpful: http://weblogic-wonders.com/weblogic/2010/03/13/managed-server-as-windows-service/

  • Requirements for managing Server Core

    Hello,
    What are the requirements for managing Server Core? We have a Windows 2008 functional level forest and domain and were thinking about installing 2012 server core servers but weren't sure we'd be able to manage them with 2008 server or Windows 7 tools.
    Thanks,
    Robert

    Hi Robert,
    To remotely manage a server in server core mode, we can use the following ways:
    Remotely using Windows PowerShell
    Remotely using Server Manager
    Remotely using an MMC snap-in
    Remotely with Remote Desktop Services
    However, we can’t use server manager in Windows Server 2008 or in RSAT for Windows 7 to remotely manage Windows Server 2012 in server core mode. To
    use server manager to remotely manage Windows Server 2012 in server core mode, we must use the version of Server Manager in Windows Server 2012 or that is available as part of the Remote Server Administration Tools for Windows 8 download package.
    Regarding how to manage a Windows Server 2012 in server core mode, the following articles can be referred to for more information.
    Manage a Server Core Server
    http://technet.microsoft.com/en-us/library/jj574205.aspx#BKMK_1_1
    Server Core remote management – Part 1
    http://4sysops.com/archives/server-core-remote-management-part-1/
    Best regards,
    Frank Shen

  • Startup problems for managed server

    I am starting up a managed server - although I havent designated this server
              to be in a cluster yet and on startup, I get the exception below.
              Does anyone have any suggestions as to what the cause might be - or what I
              should investigate to narrow it down.
              I am using WLS6.1 GA (it is an eval license).
              Cheers, Nick
              <31-Aug-01 01:44:01 BST> <Info> <WebLogicServer> <Using low strength
              (exportable) SSL.>
              <31-Aug-01 01:44:02 BST> <Info> <Dispatcher> <Exception thrown by rmi
              server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid:
              '-8115623877909240659S:192.168.0.2:[8080,8080,8090,8090,8080,8090,-1]:CCOMDe
              v:CCOMServer01', oid: '9', implementation:
              'weblogic.jndi.internal.RootNamingNode@2130c2''
              javax.naming.NameNotFoundException: Unable to resolve
              weblogic.transaction.resources.CCOMServer01. Resolved:
              'weblogic.transaction.resources' Unresolved:'CCOMServer01' ; remaining name
              at
              weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
              ode.java:802)
              at
              weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
              at
              weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129
              at
              weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
              at
              weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
              at
              weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
              at
              weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
              at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
              Source)
              at
              weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
              at
              weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
              :93)
              at
              weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
              at
              weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
              at
              weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
              at
              weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
              at
              weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
              :253)
              at
              weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
              :220)
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
              at $Proxy6.list(Unknown Source)
              at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:151)
              at
              weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(Serv
              erCoordinatorDescriptor.java:1008)
              at
              weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoo
              rdinatorDescriptor.java:944)
              at
              weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCo
              ordinatorDescriptor.java:936)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              <31-Aug-01 01:44:02 BST> <Info> <Connector> <Initializing J2EE Connector
              Service>
              <31-Aug-01 01:44:02 BST> <Info> <Connector> <J2EE Connector Service
              initialized successfully>
              

    Make sure you have admin server running when you start your managed server.
              Also, in your admin server you have already configured this managed server
              name and it's ip address.
              Wenji
              "Movva" <[email protected]> wrote in message
              news:[email protected]...
              > Hi,
              > Iam also having the same problem. Iam starting the weblogic servers
              > as windows 2K services. The service install script is as follows:
              > (Infact it is the same in case of starting the servers using scripts
              > in the cmd shell also).
              > ------------------------------------------------------
              > @echo off
              >
              > SETLOCAL
              >
              > cd C:\bea\wlserver6.0\config\cdes
              >
              > rem *** Set Classpath to load Weblogic Classes
              > set
              CLASSPATH=.;C:\bea\wlserver6.0\lib\weblogic_sp.jar;C:\bea\wlserver6.0\lib\we
              blogic.jar;C:\bea\mssqlserver4\classes;C:\bea\mssqlserver4\license
              >
              > rem *** Set Command Line for service to execute
              > rem *** %JAVA_HOME%\java will automatically be prepended.
              > rem C:\bea\jdk130\bin\java -ms128m -mx256m -classpath
              >
              .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;C:\bea\mssqlserver4\classes;C:\be
              a\mssqlserver4\license;
              > -Dweblogic.Domain=cdes -Dweblogic.Name="cdesServer11j2"
              > "-Dbea.home=C:\bea" -Dweblogic.management.server="156.15.59.38:7001"
              > "-Djava.security.policy==C:\bea\wlserver6.0/lib/weblogic.policy"
              > -Dweblogic.management.password=weblogic weblogic.Server
              >
              > set CMDLINE="-ms64m -mx256m -classpath \"%CLASSPATH%\"
              > -Dweblogic.Domain=cdes -Dweblogic.Name=cdesServer11i1
              > -Djava.security.policy==\"C:\bea\wlserver6.0/lib/weblogic.policy\"
              > -Dbea.home=\"C:\bea\" -Dweblogic.management.server=156.15.59.38:7001
              > -Dweblogic.management.password= weblogic.Server"
              >
              > rem *** Install the service
              > "C:\bea\wlserver6.0\bin\beasvc" -install -svcname:cdesServer11i1
              > -javahome:"C:\bea\jdk130" -execdir:"C:\bea\wlserver6.0"
              > -extrapath:"C:\bea\wlserver6.0\bin" -cmdline:%CMDLINE%
              >
              > ENDLOCAL
              > ------------------------------------------------------ END OF FILE
              >
              > Any problem in this script ? please let me know.
              >
              > Thnx in Adv,
              > Movva
              >
              >
              > "Prasad Peddada" <[email protected]> wrote in message
              news:<[email protected]>...
              > > Did you use scripts to start servers or do you have your own scripts. If
              > > have your own, could you tell me how you did it.
              > >
              > > -- Prasad
              > >
              > > "Nick Minnutello" <[email protected]>
              wrote
              > > in message news:[email protected]...
              > > > I am starting up a managed server - although I havent designated this
              > > server
              > > > to be in a cluster yet and on startup, I get the exception below.
              > > >
              > > > Does anyone have any suggestions as to what the cause might be - or
              what I
              > > > should investigate to narrow it down.
              > > >
              > > > I am using WLS6.1 GA (it is an eval license).
              > > >
              > > > Cheers, Nick
              > > >
              > > > <31-Aug-01 01:44:01 BST> <Info> <WebLogicServer> <Using low strength
              > > > (exportable) SSL.>
              > > > <31-Aug-01 01:44:02 BST> <Info> <Dispatcher> <Exception thrown by rmi
              > > > server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid:
              > > >
              > >
              '-8115623877909240659S:192.168.0.2:[8080,8080,8090,8090,8080,8090,-1]:CCOMDe
              > > > v:CCOMServer01', oid: '9', implementation:
              > > > 'weblogic.jndi.internal.RootNamingNode@2130c2''
              > > > javax.naming.NameNotFoundException: Unable to resolve
              > > > weblogic.transaction.resources.CCOMServer01. Resolved:
              > > > 'weblogic.transaction.resources' Unresolved:'CCOMServer01' ; remaining
              > > name
              > > > ''
              > > > at
              > > >
              > >
              weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
              > > > ode.java:802)
              > > > at
              > > >
              > >
              weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
              > > > at
              > > >
              > >
              weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129
              > > > )
              > > > at
              > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
              > > > at
              > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
              > > > at
              > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
              > > > at
              > > > weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
              > > > at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
              > > > Source)
              > > > at
              > > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
              > > > at
              > > >
              > >
              weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
              > > > :93)
              > > > at
              > > >
              > >
              weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
              > > > at
              > > > weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
              > > > at
              > > >
              weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
              > > > at
              > > >
              weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
              > > > at
              > > >
              > >
              weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
              > > > :253)
              > > > at
              > > >
              > >
              weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
              > > > :220)
              > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
              > > > at $Proxy6.list(Unknown Source)
              > > > at
              > > weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:151)
              > > > at
              > > >
              > >
              weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(Serv
              > > > erCoordinatorDescriptor.java:1008)
              > > > at
              > > >
              > >
              weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoo
              > > > rdinatorDescriptor.java:944)
              > > > at
              > > >
              > >
              weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCo
              > > > ordinatorDescriptor.java:936)
              > > > at
              weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > >
              > > > <31-Aug-01 01:44:02 BST> <Info> <Connector> <Initializing J2EE
              Connector
              > > > Service>
              > > > <31-Aug-01 01:44:02 BST> <Info> <Connector> <J2EE Connector Service
              > > > initialized successfully>
              > > >
              > > >
              

  • Disaster recovery of remaining OVM server

    Hi,
    I hope some of you can help me with some disaster recovery tests I have to do shortly.
    The environment has 2 OVM servers: servre1 and server2 in a server pool.
    Server1 has the cluster filesystem shared to it via multiipathing, and in turn, server1 shares the repository and cluster fs with server2 via NFS.
    In the meantime, there are other LUNS shared with just server2, which are being replicated with the repository and cluster fs that is currently being used.
    If server1 "dies" and this is easy to simulate as just shutting it down, it will stop sharing the repository and fs with server2, the server pool will have errors, and so will server 1 (it cannot be contacted), and so will server2 (it has lost access to repository and cluster fs).
    Oracle documentation explains very clearly how to add and remove server pools and servers neatly, but it makes no mention of how to clean up a server in order to reuse in on a new server pool, with a new repository, in this case, the replicated LUNs that were only in server2.
    Has any of you done something similar to this? Do I have to go into the OVM Manager database at row level to delete every mention of the old repository? Is there a way of cleaning up the server2 for reuse (other than reinstalling)? In OVM 2.2 there was a cleanup.py script, but I didn´t find such script in 3.0.3...
    Any suggestions on how to test this will be welcome. If I have overlooked some useful documentation on this, please point me to it...
    Regards,
    T.

    Dan,
    do you mean
    sh ./ovm_upgrade.sh dbuser=ovs dbpass=<password> --fixup
    Regards,
    T.

  • Disaster Recovery on another Sun Server

    I have a question in regards to disaster recovery of Sun servers. We have a client that hosting applications within Sun T platform which utilizes LDOM configuration. These boxes host around five guests.
    Currently we use a software called EMC HomeBase(http://www.emc.com/backup-and-recovery/homebase/homebase.htm) to enhance our DR recovery by profiling the Sun box and transmitting that profile to our DR vendor. DR vendor in turn with help from EMC will install the OS, patch level and apply that profile to setup the system with NIC information, file systems and other components so we would only
    need to restore our data from NETBACKUP and don't do any system recovery.
    Unfortunately, EMC does not support LDOMs nor containers. Now my question is if Sun has a way around this? Please note that the servers will be different models at DR. for example T5220 to a T5440 or V890 to V490.

    It'd be rather easy to manually install same LDOM configuration on DR site... all EMC seems to be doing is getting the profile & then someone is creating setup manually...
    Anyways... here you go:
    Backup & Recovery of guest domain
    Archive and backup the guest domain configuration:
    ldm list-constraints -x <ldom> > <ldom>.xml
    Backup the guest domains over the network with backup software as regular server
    Restore the guest domain configuration, assuming that your VSW and VDS resources are available:
    ldm add-domain -i <ldom>.xml
    Make sure that you have enough VCPU, MAU, and Memory to boot your guest domain.
    Jumpstart guest domain and install backup client. Restore data from backup.
    Backup LDOM configuration
    You can take the backup of the configuration using "ldm add-spconfig saveconfigurtion" command which will store in SP of the server.
    For taking the backup of the individual domain use "ldm ls-constrants >> filename.xml" it will give the xml output just redirect it to a file.
    While creating the domain again use "ldm create ldomname -f filename.xml"
    You can not create control domain by the above procedure we hve to configure manualy or even if your control domain crashed install new OS and install LDOM Manager in the Base OS create /etc/hostname.vsw0 & vsw1 files poweroff the server from SP. set bootmode config=saveconfiguration
    How to backup the primary domain
    Backup the LDM db files in: /var/opt/SUNWldm
    Archive and backup the primary domain configuration:
    ldm list-constraints -x primary > primary.xml
    Backup the primary domains over the network with backup software as regular server.
    How to recover primary domain
    Update firmware
    Install backup client & LDM software
    Restore /var/opt/SUNWldm
    Start up LDM services
    If all goes well, the LDM config will be read and you will be in initial configuration mode. Save the config to the hypervisor and
    reboot. If not, parse the primary.xml file to recreate the primary domain configuration, save config, and reboot.
    Restore guest domain configs and data. Then bring up guest domains.

  • Disaster Recovery Solutions for KVM Hypervisors

    Thanks to all the help and ideas in my Server Specs for Virtual Environment thread, I think a hyper-converged solution is going to be the right fit for my small business environment. I’m looking at hyper-converged systems because it reduces the overall management of the virtual world. This is important for me as well since I am the “all-one-IT-guy” running everything from programming, help desk support, and sys admin roles here at the office.
    Question - Scale Computing offers a disaster recovery solution that allows one to have a secondary HC3 stack at a different geographical location. Thus if one location gets wiped out, you can fall back to your secondary.
    My company does not have a another geographical location, so I was looking at data center solutions to replicate to. It appears that most data centers only support Hyper-V and...
    This topic first appeared in the Spiceworks Community

    Thanks to all the help and ideas in my Server Specs for Virtual Environment thread, I think a hyper-converged solution is going to be the right fit for my small business environment. I’m looking at hyper-converged systems because it reduces the overall management of the virtual world. This is important for me as well since I am the “all-one-IT-guy” running everything from programming, help desk support, and sys admin roles here at the office.
    Question - Scale Computing offers a disaster recovery solution that allows one to have a secondary HC3 stack at a different geographical location. Thus if one location gets wiped out, you can fall back to your secondary.
    My company does not have a another geographical location, so I was looking at data center solutions to replicate to. It appears that most data centers only support Hyper-V and...
    This topic first appeared in the Spiceworks Community

  • [Disaster recovery] Moving the Essbase server to another physical server

    Hi All,
    I have 3 Solaris servers part of the EPM 11.1.2.1 environment:
    Server1.company.com:
    Foundation services, APS, EAS
    Server2.company.com:
    Essbase Server, Essbase Studio Server.
    Installation done on a SAN disk using user ID hypadmin
    Server3.company.com:
    *Nothing installed here*.
    Its the standby server in case Server2 goes down.
    Note: I couldn't find any documentation for my below approach... So please understand the risk involved before attempting the same.
    Pre-disaster recovery:
    I copy the home directory of hypadmin from Server2 to Server3.
    During disaster recovery:
    I update the Essbase server host name from Server2.company.com to Server3.company.com and similarly update the opmn.xml file.
    Finally mount the SAN onto Server2 and start up the services.
    Has anyone done the same..? Have you faced any issues? Is there a better way of doing this?
    Thanks
    Regards,
    Kent

    Hi,
    I believe the usual way of doing this is to have a DR environment, rather than just one server (so for you you would have 2 DR servers). The DR environment has hosts file entries to map Production host names to DR IP addresses.
    In DR you are connected to a separate SQL instance and you install and configure the products exactly as you would for Production (exactly the same hostnames).
    Then when you are finished you shut down the DR environment and turn on SQL log shipping between the Production and DR databases.
    If your Production environment goes down you stop the SQL log shipping, then you can bring up DR and change the DNS names (as required) to give your users access.
    For Essbase storage you can either backup Production cubes to DR or mount the Production SAN in DR. The only problem with the latter is that if Production goes down and the SAN is lost you can't bring up DR fully either.
    Let me know if you still have questions.
    -Dan

  • Disaster Recovery scenario for MSCS Production system.

    Hi
    Our production system is on win2008/sql2008 MSCS. We decided to install a disaster recovery system. We will use a database replication software. If we have a standalone production system, not a MSCS system, i know that i can install Disaster Recory system with same SID and hostname and i don't need any homogeneous system copy procedure to switch to DR system. But in our scenario, we have many hostname (sap cluster group, sql cluster group, hostnames of nodes... etc.).
    How can i install my DR system (which hostname.. etc.) to make our DR scenario easy?
    Best Regards...

    You May have trouble with RFC connections:
    So, one possible solution is, your new server name(Host name) should be your message server name to minimise the trouble and you have to maintain this for all RFC connections (to Prod ECC system) to virtual host which could be message server.
    If I could think if any other possible issues, I will update.
    Krishna

  • Problem adding classpath for managed server in 10.3

    Hi All,
    I have a managed server that uses startup classes. According to the documentation, you have to put the absolute path to the startup classes in the server's classpath. I go to the server's configuration and the Server Startup tab to enter the classpath information. When I do this and try to start the managed server I receive the following message:
    <Jun 30, 2009 8:24:47 AM PDT> <Error> <NodeManager> <BEA-300048> <Unable to star
    t the server IntegrationServer : Exception while starting server 'IntegrationSer
    ver': java.io.IOException: Server failed to start up. See server output log for
    more details.>
    The server output log shows:
    <Jun 30, 2009 8:24:47 AM> <Debug> <NodeManager> <Waiting for the process to die: 4288>
    <Jun 30, 2009 8:24:47 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    <Jun 30, 2009 8:24:47 AM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    If I don't put the classpath in, the managed server will start up, but will throw classnotfound exceptions for the start classes.
    I am not sure what I am doing wrong.
    We are in a time crunch so any help would be greatly appreciated.
    Thank you,
    Greg

    I've seen something like this before on a windows machine where the PATH environment variable had some additional values which contained spaces.
    If it's a windows machine, could you check your path and see if there is more there then the default:
    %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
    In my case there where values like c:\program files\.... and WL couldnt handle that apparently.
    when I removed them from my windows path it was fixed.
    the logging you showed, is it the MS logging ?
    Could you post the nodemanager logging as well, maybe it has more detailed information.

Maybe you are looking for