• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Configuration Backup. Advise please

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We would like to have your advise for the below.

Our team have written configuration scripts for functionalities such as creation of JDBCProviders,URLproviders,ResEnvProviders. Also, scripts for configuring JVM and modifying variables etc.

All of our scripts scopes the cluster and not individual nodes.

Now before using the scripts, we will surely need to take a backup of the existing configuration.

1. Do you recommend taking the backup using BackUpConfig.sh or do you recommend any other way of taking the backup?

2. As we are targetting the cluster we are not sure of taking the backup as a whole. If it is an individual node, we can use the above script. Do we take it individually?

3. Can you specify the steps that need to be taken before we execute the scripts so that we can revert back for any failure.
 
Ranch Hand
Posts: 126
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here are my comments to your 3 questions.

1. The best way to do it to have a wrapper sciprt which invokes BackUpConfig.sh and place it on the cront tab of Dmgr. BackUpConfig.sh script backups all clusters, resources and applications.

2. If you are using a Network Deployment, then just running on the DMGR is sufficient. If its a standalone servers, then run it on each individual servers.

3. You can use restoreConfig.sh to restore your configuration but be aware that if you restore the configuration to a directory that is different from the directory that was backed up when you performed the backupConfig command, you might need to manually update some of the paths in the configuration directory.
For example take serverindex.xml file, it has the hostname or ipaddress.

Anant
 
reply
    Bookmark Topic Watch Topic
  • New Topic