I can speak for Dreamgrid, as I am the author. In Dreamgrid, backups can be set to run automatically, or you can start one at any time with a few clicks, DG always uses --publish and for IARs the --home . However, you can just type in what you want, or press the up arrow in any region and change the text there to anything you want.
This is a very good overview, but not the best OAR link as that link is describing Load OAR from an old, insecure 0.8.2.1 era. The best link is now Load Oar 0.9.0+, or
http://opensimulator.org/wiki/Load_Oar_0.9.0%2B which has more commands to rotate, move and cut and merge oars. as well as much better help.
No one should be using 0.8.2.1 or 0.9.0. It's hypergrid is 100% unsecure. It's a 10 on a scale of easy to hack, and is a 10 out of 10 for risk of data exposure. For example, anyone can read etc/password on Linux. This was fixed in 0.9.2.1 (non PBR) and all later versions. Ubit also just accepts another security fix for a simple DOS attack a few days ago. We all work very hard to keep Opensim safe and secure.
Also I disagree on OARS and --noassets. Those are not backups. They are useful if you want to copy a region on an existing server. Its okay on DreamGrid to make a copy this way, but this is not a good thing to do on Dreamgrid if you have deleted the original region and want to reload it. This is because, unlike regular Opensim, DG always clears the region database if you delete the region. This saves gigabytes of disk space over time. I run 375 regions on my laptop and reload them often for testing. My database does not grow.
Technically, IARs and OARs are just a way to move things. Neither backup everything, For example, IARs, until very recently, broke all gloss and normal maps. All old IARs destroy outfits, which has now been fixed in new IARs in the beta channel. But it will not fix old ones. Linux and other grids have to run a SQL command to fix them. DreamGrid automatically fixes old IARS.
OARs don't back up users, the necessary region files, and don't back up script state. Dreamgrid can auto-create the region file, and also check its the right size, as it examines the OAR befopre loading.
Secondly, since fsassets was created, assets will never be duplicated becasue the fsassets hash used by Robust will not allow it. As one example, a very large grid owner once attacked another major grid, and rezzed millions of prims tryng to kill it. There was effect on disk size, as they were all copies of a single cube prim which is one asset. It did put a millions of extra rows in the fsassets table, which I easily cleared.
The contents of opensim\bin\fsassets are immutable (never changed). But if your disk starts to fail, dies or gets encrypted, the --noassets switch will kill your grid dead. You don't have a backup.
FYI: All but very small grids should be running fsassets. All major grids and DreamGrid do. Without fsassets, MySQL is slow, bloated and makes it very time consuming and laggy to backup the MySQL folder. A mysqldump and bin\fsassets is the ONLY complete backup. After a non-fsassets grid is changed to fsassets, which any grid can easily do, the MySQL Database for assets drops to a few hundreds of rows and all images, mesh, scripts and other asets are zipped and saved as files on disk, which also bypass robust and are sent directly to the region. This is all much faster and safer.
Otherwise MySQL makes a very large single file on disk for assets that is prone to failure. I've personally spent weeks moving and then writing code to locate and fix a MySQL database that had a single character change due to a bit flip. Backing up OARs and their IARs would have lost 1,500 user accounts, and all settings on all regions. Most small grids wil not have this problem, though.
Speakign of backups, the best backup is mysqldumps and a copy of bin\assets and bin\region on a USB HDD, Rotate that disk periodically with a second USB disk and keep one in a fire safe, and put a copy in the cloud, Backblaze is very inexpensive. Or use dropbox, as it takes no disk space and you can easily restore as the disk is virtual. I have a 2 TB dropbox about half full of stuff, dating back to 2006.
Make sure any hard disk you get is > 8 TB, as all disks smaller than that are SMR, which are poor performing and prone to failure due to the writing technique that they use. Most > 8 TB are CMR, which is archival quality. Please do not use a a SSD for long term backup. They don't last - much like the ink used on a CDRW will die after a few years, but due to electron drifting in the silicon dioxide.