Microlite BackupEDGE Version 01.01.08
Naturally, the first thing I tried to do was a small test backup of about 9MB using my /etc directory. When I first tried this, the backup failed. Possibly the scan for sparse files affected the SCSI host adaptor. In any case, once I rebooted my system, I got successful backups on both of my tape drives.
The reason for the reboot was that I used another computer to test backups over the network, a process Microlite calls “remote backups”. I reconfigured BackupEDGE to use ssh because I already have ssh working with public key authentication, thus allowing secure transfers of data without passwords. I was able to configure the client machine and start a backup, but it locked up the server. Oops. After rebooting the server, I was able to back up on the server, but not on the client. My second attempt did not crash the server, which was an improvement. You also can use any host to administer another host. Apparently, the rsh or ssh connection is made and broken over the course of a session, so you may have waits while hosts authenticate.
Verifications can be done against the original file or by checking the CRC checksums stored with the data. The latter is useful for verifying a file after the original has changed. It is also a quick-and-dirty acceptance test of tape-drive head alignment, which is useful for less expensive tape drives, like some of the QIC offerings. Verification can be done as a routine part of the backup process, which is great.
Restoration is easily done from the edgemenu program. You can restore redirected files to another location via any of the three interfaces. For the GUI addicts, there is an X-based restore tool, edge.emx (see Figure 5), that you may launch from edgemenu. It is suited for restoring individual files. Selecting a directory also selects the files and directories under it, if the directory is not expanded. The process is simple enough: select a database and click on it. Click your way down the tree until you select all the files you want. Click on Transfer to add the selected files to the restore window. Then click on Restore to restore the data.
The manual is large, over 270 pages. With reasonably large type and a fair amount of white space, it is easy to read. Seventy pages of the manual duplicates the man pages, and some of that is for operating systems other than Linux. Then there is another 130 pages of documentation on the crash recovery software. A good contents page is provided in each volume, but the index is a bit sparse. For example, there is no entry for sparse files, and you have to already know that Microlite calls them “virtual files”. Overall, the documentation is plentiful, extensive, conversational and easy to read. Microlite gets an “A” here.
Part of the documentation expands on error messages. When a program produces a terse error message, you can look it up in the documentation and get a more detailed explanation. Other software vendors should learn to do this.
The documentation even tells you how to customize some aspects of BackupEDGE. For example, remote backups are done using rsh. However, the exact steps you need to take in order to use ssh are documented.
Customer support is provided via e-mail, phone, fax or web site. There is no e-mail list that allows customers to exchange experiences directly. I did run into one problem that led me to customer support: I tried to substitute ssh for rsh. We never did get that to work, possibly because I took sick while trying to debug this problem. The support I got was polite but appeared to be perfunctory. E-mail responses were timely and had I not gotten sick, we probably would have gotten ssh working in time for this review.
Disaster recovery should be very easy to do with RecoverEDGE, BackupEDGE's disaster recovery software, once you have it set up. I say “should be” only because I actually have not tested the restore process. Using HP's OBDR (basically a bootable tape drive) or a floppy disk set you build with BackupEDGE, you can make a backup tape for disaster recovery. When you need it, boot to the floppy or tape drive and away you go. The Microlite RecoverEDGE software will also adjust your partition sizes as needed in case you are restoring to a larger hard drive. Even machines that back up over the Net can use RecoverEDGE, which is more than you can do with OBDR.
Please note: the current version of this product was not available at the time of this writing.
Charles Curley (w3.trib.com/~ccurley“) is a freelance software engineer, writer and occasional cowpoke in the wilds of Wyoming.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- SourceClear Open
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide