Test Drive of Orbit Delta Backup
by
Shawn M. Gordon
President
The Kompany
What it can do?
Orbit has been around for many years selling high speed and online backup. I’ve used it personally for over ten years now. For the last few years they have been talking about a radical new approach to backups on the HP 3000 called Delta backup, and I’m very excited to get my hands on it. Delta backup takes the concept of a partial backup to a new level. Instead of storing the files that have been accessed since the last backup, it actually stores the pieces of the files that have changed, not the entire file. So in the case of a database, you could have a table with 20 million records in it, but if you only add 10,000 a day, and you do a delta backup every day, then you will only store the 10,000 records.
This new functionality is an optional part of Backup+, so you can still do your online backups and zero downtime backups and all the other great tricks that are part of Backup+, you just have a new weapon in your arsenal for improving up time.
How does it work?
The focus on this review is for the Delta backup since that is the really new piece here. I’ll talk a bit about some of the other features, but this is the neat bit. I’ve already explained the idea of how it works, it takes the concept of a partial backup and makes it more granular, we are talking about pages that have been touched now instead of files. The first time you do a baseline backup for Delta it starts a file monitor that tracks the changes to the fileset that was used for the baseline. This is cumulative, so the pieces of files that were modified on Monday are also on Wednesday’s backup for example. The technology is similar to what is used in their online backup, at least on the surface to someone like myself. Because of this logging process, it means there can be no more than 5 Delta or Online (cumulative) backups going at once. Let me explain this piece a little more, since it can be confusing at first.
Because of the logging that goes on, you could have done 4 different Delta baseline stores, so @.@.PROD, @.@.AR, @.@.DEV, and @.@.QA. Once you have done the baseline delta backup, these logging processes stay “live”. So say you want to go and do an ONLINE backup of some other file set. This would still be acceptable, because you are now at the limit of 5. But if you had 2 tape drives, and tried to do 2 online stores at the same time, this would have exceeded the threshold of available logging. To me this seems like a pretty reasonable limit, I’m not sure why it’s there, but you need to be aware of it.
Features
Backup+ contains many features to allow for high speed, online backup. Options such as ONLINE and ZERODOWN will let users continue to work during a backup and once they synchronization point is reached, they will be suspended for a minute or so while the tape finishes writing. There is the Delta backup option, which we are covering mostly. There are the compression options to improve your tape usage, however if your tape drive supports hardware compression, you are better off using that because it will be faster typically than software compression. You don’t want to use both because that will slow it down and make it larger probably. There is a very robust file selection protocol for STORE and RESTORE that allows you to use a wide variety of file objects such as type and various dates to select files, rather like MPEX.
Store to disk is also a very cool option. I did a test storing a database to disk and it was so fast and so small that I thought there must be a problem. I restore the database into another group, and it was fine. If you have the disk space for it, the store to disk is a great way to do your backup quickly, and then move the file off to tape. There is only one thing that I don’t like about it. The file type is so bizarre that you can’t use any tool that I’ve been able to find (FTP, DSCOPY, NBCOPY) to move it between systems. I would find this a very fast and convenient method to get a fileset onto a shadow machine, if there was someway to transfer the files.
A couple of options you can get are the Tape Manager and Librarian (TML) and the Restore Wizard. The TML is a very full featured tape library and management system that let’s you track everything and everywhere. It is extremely robust, but has a pure command line interface which can make it a bit tedious to learn all the commands. I was hard pressed to find any features it was lacking, overall it is well implemented. In conjunction with TML is the Restore Wizard.
Theoretically the Restore Wizard will, given a specific restore instruction, tell you exactly what tape/tapes to use. This relies on the fact that you are properly labeling your tapes as required, there is no way around this, there has to be some human intervention. I spent a fair amount of time going through the manual, and could not find anything that talked about the Restore Wizard. I had assumed there would at least be some mention of it, but I couldn’t find it.
Virtually any type of device is supported by Backup+ including auto-changers and such. You can make even more frugal use of your tapes by using appended backups, although this might become confusing unless you are carefully tracking what is where. There is a lot in Backup+, and while you can get by with using just a small amount of features, you should at least browse what is available as you might find it useful.
One other important note that people always wonder about. Backup+ uses the MPE STORE facility to put a small version of Backup+ at the front of the tape that will restore whatever is on that tape, so you will always be able to restore your information without a problem.
Installation and Documentation
For the installation you restore a single file, put the tape back online, run the program you restored, answer a couple of questions, and then all the files are restored, directory structure adjusted as required and installation programs run.
I was rather dissapointed with the documentation. It weighs in at a hefty 500 pages, and has a fair number of errors and duplicated information. It’s not really cohesive and for a new user can be very daunting. I was also dissapointed that it was only distributed as a PDF file on the HP. PDF is a pretty decent format, but the manual wasn’t indexed, and doesn’t use real page numbers, it is chapter and page within the chapter, so you can even jump to a section by looking at the table of contents. Basically the manual is almost useless in this format because it is so large and so tedious to find anything. It is also too large for most people to print out on their own. To be fair, I talked to Orbit about it, and they agreed and are fixing the online manual now, so it will be available when you see this review. I think that the quick reaction from Orbit was very positive. You can still get a hard copy from Orbit, but this is the new default.
The Test Drive
Well the first thing to do for Delta is to get a baseline store of your fileset, for my purposes that was an @.@.@ store of the whole system. On my box and tape drive it took 114 minutes to store 1.2 GB of data. I then ran a process that touched most of the files on the system but only updated a couple of datasets and flat files. I then ran the delta backup specifying the prior baseline id for the backup. This time the backup took 2 minutes and only stored those pieces of the files I was concerned with. Take a look at figure 1 to see the various dialog and statistics that took place.
Now you’ll notice an error message on TRACE.PUB.SMGA, I had done a test with this database and the Delta backup before I did the sample here, and it worked without a problem, I even rebooted the system before I did this latest test. I have no idea what this error message is supposed to mean, or why I suddenly started getting it, and points to the only other real problem with the software other than the doc, and that is the error messages. They need serious work.
The next step is the Restore process. Here is where the Delta backup can be confusing, and it’s fortunate that it is integrated with TML. In any case, what I did is physically purge one of the dataset files that was modified between the baseline store and the delta store. Now I wanted to restore the dataset file to it’s state after the delta store, so this is a two stage process. You must first restore the file from the baseline store, then take the tape that has the delta iteration that you are interested in, and restore the file again from that tape.
While this might sound like a bit of extra work, just remember that you don’t restore files that often, it is typically for emergency purposes. One thing to keep in mind, the delta backups are cumulative, much like an MPE Store partial backup, it’s just that we are cumulatively storing the pieces of the file. So if you have the need to get a file from it’s state on the third delta of a set, you only have to restore the baseline and the third delta, you don’t have to restore the first and second delta’s, which certainly reduces any confusion.
If you try to specify BASELINE on a restore from a tape that is a DELTA, then Backup+ will tell you very clearly that you have the wrong tape and instruct you to put in the right one.
Conclusions
This is fascinating, important and unique technology. People are now having enormous disk farms that have to be backed up and are requiring constant up time. You could do things like buy a backup machine and shadow to it and just back it up, but given the large amounts of data involved at some shops, it still might not be practical.
Using something like the Delta backup option in Backup+ in conjunction with their Online and Zero Downtime options can radically improve the throughput in performance. You will still need to do a new basline backup every week or so, but this does dramatically improve your overall system availability and reduce your cost of ownership for backups. DLT tapes aren’t very cheap, and neither are people that have to sit around and change tapes. Reducing all of that adds up over time.
While I wouldn’t say that the Delta option is for everyone, I can certainly recommend the Backup+ product in general to anyone that is doing backups, it’s just faster and more convenient than Store. Orbit has some of the brightest developers of any company around, and that has always given me a high confidence level in their software.
Road Report
Backup+/iX version 6.52G
ORBiT Software
315 Diablo Road, #210
Danville, CA 94526
USA
800.89-ORBIT or 925.837.4143
fax: 925.837.5752
sales@orbitsw.com
support@orbitsw.com
http://www.orbitsw.com
Backup+/iX includes the 3000 based software required to perform all the STORE and RESTORE operations.
Standard version is $1,500 to $20,000, the Online option is another $1,500 to $20,000 and the Delta option is another $1,500 to $20,000. TML is $3,000 to $4,500. Support is 15% and includes 7×24 access and new software releases. There are discounts for multiple copies. All prices are in US dollars.
Figure 1
The Kompany: FILE T;DEV=TAPE
The Kompany: BACKUPPL.PUB.ORBIT
BACKUP+/iX 6.52G (c)Copyright 1991-00 ORBiT SOFTWARE HOLDING AG 22Oct00 11:48am
Wizard module 3.46 (c)Copyright 1990-99 ORBiT SOFTWARE HOLDING AG
+------------------------------------------------+
! BACKUP+/iX : 26 DAYS LEFT IN DEMO PERIOD !
! Online module : 26 DAYS LEFT IN DEMO PERIOD !
! Delta module : 26 DAYS LEFT IN DEMO PERIOD !
! Wizard module : 26 DAYS LEFT IN DEMO PERIOD !
+------------------------------------------------+
>STORE @.@.@;*T;ONLINE;ZERODOWN;BASELINE=DC1
26 days left in BACKUP+/iX demo period; expires on 11/17/0
Building intermediate scratch files ...
Mount tape volume 1 of volumeset unnamed on dev TAPE
This unlabelled BACKUP+/iX volumeset was created Oct 19,2000 12:48:34 on dev 7
NMSTORE of BACKUP+/iX program found at beginning of volumeset
Found backup # 1 (unnamed) created Oct 19,2000 12:49:47 on dev 7
BACKUPPL written to volumeset in NMSTORE format
Using block size of 32760 bytes ...
Starting online logging ...
Selecting files for store ...
6412 files - 5299680 sectors (1.26 gigabyte(s)) of disc space to store
26 files de-selected because they are non-archivable
Optimizing selected file information for faster backup ...
Storing selected files ...
Finished storing selected files, preparing logging data ...
Storing logging data ...
Will log 576 sectors in logging pass 1
Logging pass 1 of 2 is 100% complete
Suspending users for ZERODOWN (zero downtime) option ...
Could not quiesce data base /SMGA/PUB/TRACE, error codes =-235,12
Performing secondary file scan ...
Storing final logging data ...
Will log 976 sectors in logging pass 2
Resuming users for ZERODOWN (zero downtime) option ...
Logging completed, all files have been released
Logging pass 2 of 2 is 100% complete
Writing store directory ...
Synchronization point occurred at Oct 22,2000 13:36:42
**************************************************************************
* Tape statistics for volume # 1 Volumeset: Volume: *
* compression percentage: 14 % Backup : # 1 Name: *
**************************************************************************
* total number of tape errors : 0 backup ldev number: 7 *
* total number of tape retries: 0 *
* total number of data blocks :35713 ( 4535551 sectors, 1.08 GBytes) *
* time: beginning: 11:49:56, ending: 13:39:14, elapsed: 01:49:18 *
* amount of disk space stored: 5301232 sectors ( 1.26 gigabyte(s)) *
**************************************************************************
Label tape volume 1 as containing the store directory
Store to ldev 7 completed; drive released
BACKUP+/iX version 6.52G, list date 22Oct00 01:39pm, store date 22Oct00 01:36pm
DELTA STORE=BASELINE:DC1,ONLINE,ZERODOWN
PATHNAME NOT STORED BECAUSE
/SMGA/PUB/TRACE DBQUIESCE RETURNED ERROR, CODES =\,\
FILES STORED: 6385
FILES NOT STORED: 1 (listed above)
**************************************************************************
* BACKUP+/iX online logging statistics *
**************************************************************************
* number of I number of files *
* logging sectors I modified I created I renamed I purged I saved *
* 1552 I 14 I 0 I 0 I 0 I 0 *
**************************************************************************
total number of blocks: 35713 (4535551 sectors, 1.08 gigabyte(s))
number of blocks on first volume: 35713 (4535551 sectors, 1.08 gigabyte(s))
compression percentage: 14 %
required size of filebuffer: 0 sectors (0.00 megabyte(s))
total amount of disk space stored: 5299680 sectors (1.26 gigabyte(s))
total number of tape errors: 0 + 0 errors in store directory
total number of tape retries: 0 + 0 retries in store directory
This store took 110 minutes, 36 seconds
************************************************************************
* # of files * size (Ksectors/Mb) * file type *
************************************************************************
* 1070 * 1131.02 / 276.13 * program files *
* 103 * 118.50 / 28.93 * IMAGE database files *
* 12 * 22.75 / 5.55 * KSAM files *
* 9 * 9.84 / 2.40 * VPLUS files *
* 56 * 1.15 / 0.28 * SPOOL files *
* 3831 * 367.04 / 89.61 * ASCII files *
* 2555 * 4932.64 / 1204.26 * BINARY files *
* 1195 * 32.90 / 8.03 * Byte stream files *
* 198 * 3.17 / 0.77 * Symbolic links *
* 0 * 0 / 0 * Device links *
* * * *
* 6206 * 5112.78 / 1248.24 * not modified in past 7 days *
* 6206 * 5112.78 / 1248.24 * not modified in past 30 days *
* 5946 * 4474.82 / 1092.48 * not modified in past 6 months *
* 3191 * 1958.08 / 478.05 * not modified in past 1 year *
************************************************************************
>E
The Kompany: RUN DBTREND2.PROG.SMGA
This is a perm copy of DBTREND licensed to S.M.Gordon & Associates
Begin run of DBTREND2 at 13:42:20
Enter MPE fileset - // to end: @.@.@
@.@.@
Enter MPE fileset - // to end: //
//
Loading TMLDB.DATA.ORBIT @ 13:43:07
Loading SPELL.DATA.SMGA @ 13:43:08
Loading ASMDB.PUB.SMGA @ 13:43:08
Loading DUMB.PUB.SMGA @ 13:43:08
Loading FYIDB.PUB.SMGA @ 13:43:08
Loading PIMDB.PUB.SMGA @ 13:43:09
Loading SPWDB.PUB.SMGA @ 13:43:09
Loading TRACE.PUB.SMGA @ 13:43:09
Loading TREND.PUB.SMGA @ 13:43:10
Loading KMENU.SPRING.SMGA @ 13:43:10
Loading OPSDB.PRED.SYS @ 13:43:10
Loading VEOPNT.DEMO.VESOFT @ 13:43:11
End of DBTREND2 at 13:43:11
END OF PROGRAM
The Kompany: DO BACK
The Kompany: BACKUPPL.PUB.ORBIT
BACKUP+/iX 6.52G (c)Copyright 1991-00 ORBiT SOFTWARE HOLDING AG 22Oct00 01:57pm
Wizard module 3.46 (c)Copyright 1990-99 ORBiT SOFTWARE HOLDING AG
+------------------------------------------------+
! BACKUP+/iX : 26 DAYS LEFT IN DEMO PERIOD !
! Online module : 26 DAYS LEFT IN DEMO PERIOD !
! Delta module : 26 DAYS LEFT IN DEMO PERIOD !
! Wizard module : 26 DAYS LEFT IN DEMO PERIOD !
+------------------------------------------------+
>
STORE @.@.@;*T;ONLINE;ZERODOWN;DELTA=DC1
26 days left in BACKUP+/iX demo period; expires on 11/17/0
Building intermediate scratch files ...
Mount tape volume 1 of volumeset unnamed on dev TAPE
This unlabelled BACKUP+/iX volumeset was created Oct 19,2000 14:44:42 on dev 7
NMSTORE of BACKUP+/iX program found at beginning of volumeset
Found backup # 1 (unnamed) created Oct 19,2000 14:46:25 on dev 7
BACKUPPL written to volumeset in NMSTORE format
Using block size of 32760 bytes ...
Starting online logging ...
Selecting files for store ...
17 files - 17376 sectors (4.24 megabyte(s)) of disc space to store
DELTA will actually store 17 file(s) - 1936 sector(s) (0.47 megabyte(s))
Optimizing selected file information for faster backup ...
Storing selected files ...
Store is 100% complete
Finished storing selected files, preparing logging data ...
Logging pass 1 of 2 is 100% complete
Suspending users for ZERODOWN (zero downtime) option ...
Performing secondary file scan ...
Storing final logging data ...
Will log 224 sectors in logging pass 2
Resuming users for ZERODOWN (zero downtime) option ...
Logging completed, all files have been released
Logging pass 2 of 2 is 100% complete
Writing store directory ...
Synchronization point occurred at Oct 22,2000 14:01:01
**************************************************************************
* Tape statistics for volume # 1 Volumeset: Volume: *
* compression percentage: 0.0% Backup : # 1 Name: *
**************************************************************************
* total number of tape errors : 0 backup ldev number: 7 *
* total number of tape retries: 0 *
* total number of data blocks : 84 ( 10668 sectors, 2.60 MBytes) *
* time: beginning: 14:00:19, ending: 14:01:14, elapsed: 00:00:55 *
* amount of disk space stored: 2160 sectors ( 0.53 megabyte(s)) *
**************************************************************************
Label tape volume 1 as containing the store directory
Store to ldev 7 completed; drive released
BACKUP+/iX version 6.52G, list date 22Oct00 02:01pm, store date 22Oct00 02:00pm
DELTA STORE=DELTA:DC1,ONLINE,ZERODOWN
FILES STORED: 17
FILES NOT STORED: 0 (listed above)
**************************************************************************
* BACKUP+/iX online logging statistics *
**************************************************************************
* number of I number of files *
* logging sectors I modified I created I renamed I purged I saved *
* 224 I 1 I 0 I 0 I 0 I 0 *
**************************************************************************
total number of blocks: 84 (10668 sectors, 2.60 megabyte(s))
number of blocks on first volume: 84 (10668 sectors, 2.60 megabyte(s))
compression percentage: 0 %
required size of filebuffer: 0 sectors (0.00 megabyte(s))
total amount of disk space stored: 1936 sectors (0.47 megabyte(s))
total amount of disk space selected: 19680 sectors (4.80 megabyte(s))
percentage of disk space changed: 9.8 %
total number of tape errors: 0 + 0 errors in store directory
total number of tape retries: 0 + 0 retries in store directory
This store took 2 minutes, 12 seconds
*****************************************************************************
* # of files * size (Ksectors/Mb) %ST * file type *
*****************************************************************************
* 0 * 0 / 0 * program files *
* 8 * 0.03 / 0.01 0.2 * IMAGE database files *
* 0 * 0 / 0 * KSAM files *
* 0 * 0 / 0 * VPLUS files *
* 3 * 0 / 0 * SPOOL files *
* 7 * 0 / 0 * ASCII files *
* 10 * 0.74 / 0.18 4.3 * BINARY files *
* 0 * 0 / 0 * Byte stream files *
* 0 * 0 / 0 * Symbolic links *
* 0 * 0 / 0 * Device links *
* * * *
* 0 * 0 / 0 * not modified in past 7 days *
* 0 * 0 / 0 * not modified in past 30 days *
* 0 * 0 / 0 * not modified in past 6 months *
* 0 * 0 / 0 * not modified in past 1 year *
*****************************************************************************
>