[Info-vax] What is preserved by BACKUP/IMAGE/NOIINIT?

[Phillip Helbig---undress to reply]

In article
<489cb105-9de8-4ff3-892a-5545a1fd3626 at b8g2000vbi.googlegroups.com>,
abrsvc <dansabrservices at yahoo.com> writes: 

> On Feb 13, 2:26 pm, hel... at astro.multiCLOTHESvax.de (Phillip Helbig---
> undress to reply) wrote:
> > Just to be on the safe side, before booting one of my former satellites
> > from a copy of the system disk, I decided to make a backup of it.  Sinc=
> e
> > the output volume was properly initialised, I went for /NOINIT,
> > especially since I wasn't sure if the /HEADERS value on the input volume
> > is high enough for the future.  (I would then boot from the copy.)
> >
> > I got some messages telling me that the expansion size limit and logical
> > volume size on the output volume would not be preserved.  

In the case of another disk, I got the same message, but both the
cluster size and the expansion-size limit were NOT overwritten by the
BACKUP/IMAGE/NOINIT.  (This was a 4.3 GB disk.  The source had 20% free
space and the target, after the backup, 16%.  About half of the "lost"
space is due to the larger allocated size of INDEXF.SYS (1-TB limit) and
half to the larger cluster size (went from 9 to 16).  So, it looks like 
the message is incorrect.

> > Also, HELP says:
> >
> >      Beginning in OpenVMS Version 7.2, when you use the BACKUP/IMAGE
> >      command to restore or copy a volume, the BACKUP utility preserves
> >      the cluster factor.

With /NOINIT it doesn't, despite the message.

> > What, exactly, is preserved with BACKUP/IMAGE/NOINIT?

It appears that the cluster size and the expansion-size limit are not.

What about with /INIT?  Presumably everything would be preserved.