For every successful backup, Jira will save a zipped XML backup to /export.On the Edit service page, save the backup service configuration by selecting Update. ![]() Under the Class field, select Built-in services > Backup service.Ĭonfigure a Schedule and Interval by selecting one of the following options:ĭaily-the service will run once or multiple times per day based on the set Interval.ĭays per week-the service will run once or multiple times per day on specific days of the week based on the set Interval.ĭays per month-the service will run at a specific time on a specific day of the month based on the set Interval.Īdvanced-allows you to enter a custom cron expression for finer control over the schedule. In the Add Service section, enter a descriptive, unique Name for the backup service. In the side panel, under Advanced, select Services. In the upper-right corner of the screen, select Administration > System. To create a new database backup service or restore the default one if it’s been removed: Jira doesn't report any warnings or error messages when an XML backup is generated with inconsistencies and such backups will fail during the restore process. When Jira is in use, there’s no guarantee that XML backups will be consistent as the database may be updated during the backup process. Native database backup tools offer a much more consistent and reliable means of storing (and restoring) data while Jira is active. Using that kind of pricing strategy increases attrition in our experience, as well as the resources needed to deal with the complexity of the sales cycle.For large Jira installations and regular backups in production, we strongly recommend that you use native database backup tools instead of Jira's XML backup service. In our experience, customers prefer to see a single quote that covers the entire solution and can be very resistant to being nickel and dimed for add-ons, support, or even restoring data. Whether you go with a per GB or tiered model, decide on a price that includes everything you want to offer in your service. Quote one price that includes everything (don’t nickel and dime customers) This means you can market it as 500GB but see actual margins based on only 250GB of cost as an average.Ĥ. $80/month for 500GB), but will likely be somewhere in the middle of the tier statistically. Customers see the max they can backup up at each level (e.g.Storage is easy to acquire for minimal cost, so the higher tiers scale down the cost quickly.Software/support costs remain high no matter the size of the backup, especially for a managed service, so the lower tiers are more expensive relative to the data.Here are some price points to consider, with the caveat that each provider is dealing with unique regional markets, client budgets, and competitive landscapes.Īssumptions when using this kind of tiered pricing model: The key is to choose a per GB cost that makes sense. This is a great way to price your managed backup service, as it’s easy to track either selected data or compressed storage, it’s very fair, and it scales as your client’s data grows. As you’ll see below, you can craft an aggressive per GB or tiered pricing model that is fair to both you and your end-users. It may sound more attractive to customers upfront, and for good reason, but in the long run you will want the flexibility to charge more if a client’s backups grow exponentially. Over time your storage, bandwidth, and support costs scale with the amount of data and number of machines your customer is backing up, so don’t sell yourself short by agreeing to a fixed fee plan. Using fixed pricing is the easiest way to lose money on a managed backup service, especially if you bundle it with “unlimited” storage. Never use a fixed fee plan (or unlimited storage)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |