Make backup profiles and schedules Features exportable

As I see, it's not possible now. I try to make it, if I will have time, because this would be useful feature for me too.

#373786: Add option to store backup profiles in code

The above issue states that the functionality exists, but I can't find any evidence of the functionality. Was it removed maybe?

Shouldn't be too hard to add the functionality back in, but it would be interesting to know the story behind this.

I'm also interested in this. No export links show up and I have cTools enables.

Chiming in to confirm this issue. The functionality is partially present. I am not seeing any UI to expose the links.

For example the following links result in the form with the ctools exportable code;

• /admin/content/backup_migrate/profile/list/export/PROFILE-ID
• /admin/content/backup_migrate/schedule/list/export/SCHEDULE-ID

You can just click on edit for a backup_migrate 'entity' (profile/schedule) and change 'edit' to 'export' for the same result.

However it would be great if you could build a feature through the GUI as provided by the features module.

Subscribe.

sub

Anyone wondering about those hidden path should check at the equivalent of this for D7:

admin/config/system/backup_migrate/profile/list/export/PROFILE_ID

Ex: admin/config/system/backup_migrate/profile/list/export/default

It would be nice if someone could create a "features.inc" file at least for the D7 version.

You can find the schedules the same way as #8:

../admin/config/system/backup_migrate/schedule/list/export/[schedule ID]

Features support would be great, or any way to import these exportables.

How to use the exported array? Clues in this issue: #373786: Add option to store backup profiles in code.

+1 on Features integration.

Marked #373786: Add option to store backup profiles in code as a duplicate. (The solution there no longer reflects the current state of the data structure.)

Example implementation of the export code found at admin/config/system/backup_migrate/profile/list/export/PROFILE_ID:

/*
 * Implements hook_backup_migrate_profiles().
 */
function mymodule_backup_migrate_profiles(&$profiles) {

  $out = array();
  $out['my_profile'] = backup_migrate_crud_create_item('profile',

// paste exported code here, starting with "array("

  );
  
  return $out;

Working example code here.

This is possible in the 3.x branch.

Should this work now? I am able to export my configurations, but they don't end up on the other environments. Reverting the features doesn't seem to create the schedules? The custom destinations seem to work, but the schedules don't.

This is the in-code solution for 7.x-2.x (in case someone can't upgrade to 7.x-3.x): #1820530: Document the ability to enable/disable backup scheduling in settings.php

The latest dev should fix the issues with ctools and features.