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

[Phillip Helbig---undress to reply]

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.  Since 
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.  (Actually, I
don't expect them to change, since I had used SET VOLUME (see earlier
post) to set them on the input volume; also, the disks are exactly the 
same size.)  Presumably, like with DEFINE in all tables but cluster-wide 
ones, the message that the value will be overwritten is displayed 
without checking if the value is the same.  (With DEFINE, the situation 
is probably slightly different, i.e. if the old and new values are the 
same, then no redefinition is done, probably to save overhead.)

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. 

This leads to the following questions:

Why the change with 7.2 mentioned above?

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

Is there anything which is NOT preserved with BACKUP/IMAGE/INIT?