Automate backup for VMS v7.3

[J Ancheta]

Hello Jon,

Thanks for your reply. We believe that the VMS is a stable machine and has been stable for us for over a decade now. Only issue we've encountered twice was the TableTop had to be replaced. The last time I think something went wrong with the leader.

We are trying to remove the necessity of having the presence of an operator throughout the day. The VMS would be un-manned and a script would trigger at night and perform the backup.

If a problem arises, notifications will be sent out and if necessary someone would be sent to the machine.

J

[J Ancheta]

Hello Andy,

Thanks for your comments. I think we have a 10GB circuit. Our Fibre SAN should do the trick but it is available for me to use.

I will look into the Symantec Veritas Backup server but I doubt we have it since heavy investments are in the SAN.

The AS1200 is extremely important for one of our businesses which is why I think we have the 24x7, 3 hour on-site response with HP.

J

[jjinva]

Could you post your current backup script? Give some idea how much data is backed up? How much disk space you have available on the System being backed up?

One thing you could possibly do is backup to a saveset on the disk then ftp/copy to the SAN.

This would require some/maybe significant testing to make sure what you backed up was restorable. All this could be put in a script.

[J Ancheta]

jjinva thanks for your reply. Script attached.

Can you please let me know if this script backup everything including OS?

[RBrown_1]

You ask, "Does it back up everything, including the OS?"

Can't tell.

This command file backs up DKB0, DKB100, DKB200, DKB300, DKB400, DKB500, and DKB600. If there are other disks, they are not backed up.

Earlier in this command file is code to find all disk drives, but is broken, so that it only finds the first disk drive. And whatever drives is may find are unrelated to the drives that are actually backed up. There are many problems with the code in that section, and improvements are possible, if the command file actually used the information it was trying to find here.

Your backup commands specify /IGNORE=INTERLOCK (spelled /IGNORE=INTER in your command file), which allows files that are open to be backed up. This might work for you, and it might not. Others can give you detailed cautions.

After doing the backups, the command file tries to do a bunch of file cleanup. This may partly work, and may not work at all, since the disk names used are not the same as the disk names specified in the backup commands. The "DISK0" name created before the backups is not correctly used. The command file turns off error messages in that part of the command file, and does not check for errors, so you don't know if any of the cleanup commands work at all.

I can't tell how well this command file works for you, but it would work no worse if you deleted all lines except line 21, the seven lines beginning "$ BACKUP", and perhaps the lines that reference ZERO$DKB.

To your original question "... without user intervention", you could remove the lines 91 and 92 that ask the operator to "press return", and run the command file in batch, and hope for the best. This ought to go if the drive and tape work well. If not, then the operator should get a message requesting assistance, which is probably what you want.

[Jon Pinkley]

J Ancheta,

Have you ever restored from tape to test the backup procedure? That's the best test of whether it works. You need a spare drive you can restore to. Do you have a script or the knowledge to do the restore? Do you have a VMS distribution CD you can boot from if your system disk becomes unbootable?

The backup procedure you posted has no blade guards, other than the "press return to overwrite tape" prompt. If someone puts the wrong tape in, it will be overwritten. That would not be acceptable in our environment. Running the backup as a batch job only makes this more dangerous, unless you allow backup to do some checking before it starts to overwrite the tape.

BACKUP does have the ability to offer some protection with tape labels and /tape_expiration dates. Specifically, you are using /ignore=LABEL_PROCESSING, so backup does not check that the correct tape is being used, and you are not using /tape_expiration, so the tape is marked as available as soon as it is created. We use /LABEL=xxxx and /EXACT_ORDER to avoid using the wrong tape, and when the tape is initialized with BACKUP /REWIND, we use /TAPE_EXPIRATION=date to prevent accidentally reinitializing a tape prior to its reuse date. See help backup for more details.

Since the script you posted uses /IGNORE=INTERLOCK, backup makes a best effort backup of the drives listed, with no coordination with any other file activity on the disk, or what is being cached at the application level. If the AS1200 is a standalone system (not part of a VMS Cluster), then backup will tell you what files may not have been backed up correctly. If you aren't paying attention to the warning messages displayed on the terminal, you will have no record of what files are suspect; all that is lost as it scrolls off the screen (the files with the .log extension are not log files, they are backup listing files). Also, any files that are marked as /nobackup will have only the metadata backed up, allowing a content free file to be created with the correct size and ownership. Normally PAGE and SWAP files are set to /nobackup, because the contents of these files is not important in a recovery situation, only that they exist is important. Some sites mark files /nobackup for other reasons, and if this is done, the backups won't have the contents of the files.

Use forum search for backup /ignore=interlock to find relevant topics concerning the implications of /ignore=interlock. Given your requirement for unattended operation, and lack of shadowing, and no budget, I recommend that you use /ignore=interlock, but you need to be aware of what it means. The alternative (not using /ignore=interlock) means you will not get a backup of any file that backup can't guarantee to be valid. So any files that are opened for write access will not be backed up. See other posts for ways to get consistent copies of volatile files.

Please see the thread http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1143795 and grab the DLT_REMAINING command procedure. You can then determine how much of the raw capacity of the DLTIV cartridge you are currently using. If your data isn't changing much, then you may be able to append incremental backups to the same tape, i.e. a complete image backup with /record once a week followed by incremental backups with /norecord on a daily basis.

However, you haven't told us what you are trying to protect against. Having all your backups onsite won't help you if the computer room is destroyed by fire, etc.

Your question started out open ended, but you have since placed so many constraints on it that I wonder if a solution exists that you will find acceptable, or will be supportable.

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=965502

has a method that allows cheap PC disk storage to be used as "tape", but it probably requires more expertise than is available at your site, and it doesn't address a DR situation well, unless you create a custom bootable CD with the driver installed. And it isn't extremely fast either.

In what capacity are you involved with this system? Are you the system manager, or part of a service organization that is providing management for another company? Do you have any influence on the budget?

"The AS1200 is extremely important for one of our businesses". How much will they be willing to spend trying to recover if there is a problem? There is no free lunch. If you are responsible for this system, you need to understand your backups, and verify that they work, and that you have a reasonable tape retention policy. The VMS Documentation is available in PDF format online. If you are the acting system manager, you should be familiar with everything in the OpenVMS System Manager's Manual,Volume 1: Essentials. Here's a link to the V73 version of the manual.

http://h71000.www7.hp.com/doc/73final/documentation/pdf/OVMS_73_sysman1.PDF

At least skim the whole book. Then read the sections that apply to you. Have a terminal handy so you can try things; reading alone is not nearly as instructive as doing.

Jon

[J Ancheta]

Thanks for your comments. I'm disappointed to learn that our script can be buggy. I've attached a show devices command if this makes any sense. Looking at your responses it looks like the DKB* are our drives (I think we have 5 or 6) and probably the our script is hard coded to back these up.

Restore? Yes, with the assistance of our software vendor, we have restored a file or two from a backup tape probably 3 times in the past 10+ years. On our end, we just put the previous backup tape in the drive. We have about a 25+ tape rotation, full backup is done on a different tape every day. Every week one tape is sent to off-line storage. So far, since we've acquired the AS1200, the only problems that we've encountered was with the tape drive - once was a replacement and the other time it had something to do with the leader falling down.

[J Ancheta]

Thanks for your comments. I'm disappointed to learn that our script can be buggy. I've attached our devices to this reply.

Restore? Yes, with the assistance of our software vendor, we have restored a file or two from a backup tape probably 3 times in the past 10+ years. I don't know how they did it but for our end, we just merely put the previous backup tape in the drive. We have about a 25+ tape rotation, full backup is done on a different tape every night. Every week one tape is sent to off-line storage. So far, since we've acquired the AS1200, the only problems that we've encountered was with the tape drive - once was a replacement and the other time it had something to do with the leader falling down.

We are aware that something needs to be done, but I only have a small budget to work with.

[J Ancheta]

I was just informed that we have a software called HP data protector and a hardware called Spectra T50. I do not know what these things are but can this be used for an automated backup instead of using our DLT tape?

Thinking along the lines that this is some kind of software, can the HP data protector be loaded on the AS and perform the backups.

[Hoff]

HP Data Protector (DP) is used by some HP sites to perform remote data archival processing for various operating system platforms, and an OpenVMS client for DP is available from HP.

Google finds the Spectra Logic T50 LTO tape library, which appears to be the device mentioned to you.

Which means that yes, DP and the T50 can likely be used. (Well, I haven't checked to see if DP is compatible with the T50, but if you're already using this combination and this hardware with DP, then it obviously is.)

Yes, DCL (also) can be used (as has been mentioned in the thread). Whether with DP and the T50 library, or with your existing drive, or with a replacement drive.

DP info:

http://h20338.www2.hp.com/enterprise/w1/en/software/information-management-data-protector.html

And yes, there are other options and archival tools and products. Though having an existing DP set-up usually means you'll want to seriously investigate its use here.