[Info-vax] FTP FYI

[Tom Wade]

On 2020-11-21 20:24, Jeffrey H. Coffield wrote:
> I was moving savesets from one OpenVMS system to another one during a 
> data center migration using (not my choice) an Amazon ftp service and 
> found that on occasion a saveset file would not restore on the new 
> system. I got this error :
> 
> %BACKUP-F-INSBUFSPACE, insufficient virtual memory to accommodate 
> minimum buffer count
> 
> Googling the error provided no help. After digging into the problem I 
> discovered the save sets in question had the correct file size but 
> contained nothing but nulls. Re-pulling the files from the ftp server 
> corrected the problem.
> 
> It was not a case of pulling the files too soon as the restore command 
> was only started until after the entire file had been pushed.
> 
> 
> 
> 
I have seen this before.  The cause (in my case) was that the saveset 
files were marked SET FILE/NOBACKUP.  When the disk they were on was 
image copied to another machine, the saveset files within the directory 
were all null blocks.  The weird error message is what Backup says when 
asked to restore from a saveset with the correct file attributes but 
containing only nulls.

> AMOK-# backup wd$:[twade...]*.*;0 temp.bck/save/nocrc/group=0
> AMOK-# set file temp.bck/nobackup
> AMOK-# backup temp.bck $13$dke0:[temp]temp.bck
> %BACKUP-I-NOBACKUP, US$:[TWADE]TEMP.BCK;1 data not copied, file marked NOBACKUP
> AMOK-# backup/list $13$dke0:[temp]temp.bck/save
> Listing of save set(s)
> 
> %BACKUP-F-INSBUFSPACE, insufficient virtual memory to accommodate minimum buffer
>  count


Tom Wade
tom dot wade at tomwade dot eu