Bug 1124147 - [DOCS] Expand the backup section in the A&C Guide
Summary: [DOCS] Expand the backup section in the A&C Guide
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Documentation
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 6.2.0
Assignee: Vidya
QA Contact: Lukáš Petrovický
Dawn Eisner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-29 05:36 UTC by Vikram Goyal
Modified: 2016-10-14 14:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Vikram Goyal 2014-07-29 05:36:59 UTC
Expand the backup section info in the Admin and Config Guide based on email thread in the SME list:

Hi Vikram,

I echo Jeremy’s comments. I come across lot of customers who have not yet adopted Git as their version control system.
They actually are concerned when we tell them that BRMS/BPMS is backed by Git. We tell them that it is abstracted away from them for the most part.
So if we can provide a good approach for backing up the repository, it will help ease their concerns.

I would also take this one step further and add some guidelines around how to maintain their maven repository for their BRMS/BPMS deployments.

Thanks
Balaji

On Jul 28, 2014, at 9:40 PM, Jeremy Phuah <jphuah@redhat.com> wrote:

> Hi Vikram, 
> 
> For some customers using our product may be their first exposure to git.  As such it would be good for us to not assume that they know it all. It could be a simple section with all the relevant links to recommended documents.  
> 
> 
> 
> Regards, 
> 
> Jeremy Phuah
> Middleware Domain Architect,  ASEAN
> 
> 
> Vikram Goyal <vigoyal@redhat.com> wrote:
> 
> Hi Balaji,
> 
> Do you think there should be a recommended BRMS backup strategy in the documentation? 
> 
> Please correct me if I am wrong but since the backup is essentially a git backup, there is nothing special that needs to happen and there is plenty of information for that available otherwise.
> 
> If not, I am happy to consider devoting a section about this in the Developer Guide.
> 
> ----
> Vikram Goyal,
> Docs Lead - BRMS/BPM Suite,
> Red Hat Brisbane, Australia
> vikram@redhat.com
> 
> ----- Original Message -----
> From: "Balaji Rajam" <brajam@redhat.com>
> To: "sme-brms" <sme-brms@redhat.com>
> Sent: Tuesday, July 29, 2014 8:39:30 AM
> Subject: BRMS 6.0 Backup strategy
> 
> Since now BRMS is backed by Git, what is the recommended strategy for backing it up. Do we periodically do git clone or git bundle to do it? Or is there a better seamless way to do this?
> Maybe setup BRMS on a SAN mount so it has resiliency? 
> 
> Our documentation doesn’t seem to provide any such guidance. I would appreciate any input in this regard.
> 
> Thanks
> Balaji
> 
>


Note You need to log in before you can comment on or make changes to this bug.