Application Sms Backup Amp; Restore
Gro Bert
Hi @MarkVolz , there isn't a general workflow to backup data from ArcGIS Online to a local drive for the main reason that Esri takes care of the data backup behind the scenes as part of the license agreement. Have you noticed an issue with your content that is causing you to want to backup your items? Also, can you give some more detail on what you mean when you say "restore"?
ArcGIS Online and Portal for ArcGIS are similar applications, but they aren't meant to be used interchangeably like that and not all items from one will work in the other because of the way both are configured (talking more about applications not data types). Moving data layers between them will work pretty seamlessly but there could be a few bumps depending on how the ArcGIS Server / DataStore are configured within the ArcGIS Enterprise environment.
ArcGIS Hub has the ability to use drafts, so you can make changes, save them as a draft, then publish to test said changes. If you don't like it, or the changes broke some aspect of your site, you can revert back to a previous state of the site. While ArcGIS Hub basic is similar to Enterprise Sites, ArcGIS Hub Premium has no Enterprise counterpart and neither of them can be taken out of the ArcGIS Online environment because of how they tie back to the user account and data items that may be shared within the website. Hub and Sites are meant as an extension of that single organization (or deployment of Portal for ArcGIS).
I can certainly understand the want for a "trash can" type feature that you can remove or archive features and bring them back at a later time. Your best bet for that would be to post an idea in GeoNet under ArcGIS Online ideas.
You can shut down the container and copy the whole thing over to a new server, excluding the tmp, backup, and cache directories (and I think another one? ). That should work. I have some this recently, I think for a similar reason.
One of the main reasons is that when you build / bootstrap Discourse, it (launcher as I recall off the top of my head) will check if a base Discourse container (image) exists and pull down the base discourse Docker image (if not) and start up that base docker image into a container.
In a nutshell, I just confirmed that we can use docker save (for the base and the app containers) and tar for the /var/discourse directory, and completely save, transfer (backup), and restore the app this way.
In each case, I was able to load my saved docker images, untar the /var/discourse directory, run ./launcher start app and Discourse started up flawlessly and to prove it, I could do a normal backup from the UI, proving all was good.
Not sure if this answers your question (and have not been participating in the Postgres 10 to 12 upgrade or discussions); but regarding your question of just tarring up the app as a backup, and restoring, the answer is yes but you must use not only archive the /var/discourse directory, but you must also docker save your images.
Keep in mind that this method is not officially supported; but out of curiosity, I wanted to see how to do it from the sys admin perspective, and found out it was easier than my replies earlier indicated.
This type of backup is not supported and so it is not recommended, for most Discourse sys admins. I recommend users follow the recommended (and officially supported) Discourse backup and recovery method.
Being curious by nature, I wanted to see how to backup and restore Discourse in what some people might call the "traditional unix way" In a nutshell, I just confirmed that we can use docker save (for the base and the app containers) and tar for...
As a cluster administrator, you might need to stop an OpenShift Container Platform cluster for a period and restart it later. Some reasons for restarting a cluster are that you need to perform maintenance on a cluster or want to reduce resource costs. In OpenShift Container Platform, you can perform a graceful shutdown of a cluster so that you can easily restart the cluster later.
You must back up etcd data before shutting down a cluster; etcd is the key-value store for OpenShift Container Platform, which persists the state of all resource objects. An etcd backup plays a crucial role in disaster recovery. In OpenShift Container Platform, you can also replace an unhealthy etcd member.
OADP backs up and restores Kubernetes resources and internal images, at the granularity of a namespace, by using the version of Velero that is appropriate for the version of OADP you install, according to the table in Downloading the Velero CLI tool. OADP backs up and restores persistent volumes (PVs) by using snapshots or Restic. For details, see OADP features.
The CloudStorage API for S3 storage is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
App Backup and Restore is an updated version of this app that lets you make backup copies of all your installed apps. Basically, it offers all the same features as the original App Backup and Restore.
The app lets you store, archive, or delete backups (without leaving a single trace) by simply selecting them from the main interface. Once they're archived, you can even send the APK file by email, allowing you to easily store it on any disk drive. Of course, you can also restore any app.
I\'d like to change the Backup Path to a folder on the internal SD card. When I check the box for Edit Full Path, the Warning says that editing the absolute path may cause damage to the system. How do...
Uptodown is a multi-platform app store specialized in Android. Our goal is to provide free and open access to a large catalog of apps without restrictions, while providing a legal distribution platform accessible from any browser, and also through its official native app.
I have used an old version of backup and FTP for a number of years. The One-Click restore feature was incredible. Even when Microsoft management studio was problematic your restore just worked magically. This was my favorite and I literally use it everyday restoring and deploying databases. After installing the new version none of these features are now available. Is there a way of getting them back or should I look at downgrading back to the version I had from a number of years back.
It sounds as though it is permissions error but I am not sure how. I opened your software as administrator and checked permissions on the file path. I never had any of these problems with the older version so kind of expected this new version to work magically like the the last one.
I dont really want to downgrade back to the old version since one of my clients wants to make sure of the One Drive backups and my old version only supports FTP. I think not having One-Click feature is a shop stopper for me. I kind of rely on that feature now. I was thinking would there be any way to get both versions working on the same server. So use the new version for the cloud storage backups and the existing version for its awesome One-Click restore features?
I have to give everyone read/write permissions on the .bak file. Really annoying that I will have to do that for every file. I suppose a work around could be to have backups stored in a folder with full permissions then when I want to restore a database I first copy it into that folder and start from there. (not ideal)
If you have single instance where you have take that backup, then you should use separate dummy/empty instance where to restore it. I suppose that even that case you will have some issues with files e.g. hot buckets and buckets which has switch state from warm to cold or cold to frozen during your backup time. If you have used e.g. snapshot for backup then this is not so big issue. After restoration just switch this service up (change splunk node name or shutdown the primary instance first).
Once the team is further along with the design phase can you break that down from a technical perspective and the end-user experience for community feedback? Perhaps that could be here or a blog post?
Exactly what is needed for some apps. My nextcloud backup is taken within my container, it does the documented nextcloud backup steps and I never lose anything. Same for mariadb container and a few more.
For custom installed compose apps, we expect to store the original YAML (in the case where a user supplied their own) on the data pool, as well as the host mounts and other persistent data. This can be used to migrate / deploy an existing app to a new system, assuming you move the persistent App data over via ZFS Replication or some other means.
For Apps installed via the UI, those are a bit different since we have a lot of extra meta-data to consider from the UI questions. Those will be stored in the TrueNAS configuration database and have an option to export / import those config files. (JSON or YAML not yet sure). With the configuration in the DB, it means losing the boot pool you can bring your apps configuration back if you restore your config file, and manually export them if needed in the case of migrating to a new system.
But, for the sake of the many, many casual users who will not hear of best practices until after disaster has occurred, it would be good if apps could be restored from their own pool alone, even if the boot pool is lost.
d3342ee215