Frequently asked questions(FAQ's)
Jira cloud data backed-up is retained for a period of upto 3 years
A backup job automatically runs every 24 hours and 12:00 AM UTC. You as the administrator do not have to do anything to schedule the backups, they occur automatically.
The first backup of Issues can take long time depending on number of issues and attachments to be backed up. All the subsequent backups after that are forever incremental which means it will always transfer only updated / created issues & attachments since previous successful backup.
Yes we offer a free trial for a minimum of 30 days and a maximum of 59 days. The exact number of days is determined by Atlassian based on your billing cycle.
Once you install the app from the marketplace, the first backup is automatically triggered and your future daily backups are immediately scheduled.
The backend infrastructure we have built is all server less, it takes a minute or so for a new “container” to get spun up to get the job worked on. This is true for both backups and restores.
Revyz backs up your Jira data into Revyz’s Amazon Web Services (AWS) tenant. The supported AWS data centers are:
us-east-1 (Northern Virginia)
We plan to add support for additional AWS data centers over the course of time.
Data security is paramount at Revyz. We ensure data is encrypted in-motion and at-rest.
Data at-rest is encrypted using industry standard envelope encryption scheme.
Transport Layer Security (TLS) 1.2 to protect data in-motion over the internet
TLS is terminated in Revyz’s cloud compute process
Tenant specific and unique key encryption key (KEK) is created and stored in AWS Key Management System (KMS)
A unique data encryption key (DEK) is generated per “n” objects used to encrypt data at-rest stored in S3. Objects references Jira issues, attachments and configuration elements within Jira
DEK is further encrypted using KEK and is stored in S3 along with the corresponding objects that where encrypted with that specific DEK
Learn more about envelope encryption here
Revyz utilizes the role based access control (RBAC) offered by Atlassian. Any user in the “site-admins” group will have access to the Revyz app. All their actions are logged for audit purposes.
Customer data backed up within Revyz is encrypted and not accessible or readable by Revyz employees as part of their regular operations. Access to data stored within Revyz is solely subject to policies and authorized user permissions established and managed by the customer.
The encryption scheme built by Revyz allows for the customer to control the main encryption key also known as the Key Encryption Key (KEK) [Reference our encryption scheme]. Revyz plans to support BYOK as soon as Atlassian publishes a framework for third party app vendors for enabling BYOK for apps. It is critical for a framework for all apps to be in place as it will minimize the management over head of managing keys across multiple apps for the end user admin.
All activity within the Revyz app is logged. Please reference the audit log feature available within the Revyz app under the “Settings” menu.
Yes Revyz SOC2 Type II, if you need the SOC2 report, please open support request here.
After the completion of the free trial, if you decide to continue with the Revyz Backup & Restore app, your data continuous to reside with Revyz, if for some unforeseen reason you decide to not to continue with Revyz, your data will be automatically deleted on the 5th Saturday after you have un-installed our application.
To learn more about Revyz’s Security policies, please Revyz’s security documentation available here.