BrightStor® ARCserve® Backup for Windows
Version 9.01 Update

17.0 Contacting Technical Support

1.0 Welcome

Note:

• If you have already installed from the BrightStor ARCserve Backup Version 9.01 CD, you don't need to install this Version 9.01 Update. If you have BrightStor ARCserve Backup Version 9 installed on Windows and are using Backup Agent for Open Files, Notes Open File Agent, Image Option, or Serverless Backup Option on that server, you must update these products before you upgrade your OS to Windows Server 2003.
• If a server which has the 9.01 level installed is upgraded to Windows Server 2003, you will need to re-apply the Client Agent for Windows in order to support VSS on Windows Server 2003.
• For Windows Server 2003 servers that do not yet have BrightStor ARCserve Backup installed, please obtain a full version of BrightStor ARCserve Backup Version 9.01 CD to avoid the update process. This CD can be obtained from the trial link on the support website: http://ca.com/solutions/enterprise/storage/arcserve_v9_windows/evaluation_form.htm
• All lines below starting with [Txxxxxx], where xxxxxx is the test fix number, are included in this update. If you received a test fix not listed below, please contact support to determine how the fix may be re-applied.

2.0 Installation Considerations

Note: After the 9.01 Update installation completes, you may be prompted to reboot your system. This typically occurs if a system driver is replaced or any files are in use when the update process replaces them.

2.1 Local Install

1. If you have received the 9.01 Update on CD, please insert the CD into CDROM and proceed to step 5.
2. Download and run the self-extracting file BABv901W.exe.

3. Choose an option to leave or delete the unpacked files after the 9.01 Update operation is completed. If you chose to leave the unpacked files, you may change the destination folder to which you want to extract the source files or click Next to extract to the default folder C:\BABv901W. Once the extraction is completed, setup automatically launches 9.01 Update package to start the installation.

4. Click Next and proceed to step 7.
5. Select Install from the Product Installation Browser.
6. Click Install.
7. Choose Local Install to apply 9.01 Update locally.

8. Choose components you want to install and click Next to continue applying the selected Updates. By default, all the available Update packages are pre-selected. For those which require pre-requisite installation cannot be selected individually. For example, Tape Library Option cannot be selected unless BrightStor ARCserve Backup Base component is selected.

9. When the installation of 9.01 Update is completed, and if you want to delete the unpacked files, the extracted source files can be deleted. If you want to leave the unpacked files, you may run the 9.01 Update again later by launching Setup.exe from the extracted folder.

10. The setup log file can be found at the system temp folder (%Temp%\CASPsetup.log).

2.1 Silent Install

1. If you have received the 9.01 Update on CD, copy the contents to a folder on the local machine and proceed to step 5.
2. Download and run the self-extracting file BABv901W.exe.

3. Choose an option to leave the unpacked files and specify a destination folder to which to extract the source files, or click Next to extract to the default folder C:\BABv901W.

4. Once the extraction is completed, setup automatically launches 9.01 Update package to start the installation. Click Cancel to exit from the setup.

5. Find Install\setup.icf file in the folder and modify this file by adding component names to ProductList= key, then save it. For example, if you want to apply Base component Update, Tape Library Update, and Disaster Recovery Update, modify the setup.icf file as follows;

   [Install]
   ProductList=ARCserve, TLO, DRO
   

   Below is the complete list of component names:

   BrightStor ARCserve Backup
   ProductList=ARCserve
   
   Client Agent for Windows
   ProductList=NTAgent
   
   Tape Library Option
   ProductList=TLO
   
   Optical Library Option
   ProductList=OLO
   
   Storage Area Network Option
   ProductList=SANO
   
   Serverless Backup Option
   ProductList=SBO
   
   Image Option
   ProductList=IO
   
   Disaster Recovery Option
   ProductList=DRO
   
   Unicenter Integration Option
   ProductList=TI
   
   NAS Option
   ProductList=NASAgent
   
   Tape RAID Option
   ProductList=RO
   
   Backup Agent for Open Files
   ProductList=BAOF
   
   Backup Agent for Microsoft Exchange
   ProductList=DBAEXCH
   
   Backup Agent for Informix
   ProductList=DBAINFO
   
   Backup Agent for Advantage Ingres
   ProductList=DBAINGRES
   
   Backup Agent for Lotus Notes/Domino
   ProductList=DBANOTE
   
   Backup Agent for Sybase
   ProductList=DBASYBASE
   
   Backup Agent for Oracle
   ProductList=DBAORA
   
   Backup Agent for Microsoft SQL
   ProductList=DBASQL
   
   Backup Agent for SAP R/3 Oracle
   ProductList=DBASAPORA
   
   Diagnostic Utility
   ProductList=CADIAG
   

6. At the command line, change to the folder containing the extracted files. Run MasterSetup.exe under Install folder with a parameter "/i:" and the path to setup.icf file. For example,

   C:\ BAB901W\Install\MasterSetup.exe /i:c:\temp\setup.icf

7. The setup log file can be found at system temp folder (%Temp%\CASPsetup.log). Please verify whether all the 9.01 Update installations successfully completed. When running in silent mode, all reboot requests are logged in the log file. After performing a silent installation, check the log file for reboot requests.

8. When the 9.01 Update silent installation is completed, the extracted source files can be deleted.

2.3 Remote Install

1. If you have received the 9.01 Update on CD. Please insert the CD and proceed to step 6.
2. Download and run the self-extracting file BABv901W.exe.

3. Choose an option to leave or delete the unpacked files after the 9.01 Update operation is completed. If you chose to leave the unpacked files, you may change the destination folder to which to extract the source files, or click Next to extract to the default folder C:\BABv901W.

4. Once the extraction is completed, setup automatically launches 9.01 Update package to start the installation.
5. Click Next and proceed to step 8.
6. Select Install from the Product Installation Browser.
7. Click Install.
8. Select "Remote Install" and continue.

9. Enter the name of the computer in the Computer Name field or select one from the list, then click the Add button to add to login to the selected server. You may repeat this process to install 9.01 Update to multiple servers. Once you have logged in to all the servers, click Next to continue.

10. The computers you selected for remote installation are listed on the screen. Double click each one of them to configure remote installation.

11. The available 9.01 Update components are listed for the target server. Choose components that you want to install and click Next to continue applying the selected 9.01 Updates. By default, all the available Update packages are pre-selected. Those which require pre-requisite installation cannot be selected individually. For example, Disaster Recovery Option cannot be selected unless BrightStor ARCserve Backup Base component is selected.

12. Repeat step 5 and step 6 for all selected servers.

13. The setup log file can be found at system temp folder (%Temp%\CASPsetup.log) on the target machine. Please verify whether all the 9.01 Update installation successfully completed or failed, as well as whether the remote machine needs to be rebooted.

14. When the installation is completed and if you chose to delete the unpacked files, the extracted source files are deleted. If you chose to leave the unpacked files, you may run 9.01 Update again by launching Setup.exe from the extracted folder. When the 9.01 Update remote installation is completed, the extracted source files can be deleted

3.0 BrightStor ARCserve Backup v9 Base for Windows

The following section addresses issues related to the BrightStor ARCserve Backup v9 Base product:

1. On NT 4.0 a RSM setting was available (it was not grayed out). Using this setting had no effect so it is now unavailable ( grayed out )on NT 4.0.
2. The WINNT\Temp folder is now backed up and restored but not the files contained in the folder. Previously we did not restore this folder at all.
3. From Manager GUI, Help, About BrightStor ARCserve Backup, License and Register did not display BAOF product even if the product was installed.
4. When a Backup of a drive was done immediately after formatting, an error E3322 occurred and the job failed.
5. To backup an empty(no files) drive through a Client Agent, error occurred and the job failed "AE0300 Failed to find(FILE=,EC=2, The system cannot find the file specified.) *=Drive Letter".
6. Users could not delete drives when BrightStor ARCserve Backup for Windows was installed on NT 4.0 environment. When user selected and then deleted a drive(other than system drive) using Disk Administrator, an error message appeared "Error-The drive cannot be locked for exclusive use. Please check to see if some applications are currently accessing the drive. If so, close them and try again. [OK]".
7. Restore Job would show "complete successfully" although a Restore of Quorum had failed (E3250) on System State.
8. On Restore by Session, when expanding a session tree by clicking on "+", instead of expanded to the next level of the tree it collapsed trees and went up to its parent level.
9. The buffer size value on Configuration, Job Engine tab changed every time a user opened Configuration and click OK button.
10. On Full Backup, BrightStor.log was not fully and successfully backed up. When the data was restored, activity log appeared partially segmented.
11. If iGateway was running, Users were unable to change Volume Format and Drive letters.
12. From "Select what diagnostic information you want to generate", selecting "Get information during the previous" on Activity Log would prevent "BrightStor.log" from being retrieved.
13. Using the Diagnostic Wizard to select Backup/Restore job data on other machine the target machine displayed error message. In addition, time out error occurred if Wizard was running on that machine. "CADiagInfo.exe - Cannot find DLL. Cannot find Dynamic Link Library BRAND.dll in specified path XXXXX".
14. If iGateway was running during a Backup operation, a message appeared and stated that a file remained open. Consequently, restore by Image was not available.
15. When using Command line to restore remote data "By Session", the data would be restored locally.
16. When a folder name contained an Unicode character, it was unable to be selected as an installation destination.
17. If Job Property dialog box was opened during a Job operation, the ARCserve manager window could not be maximized/minimized by clicking Task Bar at the bottom of Windows screen.
18. Launching the Diagnostic Wizard would display messages "Cannot find C:\Program Files\Common Files\CA\BrightStor\Diagnostic\System.Evt" and "Information of this machine is successful", and the information was not collected.
19. BrightStor Manager would unload when the following operation proceeded
    • Display [Restore] screen on Manager.
    • Select Restore [By Tree].
    • Select [SQL Server].
    • Right-click on any Database name to select [SQL Agent Option].
    • Press Enter key immediately after a dialog box appears.

20. Copy did not submit to job queue if the destination was entered manually instead of browsing to the destination machine and selecting it.
21. On restore, when the user typed in an UNC path as the destination, the Restore Manager would GP during job submission.

22. If Microsoft JVM was not installed on Windows Server 2003 or Windows XP, some of the BrightStor ARCserve Backup Manager GUI did not display.
23. The Device Configuration Wizard did not retain the password when the option "Remember the Security Information" selected.
24. Backup Job Submit Summary showed the incorrect local server name if local server was selected for backup.
25. [T1A5123] On ARCserve 9 server which had a SCSI disk array attached as drive E. Used the disk array to do File System backups or disk to disk backup. There were four device groups setup with three of these groups containing 13 media folders for 7-day differential backups with GFS enabled. The fourth group had 5 media folders for a 5-day full backup rotation. A fifth device was an IBM LTO tape drive on a separate SCSI controller. When you started the Tape Engine and it read the contents of each of the File system folders on the CA FSAdapter, one or more of these folders were labeled Unreadable Media. If stopped and restarted the Tape Engine, other folders would show Unreadable Media while the folders with the original Unreadable Media label were correctly read.
26. [T1A5125] On Device Manager when the media was selected under Details - Usage MB Written was displayed as 0.
27. [T2D2162] Directories with Hebrew names were not displayed correctly.
28. [T369045] Merging a tape into a distributed server might have updated the database incorrectly. Symptoms would be an extra session containing no data and/or mislabeled sessions.
29. [T31A104] Certain database operations could interfere with database record insertion (merge). It was possible that the RAIMA VLDB Database could get corrupted. This usually manifested itself in Dr Watson errors when mergecat.exe was running, or in sessions missing detailed information in the database.
30. SRM services failed to start when BAB9 and SRM co-existed on the same system.
31. [T36A019] The Buffer Size dropdown list from Server Admin didn't display data correctly. When the "Configuration" dialog box opened, incorrect values were highlighted.

NOTE: If you are experiencing problems sending SMTP alerts, please review the patch at http://support.ca.com/Download/patches/ilitnt/QO19642.html

4.0 Exchange Agent for Windows

The following section addresses issues related to the Exchange Agent product:

1. When users selected to restore only one Store from a session, which backup had been done by Storage Group Basis, a new folder would be created without the last letter of Temp folder name. i.e.) When Temp folder is in C:\temp, it creates a new folder "C:\tem" and uses this folder as a temp folder for restore operation.
2. [T31A123] Exchange Agent configuration failed when trying to configure the Exchange Agent on a NT/2000 server with the name of server.

5.0 SQL Agent for Windows

The following section addresses issues related to the SQL Agent product:

1. Restore of File or File Groups to an alternate location would fail with error "move failed".
2. Backup would fail if Logon Account to the server was not set. Users would not notice this because the Security options were displayed after submission.
3. [T369062] Some lines were out of order in the SQL Agent debug trace file and log file.
4. [T369059] File/File Group restore failed if the location of the data files were modified. The agent log file showed an error such as "'MOVE' is not a recognized RESTORE option."

5. [T369049] The SQL password was displayed in the debug trace.

6.0 SAP Oracle Agent for Windows

The following section addresses issues related to the SAP Oracle Agent product:

1. [T369051] Restore using backint or brrestore of more than 100 files failed.
2. [T369050] Fixed spelling error "Valume" in BACKINT configuration dialog title.

7.0 Oracle Agent

The following section addresses issues related to the Oracle Agent product:

1. Backup showed "completed successfully", but error message appeared "E8608 Cannot display database" and status showed Backup completed on 0 file(s);
2. [T369053] When performing a backup of Oracle 7, the agent log file contained an Oracle error message "invalid column" for each tablespace it backed up. Although the errors appeared in the log, the backup succeeded.
3. [T369055] Added support for more than 17 Oracle instances.
4. [T369058] RMAN restore operation fails with errors such as_ASFileRestore() failed, ASResult=-1. RMAN backup file \\dbserver\dbaora8@RMAN\DORM722@\0ne7jphe_1_1 cannot be found.".

8.0 Notes Agent for Windows

The following section addresses issues related to the Notes Agent product:

1. On Server Configuration dialog box for Notes Agent installation, valid paths manually entered (not from Browse button) into "Directory of NOTES.INI" field while leaving the cursor in the "Directory of NOTES.INI" field and clicking the Enter button, would revert the process and display "Select the backup agent type". This problem occurred on BAOF Version and Notes Agent Version.
2. When BAOF version of Notes Agent was installed, OFANT.sys would cause a blue screen on Windows Server 2003.

9.0 Backup Agent for Open Files for Windows

The following section addresses issues related to the Open Files Agent product:

1. BAOF uninstallation did not delete "ofawin.GID"(hidden attribute) from "C:\program files\CA\BrightStor Backup Agent for Open Files".
The installation of OFA was not successful. While trying to install the Open File Agent, OFANT.SYS caused a blue screen on Windows Server 2003.

10.0 Client Agent for Windows 9x/ME

The following section addresses issues related to the Client Agent for Windows 9x/ME product:

1. Although an old Agent was uninstalled prior to an install, Install Product selection screen displayed message "Setup detected previous version of ARCserve/ARCserveIT Client Agent for Windows v7.0 on your system. You need to uninstall existing product before upgrade the product to BrightStor ARCserve Backup Client Agent for Windows" in Detail field. This caused the installation to fail.
2. When performing an upgrade installation from version 6.61, the install prompted for inserting version 6.61 CD. System would freeze when Cancel was pressed.

11.0 Tape Library Option for Windows

The following section addresses issues related to the Tape Library Option product:

1. During installation, after entering caroot password and then unchecking "save this information" checkbox to start installation, the Device Configuration "Tape/Optical Library" became unavailable while Tape Engine was running.

12.0 Disaster Recovery Option for Windows

The following section addresses issues related to the Disaster Recovery Option product:

1. Support for English Advanced Server SP3 and Server SP3 integrated OEM CD as well as Windows Server 2003.
2. Remote DR did not delete "DRBOOT.TMP" on NT 4.0.
3. For Recovery (Local/Remote) of a machine with MO drive, Disaster Recovery Wizard displayed File System as RAW and was unable to recover the drive on Windows 2000.
4. On Disaster Recovery Wizard, tape name display area was too narrow. A tape name with maximum text length (23 characters) appeared truncated.
5. Disaster Recovery did not recover "All Users\DRBOOT.TMP" and "Default User\DRBOOT.TMP" folders under "C:\Documment and Settings".
6. [T36A020] Disaster Recovery crashed during Restore operation when file or directory name contained "%s" string. For example: abc%sdef
7. Disaster Recovery was not able to recover Windows Server 2003 with Active Directory Service enabled.
8. During remote Windows 2003 CD Disaster Recovery, after the DR Wizard copied the machine specific disk and rebooted, the DR Wizard was not able to connect to the Backup Server (Windows 2003). It failed with error "Error in connecting to the remote server 1312".
9. Disaster Recovery failed to restore the distributed server in a SAN environment.

Note: In the unlikely event that a floppy based DR for a Windows 2000 server is attempted, versus the more efficient CD recovery, after applying BAB9.01 Update please download this BAB901WDR.exe file and this DR901upd.bat file, and follow the steps below:

For Windows 2000 (local and remote floppy method)

• Copy BAB901WDR.exe, DR901upd.bat to a blank floppy and preserve the floppy along with the Boot diskettes
• During the DR recovery process after the First Reboot (when First time DR wizard screen appears), go to command prompt by holding down "Ctrl" + "Shift" and double click in the graphic on the left hand side(The double click produces a drop down menu)
• Choose Command Line.
• Change the directory to dr by typing cd DR. So the directory is c:\drboot.tmp\system32\dr. (Where c:\ is your system partition drive.)
• Copy the executable and batch file from the floppy to DR folder.
• Run the DR901upd.bat from the DR folder c:\drboot.tmp\system32\dr\DR901upd.bat
• In the pop up window use the default location c:\drboot.tmp\system32\dr\ (Change the drive letter if your system partition is not on c:\), and then click the Unzip Button to extract.
• Close the Window once the extraction is completed.
• Minimize the Command Window.
• Continue the DR process by Clicking Next in the DR Wizard Screen.

Trouble Shooting: When performing a remote Windows NT 4 Disaster Recovery, it fails to connect to my backup server, which is a Windows 2003 Active Directory Server. Why?

When installing the Active Directory server on a Windows 2003 server, the promoting process tightens the local security policy for the new domain controller. Because of that, Windows NT 4 remote Disaster Recovery may fail to connect to the server. Follow the steps listed below to enable Windows NT 4 compatibility on this type of system.

• Go to Domain Controller Security Policy from Administrative Tools.
• Go to Local Policies.
• Go to Security Options.
• Disable "Microsoft network server : Digitally sign communications (always)"
• Disable "Domain member : Digitally encrypt or sign secure channel data (always)"

13.0 Image Option for Windows

The following section addresses issues related to the Image Option product:

1. Image Backup Option is now supported on Windows Server 2003.

14.0 Serverless Backup Option for Windows

The following section addresses issues related to the Serverless Backup Option product:

1. Serverless Backup Option is now supported on Windows Server 2003.

15.0 Storage Area Network (SAN) Option for Windows

The following section addresses issues related to the SAN Option product:

1. In a SAN environment, if the Windows OS password changed before trying to configure the SAN server (remove previously configured server), entering the new credentials in the popup dialog box, would cause the SAN configuration to hang.
2. On Windows Server 2003, in a SAN environment using ADIC Scalar 1000 with IBM LTO drives in a RAID 1 configuration, the Restore and Merge operations would fail with a return error E3801 "invalid session header signature. (SIG=00000000)".

16.0 Device Support

This patch includes updated device support. Please refer to the Certified Device List posted on the following Web site for a complete list of supported devices:

http://support.ca.com/techbases/basb9/basb9_cdl.html