Инструкции к Симантек Бэкап

автор rls Ср 12 Июн - 18:13

Symantec Backup Exec System Recovery 2010 Readme

[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8721447]About this readme[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8721450]Getting help while using Backup Exec System Recovery 2010[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v27543029]What is new in Backup Exec System Recovery 2010[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v27543065]System requirements[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v15967938]Install[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v15967986]Uninstall[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v15968040]Backup destinations and Offsite Copy[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v15968053]Symantec Recovery Disk[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8926036]LightsOut Restore[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8723813]Active Directory support[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8723823]Remote management[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v15968067]General issues[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8721579]Backup Exec System Recovery Granular Restore Option[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v25634509]Third-party code[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v9079252]About Windows Vista manifests[/url]
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#v8721595]Copyright notice[/url]

About this readme
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
Carefully read the issues in this section before installing and using Symantec Backup Exec™ System Recovery 2010. This document contains important information that was discovered after the product was released to manufacturing.
Getting help while using Backup Exec System Recovery 2010
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
To learn more about Backup Exec System Recovery 2010, visit the Help and Support page. Depending on which version and language of the product you have installed, the Help and Support page includes one-click access to more information, including the product help system, the product User's Guide, and access to the Symantec Knowledge Base where you can find troubleshooting information.
To access Help and Support

Start Backup Exec System Recovery 2010.
On the Home page, click Help > Help and Support.

What is new in Backup Exec System Recovery 2010
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
Backup Exec System Recovery includes many enhancements and new features. Refer to the following table for information about the latest features and enhancements:

Note:

Not all listed features are available in all versions of this product.

Table: What is new Backup Exec System Recovery 2010
[th]Feature[/th][th]Description[/th]

Improved support for virtual formats	Backup Exec System Recovery now includes support for the following virtual platforms: VMware ESX 3.5 and 4.0 VMware ESXi 3.5 and 4.0
Improved platform support	Backup Exec System Recovery now includes support for the following platforms: Windows 7 (includes Starter, Home Basic, Home Premium, Professional, Enterprise, and Ultimate) Windows Server 2008 R2 Exchange Server 2010
The Granular Restore Option is now included with Backup Exec System Recovery 2010.	In previous versions of Backup Exec System Recovery, you were required to purchase the Granular Restore Option as a separate product. Backup Exec System Recovery now includes the Granular Restore Option. No additional purchase is necessary.

System requirements
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
The following table lists the system requirements for Backup Exec System Recovery to function properly.
Table: Minimum system requirements
[th]Component[/th][th]Minimum requirements[/th]

Operating system	The following Windows 32- or 64-bit operating systems are supported: Windows 7 (all editions) Windows Vista Ultimate Windows Vista Business Windows Vista Enterprise Windows XP Professional/Home (SP2 or later) Windows XP Media Center (SP2 or later) Windows Server 2003 Windows Small Business Server 2003 Windows Server 2008, including SP1 Windows Server 2008 R2 Windows Essential Business Server 2008 Windows Small Business Server 2008
RAM	The following are the memory requirements for each component of Backup Exec System Recovery: Backup Exec System Recovery Agent: 512 MB Backup Exec System Recovery user interface and Recovery Point Browser: 512 MB Symantec Recovery Disk: 1 GB minimum (dedicated) LightsOut Restore: 1 GB
Available hard disk space	The following are hard disk space requirements for Backup Exec System Recovery and other areas: When you install the entire product: Up to 430 MB is required for a full install, depending on the language of the product you select. Microsoft .NET Framework 2.0: 280 MB of hard disk space is required for 32-bit computers, and 610 MB is required for 64-bit computers. Recovery points: Sufficient hard disk space on a local hard disk or network server for storing recovery points. The size of recovery points depends on the amount of data you have backed up and the type of recovery point that is stored. LightsOut Restore: 2 GB
CD-ROM or DVD-ROM drive	The drive can be any speed, but it must be capable of being used as the startup drive from the BIOS. Backup Exec System Recovery uses Gear Software technology. To verify that your CD writer or DVD writer is compatible, visit the Gear Software Web site. http://www.gearsoftware.com/support/recorders/index.cfm You can look up information about your writer if you know the name of the manufacturer and model number of your writer.
Software	The Microsoft .NET Framework 2.0 or later is required to run Backup Exec System Recovery. If .NET Framework is not already installed, you are prompted to install it after Backup Exec System Recovery is installed and your computer is restarted.
Virtual platforms (for converted recovery points)	The following virtual platforms are supported: VMware Workstation 4, 5, and 6 VMware ESX 3.0, 3.5, and 4.0 VMware ESXi 3.5 and 4.0 VMware Server 1 and 2 Microsoft Virtual Server 2005 R2 and later Microsoft Hyper-V 1.0 and 2.0

Note:

Windows 2000 Server, Windows 2000 Advanced Server, and Windows Small Business Server 2000 are not supported in Backup Exec System Recovery 2010. You can still use Backup Exec System Recovery 8.5 on these versions of Windows 2000. You can also perform backup and restore functions remotely on Windows 2000 computers using Backup Exec System Recovery 2010 or Backup Exec System Recovery 2010 Management Solution.

Install
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

If your computer shares RAM with another device, such as your graphics card, then your computer might not meet the minimum RAM requirements for using one or more features of Backup Exec System Recovery 2010. You should avoid sharing RAM if your computer only meets the minimum amount of RAM required by Backup Exec System Recovery 2010.
For example, the minimum RAM requirement for Symantec Recovery Disk is 512 MB. The entire RAM amount must be unshared and dedicated exclusively to Symantec Recovery Disk. If it is not dedicated and unshared, you may run out of memory when you restore recovery points or perform other tasks using Symantec Recovery Disk.
Refer to the Backup Exec System Recovery 2010 User's Guide for minimum system requirements.
RAM requirements for using the Symantec Recovery Disk are 512 MB. However, if you use the multilingual version of Backup Exec System Recovery 2010, the requirement is 1 GB.
Under Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, if you use Microsoft BitLocker to secure the data on a drive, consider the following key points:
- LightsOut Restore does not work on Windows Vista BitLocked drives. Therefore, if you BitLock your system drive, you cannot recover the drive using LightsOut Restore.
- You can back up a BitLocked drive and then restore it using the Symantec Recovery Disk CD (or a customized version of Symantec Recovery Disk).
- After restoring a BitLocked drive, you must set up BitLocking again because the drive is no longer BitLocked after it is recovered.
- If you are concerned about securing the data on a drive (which is a common reason for using BitLocker), you can encrypt your recovery points as a way of securing the data contained in them.
- If you are restoring a recovery point of a Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 computer that contains data from a previously BitLocked drive to a new drive, you must have a recovery point of both the boot partition and the system partition.
  You must restore the boot partition first, and then restore the system partition second. The boot configuration data (BCD, a new data store introduced with Windows Vista) is updated so that your computer starts correctly.
Backup Exec System Recovery 2010 does not support computers that use the GRUB Boot Loader.
Backup Exec System Recovery 2010 does not support computers that use Fedora Core3 Ext2/Ext3 or Grub 2 boot managers.
Up to 430 MB is required for a full install of Backup Exec System Recovery 2010, depending on the language of the product you select. If your system drive (typically, C) is low on disk space and you select an alternate drive to install Backup Exec System Recovery 2010 to, approximately 30 MB of disk space is still required on your system drive. If your system drive is dangerously low on disk space (less than 100 MB), you should first free up more space before installing Backup Exec System Recovery 2010.
If you are upgrading to a support pack release using a CD you created from an .iso file, you might receive a message to "insert disk 1". If you receive this message, copy the contents of the CD to a location on your hard drive and run the installation from there.
After installing Backup Exec System Recovery 2010, you are prompted to reboot your computer. Rebooting your computer is necessary to install and activate the system drivers, symsnap.sys and v2imount.sys.
If you are going to install Backup Exec System Recovery 2010 using a silent install, you must install Microsoft Installer 3.x and dotnetfx.exe (in that order) before running the silent install. If you attempt to run a silent install without installing Microsoft Installer 3.x and dotnetfx.exe first, you might encounter errors.
The Backup Exec System Recovery 2010 install disables the Windows Last Access Time setting. This setting is used to record the date and time when files are accessed. However, this setting significantly slows down backup jobs that have search engine support enabled.
Note: On Windows Vista, this setting is already disabled by default.
If you depend on Last Access Time and can accept its effect on the speed of backup jobs that have search engine support enabled, you can use the following set of parameters at installation time to ensure that Last Access Time is left enabled. You must run this command from within the \Install folder on the product CD.
The easiest way to run the install with these parameter settings is from the Windows Run command:

To leave Last Access Time enabled

On the Windows taskbar, click Start > Run, and then type the following command:
setup.exe /s /v"/qn DMFILEACCESS=1"
Click OK.

Uninstall
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

When you uninstall Backup Exec System Recovery 2010, LiveUpdate remains installed on your computer. If you want to uninstall LiveUpdate, refer to your operating system's documentation for information about how to remove applications.
If you uninstall Backup Exec System Recovery 2010, the capicom.dll file might still appear in the system directory. This is a shared .dll file that is used to perform LiveUpdate for all Symantec products. If you have multiple Symantec products on your computer, or if it is unclear whether the file is needed, you can leave it there. Or if you are certain that the file is not longer needed, you can delete it.
If you uninstall any earlier version of this product, you might encounter a problem with the virtual volume driver. Uninstall and reinstall Backup Exec System Recovery 2010. If this does not correct the issue, you may need to call Symantec Technical Support for assistance in correcting the product's registry entries.
The following folder contains files that remain on a computer following an uninstall of the software. If you want, you can manually delete the files inside the specified folder; however, it is not necessary to remove them.
You can manually remove the following folder when you uninstall Backup Exec System Recovery 2010:
- system_drive_letter:\Documents and Settings\Administrator\Application Data\IsolatedStorage.
  The IsolatedStorage folder contains folders and several .xml and .dat files. These files are used by the Microsoft .NET Framework application to store window sizes, locations, and so forth.
  Warning: You should determine whether other applications are using the IsolatedStorage folder before removing it.
GEARAspi.dll is installed outside the default folder location where the software is installed. This file is removed during an uninstall of the software from the following locations:
- Windows XP
  <system_drive_letter>:\WINDOWS\system32

Backup destinations and Offsite Copy
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

If you use an Iomega REV drive to back up your system, you must download the correct REV driver from the Iomega Web site if you want to write to the drives. The REV driver that shipped on the REV drive CD is not compatible with Backup Exec System Recovery 2010. The driver to download is rev_system_software-w32-x86-30345 (or the most recent version).
If you are using a network location as your backup destination, make sure that you have provided a valid network user name and password. Backup Exec System Recovery 2010 frequently accesses the backup destination to verify that you have valid recovery points. If your network account is in a domain, common security procedures lock your account after a certain number of failed logon attempts. If your logon credentials are invalid, you could be locked out of your network account after multiple, failed attempts by Backup Exec System Recovery 2010 to access the backup destination.
Backup Exec System Recovery 2010 does not support writing to a shared CD drive on another computer.
Sometimes Windows incorrectly reports insufficient hard disk space when saving a recovery point to a Linux Samba share. To solve this issue, verify that Windows identifies the correct amount of space.

Symantec Recovery Disk
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

You cannot create a customized Symantec Recovery Disk CD if you deselected the CD/DVD option during a custom installation of Backup Exec System Recovery 2010. If you chose not to install the CD/DVD option, you must run the install again and add the option back in before you can successfully create a customized Symantec Recovery Disk CD.
When creating a customized Symantec Recovery Disk CD, you might receive the following error:
file:\\windows\system32\winload.exe status: 0xc0000001 The selected entry could not be loaded because the application is missing or corrupted.
This error is known to occur if your operating system resides on a drive that is formatted to FAT32.
To resolve this issue, reset %TEMP% to point to a secondary drive that is formatted to NTFS and that has enough disk space to host temporary program files included in the SRD .iso file (approximately 400 to 600 MB, depending on the language being used). Then re-create a custom Symantec Recovery Disk.
If you want to use a dynamic disk as your backup destination, you should run Symantec Recovery Disk to see if the dynamic disk is accessible. You must have access to the recovery points stored in your backup destination in order to recover your computer. If you cannot access the dynamic disk from Symantec Recovery Disk, you can create a customized Symantec Recovery Disk CD.
See "Creating a customized Symantec Recovery Disk CD" in the User's Guide or online Help system.
When you create the custom CD, you can add the necessary storage drivers that let you access the dynamic disk from Symantec Recovery Disk.

LightsOut Restore
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

When LightsOut Restore is set up, it installs the Symantec recovery environment directly to the file system on the system partition (you cannot change this location), and places a Symantec recovery environment boot option within the Windows boot menu.
LightsOut Restore does not work on BitLocked drives. Therefore, if you BitLock your system drive, you cannot recover the drive using LightsOut Restore.
If you cannot boot your computer using LightsOut Restore, it could be because your operating system resides on a drive formatted to FAT32.
To resolve this issue, reset %TEMP% to point to a secondary drive that is formatted to NTFS. Then re-create a custom Symantec Recovery Disk CD.

Active Directory support
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

The software adds 46 bytes of data as a Service Principal Name to the Computer Object of the base schema. This attribute is added for every computer in the domain on which the agent is installed.
The application does not have any special requirements for the network traffic to replicate the updates to full or partial replicas.
The software uses the Computer Object from the base schema and adds the Service Principal Name as an attribute to the object. This is the attribute that the software reads from the directory.

Remote management
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

You cannot deploy the Backup Exec System Recovery 2010 Agent to Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. Instead, you must manually install the agent to computers that run Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2.
After you have manually installed the agent, you can then use Backup Exec System Recovery 2010 to remotely manage the Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 computer.
If you deploy the Backup Exec System Recovery 2010 Agent to a computer that is already running LiveState Recovery 6.0 or Norton Ghost 10, the older product is automatically uninstalled without warning. Backup jobs and histories are also automatically deleted.
You might receive a reconnect error when trying to manage a second computer.
To resolve this issue, use Windows Firewall to open TCP port 135 on both the source and target computers, and then try the connection again.
You might receive a reconnect error when trying to manage a second computer. This error message appears in the status bar of the product user interface:
Connecting to agent on <remote computer name/IP address>. You do not have sufficient privileges to perform this operation.
This error might occur because Distributed COM (DCOM) is disabled on the computer.

To enable DCOM:

From the Windows Start menu, click Run.
For Windows Vista, if the Run option is not visible, do the following:
- Right-click the Start icon, and click Properties.
- On the Start Menu tab, click Customize.
- Scroll down and check Run command.
- Click OK.

Enter dcomcnfg.exe, and then press Enter.

In the tree on the left, double-click Component Services, and then double-click Computers.

Right-click My Computer, and then select Properties.

Click the Default Properties tab, and then select the Enable Distributed COM on this Computer check box.

Click OK to save the settings.

General issues
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

Backup Exec System Recovery 2010 now supports both backing up and restoring systems that boot into Windows from SAN-attached volumes.
Backup Exec System Recovery 2010 Support for Windows 2000
Backup Exec System Recovery 2010 is not supported under Windows 2000. To run Backup Exec System Recovery under Windows 2000, you must install and use Backup Exec System Recovery 8.5.
Managing Newer Versions of Backup Exec System Recovery
You cannot use previous versions of Backup Exec System Recovery to manage newer versions. For example, you cannot manage Backup Exec System Recovery 2010 using Backup Exec System Recovery 8.5.
Backup Exec System Recovery 2010 Backup Performance
Backup Exec System Recovery 2010 is configured to provide optimal performance for most users. The default performance settings are recommended except in certain situations that require the backup window to be highly optimized. To facilitate performance tuning in these limited situations, go to the Symantec Knowledge Base.
In some cases the alternate settings may improve performance. Alternate performance settings generally have the most impact when the recovery point (V2i file) is saved to a network share. When the recovery point is saved to a second internal hard drive or to an external USB or FireWire hard drive, the default settings generally provide the best results.

If you cannot run Backup Exec System Recovery 2010 on a server that you have "hardened" using Microsoft's guidelines, do the following:
- If the Backup Exec System Recovery 2010 service is running, stop it by using either the Services Control Panel or by using a command prompt and typing the following command:
  ' net stop "Backup Exec System Recovery"
- Open a command prompt, and change to the root of your Backup Exec System Recovery 2010 install (the default is C:\Program Files\Symantec\Backup Exec System Recovery).
- Run the batch file, fixinstall.bat by typing the name of the batch file from the command prompt in the installation folder.
- Start the Backup Exec System Recovery 2010 service from the Services Control Panel or by using a command prompt and typing the following command:
  ' net start "Backup Exec System Recovery"
If the drive letter of the CD-ROM drive has changed since you installed the software, you will get an error message (the MSI file cannot be found) when you run the "Repair" or "Modify" installation option from the product CD. This error typically occurs if you are adding or removing external devices to a desktop PC or internal devices to a laptop.
To avoid this issue, you must ensure that Windows "sees" the CD-ROM drive as the same drive letter as when Backup Exec System Recovery 2010 was first installed. Therefore, you should assign the drive a drive letter that is toward the end of the alphabet and is not likely to be used.
If you are running Japanese and English computers on the same network, Japanese computer names may appear garbled in the console.
When configuring a backup job to start a new recovery point set, be sure that you do not schedule the new set to start when the backup job is scheduled to create an incremental recovery point. If you do, the backup job scheduled to create the new recovery point set might not run as expected.
Backup Exec System Recovery 2010 uses the Microsoft DISKPART utility to create and delete dynamic volumes. If you have a dynamic volume you want to delete, you must use this utility, which shipped in base versions of Windows XP/2003.
If you are running Windows Vista and Windows Server 2008 and attempt to restore your system drive using recovery points that span multiple CDs or DVDs, you might encounter a known error. It appears that a conflict exists between Windows Vista or Windows Server 2008 and Gear CD/DVD drivers. To work around this issue, you should copy the required recovery points from CD or DVD to a second internal or external hard drive, and then restore your computer from the second drive.
The following files are temporary shortcuts and icons created by MSI:
(Windows XP) <system_drive_letter>:\WINDOWS\Installer\{guid_number}\
- _F2526B23_3845_44C8_A4C5_5D43FF9A707F
  Код:
  1033.MST
  
  Код:
  ARPPRODUCTICON.exe
  
  Код:
  ConsoleDesktop_32_digit_number.exe
  
  Код:
  GranularRestoreOpt_32_digit_number.exe
  
  Код:
  ImageBrowser_32_digit_number.exe
  
  Код:
  SecurityV2i_32_digit_number.EXE

Backup Exec System Recovery Granular Restore Option
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
Granular Restore Option is now included with Backup Exec System Recovery 2010.
Compatibility
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
The following are compatibility issues you may encounter:

Granular Restore Option is compatible with Backup Exec System Recovery version 7.0 and later.
Granular Restore Option is not compatible with Microsoft Outlook 2000.

General issues
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]

For Granular Restore Option to have full functionality, you must install Microsoft Outlook 2003, 2007, or 2010 on the server that is running the Granular Restore Option console.
Opening a recovery point set (.sv2i) that is stored on the network may not display all email messages if a network outage occurs while loading the file. A workaround for this issue is to reload the file.
When you back up your Microsoft Exchange server, make sure that you include all of the volumes that Exchange uses in the backup job. These include the drive that contains the installation of Exchange and the drive or drives that contain the Exchange data.
When you try to forward a recovered message when Outlook is not running, if you close the message, you are prompted to save it. If you choose to save the message, it is saved to your Inbox rather than the Drafts folder.

Third-party code
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
Portions of this product include third-party licensed code as provided below.
Copyright © 2003, Dr. Brian Gladman (brg@gladman.me.uk), Worcester, UK. All rights reserved.
License terms
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that:

Distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer;
Distributions in binary form include the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other associated materials;
The copyright holder's name is not used to endorse products built using this software without specific written permission.

ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given above.
DISCLAIMER - This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and/or fitness for purpose.
About Windows Vista manifests
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
The following table lists applications that have been tested on Windows Vista by Symantec but are provided by third-party software vendors and do not include embedded Windows Vista manifests:

bootsect.exe
dotnetfx.exe
IDriver.exe
IDriver2.exe
IDriverT.exe
gearinstall.exe
geardrvsetup.exe
IDriver.NonElevated.exe
ARPPRODUCTICON.exe
ImageBrowser1_32_alpha-numeric_characters.exe
NewShortcut12_32_alpha-numeric_characters.exe
SecurityV2i1_32_alpha-numeric_characters.exe

Copyright notice
[url=file:///C:/Program Files (x86)/Symantec/Backup Exec System Recovery/Shared/Readme.htm#pagetop]^Back to top[/url]
Copyright © 2010, Symantec Corporation.
All rights reserved.
Version: 9.0.2