Configuration

Running as HTTPS

1. To run BackupMyOrg as HTTPS, you will need both a certificate and key .pem file. If you need to generate these, you can do so by downloading OpenSSL at https://www.openssl.org/,
2. Open a Command Console in Windows
3. Run the following commands to generate your private key and public certificate:
   
   openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem
   
   openssl x509 -text -noout -in certificate.pem
   
   
4. Once you have the cert and key files, copy them to your BackupMyOrg main folder
5. Edit the config/nodeconfig.json file and make the following modifications:
1. “useHTTPS”: true,
2. “certificate”: <name of your certificate.pem file>,
   “key”: <name of your key .pem file>
6. Restart your BackupMyOrg server app or service, then load https://localhost:8500 or https://yourwebdomain:8500 in your browser.

Note: If you are using an absolute path in your nodeconfig.json file, be sure to use double backslashes, such as "C:\\BackupMyOrg\\Certificates\certificate.pem"

Running with password protection

If you are running BackupMyOrg in a public facing situation or wish to control access, you can enable login credentials. To enable login credentials, edit the config/nodeconfig.json file and make the following modifications:

• Under the “useSecureAuth” field, set “enabled” to true
• Using Command Prompt, go to the BackupMyOrg root directory and type:backupmyorg setpw yourusername yourpassword
• Restart your BackupMyOrg .exe or service.

General Settings

By clicking on the gear icon, under the General Settings tab you can modify several settings including:

• Delete backup after X days: you can choose a global period of time that backups will expire. If you use this setting a timer will be applied to all backups, but you can manually set a do not delete option to specific backups on the backup log page.
• Exclude content: you can choose to globally exclude items with certain tags or items with certain owners for all backups.
• Click the Save General Settings button to apply your changes.

Setting up Mail Options

To set up settings for sending email notifications, click on the cog icon in the top right of the BackupMyOrg page.

There are 3 options for mail types that can be configured:

• Service (Gmail, Outlook, etc)
• The service section provides some templates for common mail services such as Gmail and Outlook.
• Before sending email using Gmail, you will need to allow less secure apps to access Gmail. You can do this by going to https://myaccount.google.com/lesssecureapps
• The Gmail option with less secure apps will not work with 2-factor authentication, so it is advised to create a new account specifically for the purpose of BackupMyOrg email notifications.

• SMTP
• Standard SMTP options are available in this section, including host, port, username, and password. If there is a configuration that is not supported here, the Custom Mail Type can be used instead.

• Custom
• BackupMyOrg uses NodeMailer for its mail system, so any transport configuration that works in NodeMailer can be entered here. The format for this section is JSON, and you can get a list of options at https://nodemailer.com/smtp/#examples.

Running with ArcGIS login credential

You can also control access by requiring an ArcGIS login to access the BackupMyOrg client page.

• In nodeconfig.json, set the following settings to allow for ArcGIS access:
  "useArcGISAuth": { "enabled": true, "assignRoles": false, "superUsers" : [] },
• This will require an ArcGIS login from one of your licensed connectors to access the application.

Running with ArcGIS login with custom roles

In addition to controlling access by requiring an ArcGIS login to access the BackupMyOrg client, you can also create custom roles for ArcGIS users that can control which identities they can access as well as access permissions for restoring and backing up data.

• In nodeconfig.json, use the following settings to allow for customized roles:
  "useArcGISAuth": { "enabled": true, "assignRoles": true, "superUsers" : ["adminuser1", "your_admins_comma_separated"] },
• The superusers that are defined in the config will have access to all identities and permissions, and will have access to set up the custom roles in BackupMyOrg.
• To start configuring your custom roles, click on the gear icon at the top right and navigate to the Manage Role tab. Note that you must be a superUser to modify these roles.
• From the manage roles page, you can click the plus button to create a new role, or to the right side of existing roles, edit or delete the role.
• On the backup tab, you can click the tab to allow role members to perform backups, then select which identities are allowed to backup.
• On the restore tab, you can click the tab to allow role members to restore, and select which identities you can restore from and restore to.
• On the manage identities tab, you can select which identities these role members can manage, including assigning credentials and changing locations.
• And finally on the assign users tab, you can select which ArcGIS users from all of your connectors will be allowed to be assigned to those roles. Note that an ArcGIS admin can only belong to one role.
• Using the role system, any administrator who logs in and is not assigned a role will not be able to access BackupMyOrg unless they are a superuser.

Additional nodeconfig.json values

Additional values you can change are:

• port: (default: 8500) the port BackupMyOrg will be running. This will change the URL of the BackupMyOrg page to http://localhost:yournewportnumber
• hostname: the default hostname used in links for email notifications
• adminEmail: this will auto-populate the mail results field of backups and restores. Can specify multiple recipients by separating with commas.
• serverLogLevel: (default: 1) set the level of log verbosity from 0 to 5, where 0 is silent running and 5 is debug level logging. Logs will show up under BMO-logs.txt in the main BackupMyOrg directory.
• logSizeMaxMB: set the maximum file size of the BMO-logs.txt file. Once the BMO-logs.txt has hit the limit, it will copy the existing logs to BMO-archive.txt and restart the BMO-logs.txt file.
• timeoutSecondsBeforePrescanCleanup: amount of time in seconds before unused prescans are removed from the database and local files
• timeoutSecondsBeforeBackupFailed: the amount of time in seconds before a stalled backup or restore is deemed a failure and the database and local files are cleaned up
• MAX_CONCURRENT_FETCH: number of simultaneous fetches to be used at a time when processing backups and restores.
• FILETHRESHOLD: number of files in a directory archive before creating a new directory
• cacheExpirationSeconds: number of seconds before the cache automatically fetches a fresh snapshot of your items, groups and users for use in filtering and item selection.
• enableHSTS: Enable HSTS support on the BackupMyOrg server. HTTPS must be configured to run with HSTS support.
• Other settings should not be adjusted unless instructed to do so by GEO-Jobe Support.

Configuring BackupMyOrg for OAuth2

If your organization is using ArcGIS Online or ArcGIS Enterprise with OAuth2 authentication, you will need to create a BackupMyOrg application item in your organization.

• Click here to visit our Backup My Org Knowledge Base for step-by-step instructions on how to set up an application item to retrieve your App ID.
• Once you receive your App ID, copy and paste it into your Identity setup on the BackupMyOrg Add Identity page.

Backup My Org Operation

Setting up Identities

You can set up your Organization’s identities and credentials on the “Manage Identities” page. To add a new identity, click on the blue plus button next to either ArcGIS Online or ArcGIS Enterprise.

Setting up an ArcGIS Online Identity:

• Organization Name: the name your backups will be associated with in BackupMyOrg
• URL: the licensed connector to your ArcGIS Online organization
• App ID: You will need to set up an app in your ArcGIS Online organization to work with BackupMyOrg. Please see Configuring BackupMyOrg for OAuth2 for information on how to generate the App ID.
• File Location: the physical location on your machine that will contain all of the backup archives and restore data. Note that you should not change this directory after you have set up an identity, as that could break previous backup and restore links.
• If you wish to use a network drive, consider creating a symbolic link on the server to your map drive with:
  mklink /D "D:\yourshortcutdirectory" "\\networklocation\directory"

 Setting up an ArcGIS Enterprise Identity:

• Organization Name: the name your backups will be associated with in BackupMyOrg
• Authentication: IWA or OAuth2. 
• For IWA, no additional credentials are needed. Authentication will be done by the user identity of the web server service, or the current Windows user if run locally. Please ensure that the user has administrator privileges in your organization for backup and restore operations to function properly.
• For OAuth2, you will later need to specify an App ID. Please see Configuring BackupMyOrg for OAuth2 for information on how to generate the App ID.
• URL: the licensed connector to your ArcGIS Online organization
• App ID: If you are using OAuth2 authentication, you will need to set up an app in your ArcGIS Online organization to work with BackupMyOrg. Please see Configuring BackupMyOrg for OAuth2 for information on how to generate the App ID
• File Location: the physical location on your machine that will contain all of the backup archives and restore data. Note that you should not change this directory after you have set up an identity, as that could break previous backup and restore links.

Running a Backup

• There are three types of backups that can be run from the Backup Page
• Backup Entire Organization: backup the contents of the entire organization with just a few clicks.
  
  
• Quick Filters: Select from a list of predefined filters, such as backup a user’s items, items that have been modified in the last X days, or items that have been created in the last X days.
  
  
• Advanced Backup: Here you can choose specifically which items, users and groups to backup.
  
  

Backup Options

• Select your configured identity in the “Organization To Backup” section. If you have not set up an Identity yet, click the “Add Identity” button to go to the “Manage Identities” section.
• Under Backup Name, you can provide a custom name to help identify the backup later
• You can enable a notification email by enabling the switch next to  “Email Results to”. You will need to set up Mail Settings before running to receive emails. Please see Setting up Mail Options for more information.
• One or more email addresses can be entered in the email box. Multiple email addresses will need to be separated by commas.
• Skip visualizations for large backups: for very large backups, you can select this to proceed straight to the backup operation of all backups and dependencies instead of the graphic visualization stage.
• Backup Registered Services as Hosted (experimental): add service URLs to public hosted services to be backed up as registered services
• Delete backup after X days: if you would like to make this backup temporary, you can set the number of days before deletion.
• Exclude Content: You can also select tags and item owners to be ignored by the backup.

Content Selection

• For the Advanced Backup, you may choose the content you would like to backup. Select the Items, Groups or Users tab at the top, then use the Add button to select content from the organization. 
  
  
• Cache: All of the target organization’s items, groups and users are cached by BackupMyOrg locally in the database in order to allow advanced filtering to take place. At the top right, the latest cache time is visible. To recache, click the recache button.
  
  
• Filtering: On the top left is the Add filter button. You can add as many filters as you like to select your content.
  
  
• Make your selection: once you have filtered your items, use the checkboxes next to the content you wish to backup and click the Add Selected to Backup button at the bottom of the page.
  
  
• Once you have returned to the main selection page, you can select content and and use the Remove Selected button to remove content from the list, or click the green Backup Confirmation button at the bottom of the page to continue.

Backup Preprocessing

• The backup preprocessing steps examines your organization for your target content and finds any dependencies and related items and adds those to the queue to be processed. Once preprocessing is complete, you are presented with a visualization of your target content and their dependencies 
  
  
• The Backup Preprocessing screen will display all of the selected content as well as any dependencies of those contents. From here, you can select which content to continue with on the backup. Right click on a node to get more details on a particular content. Nodes in red have an error that prevents backup of that item, group or user. This could be an issue with the actual organization item, group or user, or a dependency that no longer exist from the parent content.
  
  
• Visual View: Use the left mouse button to select the Nodes you wish to backup. You can also change the selection options in the right column to select individual nodes or nodes and dependencies. If you plan to restore to a separate destination, be sure to select the dependencies to backup as well.
  
  
• Verbal View: If you wish to select items via a text-based interface, select the verbal view on the right side. This will allow you to click on checkboxes to select your backup content.
  
  
• Start Backup: Click the Start Backup button to begin backing up your selected items.

Configuring a Scheduled Backup

• Clicking on Scheduled Backup  from the main menu will open the list of Scheduled Backups that have been created. 
• Toggling the switch under the “Repeating” column will disable or re-enable the backup.
• To edit an existing backup, double click on a row or click the Edit button on the right of the row.
• To delete a backup, click the Delete button the the far right of the row.
• To create a new scheduled backup, click the Add Backup button at the top right.
• The Scheduled Backup settings are very similar to the On Demand settings, with different ways to select content. 
• Click the Save Settings to save the new Scheduled Backup. The first backup will run at the starting date specified.

Logs Page

• The Logs page will list all backups and restores that have been run to-date. 
• Select the Backup Logs or Restore Logs from the first screen.
• To view a backup or restore, double click on a row or select the Review Button under the Results column.
• To delete a backup or restore, click on the Delete button to the far right of the row. This will also delete all local files related to these entries.
• For both backup and restore, you can click the blue icon to view more information about a particular entry.
• Under restore results, you can also view the in-depth logs of the restore by clicking the View Log File.
• Additionally, in restore results you can click the Export button to download all of the related files pertaining to the restore.
• Clicking on a column will sort by that column.

Restore Content

• BackupMyOrg will allow you to restore your content from your saved backups to the same or different destination organization. BackupMyOrg provides you with a variety of configuration options in order to properly rewire your content from the original source to the destination.

Types of Restore

• Restore Specific Content: Choose and restore an individual item, user, or group based on all backups available. Once you have specified the item ID you will be able to choose from all of the available backups of that item.
  
  
• Advanced Restore: choose a backup and restore multiple files from that backup.

Select Contents to Restore

• Use the left mouse button to select the Nodes you wish to restore. You can also change the selection options in the right column to select individual nodes or nodes and dependencies. If you plan to restore to a separate destination, be sure to select the dependencies to restore as well. Note that all dependencies that are selected for restoration will restore over existing items if they exist.
  
  
• Some items we will not be able to restore over an existing item. Map Services and Feature Services with irregular indexes will not be able to be overwritten, and new items will be created.

• Verbal View: If you wish to select items via a text-based interface, select the verbal view on the right side. This will allow you to click on checkboxes to select your backup content.

• Click the Select Restore Options button to finalize your restore selections.

Restore Settings

• Select the Target Restore Destination from your Managed Identities list.
• Some restore options may not be able to overwrite the item directly, and in those cases we will need to create a new item for the restore. By clicking the “Rewire entire Org for created items” box, we will look through your organization’s web maps and web applications for references to your original item and rewire them for your new item.
• You can also specify email addresses for the restore results.
• Click the Begin Destination Prescan button to continue.

Restore Prescan Help

• During the Restore Prescan step, we can the destination organization and determine the status of the restoration content. For items, we are checking if the target item exists, if the owner and group exists, and if they do not exist, we try to find a close match for rewiring in the following configuration pages.
  
  
• Click the Next: Restore Configuration button to continue once the Prescan has been completed.

Missing User Config

• If your target items' owners are not found on the destination organization, they will be displayed here on the user configuration screen with options for rewiring the item for a new user.
  
  
• Advanced Options: By turning on advanced options, you will have the opportunity to fine tune all of your items' owners by manually selecting a replacement user.

• Global Options: Use the global options to set all of the listed users to a specific user with one click.
  
  
• User Mapping: You can save and recall commonly used mapping by clicking the Load User Mappings and clicking Apply User Mappings to set saved values to the current Items. To save the current mappings, click the Save Mappings version.
  
  
• Click the Next button once you have rewired any needed items to continue.

Missing Group Config

• If your target items' groups are not found on the destination organization, they will be displayed here on the group configuration screen with options for rewiring the item's groups.
  
  
• Advanced Options: By turning on advanced options, you will have the opportunity to fine tune all of your items' groups by manually selecting a replacement group.

• Global Options: Use the global options to set all of the listed users to a specific group with one click.
  
  
• Group Mapping: You can save and recall commonly used mapping by clicking the Load Group Mappings and clicking Apply Group Mappings to set saved values to the current Items. To save the current mappings, click the Save Mappings version.
  
  
• Click the Next button once you have rewired any needed groups to continue.

Missing Item Config

• If your target items are not found on the destination organization, they will be displayed here on the item configuration screen. For each item listed, you can either select a replacement item by clicking the Find Item button, or select the Create New button to create a new instance of the item.

• Advanced Options: By turning on advanced options, you will have the opportunity to fine tune all of your items by manually selecting a replacement item or selecting Create New to create a new instance even if one exists on the destination. Creating a new item is a good way to test a valid restore before it is needed.
  
  
• Item Mapping: You can save and recall commonly used mapping for your items by clicking the Load Item Mappings and clicking Apply Item Mappings to set saved values to the current Items. To save your current mappings, click the Save Mappings version.
  
  
• Click the next button once you have rewired any needed items to continue.

Service Credentials Config

• If you have any registered services you are restoring, you can optionally supply credentials here. These credentials will be saved with the restored item.
• Click the next button to continue.

Restore Status

• Once you have confirmed your restore, the restore status page will appear. This will show you the status of each item in progress and give you a visualization of the entire restore operation.
  
  
• Yellow nodes are restores in progress, green nodes are complete, and issues are shown in red.
  
  
• The first pass of the restore will be the restoration of the actual item’s data, and the second pass will be any rewiring that needs to be completed on that item.
  
  
• Once the restore step has completed, the postprocessing step will begin. In this step we will be confirming any files that need to be deleted, alerting you to any manual rewiring possibilities that we did not have the information for, and cleaning up local files and databases.

Postprocessing Options: Delete confirmation

• You can use the blue icons to check the current status of the new restored item and verify before clicking the checkbox to confirm deletion of the old item.

Postprocessing Options: Non-Rewired Dependencies

• Selection: Here you can optionally rewire dependencies that we did not have direct information to rewire. Select the item on the left, and fill in the correct rewiring information if needed. For IDs, you can click the find button to search the destination organization for the correct item.

• Mapping: To save these rewire settings for the future, click on the Save Remapping button at the top right. When starting a new rewiring, click the Load Rewiring Mapping button to automatically apply previously saved mappings.

Troubleshooting

I have started BackupMyOrg.exe, but the window immediately closes.

Go to the Start -> Run menu and type ‘cmd’ to open a Command Shell. Navigate to the folder using cd /D your_install_location and type BackupMyOrg. This will let you see the result of running the server app. Also note that only one instance of the BackupMyOrg.exe server can run at one time, so if there is already an instance running the second one started will fail.

BackupMyOrg is failing with ‘TypeError: Cannot read property ‘db’ of null.

You either need to install MongoDB, or your MongoDB service is not running. From the start menu, open Services and make sure the MongoDB service is running.

BackupMyOrg is failing with an ‘EACCESS’ error.

You may need to change the port from the default 8500. 

• In your BackupMyOrg folder, open up the /config/nodeconfig.json folder.
• Change the port from 8500 to another number, such as 8501.
• Stop any services or BackupMyOrg.exe processes that are running.
• Restart your BackupMyOrg.exe or service.

http://localhost:8500 is not working when I open it in a browser.

• Make sure the BackupMyOrg.exe or service is running
• Make sure the port is 8500 in config/nodeConfig.json.
• If you are using HTTP, in config/nodeConfig.json make sure useHTTPS is false.
• If you are using HTTPS, in config/nodeConfig.json make sure useHTTPS is true, and that you have the correct location of certs.certificate, and certs.key.
• If you have made any changes to the config settings, be sure to stop BackupMyOrg.exe and restart.

I am getting Invalid Redirect URI when trying to save my identity.

You will need to configure your Redirect URI in your BackupMyOrg application item in your organization. Please refer to Configuring BackupMyOrg for OAuth2 for more information.

My organization’s URL is not showing up on the Add New Identity URL field.

If you have not licensed a connector URL for that organization, please contact GEO-Jobe to purchase an additional connector. If your existing connector needs to be changed, please contact GEO-Jobe to update your build with the proper connectors.

I am unable to add new OAuth Identities in Internet Explorer.

To add OAuth Identities in Internet Explorer, you must first add your ArcGIS Enterprise or ArcGIS Online connector url to the Trusted Sites under the Security Settings.

1. In Internet Explorer, click on the gear at the top right of the window.
2. Click on the Security tab
3. Click on the Trusted Sites icon
4. Click the Sites button to add a trusted site.
5. Add the ArcGIS Online or ArcGIS Enterprise URL and click Close
6. Restart Internet Explorer and try to add a new Identity in BackupMyOrg.

Note: While creating a new identity, if you get a 404 page in the popup after entering your credentials, try refreshing that popup window.

If you are logging into a BackupMyOrg site other than localhost, you will also need to add your BackupMyOrg domain as well. If using http, be sure to uncheck the box for “Require server verification (https:) for all sites in this zone.”

Additional Support Resources

If you have any questions, problems, or feature requests, you can get in touch with us via email at support@geo-jobe.com, Live Chat on https://geo-jobe.com, or call us at 1-844-GEOJOBE.

Export Server Logs

This option will allow you to download the log files for server operations. This may be requested in the event you open a support ticket with GEO Jobe's support team. If you need to adjust the level of specficity in the server logs, you can do so in the settings menu. Please note that increased specificity may result in longer processing times.

Supported Types

* For a list of unsupported types and supported types with exceptions click here.

Version 1.4.1.22 Hotfix

• Fix for Azure mail Scheduled attachments and test mail sender (.22)
• Fix for Incorrect URL in BMO in Backup Logs (.21)
• Proxy Settings for BMOfetch, more info: https://geo-jobe.atlassian.net/wiki/spaces/GJKBASE/pages/3909582857/Configure+Proxy+Settings+for+Backup+My+Org (.20)
• Now shows all rewires in postprocessing rewire config if showAllRewiringOptions nodeconfig option is true (.20)
• Fix for error handling in saveFGDBToLocal (.20)
• Fix for changes to typeKeywords between versions of ArcGIS causing settings of feature services to be unable to be updated (.19)
• Additional logging for Hub Site Application (.19)
• Fix for rewiring issues in post processing (.18)
• Fix for restoring public images (.18)
• Added error handling to all getFilesizeInBytes calls to prevent cases where savefile returns no errors, but no file was saved (.17)
• Fix for totalBackupSize inconsistency with backupRetry (.17)
• Backup: Fix for processedFiles staying 0 (.17)
• Fix for Mail Settings not populating for Azure (.16)
• Added additional logging / error handling for individual restore users and logIndividualUserRestore variable (.15)
  config.json:
"logIndividualUserRestore": true,
• RestorePostProcessing: fix for changeOwners forEach inside of mapseries calling callback multiple time (.15)
• Client-side warning for lack of .NET 4.8 (.14)
• Fix for awaitDrain CSV attachment issue in mailer (.13)
• Force f=json even with pjson override for replica download status (.12)
• Force saveget for BMOfetch to use GET for replica download instead of POST (.12)
• Added check for if item type is not null before adding it to itemTypeStore (.11)
• Added ability to name restores (.10)
• Post-processing: fix for syntax regex in webmap/generic rewire not properly escaping an opening parenthesis (.09)
• Fix for IIS mode using ArcGIS authentication (.09)
• Remove / replace invalid characters in layer names before initial publish (.08)
• Restore: publish now replaces all invalid characters in layer names with _ when removeInvalidServiceLayerNameCharacters nodeconfig param is true (.07)
  Nodeconfig.json option: removeInvalidServiceLayerNameCharacters: true
• IIS-mode: run the BMO client-side from IIS. i.e. domain.com/backupmyorg instead of domain.com:8500 (.06)
  In html/config/config.json set "iisMode": true,
  More info at: https://geo-jobe.atlassian.net/wiki/spaces/GJKBASE/pages/3761569793/How+to+Run+BackupMyOrg+in+IIS+Mode
• Removed units from publish params in hosted FS update (.06)
• Fix for rewiring layers with unusual characters, potential fix for layer rewiring in general (.05)
• Config options to remove special characters from service names when restoring (.05)
  Nodeconfig options: "removeInvalidServiceNameCharacters": true
• .NET 4.8 check on startup (.05)
• Client-side authentication debug logging (.04)
  html/config.json: set "logRoleLogin": true
• Quick Filter backup confirmation: remove unused cards (.04)
• Backup: Cancel in progress backup improvements (.04)
• Added restore status CSV report to Restore Logs (.04)
• Added internal EULA setting (.04)
• Fix for multipart upload error caused by backupGlobals.isBackupRetry (.03)
• You can now have a separate max concurrency for backup retries (.02)
  Set MAX_CONCURRENT_BACKUP_RETRY_FETCH: 1 in Nodeconfig.json for desired amount.
• Fix for Azure Mail and Nodemailer attachments (.02)
• Fix for Create CSV report not saving to directory (.02)
• Fix for IWA-based ArcGIS authentication (.02)
• Fix for restore symbology not being published correctly on create new option (.02)
• Option to automatically run a backup retry x hours after a backup finishes (.02)
  Nodeconfig options:
"automaticallyRetryBackupErrors": {
"enabled": false, - set to true to enable
"minHoursToCheckBackupAge": 5, - set the minimum hour before retrying the backup errors
"maxHoursToCheckBackupAge": 72 - set the maximum hour before retrying the backup errors
}
• Added wait if we cannot pull the new service definition of a newly published large service immediately (.02)
  Nodeconfig options:
"serviceInfoFetchDataRetries": 1, number of retries for service info
"serviceInfoFetchIntervalInMinutes": 2, time to wait between retries
• Improvements to Generic item rewire (.01)
• Zip path column added to backup logs single view as a hidden column option (.01)
• Restore: retry fetching a new service definition of a newly published large service if original fails (.01)
• Add debugging for issue with Azure mail verification/saving (.01)
• Fix for Backup Quick Filters not clearing out dropdowns when doing a second backup with a quick filter (.01)
• Fix for Restore rewiring failing inside embedded html fields (.01)
• Fix for Table IDs change during restore (.01)
• Backup / Restore for custom Experience Builder widgets (.01)
• Restore: In AGOL allow whitespaces in service names / titles (.01)
• Added Role-based export permissions (.01)

Version 1.4.1.0

New Features

• Support for Hub Sites item type
• Support for Hub Sites Applications item type
• Support for QuickCapture item type
• Backup Logs: You can now create a restore planning document by clicking the restore planning button
• Added startup.bat that runs at start of BMO service to allow for network drive usage/mapping
• Large-file & memory optimizations: Improved BMOfetch for large files, improved memory usage, TLS 1.3 support (requires .NET 4.8)
• Credential-override CLI: bmofetch set username@domain password Delete iwa.conf to revert

Improvements

Bug Fixes

Version 1.4.0.0

New Features

• Backup: option to backup without dependencies
• Content Selection Filters: Import from CSV option
• HTTPS: PFX certificate support
• Email: email users when token expires
• Mail Options: Azure Mail support

Improvements

• Added confirmation input for bulk delete of backups and restores
• Added FGDBRetryCount option for FGDB export retry count
• Backup: Check and handling for stalled backups
• Backup: Improved dependency gathering
• Restore: nodeconfig.json setting to force ignore changeTracking capability for restorations
• Restore: user rewiring warning if trying to overwrite existing users
• Restore: Backup connector license check no longer required for restore operations
• Added replica export retry functionality: ReplicaRetryCount setting in nodeConfig.json
• Added backup and restore support for dashboard arcadeDataSourceItems
• Additional logging of attachment size
• Backup: Added support for GeoPackage
• Backup: Added success / error tracking to backup cleanup
• Backup: added support to retry backup for items not yet started when BMO stopped
• Backup: create feature service replica status updates
• Automatic cleanup of unhandledException logs over 2 weeks old
• Backup: improved esriID detection for finding dependencies
• Backup: improved temp FGDB files on backup cleanup
• Backup: Improved zip archival for large files
• Backup: individual item stall improvements
• Backup: Logs now uses totalFiles instead of processed, more accurate with backup retry and new cleanup
• Backup: option to skip all dependencies
• Backup: Removed client side dependencies when doing skip visualization
• Backup: restart scheduled backups on server restart
• Backup: retry status check for replica backup
• Backup/Restore Logs handles correctly after multiple clicks on top 'Exports'
• Better reporting for restore prescan errors
• Check token validity only on licensed identities
• Check for string size limit in fetch calls
• Dashboard restoration improvements
• Email: Updated mailer to include backup status
• Feature Service Views now backup and restore with query definitions
• Identities: check for user get, put, delete permissions for S3
• Improved error handling for mongoDB service crashes
• Improved error handling for unsuccessful zip file uploads
• Improved mail formatting and processing
• Links for URLs during URL rewiring postprocessing
• Mail: added option to include or not include JSON attachments in email reports
• Manage Identities: check for administrator role when saving identity
• More accurate email reporting of backups
• New BMOfetch functionality
• Preprocessing: improved performance during dependency checking
• Preprocessing: improved preprocessing performance during depth processing
• Quick Filter: Added a case-insensitive filter for tags when backing up content
• Quick Filter: Added Authoritative quick filter
• Filters: added numViews filter
• Removed duplicate users during backup retry
• Restore Postprocessing: improved matching for url rewrites
• Restore Postprocessing: Secured registered services URL will be automatically placed in the URL field
• Restore Preprocessing: improvements to find similar items
• Restore selection: refactored restore content selections for improved performance
• Restore User Config: added confirmation if overwriting existing users
• Restore: Added destination group id to group config page if there are multiple groups with the same name
• Restore: always show base rewire if marked as incomplete
• Restore: improved support for KML restoration
• Restore: improved tag input for restoration
• Restore: removing republish for feature service if restoring to the same ArcGIS version
• Support for id, ID, itemID, or itemid for Import from CSV filter
• Support for title or Title for Import from CSV filter
• uncaughtException files now concatenated by date
• Updated S3 and Proxy Dependencies
• Backup: alternative split replica backup of feature services that fail the initial export to FGDB (NOTE: this will only work with create new and cannot update)
• Rewire: Added button for global apply to all blank inputs

Bug Fixes

• Backup: Fix for fetching large number of item resources
• Backup: Fix for role displaying incorrectly as org_admin
• Fix for Feature Services Modified in last X days filter pulling different item types
• Fix for Restore Dashboards to ArcGIS Online
• Fix for temporary FGDB not being deleted on failure
• Identities: fixed issue where deleting identity could affect on-demand scans
• Restore: fix for an issue rewiring StoryMaps across different ArcGIS platforms
• Restore: Fix for content showing up in individual restore when not backed up
• Restore: Fix for create groups with duplicate titles
• Restore: Fixes for scrambled layer id FS restore and web map / app rewires
• Rewire: Fix to replace all instances of id, url, and domain including in object keys during rewire
• Save Indentity: Fix for Oauth2 to OAuth2WithCredentials with S3 bucket not updating correctly
• Additional backup error checking for valid arrays
• Backup and Restore Logs now have loading indicator while fetching logs
• Backup visualization: Fix for select all doubling estimates
• Backup: added saveBackupException for debugging
• Backup: fix for an issue causing exception fault in backups
• Backup: fix for backup search deselect leaving links
• Backup: fix for error handling with valid arrays
• Backup: Fix for large GeoJson file downloads
• Backup: Fix for manifest.json fetch for custom widgets
• Backup: fix for pathname issues for save request
• Backup: fix for scheduled backup entries saving empty array
• Backup: fix for server-side finishing and client-side never reflecting
• Backup: Fix for SQLite Database
• Backup: fix for uncaught exception during FGDB export
• Backup: fix issue of previous quickfilters set when starting a new backup
• Backup: Fixes for Hosted Scene Service backup
• Backup: stall marked complete instead of error
• Better error handling for failed SD backups
• Continue backup if thumbnail fails
• Error handling for FS replica backup
• Filters: fix for org_authoritative in filters
• Filters: Fix for typekeyword filter in restore
• Fix and additional logging for postprocessing stall
• Fix for an issue restoring hosted feature service
• Fix for bmo-log.txt write issue
• Fix for cacheallusers for arcgisAuth user role
• Fix for delete error when verifying write permissions
• Fix for feature services modified in lasy X days quick scan shows undefined in confirmation
• Fix for FGDB multipart uploads not being placed in correct folder
• Fix for for split replica backup / restore
• Fix for IWA ArcGIS login authentication
• Fix for IWA ArcGIS Login option
• Fix for MongoDB issue using localhost
• Fix for Skip Visualization options
• Fix for skipVisuzation settings issue
• Fix to allow login with useArcgisAuth and OAuth2WithCredentials
• Fixed duplicate name during user backup retry
• Identities: Fix for OAuth2WithCredentaials save issue
• Log: fixed visual bug in backup log
• Log: Fixes for log errors that are objects
• Logs: log export now properly exports errors
• Postprocessing: fix for additional Url Dependencies not automatically rewiring to match dependencies new URL
• Postprocessing: Fix for additional url rewire not getting url from main rewire when layer is restored at same time
• Postprocessing: Fix for cache rewite registry
• Postprocessing: fixes for group sharing and relationship rewiring
• Preprocessing: fix for circular dependencies
• Preprocessing: Fix for issue where user preprocessing could cause loop
• Proxy fix for BMOFetch
• Restore Dashboard: fix for new ArcGIS Online format
• Restore Dashboard: fix for new ArcGIS Online version error
• Restore Feature Service: Added fix for if layerServiceDefInfo is an empty object
• Restore Rewiring: Fix for Web Map Rewiring Issue
• Restore User Config: Fix for blank destination user select on userConfig load
• Restore: Added additional error handling for getAvailableServiceName
• Restore: Bug fix and improved logging for rewiring Web Mapping Application widgets
• Restore: checkremainingconfigs error fixed
• Restore: Dashboard fix for ArcGIS Online to Enterprise restoration
• Restore: fix for a feature service error
• Restore: Fix for adding items to groups when that group has only group admins contribute content
• Restore: Fix for an issue publishing items from a service definition
• Restore: fix for call stack issue in backup / restore
• Restore: fix for checking for duplicate service renaming
• Restore: Fix for featureServiceHosted exception bug
• Restore: Fix for group name filter
• Restore: Fix for individual restore filtering
• Restore: fix for issue where user config page could be blank
• Restore: Fix for multipart feature service restore during updateDefinition for hasCapabilities field
• Restore: Fix for nonstandard layer IDs being updated after creation
• Restore: Fix for postprocessing relationship rewire not keeping user applied changes
• Restore: Fix for publishing map services from service definition in ArcGIS Online
• Restore: Fix for user page allowing continue if users aren't configured
• Restore: Fix for view restore for feature services with multiple layers
• Restore: Fixed feature service restoration using changeTracking for ArcGIS Online orgs
• Restore: Fixes for view restoration with public source and also properly assigns ownership in postprocessing
• Restore: potential fix for not rewiring dependency
• Restore: potential fix for web map rewire error
• Restore: Updated view restore to fix relationship errors
• Save Identity: Fix for S3 bucket checking
• Scheduled Backup: fixed an issue for item and feature service modified quick filter not selecting content
• Scheduled Scans: backup options number in confirmation now shows correct number
• Scheduled Scans: fix for showing as a single number with digits for days/hours instead of breakout of days hours
• Settings: Fix for token expiration warning when using roles

Version 1.4.0.16 hotfix

• Additional logging and potential fix for Could not find admin service info for item error (.16)
• Backup: Potential fix for could not find admin service info for item error (.15)
• Add raw post type to BMOFetch (.15)
• Nodeconfig option "enableHSTS" to enable HSTS support for the server. (.14)
• Improved efficiency of individual restore content fetching (.13)
• Restore: Update owner of view source, now deletes items permanently when deleting folder (.12)
• MAX_BACKUP_RETRIES ceiling set at 50 (.12)
• Node Config: showAllRewiringOptions shows all possible rewiring options (including automatic handling) in the postprocessing step (.12)
• Added additional version and hardware logging (.11)
• Node Config: MAX_BACKUP_RETRIES sets the number of automatic retry failed backup attempts (.11)
• Postprocessing: Dashboard field name rewire and other improvements (.11)
• Added startup.bat that runs at start of BMO service to allow for network drive usage (.10)
• Backup retry on server startup for scheduled backups (.9)
• Improvements to retry failed backups (.8)
• BMOTEMP files generated during backup will permanently delete and not go to recycle bin (.7)
• Fix for sort crash in MongoDB find for large amount of items (.6)
• Fix for Feature Service View restorations (.5)
• Fix for broken export to CSV in Firefox (.4)
• Improvements to export csv for users and groups to keep column layout (.4)
• Fix for update next date on Scheduled Scans (.4)
• Fix for FS views on Enterprise (.3)
• Restore: fixed an issue with downloading very large Azure storage files (.2)
• Backup: Improved large file buffering for S3 upload (.1)
• Additional logging to backupView (.1)

Version 1.4.0.0

New Features

• Backup: option to backup without dependencies
• Content Selection Filters: Import from CSV option
• HTTPS: PFX certificate support
• Email: email users when token expires
• Mail Options: Azure Mail support

Improvements

• Added confirmation input for bulk delete of backups and restores
• Added FGDBRetryCount option for FGDB export retry count
• Backup: Check and handling for stalled backups
• Backup: Improved dependency gathering
• Restore: nodeconfig.json setting to force ignore changeTracking capability for restorations
• Restore: user rewiring warning if trying to overwrite existing users
• Restore: Backup connector license check no longer required for restore operations
• Added replica export retry functionality: ReplicaRetryCount setting in nodeConfig.json
• Added backup and restore support for dashboard arcadeDataSourceItems
• Additional logging of attachment size
• Backup: Added support for GeoPackage
• Backup: Added success / error tracking to backup cleanup
• Backup: added support to retry backup for items not yet started when BMO stopped
• Backup: create feature service replica status updates
• Automatic cleanup of unhandledException logs over 2 weeks old
• Backup: improved esriID detection for finding dependencies
• Backup: improved temp FGDB files on backup cleanup
• Backup: Improved zip archival for large files
• Backup: individual item stall improvements
• Backup: Logs now uses totalFiles instead of processed, more accurate with backup retry and new cleanup
• Backup: option to skip all dependencies
• Backup: Removed client side dependencies when doing skip visualization
• Backup: restart scheduled backups on server restart
• Backup: retry status check for replica backup
• Backup/Restore Logs handles correctly after multiple clicks on top 'Exports'
• Better reporting for restore prescan errors
• Check token validity only on licensed identities
• Check for string size limit in fetch calls
• Dashboard restoration improvements
• Email: Updated mailer to include backup status
• Feature Service Views now backup and restore with query definitions
• Identities: check for user get, put, delete permissions for S3
• Improved error handling for mongoDB service crashes
• Improved error handling for unsuccessful zip file uploads
• Improved mail formatting and processing
• Links for URLs during URL rewiring postprocessing
• Mail: added option to include or not include JSON attachments in email reports
• Manage Identities: check for administrator role when saving identity
• More accurate email reporting of backups
• New BMOfetch functionality
• Preprocessing: improved performance during dependency checking
• Preprocessing: improved preprocessing performance during depth processing
• Quick Filter: Added a case-insensitive filter for tags when backing up content
• Quick Filter: Added Authoritative quick filter
• Filters: added numViews filter
• Removed duplicate users during backup retry
• Restore Postprocessing: improved matching for url rewrites
• Restore Postprocessing: Secured registered services URL will be automatically placed in the URL field
• Restore Preprocessing: improvements to find similar items
• Restore selection: refactored restore content selections for improved performance
• Restore User Config: added confirmation if overwriting existing users
• Restore: Added destination group id to group config page if there are multiple groups with the same name
• Restore: always show base rewire if marked as incomplete
• Restore: improved support for KML restoration
• Restore: improved tag input for restoration
• Restore: removing republish for feature service if restoring to the same ArcGIS version
• Support for id, ID, itemID, or itemid for Import from CSV filter
• Support for title or Title for Import from CSV filter
• uncaughtException files now concatenated by date
• Updated S3 and Proxy Dependencies
• Backup: alternative split replica backup of feature services that fail the initial export to FGDB (NOTE: this will only work with create new and cannot update)
• Rewire: Added button for global apply to all blank inputs

Bug Fixes

• Backup: Fix for fetching large number of item resources
• Backup: Fix for role displaying incorrectly as org_admin
• Fix for Feature Services Modified in last X days filter pulling different item types
• Fix for Restore Dashboards to ArcGIS Online
• Fix for temporary FGDB not being deleted on failure
• Identities: fixed issue where deleting identity could affect on-demand scans
• Restore: fix for an issue rewiring StoryMaps across different ArcGIS platforms
• Restore: Fix for content showing up in individual restore when not backed up
• Restore: Fix for create groups with duplicate titles
• Restore: Fixes for scrambled layer id FS restore and web map / app rewires
• Rewire: Fix to replace all instances of id, url, and domain including in object keys during rewire
• Save Indentity: Fix for Oauth2 to OAuth2WithCredentials with S3 bucket not updating correctly
• Additional backup error checking for valid arrays
• Backup and Restore Logs now have loading indicator while fetching logs
• Backup visualization: Fix for select all doubling estimates
• Backup: added saveBackupException for debugging
• Backup: fix for an issue causing exception fault in backups
• Backup: fix for backup search deselect leaving links
• Backup: fix for error handling with valid arrays
• Backup: Fix for large GeoJson file downloads
• Backup: Fix for manifest.json fetch for custom widgets
• Backup: fix for pathname issues for save request
• Backup: fix for scheduled backup entries saving empty array
• Backup: fix for server-side finishing and client-side never reflecting
• Backup: Fix for SQLite Database
• Backup: fix for uncaught exception during FGDB export
• Backup: fix issue of previous quickfilters set when starting a new backup
• Backup: Fixes for Hosted Scene Service backup
• Backup: stall marked complete instead of error
• Better error handling for failed SD backups
• Continue backup if thumbnail fails
• Error handling for FS replica backup
• Filters: fix for org_authoritative in filters
• Filters: Fix for typekeyword filter in restore
• Fix and additional logging for postprocessing stall
• Fix for an issue restoring hosted feature service
• Fix for bmo-log.txt write issue
• Fix for cacheallusers for arcgisAuth user role
• Fix for delete error when verifying write permissions
• Fix for feature services modified in lasy X days quick scan shows undefined in confirmation
• Fix for FGDB multipart uploads not being placed in correct folder
• Fix for for split replica backup / restore
• Fix for IWA ArcGIS login authentication
• Fix for IWA ArcGIS Login option
• Fix for MongoDB issue using localhost
• Fix for Skip Visualization options
• Fix for skipVisuzation settings issue
• Fix to allow login with useArcgisAuth and OAuth2WithCredentials
• Fixed duplicate name during user backup retry
• Identities: Fix for OAuth2WithCredentaials save issue
• Log: fixed visual bug in backup log
• Log: Fixes for log errors that are objects
• Logs: log export now properly exports errors
• Postprocessing: fix for additional Url Dependencies not automatically rewiring to match dependencies new URL
• Postprocessing: Fix for additional url rewire not getting url from main rewire when layer is restored at same time
• Postprocessing: Fix for cache rewite registry
• Postprocessing: fixes for group sharing and relationship rewiring
• Preprocessing: fix for circular dependencies
• Preprocessing: Fix for issue where user preprocessing could cause loop
• Proxy fix for BMOFetch
• Restore Dashboard: fix for new ArcGIS Online format
• Restore Dashboard: fix for new ArcGIS Online version error
• Restore Feature Service: Added fix for if layerServiceDefInfo is an empty object
• Restore Rewiring: Fix for Web Map Rewiring Issue
• Restore User Config: Fix for blank destination user select on userConfig load
• Restore: Added additional error handling for getAvailableServiceName
• Restore: Bug fix and improved logging for rewiring Web Mapping Application widgets
• Restore: checkremainingconfigs error fixed
• Restore: Dashboard fix for ArcGIS Online to Enterprise restoration
• Restore: fix for a feature service error
• Restore: Fix for adding items to groups when that group has only group admins contribute content
• Restore: Fix for an issue publishing items from a service definition
• Restore: fix for call stack issue in backup / restore
• Restore: fix for checking for duplicate service renaming
• Restore: Fix for featureServiceHosted exception bug
• Restore: Fix for group name filter
• Restore: Fix for individual restore filtering
• Restore: fix for issue where user config page could be blank
• Restore: Fix for multipart feature service restore during updateDefinition for hasCapabilities field
• Restore: Fix for nonstandard layer IDs being updated after creation
• Restore: Fix for postprocessing relationship rewire not keeping user applied changes
• Restore: Fix for publishing map services from service definition in ArcGIS Online
• Restore: Fix for user page allowing continue if users aren't configured
• Restore: Fix for view restore for feature services with multiple layers
• Restore: Fixed feature service restoration using changeTracking for ArcGIS Online orgs
• Restore: Fixes for view restoration with public source and also properly assigns ownership in postprocessing
• Restore: potential fix for not rewiring dependency
• Restore: potential fix for web map rewire error
• Restore: Updated view restore to fix relationship errors
• Save Identity: Fix for S3 bucket checking
• Scheduled Backup: fixed an issue for item and feature service modified quick filter not selecting content
• Scheduled Scans: backup options number in confirmation now shows correct number
• Scheduled Scans: fix for showing as a single number with digits for days/hours instead of breakout of days hours
• Settings: Fix for token expiration warning when using roles

Version 1.3.1

New Features and Improvements

• User Config: import user mapping on user config by loading CSV
• User Config: add 'ignore' option for destination users (if non-owner of items)
• User Config: Add select all empty options button near global settings
• Restore User Config: Import CSV mapping added to chose valid usernames to be created
• Restore User Config: Find and replace tool to format new usernames in bulk
• Restore Selection: Added CSV import to bulk select restoration items by ID
• Improvements to content caching for larger organizations
• Restore: feature service publish retry with stripped parameters on fail
• Restore: publish improvements for TPKs and Feature Service Views
• Restore Feature Service: update feature service accuracy improvments
• Filters: change title filter to "not contain" instead of "not"
• More efficient debug logging
• Updated ownerFolder filter to accept folder as a field
• Config: Added nodeconfig setting for maximum service name size
• Config: Added showExactCompletion to nodeconfig settings to show the exact number next to the percentage
• Added option for enabling fetch engine debugging
• Improved organization caching for large organizations over 10,000 items
• Improved error reporting for Createfolder actions
• Memory improvements for backup status

Bug Fixes

• Identities: fixed issue with OAuth2WithCredentials not authenticating correctly
• Manage Identities: fix to prevent infinite login loop if trying to use a non-administrator role
• Managed Identities: Fix for load issue with Azure credentials
• Restore: Fix for item ID restoring to a different destination for registered service
• Restore: Fix for table restoration for feature service view processing
• Restore: Fix for groups reporting owner as backup owner instead of token owner in createGroup
• Restore: UserAgent fix for fetch upload
• Restore Feature Service: fix for non-sequential IDs
• Restore Feature Service: publish changes the service name if service name taken error occurs
• Restore Feature Service: Fix for replace issues in updating sublayers
• Restore Feature Service: Fixes for table feature service restoration
• Restore Feature Service: Fixes for restoration to Enterprise versions from an ArcGIS backup with change tracking
• Restore Groups: support for shared update groups and admin control groups
• Restore Groups: Fixed group dependencies with gallery apps
• Restore Groups: Fix for restoring groups with member names that have changed on the destination
• Restore Groups: Fix for issue with adding users and items to groups
• Restore Users: Fix for error creating new users with OAuth2WithCredentials
• Restore Users: fix for an issue with usertypes
• Restore Users: user restore now checks if user level update is necessary
• Restore Users: fix for issue with updating user level in 10.6.1 machines
• Restore Postprocessing: Fix for registered servce rewiring with data JSON
• Restore Postprocessing: Fix for Feature Service View postprocessing crash while adding to service definition
• Restore Postprocessing: Fix for rewiring web mapping apps and instant apps dependencies
• Fix for determining dashboard version
• Fixed Confirmation popup when adding more than a page of Users or Groups does not complete
• Fix for CSV filter formatting
• Better support for backing up and restoring Instant Apps
• Fix for Restore Log deletion with incomplete db entry
• Error handling for timeouts for the organization's cache
• Fix for disk space checking network drive symbolic links
• Fix for custom fetch headers
• Fix for select all button for selection grids
• Fix for issue with the export BMO logs button

Version 1.3.0 Release Notes

New Features and Improvements

• BACKUP
• Backing up some large Feature Services can fail during a FGDB export. This update will allow users to backup a feature service from a replica, in the event the original service fails.
• Another potential backup option for Feature Services includes service definitions.
• Backing up Scene Services has been improved.
• RESTORE
• Users now have the option to restore a Feature Service from a Service Definition.
• Users can now apply saved mapping options during the restore process.
• Improvements have been made to restoring Scene Services.
• Users now have the option to tag all restored items with specific tags as part of the process.
• Users can now update Registered Services urls during postprocessing.
• Postprocessing now includes a global find/replace for remapping URLs.
• FILTERS
• When users are selecting multiple filters, they now have the option to determine whether the filters will filter for content that satisfies ALL of the filter criteria or ANY of them.
• The filter for ‘Users’ now has an option for filtering based on whether or not the user is a member of a specific group.
• Selection filters now have the option to filter by ‘contains’.
• Users can now bulk select / deselect content during on the visualization screen.
• We have added edit-in-place functionality for quick filters.
• The quick filter options now appear in alphabetical order.
• SETTINGS
• Managed Identities now has an option to save the credentials for an identity that uses OAuth2 authentication. This will prevent errors caused by tokens expiring in the middle of an operation. Note: This will not work for identities that use SAML
• Users can elect to receive an email when tokens expire for any of their registered identities.
• When performing a backup, if the number of items, users, and groups being backed up is more than 1000, the visual preview will be disabled. Instead, the preview will switch to only using verbal view. This prevents browsers from crashing due to the amount resources used for the visualizer.
• Users can now set the server log level in the options menu.
• Users can now specify e-mail recipients for scheduled scans.
• Users can now edit a backup’s name during the preprocessing step just before confirmation.
• BMO now verifies a user is a full admin in an ArcGIS Organization before saving their identity.
• There is now a confirmation when saving settings during postprocessing.
• A call-to-action to help users understand how they can interact with the visualizer on backups/restores was added.
• Users can now export a set of logs that are commonly used when working with support.
• The server config options now support custom fetch headers.
• SERVER
• The server has improved cleaning process on things that expire.
• Cancel functionality for backups that have not been completed has been improved.
• The operations for e-mailing the results of On-Demand Backups has been shifted to work serve-side, rather than client side.
• Backup My Org will now periodically check identities for invalid tokens and issue warning or error messages, as appropriate.
• We have added support for custom headers.

Bug Fixes

• Backup Status fix for memory crashes on very large On Demand backups
• When an Item is related to itself, it no longer causes the visualizer to crash.
• Backups no longer get stuck in the ‘Retry in Progress’ state.
• BMO now has error handling for when write-file permissions are missing.
• Reporting for errors with exceptions has been improved
• Fix for saving Azure and Google storage options in Managed Identities
• BMO no longer allows a backup with only errored items to proceed past the pre-processing screen.
• When specifying the save location for an identity, BMO now checks directory access permissions.
• If there was an issue when caching an organization’s content, an error or warning message (as appropriate) is displayed to let the user know.
• Fixed bug where the update group owner process would fail if the old and new owner were the same user.
• Fixed restoration failure when a group is set to ‘Create New’ during the restore process.
• Fixed error reporting issues for unzip failures.
• When looking up an item by ItemID in ArcGIS Online, BMO now checks to see if the item is in the appropriate organization.
• Fix issues when restoring map services / tile packages.
• Errored items no longer prompt for options during the restore process.
• Added check to make sure a relationship cannot be added to itself.
• When restoring Users or Groups, the displayed text no longer shows “Following users were not found” when there were no issues.
• Fixed bug where double-clicking doesn’t allow you to view an advanced restore / select backup if the process isn’t complete.
• Fix for EISDIR illegal operation on a directory
• Fix where save confirmation popup was only displaying for some mappings
• Skip ignored items from previous step for uneditable item configuration
• Fix for zip failures on scheduled scan
• Fixes for error status on scheduled backups
• Fixed bug where certain settings were not being updated when moving to previous steps during the Scheduled Scan settings.
• Delete Scan prompt properly references scan instead of asking to delete ‘undefined’
• Scheduled Scan confirmation page no longer states it will backup 0 items, users, and groups.
• Icons are now stored locally within the application instead of relying on outside calls.

Version 1.2.1 Release Notes

New Features and Improvements

• Google Cloud Storage Integration
• Azure Storage Integration
• Find and Replace for Postprocessing Rewiring

Bug Fixes

• Restore: Fix for web mapping applications without data
• Restore: Fix issue with out of sequence layers
• Restore: Fix for Vector Tile Layers failing with type not supported
• Restore: Better restore cancellation
• Restore: Fix for 10.9+ layers starting with numerical character
• Restore Config: Improve group config group select
• Restore Config: Improve user config with alphabetized and filterable input
• Backup Preprocessing: Fix error handling for preventing infinite dependency loop
• Postprocessing: Fix for URL rewires disappearing when changing items
• Caching: Fix for fetching over 10k users in org
• Patch for potential node module vulnerabilities
• Fix for persistent EULA Popup
• Users and Group Config: going back to config page choice is lost in selection
• Item Config: Select All Create New or Ignore
• Better error handling for getDiskSpace failures

Version 1.2.0 Release Notes

New Features and Improvements

• Amazon S3 Bucket Storage Option
• Restore: Original IDs preserved for ArcGIS Enterprise 10.8 and higher servers
• Backup: Storage Space Estimator when selecting content for backups
• Improvements to Notebook restoration
• Role manager now lets you know if you have expired identities on starting edit

Bug Fixes

• Fix for identity display issues for some portals
• Fix for organization fetch for over 10,000 users
• Fixed display issue for restore content selection
• Backup: Fix for visualization quick filter selection
• Fix for allOrgItems quick filter not completing
• Restore: Fix for different Dashboard Versions
• Fix for Roles Filter Caching
• Fix for role admins to now be superusers
• Fixed bug where error modal wouldn't show up in role setup

Version 1.1.1 Release Notes

New Features and Improvements

• New security option for ArcGIS organization logon for BackupMyOrg client access
  By setting the use to true in the nodeconfig.json settings, you can secure access to the BackupMyOrg app page to an authenticated user from any of your ArcGIS licensed connectors.
• Option for Backups to delete after X days
  For easier management of old backups, we offer the option to automatically delete backups after a set period of time.
• Backup Logs: Column to select to opt out of delete backup after X days
  As well as the option to delete after a certain period of time during the backup, you can also set expirations to delete in the backup log as well. You can click on the dates to be deleted button and set or remove the expiration time.
• Backup option to exclude items with certain tag
  Exclude certain items with a specific tag for easier filtering of unwanted content during full organization or individual backups.
• Backup option to exclude items with certain owner
  Exclude owners such as default esri users for easier filtering of content.
• Backup/Restore log: save the dgrid view of the logs
  Gives you the option to download the grid output using the export logs button.
• QuickFilter: Feature Services that have been modified within last X days / data range
  This new quickfiler will parse through each feature service and look for the latest modified data and add that to the backup if it meets the date criteria.
• Restore: Backup Registered Services as hosted service with wildcard regex
  This will allow you to specify a registered service url that is sync enabled and public that will backup as a hosted service, and when restored that data will live on the destination organization. Wildcards are accepted in the field to get more than one similar url. You can list multiple registered services by separating with a comma.
• Retry failed options button for Backup
  In the backup log, there is now a retry button for retrying content that returned an error during the backup process.
• Clone log that lists the dependency itemIDs that have changed
  In order to help track old and new itemIDs across destinations, you can download a rewired items report by clicking the export button in the restore logs.
• Quick Filter options to match Backup > Advanced Quick Filters
  The quick filter options are now available in both the advanced quick filters and the quick filter selection areas.
• Backups can now filter down to hours
  You can now set Items Created in Last X Days quick filter down to hour granularity for more accurate selection of backup items.

Bug Fixes

• Fix for dashboards restorations between new version and dashboard classic
• Fix for dashboard rewiring issues
• Fix for role names on user filter
• Fix for deselect nodes for users on full org restore selection causing lockup
• Fix for createUser and make sure that multiple new users are created properly
• Fix for alternate thumbnail storage issues during backup
• Fix for restore users endpoint in 10.6 stopping preprocessing
• Fix issue with currentVersion check crashing backup

Version 1.1 Release Notes

New Features and Improvements

• Cloning Button Functionality
  • The cloning workflow with guide you through the entire backup and restoration process with additional options
• Support for Web Experience Item Type
  • If a web experience contains widgets not present in the destination environment, the restore will fail.
  • If the ArcGIS version of the backed up Web Experience and the Destination Environment do not match, a warning message will be shown in the restore preprocessing stage. This is because the data structure of web experience configurations has changed between versions, which may cause a number of issues ranging from format changes to feature services not displaying.
• Backup and Restore Visual View refactor for better performance
• Backup and Restore performance improvements
• Preprocessing has been refactored for better performance
• Restore Selection: Search Nodes > Item > By Owner
• Restore Selection: Search Nodes > Item > By Group
• Caching: Better fetching for items, groups, and users of large organizations
• Restore Log: New option to email new users credentials once they are created

Bug Fixes

• Backup > Quick Filter: read correct identity / get cache when no cache available on selecting tab
• Backup > Advanced > Quick Filters: loading indicator while organization caches
• Backup > Advanced > Quick Filters: handling for cases where quick filter does not finish
• Backup Selection Cache: fixed an issue when caching does not finish for large organizations
• Backup: removed reported undefined users
• Backup: Fixed issue with the owner of groups added to dependencies
• Backup: export geodatabase fetches will now retry on fail with a configurable amount
• Restore Rewire Config: Remove undefined rewire options
• Restore Rewire Config: If url with id is specified for rewiring, apply to all similar layers
• Restore: copy symbologies working when creating feature services
• Restore: fix error updating relationship if both item types are not owned by the same owner
• Restore: Fix for restoring Non-sequential IDs of Feature Services

Version 1.0.0.6 Release Notes

• Fixed create user error with restoration on ArcGIS Online
• Fixed 10.6 issue with user backup/restore
• Fixed Feature Service Restore with non-sequential IDs

Subscribe to BackupMyOrg Updates

Click here to subscribe to BackupMyOrg updates

Other GEO Jobe Products

Admin Tools

GEO Jobe's Admin Tools for Portal is a suite of tools used to streamline administrative tasks for ArcGIS Online and ArcGIS Enterprise portals. Admin Tools specializes in workflows that allow bulk processing of administrative tasks such as updating user roles and permissions, viewing item dependencies, copying web map symbology, and managing sharing, tagging and deleting content for items, users, and groups. In addition to bulk operation workflows, Admin Tools also provides features such as CSV import and export for updates to content, thumbnail creation tools, and cloning capabilities, giving the administrator the ability to move items, users and groups from one ArcGIS organization to another.

CleanMyOrg

GEO Jobe's CleanMyOrg is an application that scans your ArcGIS Online or ArcGIS Enterprise organization for common issues to maintain order and efficiency across all your items, user and groups. After completing an on-demand or scheduled scan, ArcGIS administrators can address any issues with built-in resolution tools. CleanMyOrg finds inactive users with scans such as identifying users that have not logged in within a certain amount of time, finding users that are disabled, or users that do not have any content. Group scans can make sure that groups stay relevant by checking for groups with no items, members, or duplicate content. Item scans can help find broken references in Web Maps, check Registered and Hosted Services for valid responses, as well as provide a variety of item monitoring and tagging options. Clean My Org can be deployed as a web service on your server or locally on a client's machine.

Scheduler for ArcGIS

As you manage your ArcGIS System, you know the importance of running tasks on a regular schedule or in response to specific criteria. That's where Scheduler for ArcGIS comes in. Our automation tools are designed to simplify the setup and management of these tasks, empowering you to optimize your workflows effortlessly. With Scheduler for ArcGIS, you can construct code-free workflows, run tasks on a schedule or in real-time, and automate actions based on real-time events or triggers within your ArcGIS System. Say goodbye to manual execution and hello to increased efficiency and productivity. Let Scheduler for ArcGIS be your reliable assistant while you focus on what matters most.

Custom Solutions

GEO Jobe is a complete GIS service provider. From data creation to application development, GEO Jobe GIS is committed to doing whatever it takes to move our clients into a position where GIS technology can be used in the decision making process.