Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Backing up MIcroVAX

 
Highlighted
New Member

Backing up MIcroVAX

I have a MICROVAX 3100-96 and I need to speed up back times. Where can i get information on supported hardware for this unit
8 REPLIES 8
Highlighted
Honored Contributor

Re: Backing up MIcroVAX

Slade,

There are many ways to speed up backups, but it all depends on several factors. Hardware upgrades are a possibility, but there are other options which may speed backups without hardware changes.

For a start, What is your configuration, and what command(s) are being used for the backup operation? What network protocols are running on the system? What account (and what are the quotas) for that account?

- Bob Gezelter, http://www.rlgsc.com
Highlighted
New Member

Re: Backing up MIcroVAX

Network protocols - TCP/IP using Windows DNS

Command for backups - Back

Vax is running Open VMS I believe V5 Y2k compliant


currently it takes about 3 hours to backup less than 1000 blocks.

Highlighted
Honored Contributor

Re: Backing up MIcroVAX

> Command for backups - Back

An actual (complete) command (or at least a
few of its details) would be more useful.

> Vax is running Open VMS I believe V5 Y2k
> compliant

No need to wonder.
write sys$output f$getsyi( "version")

> currently it takes about 3 hours to backup
> less than 1000 blocks.

To what? Punched paper tape?

> For a start, What is your configuration
> [...]

I'd guess that he was hoping to learn what
you're using for a tape drive. (And, if it's
not obvious, how it's connected -- SCSI, ...)
Highlighted
Honored Contributor

Re: Backing up MIcroVAX

Slade,

Three hours for 1,000 blocks means something is either broken or mis-configured.

The command "BACK" is not a complete VMS command. This will require some more extensive digging. For a start, try the commands:

$ SHOW SYMBOL BACK
$ SHOW SYMBOL/GLOBAL BACK

By default, BACK would be an abbreviation for BACKUP, but it would then need input and output specifiers. Since they are not present, it appears that BACK is setup to invoke a command script, which means that it could be doing virtually anything (or in at least one case I encountered; nothing).

- Bob Gezelter, http://www.rlgsc.com
Highlighted
Honored Contributor

Re: Backing up MIcroVAX

Input and output specification would be a great help for being helped:
What device holds the 1000 blocks to be backed up? What device will hold the copy?
Do you use encryption/compression (if available on your VMS version)
A full specification of your backup command would help.
What VMS version? ($ sho sys/noproc)
If network, what protocol: DECNet (IV or V), IP? What versions? (if IP: $ UCX SHOW VERSION)
Willem Grooters
OpenVMS Developer & System Manager
Highlighted
Honored Contributor

Re: Backing up MIcroVAX

I don't know why everyone (else) seems to
care about your network, but if it is
actually involved in your backup scheme, then
do provide some info about it.

> Where can i get information on supported
> hardware for this unit

The VMS (VAX) Software Product Description
would probably be a good resource. Also:

http://h18002.www1.hp.com/alphaserver/vax/archive/mv3100.html
Highlighted
Honored Contributor

Re: Backing up MIcroVAX

I guess you backup to a diskette ...

In any case, you can win about 10% by specifying /group=0.

Wim
Wim
Highlighted
Honored Contributor

Re: Backing up MIcroVAX

All,

Please note Slade's post at 23:13 GMT that "the command is BACK" [without any additional items in the command line] (and my response at 23:31 GMT).

Upon reflection, it is also well within the range of possibilities that "BACK" does far more than simply run BACKUP. In that case, the performance issue (I deliberately do NOT say "problem") could be something else entirely.

While Slade does not say so, the recent ITRC registration would seem to imply that Slade may have had a system "dumped" into their responsibility recently.

- Bob Gezelter, http://www.rlgsc.com