How do I fix a corrupt BACKUP saveset?
UP savesets can be corrupted by FTP file transfers and by tools such as zip (particularly when the zip tool has not been asked to save and restore OpenVMS file attributes or when it does not support OpenVMS file attributes), as well as via other means of corruptions. If you have problems with the BACKUP savesets after unzipping them or after an FTP file transfer, you can try restoring the appropriate saveset attributes using the tool: $ @RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM This tool is available on the OpenVMS Freeware (in the [000TOOLS] directory). The Freeware is available at various sites-see the Freeware location listings elsewhere in the FAQ-and other similar tools are also available from various sources. In various cases, a SET FILE/ATTRIBUTES command can also be used. As the parameters of this command must be varied as the target BACKUP saveset attributes vary, this approach is not recommended. Also see the “SITE VMS”, /FDL, and various other file- attributes options availa
Related Questions
- I must have a corrupt recipe in my cookbook, because I get "bad record number" and "pointer" errors. What is the best procedure to fix this?
- How do I fix a "No permissions to backup exchange server or the store was not mounted" condition ater getting a system notice?
- How do I fix a corrupt BACKUP saveset?
