Backup PINsafe on a Active/Passive appliance

From Swivel Knowledgebase
Revision as of 12:52, 11 May 2017 by Admin (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Overview

To make a backup of Swivel, the Apache Tomcat process must first be stopped. On an Active/Passive Appliances this would lead to the standby server taking over, the Apache Tomcat on the primary system would be unmounted and mounted on the standby thus making the file system unavailable on the primary. To stop this we need to stop the mon process on the standby. See also Backup PINsafe How to Guide.


Prerequisites

Swivel Active/Passive appliances


Symptoms

Backup required but file system is not mounted


Solution

On the Standby

 service mon stop

On the Primary

 service tomcat5 stop

Backup PINsafe, usually under /usr/local/apache-tomcat-5.5.20/webapps/pinsafe

On the Primary

 service tomcat5 start

On the Standby

 service mon start

Check to ensure that Server appliance is running ok

1). Login to the admin console

Expected Results:

2). Run drbd check

 cat /proc/drbd

Expected results, look for Primary/Secondary status

primary

 drbd driver loaded OK; device status:
 version: 0.7.14 (api:77/proto:74)
 SVN Revision: 1989 build by buildcentos@build-i386, 2006-03-18 19:03:54
 0: cs:Connected st:Primary/Secondary ld:Consistent
   ns:8492552 nr:22716 dw:8515268 dr:284982 al:106 bm:2286 lo:0 pe:0 ua:0 ap:0

secondary

 drbd driver loaded OK; device status:
 version: 0.7.14 (api:77/proto:74)
 SVN Revision: 1989 build by buildcentos@build-i386, 2006-03-18 19:03:54
 0: cs:Connected st:Secondary/Primary ld:Consistent
   ns:22716 nr:10565672 dw:10588388 dr:36158 al:20 bm:128 lo:0 pe:0 ua:0 ap:0