                                             H                     Spiralog____________________________________________!                     Release Notes     !                     February 1997                   F                     Software Version:             Spiralog File SystemC                                                   for OpenVMS Alpha =                                                   Version 1.2   G                     Operating System:             OpenVMS Alpha Version 5                                                   7.1                  J           ________________________________________________________________           February 1997   B           Possession, use, or copying of the software described inC           this documentation is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  A           While Digital believes the information included in this E           publication is correct as of the date of publication, it is +           subject to change without notice.   @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  /            Digital Equipment Corporation 1997.              All Rights Reserved.  ;           The following are trademarks of Digital Equipment =           Corporation: DEC, Digital, OpenVMS, POLYCENTER, VAX 9           DOCUMENT, VMS, PATHWORKS, and the DIGITAL logo.   3           The following are third party trademarks:   9              POSIX is a registered trademark of the IEEE.   @           All other trademarks and registered trademarks are the/           property of their respective holders.   E           This document was prepared using VAX DOCUMENT, Version 2.1.                                  C   _________________________________________________________________   C                                                            Contents       1   1  Deciding Whether to Use Spiralog Version 1.2   (   2  What's New in Spiralog Version 1.2?  6         2.1   Compatibility with OpenVMS Alpha VersionC               7.1...........................................    2-1 C         2.2   Known Problems that Have Been Fixed...........    2-2   &   3  Upgrading to Spiralog Version 1.2  :         3.1   Restart Your Backup Schedule After UpgradingC               from Spiralog Version 1.0.....................    3-2 C         3.2   Avoid Mixing Version 1.0 and 1.2 Servers......    3-2   $   4  Products That Are Not Supported       5  Known Problems   8         5.1   The System Fails if You Restore Files to aC               Disk that is Nearly Full......................    5-1 7         5.2   Insufficient Memory Can Make File Restore C               Sessions Hang.................................    5-2 6         5.3   Volume Restore Sessions Do Not Check theC               Target Device.................................    5-2 C         5.4   Page and Swap Files Are Not Supported.........    5-3 ;         5.5   GETDVI's LOGVOLNAM Item Code Returns the Null C               String........................................    5-3 ;         5.6   You Cannot Use the PRODUCT Command to Install C               onto Spiralog Volumes.........................    5-4 C         5.7   BACKUP May Return the Wrong Status............    5-4 6         5.8   Documentation Errors in the Programmer'sC               Guide.........................................    5-4   C                                                                 iii                          I                                                                         1 I         _________________________________________________________________   I                              Deciding Whether to Use Spiralog Version 1.2     B               OpenVMS Alpha Version 7.1 supports two file systems,C               Files-11, the original OpenVMS Alpha file system, and G               Spiralog. By default, Files-11 is used for all disks, but G               if you wish, you can use Spiralog for some or all of your                user disks.   E               Before deciding to use Spiralog, carefully consider the "               following tradeoffs:  &               o  Benefits of Spiralog:  7                  -  Very fast online backup and restore   I                  -  Improved performance for write-intensive applications   E                  -  Scalability to support large numbers of files and $                     very large files  I               o  Temporary restrictions, which Digital plans to remove in .                  a future release of Spiralog:  F                  -  It is vital to ensure that Spiralog volumes do notE                     run out of disk space. Unlike other file systems, D                     Spiralog needs disk space to delete files and to*                     update existing files.  C                     This means that when the disk becomes full, you E                     may not be able to free up disk space by deleting I                     files. If this happens, you will have to create a new F                     Spiralog volume on a bigger disk, and then migrateI                     the data from the disk that is full to the new bigger H                     disk, as described in the Troubleshooting chapter of8                     the Spiralog System Manager's Guide.  D                  -  The disks that you use for Spiralog volumes mustG                     provide redundancy to protect against media errors, :                     such as RAID 5 arrays and shadow sets.  I                          Deciding Whether to Use Spiralog Version 1.2 1-1            0     Deciding Whether to Use Spiralog Version 1.2      C                 If you use Spiralog on a disk that does not provide B                 redundancy, a single unrecoverable bad block could=                 render the entire Spiralog volume unreadable.   A           Note also that in a future release of Spiralog, Digital =           plans to change the on-disk structure in a way that B           will not be compatible with the current Spiralog on-disk'           structure. When this happens:   A           o  You will need to manually migrate all your data from @              your Spiralog volumes. To do this, you will have toE              create new Spiralog volumes, then use the BACKUP command C              to copy the data from your current Spiralog volumes to '              your new Spiralog volumes.   C           o  You will not be able to restore your current savesnaps ?              to your new Spiralog volumes because the format of 1              Spiralog savesnaps will also change.                                                       4     1-2 Deciding Whether to Use Spiralog Version 1.2                         I                                                                         2 I         _________________________________________________________________   I                                       What's New in Spiralog Version 1.2?     H               This chapter describes what's new in Spiralog Version 1.2:  =               o  Compatibility with OpenVMS Alpha Version 7.1   4               o  Known Problems that Have Been Fixed  F                 ________________________ Note ________________________  @                 The description of Spiralog Version 1.2 featuresA                 provided in the OpenVMS Alpha Version 7.1 Release F                 Notes is incorrect. Spiralog Version 1.2 does not takeD                 any action to prevent Spiralog volumes from becomingA                 full; it does not reserve any free space or set a #                 capacity threshold.   F                 ______________________________________________________  8         2.1 Compatibility with OpenVMS Alpha Version 7.1  G               Spiralog Version 1.2 is the only version of Spiralog that 8               is supported on OpenVMS Alpha Version 7.1.  I               If you are using a previous version of Spiralog and want to H               upgrade to OpenVMS Alpha 7.1, you must upgrade to SpiralogD               Version 1.2. Note that you must deinstall your currentE               version of Spiralog before you upgrade to OpenVMS Alpha E               Version 7.1, otherwise you will encounter problems with H               the BACKUP command, the print and batch queuing system andF               DECdtm services. See the Spiralog Installation Guide for               more information.             I                                   What's New in Spiralog Version 1.2? 2-1            '     What's New in Spiralog Version 1.2? +     2.2 Known Problems that Have Been Fixed     +     2.2 Known Problems that Have Been Fixed   D           The following problems, described in the Release Notes forC           Spiralog Version 1.1, have been fixed in Spiralog Version            1.2:  D           o  GETDVI's MEDIA_TYPE and MEDIA_NAME item codes no longer6              return null strings for Spiralog volumes.  B              MEDIA_TYPE now returns the string "FS" and MEDIA_NAME@              now returns the string "F64" for a Spiralog volume.  ?           o  You no longer have to reinstall Spiralog after you C              reinstall or upgrade the operating system; the process D              of installing OpenVMS Alpha Version 7.1 does not remove6              any files that Spiralog Version 1.2 uses.                                                          +     2-2 What's New in Spiralog Version 1.2?                          I                                                                         3 I         _________________________________________________________________   I                                         Upgrading to Spiralog Version 1.2     F                 ________________________ Note ________________________  ?                 If you are upgrading from a previous version of =                 Spiralog, it is important that you follow the D                 instructions in the Spiralog Installation Guide very                 carefully.  E                 Because of various incompatibilities between previous C                 versions of Spiralog and OpenVMS Alpha Version 7.1, @                 if you do not follow those instructions you willE                 encounter problems with the BACKUP command, the print E                 and batch queuing system and DECdtm services. See the A                 Spiralog Installation Guide for more information.   F                 ______________________________________________________  I               The rest of this chapter provides information for customers E               who are upgrading to Spiralog Version 1.2 from Spiralog                Version 1.0.  E               Spiralog Version 1.0 and 1.2 save trails have different 2               formats. This means that you should:  B               o  Restart Your Backup Schedule After Upgrading from%                  Spiralog Version 1.0   9               o  Avoid Mixing Version 1.0 and 1.2 Servers   D               Spiralog Version 1.1 and 1.2 save trails have the sameH               format, so you do not need to restart your backup scheduleF               after you upgrade from Spiralog Version 1.1, and you can7               mix Spiralog Version 1.1 and 1.2 servers.         I                                     Upgrading to Spiralog Version 1.2 3-1            %     Upgrading to Spiralog Version 1.2 N     3.1 Restart Your Backup Schedule After Upgrading from Spiralog Version 1.0    B     3.1 Restart Your Backup Schedule After Upgrading from Spiralog         Version 1.0   >           You must restart your backup schedule after you have@           upgraded from Spiralog Version 1.0 to Spiralog Version           1.2.  E           For each of your Spiralog volumes, the first scheduled save 0           after the upgrade must be a full save.  =           If the first scheduled save after the upgrade is an D           incremental save, the save will fail with an error message           like this:  I           %SPIRAL-E-STRAILNOACC, unable to access the volume's save trail #           FSA100:[000000]save.trail K           -BCK-E-STRAILBAD, file is either corrupted or is not a save trail   0     3.2 Avoid Mixing Version 1.0 and 1.2 Servers  B           In an OpenVMS Cluster, we recommend that you upgrade allE           Spiralog Version 1.0 servers for a given volume at the same            time.   @           Spiralog Versions 1.2 cannot read Spiralog Version 1.0D           save trails, and vice versa. So, if you upgrade one serverC           and not the other, a scheduled incremental save will fail B           if the last scheduled save was done by the other server.A           Your backup schedule will be disrupted because you will >           be forced to do a full save when you wanted to do an           incremental save.                             )     3-2 Upgrading to Spiralog Version 1.2                          I                                                                         4 I         _________________________________________________________________   I                                           Products That Are Not Supported     H               Digital does not support the use of the following products(               with Spiralog Version 1.2:  0               o  DEC TCP/IP Services for OpenVMS                 o  PATHWORKS  =               o  POLYCENTER Archive Backup Server for OpenVMS   H               o  POLYCENTER File Optimizer for OpenVMS (originally known                  as DFO)  +               o  POLYCENTER HSM for OpenVMS   "               o  POSIX for OpenVMS  -               o  Storage Library System (SLS)   ;               o  Third-party software disk caching products                                   I                                       Products That Are Not Supported 4-1                          I                                                                         5 I         _________________________________________________________________   I                                                            Known Problems     G               This chapter describes known problems with Version 1.2 of                Spiralog:   H               o  The System Fails if You Restore Files to a Disk that is                  Nearly Full  H               o  Insufficient Memory Can Make File Restore Sessions Hang  G               o  Volume Restore Sessions Do Not Check the Target Device   6               o  Page and Swap Files Are Not Supported  E               o  GETDVI's LOGVOLNAM Item Code Returns the Null String   C               o  You Cannot Use the PRODUCT Command to Install onto !                  Spiralog Volumes   3               o  BACKUP May Return the Wrong Status   ?               o  Documentation Errors in the Programmer's Guide   C         5.1 The System Fails if You Restore Files to a Disk that is              Nearly Full   G               Your system may fail if you use a file restore session to 9               restore data to a disk that is nearly full.   B               If the disk becomes full when a file restore sessionD               is restoring data to it, your system may fail. If thisH               happens, use the SPIRALOG CANCEL RESTORE command to cancelF               the file restore session as soon as the system restarts.          I                                                        Known Problems 5-1                 Known Problems?     5.2 Insufficient Memory Can Make File Restore Sessions Hang     ?     5.2 Insufficient Memory Can Make File Restore Sessions Hang   A           If your computer does not have enough virtual memory, a B           file restore session may hang instead of failing with an,           insufficient memory error message.  E           Set your process PGFLQUOTA quota to at least 500,000 before D           you start or continue a file restore session. File restore>           sessions may require a significant amount of virtualC           memory; the more files you are restoring, the more memorye           the session needs.  A           If your file restore session hangs, follow these steps:V  B           1. Abort the SPIRALOG RESTORE FILES or SPIRALOG CONTINUE7              RESTORE command, for example, with Ctrl/Y.   B           2. Cancel the session, using the SPIRALOG CANCEL RESTORE              command.   %           3. Do one of the following:   @              o  Check that your system page file is sufficientlyE                 large, then increase your process PGFLQUOTA quota and                  try again.  ?              o  Split your restore session into several smaller E                 restore sessions, each of which restores fewer files. E                 The fewer files you restore in a restore session, the -                 less memory the session uses.i  E                 When the first session is finished, start the second.iE                 When the second session is finished, start the third,                  and so on.  >     5.3 Volume Restore Sessions Do Not Check the Target Device  C           Be very careful to specify the right Files-11 volume whenrC           you continue a volume restore session, or you may corrupti           the target volume.  @           For volume restore sessions, the following commands doA           not check that the Files-11 volume you specify as their B           parameter is the volume to which your restore session is           restoring data:r  2              SPIRALOG CANCEL RESTORE target-volume4              SPIRALOG CONTINUE RESTORE target-volume       5-2 Known Problems           I                                                            Known Problems I                5.3 Volume Restore Sessions Do Not Check the Target Device     4                  SPIRALOG SHOW RESTORE target-volume  B               For example, the SPIRALOG SHOW RESTORE command showsD               the volume restore session whose details are stored inG               SYS$LOGIN:V_RESTORE.SESSION, regardless of which Files-11_@               volume you supply as the parameter to the command.  A               Be careful to give the right Files-11 volume as theeD               parameter to the SPIRALOG CONTINUE RESTORE command. IfH               you give the wrong Files-11 volume you will corrupt it if:  D               o  The Files-11 volume contains a Spiralog volume, and  F               o  That Spiralog volume is not currently mounted on your                  computer.  F               For example, you start a volume restore session to DUA10C               then accidentally continue it to DUA8, which contains E               a Spiralog volume that is not currently mounted on your                computer:   @               $ SPIRALOG RESTORE VOLUME MUA1:USERS_WED.SSP DUA10K               %SPIRAL-I-SSPROCESSED, processed savesnap MUA1:USERS_WED.SSP; D               %SPIRAL-S-CONTRESTORE, restore session is not finishedL               -SPIRAL-I-RESTNEXTSS, use SPIRALOG CONTINUE RESTORE to process4               the next savesnap, MUA1:USERS_TUE.SSP;  .               $ SPIRALOG CONTINUE RESTORE DUA8=               %SPIRAL-S-RESTOREDONE, restore session finished.  E               Although the SPIRALOG CONTINUE RESTORE command reportedlE               that the session is now finished, it copied data to the G               wrong device. The Spiralog volume on DUA8 is now corrupt.   1         5.4 Page and Swap Files Are Not Supported   ;               Spiralog does not support page or swap files..  E               Your system may hang if you put page or swap files on a                Spiralog volume.  @         5.5 GETDVI's LOGVOLNAM Item Code Returns the Null String  B               GETDVI's LOGVOLNAM item code returns the null stringF               for a Spiralog volume. This affects the F$GETDVI lexicalI               function, LIB$GETDVI library routine, and SYS$GETDVI system                service.  I                                                        Known Problems 5-3  h  e           Known ProblemsK     5.6 You Cannot Use the PRODUCT Command to Install onto Spiralog Volumesn    C     5.6 You Cannot Use the PRODUCT Command to Install onto Spiralogu         Volumes   A           You cannot use the PRODUCT command to install a product !           onto a Spiralog volume.e  *     5.7 BACKUP May Return the Wrong Status  E           When you use the BACKUP command to copy or back up selected B           files from a Spiralog volume, if the operation completesE           successfully the command returns with the completion statuspC           symbol, $STATUS, set to %X1000000C. This problem does notsB           occur when you use the BACKUP command to copy or back up.           selected files to a Spiralog volume.  A           Similarly, when you use callable backup to copy or back D           up selected files from a Spiralog volume, if the operationC           completes successfully the routine sets R0 to %X0000000C.   6     5.8 Documentation Errors in the Programmer's Guide  0           Please note the following corrections:  E           o  When you flush a file using IO$_WRITEVBLK with the IO$M_ E              FLUSH modifier, the data is flushed after the write, not B              before as stated in Section 2.5, Using Flush to Force              Data to Disk.  C           o  When you insert a barrier using IO$_WRITEVBLK with the A              IO$M_WRITE_BARRIER modifier, the barrier is inserted B              after the write, not before as stated in Section 2.6,5              Using Barrier to Order Writes to a File.   B           o  You cannot set the caching options FIB field when youB              use IO$_CREATE with the IO$M_ACCESS modifier. You canC              only set this field on a call to IO$_CREATE if you use E              the IO$M_CREATE modifier (see Section 2.2, Selecting the 4              Caching Option for the Current Access).  ?           o  The caching attribute values shown in the table intC              Section 2.4, Setting and Showing the Caching Atribute,e2              should start with ATR$C_, not FIB$C_.           5-4 Known Problems