Arcserve® Backup for Windows r Readme – Download ca arcserve backup r16 client agent for windows free

 

Download ca arcserve backup r16 client agent for windows free –

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Download ca arcserve backup r16 client agent for windows free

 
 

 
 
You can download CA Arcserve R 30day free trial from below link. an ARCserve Stand-alone Server, the Client Agent for Windows and. Arcserve Backup Client Agent for Windows, r 25 MB free disk space Note: To obtain the latest patches and downloads for the Arcserve Backup Agent. r SP1. Arcserve® Backup for Arcserve® Unified Data Protection Agent for Windows How Arcserve Backup Engines Work > CA Antivirus Maintenance.

 
 
 
 

Download ca arcserve backup r16 client agent for windows free.Pricing & Licensing Overview. CA ARCserve r PDF Free Download

 

A problem with the Emulex driver released with Windows SP1 prevents Arcserve Backup from initializing correctly unless you update the Emulex driver. If you use the Master Setup to install Arcserve Backup remotely to a system in another Windows domain, you may receive a message indicating that the installation failed when it is successful.

This behavior occurs because the Master Setup cannot accurately detect the activity on the remote machine in the other domain because of a firewall or due to a lost network connection.

Check the installation status on the remote machine to verify that the installation succeeded. You must perform a full inventory of tapes to enable this option because this capability can be recognized only by reading the media. Installing bit components on a bit machine generates two copies of the file PortsConfig. The PortsConfig. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.

If you install agents on cluster nodes, do not back up the physical nodes the private drives C: and D: or non-shared disks through preferred share using the virtual server IP address, because virtual servers can be moved from one node to another.

For example, if virtual server 1 resides on physical node 1 and you backed up virtual server 1 through preferred share, the non-shared drives on physical node 1 are also backed up. If you move virtual server 1 to physical node 2, and perform a Restore to Original Location, the non-shared drives from physical node 1 are restored to physical node 2.

Special characters in media files will interfere with RMAN jobs. Job redirection is no longer supported. As an alternative, you can use the makeup job feature.

Refer to the Administration Guide for more information regarding makeup jobs. When the Windows security policy is enabled on the machine where Arcserve Backup is installed, an audit log is recorded in the event log at the time of a system application startup, such as Task Manager. If you apply the license keys for two or more different Arcserve Backup suites on a single Arcserve server, the license count on the Arcserve server may not be correct.

The Tape Compare utility does not support comparing tapes that were created using multiplexing or encryption. Broadcast Alerts do not function on systems running Microsoft Windows Server This behavior is observed because Microsoft Windows Server does not support messaging service.

After you restore the Arcserve bit ASDB, you must perform at least one full backup of the Arcserve Backup database before you perform an incremental or a differential backup. This task helps ensure that Arcserve Backup database backup sessions contain the most current data. This task helps ensure that Arcserve Backup database backup sessions are current.

A NetBIOS name resolving problem between local and remote machines may prevent you from obtaining information from the Diagnostic Wizard. To avoid communication problems, verify that the remote system is on the network and that the machine name is correctly mapped to the IP address. To do so, perform the following steps: Confirm that the remote machine is reachable across the network and that the IP Address matches the remote machine name.

If the system cannot be pinged at all, check the network connections and ensure the system is operational. If the name does not match the IP address, continue. Examine the command output for mistakes in your configurations.

If mistakes exist, the network cannot communicate properly. Open Network Connections. Click the Support tab. Click Details. Examine the output and verify the remote machine IP address matches its machine name for all types of the machine name specified. If the machine name does not match the IP address, or if no such items exist in the table, proceed to Step 4. Optional If you find a mismatch in the mapping between a System Name and IP Address, run the following command to purge the Server Name and IP address mapping on both the local and remote machines.

Otherwise, skip to Step 5. Run nbtstat -c again. The table should now be empty, or contain only a few new items with lives of about seconds. The tables should show identical information: the name of the remote system as “Registered” for the IP Address. After you restore the Arcserve Backup database, use the Merge utility to merge the Arcserve Backup database backup sessions.

Close and then reopen the Restore Manager window to refresh the information that displays in the Restore by Tree source directory tree. These objects are displayed with excluded text which will not be backed up when the makeup job is submitted. When you log off an interactive Windows session while a message such as tape mount is still displayed, some temporary files will remain in the Arcserve Backup Temp folder.

Backup jobs performed with Windows , and Windows systems may include the following files that Microsoft recommends not be backed up, even if they are specified in the FilesNotToBackup registry key: index. Arcserve Backup operations executed on the same tapekey after tapecopy has been executed could affect either the source or the destination tape. Job failure may also occur if a session is added to either the source or destination tape after Tapecopy because Arcserve Backup may not be able to restore that added session.

This is because a tape is identified by three items: the tape name, the random ID, and the sequence number. The combination of these three tape identifiers is called the tapeKey. If you do not want the destination tape to be the exact same as the source tape, you can include the —idr switch with the tapecopy command so that Arcserve Backup automatically assigns a different random ID to the destination tape and ensures that the destination tape is not exactly the same as the source tape.

If you do not include -idr switch with the tapecopy command, you could then use the destination tape at a later time to perform a disaster recovery operation because the destination tape will be exactly the same as the source tape. This release of Arcserve Backup automatically creates a new media pool with the same name given to media in an r12 or prior environment and inventoried in the current environment.

During recovery, the Arcserve Backup database is offline. So any client programs trying to access the database during this period will be denied. This message does not prevent recovery from completing successfully. Security validation is performed only on Windows or XP systems. In Citrix 4. When run with Microsoft Office , Arcserve Backup Job Status Manager can experience excessive “handle leaks”, too many open register keys that are no longer in use.

Install the latest Microsoft Office service pack to avoid this problem. When the Catalog database folder is changed to a long path name greater than characters and backed up, the catalog files may not be kept in the catalog database and an E error is recorded in the Activity Log.

If Password Security is enabled and any database, application, or messaging Agent is installed on the same machine as the Client Agent, whole node backup is not supported.

System Security is the default setting. You must not enable Password Security in the Agent Configuration on any machine running a database, application, or messaging Agent before submitting the job. However: when you perform a remote backup of an entire drive on which Single Instance Storage was activated as the backup source, the job fails and AW is recorded.

This is because Arcserve Backup is attempting to back up files that should have been excluded. Restoring the entire session to its original location also restored files that should have been excluded. When you restore SIS links using the global option “log all activity” set to on, the Job Log shows only the links have been restored, not the data files. The Remote Restore Job Log shows the files as restored. For jobs shown in the Activity Log, the Media Compression Ratio and the Media Remaining Capacity display as 0 because these parameters are not supported by the device.

Arcserve Backup does not support Windows passwords that are 24 characters and longer. When you add a Windows agent machine to Arcserve Backup, you are prompted for a hostname and password. Even though Windows supports a long password here, Arcserve Backup does not and login will fail. Arcserve Backup does not support restoring a Job Queue session to its original location using normal data recovery processes.

Although Arcserve Backup does not use the service setting, the installer changes it. This service should not have been changed to start up automatically. To eliminate Warning 3, perform the following steps:.

Set Arcserve Backup services to depend on SQL Server service to start up by using the Microsoft sc utility see Using Utility steps a through c, below or by manually setting the registry keys see Manually editing the registry, below. Using the utility:. Edit the registry manually :. Reboot the computer. The errors should not reappear. This service is disabled on Windows Server systems by default.

This problem is limited to machines that are members of a workgroup; if the machine is a member of domain, log in proceeds. To avoid the problem, use regedit to set the ForceGuest registry value to 0. When you install this release of Arcserve Backup on the cluster node of a Windows Server cluster or a Windows Server cluster, the Arcserve Backup Database is listed in the cluster virtual name on the Backup Manager.

When Japanese collation is selected, operations are Kana-sensitive, Width-sensitive and Case-sensitive.

For the Look in Directory field on the Restore by Query screen, and the Volume field on the Search dialog, you may specify only uppercase drive letters. Security information for the Agent for Microsoft SQL is not automatically loaded after upgrading from earlier Arcserve Backup versions to this release. You must retype password to continue. Arcserve Backup does not support integration with the Microsoft Management Console.

If the Arcserve Backup database is configured to use SQL Server, the Database Protection Job may not be able to successfully back up the Arcserve Backup database in a clustered environment when failover happens from one node to another node. If such a situation occurs, run the Database Protection Job again manually to verify the Arcserve Backup database is being successfully backed up. This approach is not recommended because the default locations for user data and system data for example, the Documents and Settings folder are different than that of previous Windows operating systems.

As a best practice, you should back up the folders that are referenced by the symbolic link, rather than the link itself. You may experience slow performance when you browse Windows Server x64 systems from the Windows Systems object in the Backup Manager directory tree. Arcserve Backup demonstrates this behavior due to various environmental conditions that can cause VSS writers to enumerate the VSS metadata. However, without the VSS metadata, you can browse only the disks for the specified computer.

When restoring Hyper-V virtual machines to an alternate location, Arcserve Backup may not be able to power on the target if the friendly name of the network switch is not the same as that of the original backup. To remedy this problem, verify that the friendly name of the network switch of the destination is the same as the source location before you submit the restore. An alternate solution is to edit VM settings after restore is complete and change the network switch name to one available on the destination server.

Export options override the Eject Media options but because this device does not support exporting, the device is not ejected upon job completion. When saving a Data Mover backup job script from the Backup Manager console, the Data Mover’s source, destination, and global options checks are not executed.

Therefore, the GUI will not show any messages to warn the user or block the user from submitting the job and removing the unsupported options. If you reload the saved job script from the Job Status Manager, the job will fail. Select one of the following options as a workaround:. If you select the Save or Save As menu to save the job script, you can reload the job and modify this job in the Job Status Manager, and then re-submit the job.

All checks will then be executed. If you select the Save or Save As menu to save the job script, you can click the Open menu from the Backup Manager console to open the job script and then click the Submit button to submit the job. Arcserve Backup supports only one writer e. If you include other types of source disks to this one backup job, the job will fail.

In the case of Classic View, you can change it by selecting Agent Modification from the Context menu. When adding a cloud connection from the Device Manager and you enter the domain password and proxy credentials, the system caches the credentials. If you add another connection and specify incorrect domain password and proxy credentials or leave it blank, the system picks up the cached credentials and successfully adds the cloud connection.

As a workaround, you can delete the cookies from the computer you are working from or reboot. This will cancel out the cached credentials.

After migration job completes for a disk staging job, the restore by session method searches for the specific file in two sessions staging session and migration session , while the restore by query method searches the file in only one session staging session or migration session, not both.

Note : Creating a vault after migration completes specifies the requested file in only one session staging session or migration session, not both which places only one tape into the vault. This is a Windows restriction stating that if you use an existing user name to create a connection to a shared resource, then any other user name will fail to create the connection to the same resource.

When you submit a staging job with FSD as the staging location and Cloud Device as its destination, the migration job does not resume after an unplanned cluster failover occurs as the tape engine needs time to initialize the cloud device. As a workaround, Arcserve Backup creates a makeup job for the failed migration job to continue the migration process. For the reason that Windows cannot access binary files after a failover on a cluster environment due to the back-end process of a failed caauthd.

To recover data from backup sessions that were migrated to Eucalyptus Cloud devices using a prerelease version of Arcserve Backup r16, add the following property to the CCIConfig initialization file.

File location:. Note: Set the value of the UseOldDecode property to 0 to use the new devices. The default value of UseOldDecode is 0. Backward Compatibility is not supported for proxy servers and agents running on virtual machines with different versions of Arcserve Backup. Arcserve Backup does not support backing up and performing disaster recovery operations of the System States on computers where the sector size is defined as 4KB.

To browse and back up drives that are protected by BitLocker Drive Encryption, log in to the operating system to unlock the volume before you submit the backup job. With BitLocker Drive Encryption, the Backup Manager cannot display the individual directories and files contained in the drive, which prevents you from submitting backups.

This behavior also applies to the process of restoring data to BitLocker protected drives: Log in to the operating system to unlock the volume before you submit the restore job. This behavior occurs because Arcserve Backup calculates the logical sizes rather than the physical sizes of the files from the Job Monitor.

You can find the accurate data at the end of the job in the activity log. To correct this behavior, install Windows Server hotfix With the hotfix applied to the server, you can set the state to online and Hyper-V VSS Writer backup jobs will complete successfully. Scan backup media contents and compare backup media contents to disk are not supported for Raw backups.

After restoring NTFS Deduplication optimized sessions, the quantity of bytes restored to the disk are not the actual size of the file that were restored. This behavior occurs when the data for the user files are spread across multiple NTFS Deduplication metadata files. For more information, see Article on the Microsoft website.

To correct this behavior, uninstall the Management Tools feature for both Basic and Complete versions only if the article specified in the link applies to you. When you submit backups for Arcserve D2D nodes with the global backup Compare backup media to disk option specified, the job completes successfully, however, the job status displays failed and the following message appears in the Activity Log: The Client Agent does not support comparing CA ARCserve D2D sessions.

This is expected behavior. The Compare option is not supported for Arcserve D2D sessions. When you encounter this behavior, mount the installation media on a local location.

While backup jobs of virtual machines are running from backup servers running Windows Server , the status for all virtual machines always appears as Backing Up. In addition, you cannot perform various tasks on the virtual machines such as power on, power off, save, pause, reset, rename, and enable replication. When using tapecopy to copy the sessions from a source tape to a destination tape where the destination tape is a blank media, use the -idr parameter to generate a new random ID on the destination tape to avoid any errors during spanning of tapes.

Arcserve Backup does not support multi-byte characters and unicode characters when specifying the Duplicate Media Prefix in the Backup Manager Destination tab. To retain the ASDB, you should perform interim upgrades; upgrade from an unsupported version to a supported version to the current version. For more information, see the topic, Supported Upgrade Paths.

When you upgrade from older versions of Arcserve Backup, tapes with lowercase letters in the tape names are listed in the Session View of the Restore Manager using all uppercase letters. You cannot expand the tape in the Session View. To address this problem, perform the following procedure: In the Database Manager, expand the media Records.

The tape name appears at least twice, once in uppercase letters and once in lowercase letters. Delete the uppercase entry. The Restore Manager displays the tape name and details correctly. So if the server from this Arcserve Backup release is installed with the same instance, which has been used by a previous Arcserve Backup server, the previous Arcserve Backup server will not work normally, even if you choose NOT to overwrite the existing database.

Upgrade of Arcserve Backup components may leave a copy of the older version’s files on the disk, if the components were installed in the same folder.

You need to manually remove the older version’s files from the disk. When upgrading using Agent Deployment, the Automated Upgrade option may be unavailable appear dimmed or grayed out. This happens because the Arcserve Backup database contains no remote host information.

Upgrade to the current Arcserve Backup for Windows release. Clear the check mark from Overwrite DB option on the Select database installation path dialog. Click Language Support Options. The Collation Settings dialog opens.

Click East Asian collation, specify the required language from the drop-down list, and then click OK. The Collation Settings dialog closes. Click Next. Follow the prompts and complete the required fields on the subsequent dialogs to complete the configuration. This is due to a change in the naming method policy. This only affects the first rotation job re-run after upgrade; all subsequent runs are incremental. It is therefore suggested that you upgrade to this release on the same day your GFS rotation job runs a full backup.

For example, if your NAS rotation full backup is scheduled for Fridays, perform the upgrade on a Friday. When you upgrade from Arcserve Backup r16 SP1 to r Whole node backup operations are not supported with the Client Agent for AS Alert Messages on bit machines may display several times, even after you click OK.

If you disable your VMware Adapters, messages display only once. When you uninstall an Agent from a remote system, you must restart the universal agent service on that system and restart the Backup Manager, otherwise, the Backup Manager can still browse that remote system. If you are performing a remote or local backup using Windows bit or Windows with the Delete source files after backup to media use with caution option enabled, you may need to set the following registry key to 0 to obtain the desired results: Key:.

The Client Agent for Windows lets you protect files and folders that reside in virtual hard disks VHDs that are mounted as volumes. If the mounted VHD source data contains hard link files and folders that are not associated with the operating system’s system state, Arcserve Backup backs up the hard link files as multiple, individual files.

As a result, the amount of disk space that is required to store the backup data will exceed the actual size of the data that you are backing up. When you submit a restore job and it fails due to extended time against the default timeout session, the connection breaks and the agent fails.

This scenario is based on restoring files from a session which is spanned across several tapes. As a workaround, you can increase the ReceiveTimeout value where it gives the job enough time to complete and achieve the expected results. You can do this by going to the following registry:. Change the Value data field to a value that prevents the restore job from failing. Note : The ReceiveTimeout value is in seconds. When you back up application-based writer data for example, SQL Server data or Hyper-V virtual machines that resides on remote shares, verify that the remote share is present before you start the recovery job.

Note : You cannot access application based writers when performing disaster recoveries. The solution to this behavior is to recover the system state and the volumes, bring the computer online, and then recover the writers.

You can then access the application data on remote shares after the application writer recovery starts. The following message appears in the Activity Log: The volume shadow service provider had an unexpected error. The error code is logged in the error log. Arcserve Backup will not traverse the system junction points as they are created by the system for the purpose of compatibility. The agent ignores the junction points and continues to back up the system.

Note: For more information about the dbacfg utility, see the Agent for Informix Guide. When using remote Arcserve Backup to back up or restore an Informix server, the real backup and restore jobs created by the Informix Server are scheduled on the Arcserve Backup server based on the local time from the Informix server.

Therefore, time differences between the Arcserve Backup machine and the Informix server machine can cause backup or restore delay. To prevent this delay, synchronize the time between both machines. When using the Client Agent with the Restore by Tree method for your restore operation, databases appear under the Microsoft Windows Network icon in the Restore Manager.

When expanding an Informix instance fails and the activity log displays “Agent function entry point not supported”, the failure is likely due to dbaifmx. We recommend installing Informix by GUI instead of silent install to avoid this problem. For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up. The Net Logon service must be started to support pass-through authentication of account logon events for computers in a domain.

The Agent for Informix does not support compression at the Agent side. A restore job will fail if you attempt to restore multiple Informix instances on the same media because Arcserve Backup cannot restore them sequentially. To successfully restore multiple Informix instances, you can restore them one by one by submitting a new job for each instance after the previous one has been successfully restored. Encryption is not supported. If server side encryption is enabled for Informix backups, the following message is displayed when the job is submitted: Warning: Encryption will be skipped for Informix backups.

In an Informix instance, Windows records the dbspace that is being backed up or restored until the job completes. If that job fails for any reason, the Windows registry does not erase the key value for that dbspace. You cannot enter machine IP addresses. If the Domino Server name is 79 characters or more, Arcserve Backup will truncate the name down to 79 and modify the last 2 remaining characters as shown in the following examples: Original: User First Server: User 01 Additional: User 02 Note: If you are upgrading to the current version of the Arcserve Backup Agent for Lotus Domino, the character limitation for server names is still 30 characters.

The character limitation is only for new server names. If you use Arcserve Backup to back up Lotus Domino 8. To prevent this from happening, apply the latest fix packs. Note : This issue applies to the following environment:. The following issues relating to the Agent for Microsoft Exchange Server are known to exist in this release:. The agent supports document level backups for Exchange Server data in the r When you select Microsoft Exchange server directory as the backup source and perform file system backup with the client agent, please note the following: If the Exchange Information Store is running, the Exchange server files will be skipped during the backup.

If you are restoring an old mailbox store session backed up with the MAPI 6. If Windows client agent and Exchange agent are installed at the Exchange server and Windows client agent is set to use the password security option, then the Exchange Doc level is unable to browse for backup and restore. If you browse the Exchange Document level on two different Arcserve servers using different Windows domain accounts, then browsing at the Exchange Document level will fail.

If you encounter this problem, UnivAgent service will need to be restarted in order to resolve this issue. If you choose the Encryption option for a backup job to create a session, then perform a restore job of the backed up session, the session will fail. If you do not choose the Encryption option for the backup job but perform a restore job of the backed up session anyway, the session will not fail. This scenario only happens in r For Microsoft Exchange Server , when you restore a mailbox database to a new Recovery Database and then fail, verify that the Event Log of the application specifies the following message: “Exchange Replication Service VSS Writer failed restoring a backup because the target database is online.

The message results to a known issue. Resubmit the restore job to an existing Recovery Database. Arcserve Backup does not support backing up Microsoft Exchange Server Inbox rules when performing document level backups. Microsoft is aware of this problem and is working to provide an alternative solution. When you back up Exchange Server data at the document level, the backup job may not respond after some data has been copied.

If you encounter this problem, then it is recommended to perform a backup at the database level. Select the SPSO12 component and delete it.

From the menu, click Options, Configuration. Update each field and check the box to Reset Credential. The Arcserve Backup Agent for SharePoint Server does not support restore operations of content databases that have multiple data files spanned across different disks. Restore jobs fail when restoring site collections using the Community Site and eDiscovery templates. The following message generates when the restore jobs fail: The element ‘Field’ in namespace ‘urn:deployment-manifest-schema’ cannot contain text.

List of possible elements expected: any element in namespace ‘ any’ When using the Community Site template to restore site collections, the first restore job completes successfully. However, subsequent restores using this template fail. When using the eDiscovery template to restore site collections, the first restore using the template, and all subsequent restores using this template fail. For more information, see the spbackup. To prevent this behavior from occurring, perform one of the following actions and then resubmit the restore job:.

To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started. This is a Microsoft requirement. To address this error, perform the following procedure: Locate the version of sqlvdi. From a command prompt, change to the directory containing the selected sqlvdi.

Starting with release When restoring a SQL session, the session size shown in the Restore Manager may be larger than the size of the actual session. The Arcserve Backup Agent for Microsoft SQL Server does not support backing up and restoring SQL Server databases where the sum of the characters representing the instance name, the database name, the file group name, and the data file name exceeds characters. DLL file, which causes conflicts resulting in database backup job failures.

DLL file or reboot the machine. When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

After upgrading Microsoft SQL Server or installing additional instances, you must run the Account Configuration utility to update the agent with the appropriate changes. If you do not run the Account Configuration utility, Arcserve Backup Agent for Microsoft SQL Server will be unaware of the new or changed instances, and you may not have access to additional instances or the additional features of the updated instance.

You should also perform your first backup of the upgraded or new instances immediately after running the Account Configuration utility. When you restore databases to an alternative location, the restore operation can fail and return the following messages: Failed to restore backup session. When the next differential backup starts, SQL Server searches for and locates the most recent full backup data on the primary replica server.

At such time, SQL Server dumps the differential backup data to the most recent full backup data on the primary replica server. Therefore, when you need to restore data from differential sessions of secondary replica servers, restore the full backup from the primary replica server before you restore the differential backup from the secondary replica server. Value: Set to a value greater than the number of database files you wish to exclude. For example, if there are DB files, a value of ensures all database files are excluded from the backup.

To set this parameter to true, perform the following steps: Open a sqlplus prompt. Set the Number of Copies option to a value greater than 1. Submit the backup job. When you change the system time on the machine on which Oracle Server and the Agent for Oracle are installed, archive log backups will fail.

Put the database into MOUNT status before performing full database backups without control file restore, system tablespace restore, or undo tablespace restore. For user tablespace restores, you do not need to do anything.

Backup jobs fail if used. User Profile roles were introduced with the r This version of the Agent is case sensitive. If one modifies the previous job or loads a previous job script before upgrading the agent from earlier versions to the current release, the Oracle database instance may appear twice; once as uppercase and once as lowercase.

This issue affects only display, not performance. The current release of the Backup Server cannot back up r The Agent for Open Files does not provide the eTrust Real-Time scan engine with access to open files to prevent viruses from presenting the scan engine with a version of the infected file concealed as an uninfected file.

When prompted to reboot your machine during remote installation, reboot the machine manually for the remote installation to be successful. The agent may not start if it detects that an Open File Management product from another vendor is already running on the server. Multiple Open File Management products cannot function on the same server.

To resolve this problem, remove the existing Open File Management product from your server and start the agent. Because of the way that Windows Server and Windows XP provides access to encrypted files for backup applications, access to open files is never prevented, so data integrity is not guaranteed. Therefore, the Windows Server Engine does not support the use of encrypted files and their inclusion in a group specification is ignored. Ensure that all encrypted files are closed while your systems are backed up.

If you install the Microsoft Cluster Service after you have installed the Agent for Open Files, you must restart the system to provide the agent with open file access to the shared storage resources of the cluster. Before you perform backups, make sure you close all applications that have files open in a TxF context, such as installation programs. The Agent does not support reparse points other than mount points. All other kinds of reparse points including symbolic link files, junction points, or hard links, are treated as regular files.

If you wish to add all files under a root volume to the Agent for Open Files configuration, you must use wildcards as shown in the following example. When you remotely upgrade the Agent for Open Files on an English System with Chinese locale, you must do the following before you upgrade to ensure Unicode characters are properly displayed: Open the Control Panel and choose Regional and Language Options.

Click Advanced. Choose the option, Apply all settings to the current user account and to the default user profile. Restart the machine. When you attempt to log in remotely to the server where Arcserve Backup Agent for Open Files is installed; the login fails. This issue applies to all Windows operating systems. The Local Security Policy dialog opens. Double-click Network access: Sharing and security model for local accounts from the Security Options Policy list.

The selected policy dialog opens. From the Local Security Setting tab, select Classic – local users authenticate as themselves from the drop-down list. Click OK. You can now log in remotely to the server. The following issues relating to Microsoft VSS are known to exist:. Retrying may work when the system is less busy.

After the backup is complete, return the shadow copy destination disk to an online status. This release of Arcserve Backup supports one 1 password per Oracle encrypted backup. When different table spaces are backed up using different passwords, you must restore them in separate jobs by providing the correct passwords. Avoid changing passwords after a full backup is done.

When password must be changed, do so prior to performing a full backup. If you are running an earlier version of Oracle, set an incremental value between 0 and 4. If you enabled the control file autobackup feature for the target database before using the Agent for Oracle, use your own RMAN scripts to restore an autobackup of the control file. Compare Media to Disk is not supported on Agent for Oracle sessions.

Optimize Restore functionality is not supported for the Agent for Oracle. The Restore by Media and Restore by Session options are not supported for this release.

Encryption Oracle data during the backup phase or the migration phase only supports encrypt data at Backup Server, encrypt data at Agent is not supported. The Agent can support session passwords if Encrypted data at server side is selected from Global Options during backup. You should reboot the machine whenever you install a new Oracle database to avoid problems loading a driver OCI. If you experience problems expanding the Oracle database after providing the correct login credentials, collapse the machine and then re-expand the tree to refresh the cache.

You must supply the correct host name when registering the Agent for Oracle nodes in the Arcserve Backup database. The agent does not support table-level backup or restore operations.

We recommend that you avoid canceling restore jobs. If you cancel a restore job, your database is marked Do Not Recover or Suspect. If this happens, you must recreate the database before starting another restore job. Additionally, the Backup with Delete File option is not supported on agent sessions. When Sybase Adaptive Server devices are mirrored, only the actual device information the database on the device is backed up; data in the mirror device is not backed up.

The agent does not support cluster environment backup or restore operations. The agent supports only the Restore by Tree and Restore by Session options.

If you restore the master database remotely and the Sybase source instance name is the same as the remote destination instance name, the job succeeds. However, when the Sybase source instance name is different from the remote destination instance name, the job fails. When you restore the master database, the contents of the sysservers system table of the master database in the destination instance is identical to the contents of that system table in the source instance and the row that records the Sybase backup server name is incorrect.

To address this issue, update the row using the following SQL statement:. Note: This name is case sensitive. You can find this name in the Windows registry. If a source is missing in restore tree view, it may be a case-sensitive issue. Turn on case-sensitivity during database setup process. Sybase database sessions backed up with BrightStor Enterprise Backup 9.

To resolve this issue, perform the following steps: 1. Choose the Destination tab and clear the checkmark next to the option, Restore files to their original location. Select the destination server and then select the Sybase Server instance on the destination server. Open a command line prompt and start isql.

The following issues relating to the Agent for Virtual Machines are known to exist in this release:. You can still successfully perform data restore jobs. E Selected Writer option cannot be obtained. To prevent this from happening, use VDDK 1. When you restore from an internal session of a nameless volume to an original location, it fails with an invalid drive specification error code AE After a successful recovery of VMware virtual machines, the Disk Provisioning Type of the Virtual Hard Disk depends on the backup approach that you use.

When you back up thin disks using VDDK, and that backup is not an active block backup, you can recover that disk as a thick disk. When you back up thin disks using VDDK, and that backup is an active block backup, then you can only recover that disk as a thin disk.

Using VDDK approach, the agent for virtual machines do not support backup of a virtual machine which itself is a backup proxy server. To back up this virtual machine, you must use a different backup proxy server. When multiple Hyper-V virtual machines contain multiple disks that are sharing a common parent disk; the process of recovering any of the machines in a running state can fail. This behavior is expected when the process of recovering Hyper-V virtual machines tries to overwrite the parent disk where another virtual machine is using it.

Under this condition, the job appears to complete successfully, however, the Hyper-V virtual machine is not going to start. When you back up a virtual machine using the agent and the virtual machine name on the Hyper-V manager is more than 64 characters, the backup job fails. Note : You cannot access application-based writers when performing disaster recoveries. When you back up a VMware or Hyper-V virtual machine with application-based writer data that resides on SMB shares, the backup job fails.

The agent does not support restoring the data from the VHDX transaction log, when recovering virtual machines. The agent behaves in this manner because the Hyper-V VSS writer snapshot does not quiesce or commit the transaction log data. Due to a Microsoft known issue, when you configure storage space on a VMware or Hyper-V virtual machine, backing up the virtual machine fails with a snapshot creation error. The version of Windows Hyper-V that is running on the target server is older than the version of Windows Hyper-V that is running on the server that was backed up.

To resolve this issue, restore the virtual machine that was backed up on the Windows Hyper-V server to an equal or later version of a Windows Hyper-V server. The agent does not support backing up Hyper-V virtual machines that contain disks that are equal to 64 terabytes.

To resolve this issue, you can download and install VDDK 5. When recovering data from NTFS Deduplication volumes that are optimized and a volume contains a very large quantity of files 1 million or more files , the throughput calculation in the Activity Log and the Job Monitor is incorrect.

When VMware-based virtual machines contain independent disks and raw device mappings that are configured in the physical mode, Arcserve skips these volumes during backup jobs. However, the fact that the volumes were skipped during backup jobs is not recorded in the Activity Log.

When the process of retrieving the used data blocks on VMware-based virtual machines using VMware changed block tracking CBT fails, the agent currently cannot reset CBT when the virtual machine contains snapshots. To correct this behavior, remove the snapshot manually so that you can reset CBT. VMware is a aware of this problem and is working to provide a solution to this behavior. Backing up on Windows Server guest operating systems or later is not supported with Windows Server R2 or older versions as the proxy server.

When you perform a file mode backup on a Windows Server VM, the job does not complete for the following reasons: The VM contains one or more dynamic disks.

The VM is backed up with a Windows Server proxy server. To resolve this problem, install the agent inside the VM to perform the file mode backups. VMware is aware of this problem and is working to provide a solution to this behavior. The following issues relating to the Enterprise Option for AS are known to exist in this release:. To prevent this failure, ensure that the most current IBM tape driver is installed on the primary and distributed machines.

To do so, perform the following procedure on each machine:. For example, for an Ultrium drive, find the registry key for the drive in the following directory:. Exit regedit and restart your computer.

The Client Agent for Windows prompts you to specify the Use Computer Name Resolution option or the IP address to include the databases when backing up the entire machine. The IP address and hostname of the Agent and base machines should be added to the hosts file on each system before running any backup and restore jobs. The NetLogon service must be started to support pass-through authentication of account logon events for computers in a domain.

If you are running the Enterprise Option for SAP on a remote system and submitted backup jobs to a backup server having more than one NIC installed, the jobs fail due to connection problems. Open the hosts file. Save and close the hosts file. The option does not support the following: Submitting restore jobs using the Restore by Query restore method.

Using multistreaming when backing up SAP data to data deduplication devices. With multistreaming, Arcserve Backup backs up SAP data to multiple devices that reside in different device groups simultaneously. As a result, Arcserve Backup backs up SAP data to device groups that do not contain deduplication devices. Using the Optimize Restore functionality.

Using Compare Media to Disk functionality. This option does not support using multistreaming when backing up SAP data to data deduplication devices. If you register a data mover server with a different primary server after you install and configure option, you must reconfigure the option using the sapsetup script. If you do not reconfigure the option, jobs submitted through the affected data mover server will fail. However, the option does not support compressing the data during the backup.

However, you can perform this restoration by using the “brrestore” module from the Command Line. The brrestore module is used to restore database data files, control files, and offline redo log files. The following issues relating to the Disaster Recovery Option are known to exist in this release:. After Disaster Recovery is completed, the size of the last partition recovered can be expanded from the original size by as much as 8 MB.

The problem occurs if there is free space at the end of the last partition on the disk being recovered. During Disaster Recovery from a bootable CD, you may be prompted to insert a disk into the floppy drive before inserting the Machine Specific Disk.

It is safe to ignore this message and click OK to continue. The database engine will not start automatically after successful recovery of the Arcserve Backup database.

Upon the first reboot after performing Disaster Recovery of the Arcserve Backup server hosting the Arcserve database, you must restart the database engine. Do so through the Arcserve Backup Manager Console. To save logs, create a new folder using the mkdir command with the Open Console button or save logs into an existing folder. If your system is configured with a number of volumes mounted via mount points, Disaster Recovery cannot be performed correctly. You must format and restore data manually.

Consider the following situation: Arcserve Backup is installed on Server A. When using the Disaster Recovery option to restore backup data from these devices, Arcserve Backup will be able to connect to only one.

When you perform a remote upgrade from Arcserve Backup r12 or Arcserve Backup r This behavior affects only computers running Windows 7. This problem does not occur on all remote upgrades to computers running Windows 7. If you encounter this problem, log in to the computer directly to perform the upgrade.

Note: Please make sure that no browse operation is performed, and no backup or restore job is running before stopping this service. Start the CA Universal Agent service. The Arcserve Backup server must be able to ping all machines in the SharePoint environment by name.

For SharePoint Server farm environments, you must run the Microsoft SQL Server database instance with a domain account; for SharePoint Server standalone environments, you must run the Microsoft SQL Server database instance with a domain account or a local system account, depending on the configuration of the SharePoint installation.

To avoid this situation, launch License Management and manually release the licenses for old versions of the Agent that have been upgraded. If the Agent for Microsoft SharePoint Server , which is no longer supported, is detected during upgrade, the agent is automatically uninstalled.

Before you begin, determine whether the Vista machine is part of a domain or part of a workgroup. Use a Domain Administrative account if the target computer is part of a domain. Grant a domain account with administrator privileges on the Vista machine and use that domain account to log on. You may then remotely install the Agent for Open Files on the Vista machine. If the target computer is part of a workgroup, disable the client computer’s local account filtering policy by creating a new registry key, as follows:.

After installation, set the LocalAccountTokenFilterPolicy setting to 0 to re-enable local account filtering. When installing the Agent for Open Files, a reboot is recommended, but not necessary. Without rebooting, any files open before the Agent was installed may not be accessible during backup. The following section provides information about installation prerequisites, configuration, and issues to consider when installing the Arcserve Backup Enterprise Module.

Secure the host name of the Arcserve Backup primary server. Secure the password for the caroot user name for the Arcserve Backup primary server. Ensure that the Arcserve Backup primary server and the target data mover server can communicate with each other. You can verify that the servers can communicate using the ping host name command. You do not need to uninstall the following components from the target data mover server to upgrade to this release: Client Agent for Linux r If the installation script detects a supported platform, you will be prompted to install the latest versions of the above file system agents.

The following section provides information about general considerations while installing the current release for Patch Manager. You will need to upgrade to current release of Patch Manager if you have an earlier version in order to get the patches for the current release of Arcserve Backup. While upgrading the client and if the client is connected to the Staging server, ensure that the Staging server is also upgraded. Note : The backup proxy system should have Microsoft.

NET framework 2. Hyper-V Systems: Install the Arcserve Backup Server components on the system intended to operate as the primary or standalone server. You may then remotely install the Client Agent on the Vista machine. In a clustered Arcserve Backup environment, the Client Agent for Windows needs to be installed on the local drive on each cluster node. If you install the Client Agent Windows, UNIX on a virtual machine, you will be able to back up the data as if it were a physical machine.

If the previous installation was that of a member server, you must upgrade the Arcserve Backup components that apply to Member server installation. The Server Configuration Wizard lets you change the role of the server after you complete the upgrade process. Optionally, you can uninstall and then reinstall Arcserve Backup. However, to ensure that you do not lose records of your backup and restore data, you must not overwrite the Arcserve Backup database instance that is detected by the Installation Wizard.

For more information on supported upgrades, please refer to the Arcserve Backup for Windows Implementation Guide – Supported Upgrades section. When you customize job scripts on the primary server using the previous Arcserve Backup release, you will not be able to modify the job scripts after upgrading to the current release and will get an error message warning you that the job cannot be unpacked.

To use job scripts created with previous versions of Arcserve Backup after upgrading, you must manually select the sources and then submit the jobs. The upgrade process does not install the drivers required by the Image Option. As a result, scheduled jobs involving the Image Option can fail. To remedy this problem, you must install the required drivers manually using the Enterprise Module configuration utility.

Ensure the Regional and Language options for the Arcserve Backup Server and Arcserve Backup Agents are set identically to avoid browsing and encryption problems typical when operating the current version of Arcserve Backup with agents from previous versions.

The name of the Arcserve Backup home directory has changed since the previous release. If you specified the Arcserve Backup home directory as a parameter in the commands of any generic jobs created prior to upgrading, you need to modify those jobs and correct the path to the current Arcserve Backup home directory name.

The setup process automatically stops these services and programs unless you are performing an SDO installation. In this case, you should stop all services and back end programs manually before you proceed.

After the restore operation is complete, run a discovery in the Access Manager. When restoring folders and files, note the following: When Restore and Preserve Directory Attributes and Security Information is enabled, and Restore and Preserve File Attributes and Security Information is disabled, the encryption attributes of files are restored.

When Restore and Preserve Directory Attributes and Security Information is enabled, and Restore and Preserve File Attributes and Security Information is disabled, the compression attributes of directories are not restored.

When Restore and Preserve Directory Attributes and Security Information is disabled, and restore and Preserve File Attributes and Security Information is disabled, the encryption attributes of files are restored. When connecting to a new server, you must provide the Arcserve Backup user account, caroot. Note: The caroot user profile controls access only to the Arcserve Backup Manager and backup-related functions, and should not be confused with the user credentials required to log in to the Microsoft Windows operating system.

For more information regarding this user profile, see the Arcserve Backup Administration Guide. You should not leave the password blank for caroot. The following information concerns the backup and restore of Hyper-V based virtual machines.

However, when the Client Agent is installed on a Virtual Machine, remote Disaster Recovery is supported the same as if on a physical machine. The following provides general information to consider when using the Arcserve Backup Global Dashboard:. During a full data synchronization, the Arcserve Backup database engine service is stopped for a few minutes.

This may affect the status of any backup jobs in Arcserve Backup that are already running especially jobs related to logging any information in the branch ASDB. The following provides general information to consider when using the Arcserve Backup Agent for Virtual Machines:. VCB Framework 1. The following section provides general information to consider when integrating Arcserve Backup and Arcserve D2D:.

The following are unsupported scenarios and limitations to consider when backing up Arcserve D2D destination files and folders: For Arcserve Backup to skip the Arcserve D2D destination files and folders, you must select the Arcserve D2D folder at the root or shared folder level. Therefore, Arcserve D2D integration with Arcserve Backup will be supported in the following scenarios: User selects the shared or root folder.

User selects the volume that has the Arcserve D2D destination. User selects the entire machine. If a shadow copy is created specifically for backing up Arcserve D2D destination, the backup of the Arcserve D2D destination will not be consistent in the following scenarios: The Arcserve D2D destination of a machine is spread across multiple volumes.

The Arcserve D2D destination of a machine is spread across multiple root folders. If the Arcserve D2D destination for the same machine is encountered, a new VSS shadow copy has to be created again which will not be consistent with the VSS shadow copy created previously. Arcserve Backup r However, if you wish to retain the database information from your previous implementation, you must upgrade the previous implementation to Arcserve Backup r To obtain Arcserve Backup r The following issues relating to the Arcserve Backup base product are known to exist in this release:.

A problem with the Emulex driver released with Windows SP1 prevents Arcserve Backup from initializing correctly unless you update the Emulex driver. If you use the Master Setup to install Arcserve Backup remotely to a system in another Windows domain, you may receive a message indicating that the installation failed when it is successful.

This behavior occurs because the Master Setup cannot accurately detect the activity on the remote machine in the other domain because of a firewall or due to a lost network connection.

Check the installation status on the remote machine to verify that the installation succeeded. You must perform a full inventory of tapes to enable this option because this capability can be recognized only by reading the media. Installing bit components on a bit machine generates two copies of the file PortsConfig. The PortsConfig. If you make changes to one, you must make the same changes to the other, or the components may not be able to contact one another.

If you install agents on cluster nodes, do not back up the physical nodes the private drives C: and D: or non-shared disks through preferred share using the virtual server IP address, because virtual servers can be moved from one node to another.

For example, if virtual server 1 resides on physical node 1 and you backed up virtual server 1 through preferred share, the non-shared drives on physical node 1 are also backed up. If you move virtual server 1 to physical node 2, and perform a Restore to Original Location, the non-shared drives from physical node 1 are restored to physical node 2.

Special characters in media files will interfere with RMAN jobs. Job redirection is no longer supported.

As an alternative, you can use the makeup job feature. Refer to the Administration Guide for more information regarding makeup jobs. When the Windows security policy is enabled on the machine where Arcserve Backup is installed, an audit log is recorded in the event log at the time of a system application startup, such as Task Manager. If you apply the license keys for two or more different Arcserve Backup suites on a single Arcserve server, the license count on the Arcserve server may not be correct.

To remedy this problem, apply the licenses that you require and contact Arcserve Technical Support to correct the license count. The Tape Compare utility does not support comparing tapes that were created using multiplexing or encryption. Broadcast Alerts do not function on systems running Microsoft Windows Server This behavior is observed because Microsoft Windows Server does not support messaging service.

After you restore the Arcserve bit ASDB, you must perform at least one full backup of the Arcserve Backup database before you perform an incremental or a differential backup. This task helps ensure that Arcserve Backup database backup sessions contain the most current data. This task helps ensure that Arcserve Backup database backup sessions are current.

A NetBIOS name resolving problem between local and remote machines may prevent you from obtaining information from the Diagnostic Wizard. To avoid communication problems, verify that the remote system is on the network and that the machine name is correctly mapped to the IP address.

To do so, perform the following steps: Confirm that the remote machine is reachable across the network and that the IP Address matches the remote machine name. If the system cannot be pinged at all, check the network connections and ensure the system is operational. If the name does not match the IP address, continue.

Examine the command output for mistakes in your configurations. If mistakes exist, the network cannot communicate properly. Open Network Connections. Click the Support tab. Click Details. Examine the output and verify the remote machine IP address matches its machine name for all types of the machine name specified. If the machine name does not match the IP address, or if no such items exist in the table, proceed to Step 4.

Optional If you find a mismatch in the mapping between a System Name and IP Address, run the following command to purge the Server Name and IP address mapping on both the local and remote machines. Otherwise, skip to Step 5. Run nbtstat -c again. The table should now be empty, or contain only a few new items with lives of about seconds. The tables should show identical information: the name of the remote system as “Registered” for the IP Address.

The Arcserve Backup database may not contain up-to-date database information for example, file lists and physical locations and the Restore Manager, Restore by Tree, source directory tree may not display up-to-date information immediately after you restore the Arcserve Backup database to its original location original computer or original database instance or to a different location different computer or different database instance.

To remedy this problem, do the following:. After you restore the Arcserve Backup database, use the Merge utility to merge the Arcserve Backup database backup sessions.

Close and then reopen the Restore Manager window to refresh the information that displays in the Restore by Tree source directory tree. These objects are displayed with excluded text which will not be backed up when the makeup job is submitted. When you log off an interactive Windows session while a message such as tape mount is still displayed, some temporary files will remain in the Arcserve Backup Temp folder.

Backup jobs performed with Windows , and Windows systems may include the following files that Microsoft recommends not be backed up, even if they are specified in the FilesNotToBackup registry key: index.

Arcserve Backup operations executed on the same tapekey after tapecopy has been executed could affect either the source or the destination tape. Job failure may also occur if a session is added to either the source or destination tape after Tapecopy because Arcserve Backup may not be able to restore that added session.

This is because a tape is identified by three items: the tape name, the random ID, and the sequence number. The combination of these three tape identifiers is called the tapeKey.

If you do not want the destination tape to be the exact same as the source tape, you can include the —idr switch with the tapecopy command so that Arcserve Backup automatically assigns a different random ID to the destination tape and ensures that the destination tape is not exactly the same as the source tape.

If you do not include -idr switch with the tapecopy command, you could then use the destination tape at a later time to perform a disaster recovery operation because the destination tape will be exactly the same as the source tape.

This release of Arcserve Backup automatically creates a new media pool with the same name given to media in an r12 or prior environment and inventoried in the current environment. During recovery, the Arcserve Backup database is offline. So any client programs trying to access the database during this period will be denied. This message does not prevent recovery from completing successfully.

Security validation is performed only on Windows or XP systems. In Citrix 4. When run with Microsoft Office , Arcserve Backup Job Status Manager can experience excessive “handle leaks”, too many open register keys that are no longer in use. Install the latest Microsoft Office service pack to avoid this problem.

When the Catalog database folder is changed to a long path name greater than characters and backed up, the catalog files may not be kept in the catalog database and an E error is recorded in the Activity Log. If Password Security is enabled and any database, application, or messaging Agent is installed on the same machine as the Client Agent, whole node backup is not supported.

System Security is the default setting. You must not enable Password Security in the Agent Configuration on any machine running a database, application, or messaging Agent before submitting the job. However: when you perform a remote backup of an entire drive on which Single Instance Storage was activated as the backup source, the job fails and AW is recorded.

This is because Arcserve Backup is attempting to back up files that should have been excluded. Restoring the entire session to its original location also restored files that should have been excluded. When you restore SIS links using the global option “log all activity” set to on, the Job Log shows only the links have been restored, not the data files.

The Remote Restore Job Log shows the files as restored. For jobs shown in the Activity Log, the Media Compression Ratio and the Media Remaining Capacity display as 0 because these parameters are not supported by the device. Arcserve Backup does not support Windows passwords that are 24 characters and longer.

When you add a Windows agent machine to Arcserve Backup, you are prompted for a hostname and password. Even though Windows supports a long password here, Arcserve Backup does not and login will fail. Arcserve Backup does not support restoring a Job Queue session to its original location using normal data recovery processes.

Although Arcserve Backup does not use the service setting, the installer changes it. This service should not have been changed to start up automatically. To eliminate Warning 3, perform the following steps:. Set Arcserve Backup services to depend on SQL Server service to start up by using the Microsoft sc utility see Using Utility steps a through c, below or by manually setting the registry keys see Manually editing the registry, below.

Using the utility:. Edit the registry manually :. Reboot the computer. The errors should not reappear. This service is disabled on Windows Server systems by default. This problem is limited to machines that are members of a workgroup; if the machine is a member of domain, log in proceeds.

To avoid the problem, use regedit to set the ForceGuest registry value to 0. When you install this release of Arcserve Backup on the cluster node of a Windows Server cluster, the Arcserve Backup Database is listed in the cluster virtual name on the Backup Manager.

When Japanese collation is selected, operations are Kana-sensitive, Width-sensitive and Case-sensitive. For the Look in Directory field on the Restore by Query screen, and the Volume field on the Search dialog, you may specify only uppercase drive letters. Security information for the Agent for Microsoft SQL is not automatically loaded after upgrading from earlier Arcserve Backup versions to this release.

You must retype password to continue. Arcserve Backup does not support integration with the Microsoft Management Console. If the Arcserve Backup database is configured to use SQL Server, the Database Protection Job may not be able to successfully back up the Arcserve Backup database in a clustered environment when failover happens from one node to another node. If such a situation occurs, run the Database Protection Job again manually to verify the Arcserve Backup database is being successfully backed up.

This approach is not recommended because the default locations for user data and system data for example, the Documents and Settings folder are different than that of previous Windows operating systems. As a best practice, you should back up the folders that are referenced by the symbolic link, rather than the link itself.

You may experience slow performance when you browse Windows Server x64 systems from the Windows Systems object in the Backup Manager directory tree. Arcserve Backup demonstrates this behavior due to various environmental conditions that can cause VSS writers to enumerate the VSS metadata. However, without the VSS metadata, you can browse only the disks for the specified computer. When restoring Hyper-V virtual machines to an alternate location, Arcserve Backup may not be able to power on the target if the friendly name of the network switch is not the same as that of the original backup.

To remedy this problem, verify that the friendly name of the network switch of the destination is the same as the source location before you submit the restore. An alternate solution is to edit VM settings after restore is complete and change the network switch name to one available on the destination server. Export options override the Eject Media options but because this device does not support exporting, the device is not ejected upon job completion.

When saving a Data Mover backup job script from the Backup Manager console, the Data Mover’s source, destination, and global options checks are not executed. Therefore, the GUI will not show any messages to warn the user or block the user from submitting the job and removing the unsupported options.

If you reload the saved job script from the Job Status Manager, the job will fail. Select one of the following options as a workaround:. If you select the Save or Save As menu to save the job script, you can reload the job and modify this job in the Job Status Manager, and then re-submit the job. All checks will then be executed. If you select the Save or Save As menu to save the job script, you can click the Open menu from the Backup Manager console to open the job script and then click the Submit button to submit the job.

Arcserve Backup supports only one writer e. If you include other types of source disks to this one backup job, the job will fail. In the case of Classic View, you can change it by selecting Agent Modification from the Context menu. When adding a cloud connection from the Device Manager and you enter the domain password and proxy credentials, the system caches the credentials.

If you add another connection and specify incorrect domain password and proxy credentials or leave it blank, the system picks up the cached credentials and successfully adds the cloud connection. As a workaround, you can delete the cookies from the computer you are working from or reboot. This will cancel out the cached credentials. After migration job completes for a disk staging job, the restore by session method searches for the specific file in two sessions staging session and migration session , while the restore by query method searches the file in only one session staging session or migration session, not both.

Note : Creating a vault after migration completes specifies the requested file in only one session staging session or migration session, not both which places only one tape into the vault. This is a Windows restriction stating that if you use an existing user name to create a connection to a shared resource, then any other user name will fail to create the connection to the same resource. When you submit a staging job with FSD as the staging location and Cloud Device as its destination, the migration job does not resume after an unplanned cluster failover occurs as the tape engine needs time to initialize the cloud device.

As a workaround, Arcserve Backup creates a makeup job for the failed migration job to continue the migration process.

For the reason that Windows cannot access binary files after a failover on a cluster environment due to the back-end process of a failed caauthd.

To recover data from backup sessions that were migrated to Eucalyptus Cloud devices using a prerelease version of Arcserve Backup r16, add the following property to the CCIConfig initialization file. File location:. Note: Set the value of the UseOldDecode property to 0 to use the new devices. The default value of UseOldDecode is 0. When you upgrade from older versions of Arcserve Backup, tapes with lowercase letters in the tape names are listed in the Session View of the Restore Manager using all uppercase letters.

You cannot expand the tape in the Session View. To address this problem, perform the following procedure: In the Database Manager, expand the media Records. The tape name appears at least twice, once in uppercase letters and once in lowercase letters. Delete the uppercase entry. The Restore Manager displays the tape name and details correctly.

So if the server from this Arcserve Backup release is installed with the same instance, which has been used by a previous Arcserve Backup server, the previous Arcserve Backup server will not work normally, even if you choose NOT to overwrite the existing database. Upgrade of Arcserve Backup components may leave a copy of the older version’s files on the disk, if the components were installed in the same folder.

You need to manually remove the older version’s files from the disk. When upgrading using Agent Deployment, the Automated Upgrade option may be unavailable appear dimmed or grayed out. This happens because the Arcserve Backup database contains no remote host information. If you protect data that contains Unicode-based characters from East Asian languages, for example, JIS you must enable SQL collation to ensure that you can search and sort the data.

To specify SQL Server collation settings, do the following:. Upgrade to the current Arcserve Backup for Windows release. Clear the check mark from Overwrite DB option on the Select database installation path dialog. Click Language Support Options. The Collation Settings dialog opens. Click East Asian collation, specify the required language from the drop-down list, and then click OK. The Collation Settings dialog closes.

Click Next. Follow the prompts and complete the required fields on the subsequent dialogs to complete the configuration. This is due to a change in the naming method policy. This only affects the first rotation job re-run after upgrade; all subsequent runs are incremental. It is therefore suggested that you upgrade to this release on the same day your GFS rotation job runs a full backup.

For example, if your NAS rotation full backup is scheduled for Fridays, perform the upgrade on a Friday. Whole node backup operations are not supported with the Client Agent for AS Alert Messages on bit machines may display several times, even after you click OK. If you disable your VMware Adapters, messages display only once. When backing up files on IA64 systems, note that a file’s Last Access Time is not updated even when the Preserve file access time option is not selected.

This problem appears limited to jobs in which the Keep Archive Bit option is selected. When you uninstall an Agent from a remote system, you must restart the universal agent service on that system and restart the Backup Manager, otherwise, the Backup Manager can still browse that remote system.

If you are performing a remote or local backup using Windows bit or Windows with the Delete source files after backup to media use with caution option enabled, you may need to set the following registry key to 0 to obtain the desired results: Key:.

The Client Agent for Windows lets you protect files and folders that reside in virtual hard disks VHDs that are mounted as volumes. If the mounted VHD source data contains hard link files and folders that are not associated with the operating system’s system state, Arcserve Backup backs up the hard link files as multiple, individual files.

As a result, the amount of disk space that is required to store the backup data will exceed the actual size of the data that you are backing up. When you submit a restore job and it fails due to extended time against the default timeout session, the connection breaks and the agent fails.

This scenario is based on restoring files from a session which is spanned across several tapes. As a workaround, you can increase the ReceiveTimeout value where it gives the job enough time to complete and achieve the expected results. You can do this by going to the following registry:. Change the Value data field to a value that prevents the restore job from failing. Note : The ReceiveTimeout value is in seconds.

Note: For more information about the dbacfg utility, see the Agent for Informix Guide. When using remote Arcserve Backup to back up or restore an Informix server, the real backup and restore jobs created by the Informix Server are scheduled on the Arcserve Backup server based on the local time from the Informix server. Therefore, time differences between the Arcserve Backup machine and the Informix server machine can cause backup or restore delay.

To prevent this delay, synchronize the time between both machines. When using the Client Agent with the Restore by Tree method for your restore operation, databases appear under the Microsoft Windows Network icon in the Restore Manager. When expanding an Informix instance fails and the activity log displays “Agent function entry point not supported”, the failure is likely due to dbaifmx.

We recommend installing Informix by GUI instead of silent install to avoid this problem. For remote backups, you must enable File and Printer Sharing for Microsoft Networks on the agent machine you are backing up.

The Net Logon service must be started to support pass-through authentication of account logon events for computers in a domain. The Agent for Informix does not support compression at the Agent side. A restore job will fail if you attempt to restore multiple Informix instances on the same media because Arcserve Backup cannot restore them sequentially. To successfully restore multiple Informix instances, you can restore them one by one by submitting a new job for each instance after the previous one has been successfully restored.

Encryption is not supported. If server side encryption is enabled for Informix backups, the following message is displayed when the job is submitted: Warning: Encryption will be skipped for Informix backups. In an Informix instance, Windows records the dbspace that is being backed up or restored until the job completes. If that job fails for any reason, the Windows registry does not erase the key value for that dbspace.

You cannot enter machine IP addresses. If the Domino Server name is 79 characters or more, Arcserve Backup will truncate the name down to 79 and modify the last 2 remaining characters as shown in the following examples: Original: User First Server: User 01 Additional: User 02 Note: If you are upgrading to the current version of the Arcserve Backup Agent for Lotus Domino, the character limitation for server names is still 30 characters.

The character limitation is only for new server names. If you use Arcserve Backup to back up Lotus Domino 8. To prevent this from happening, apply the latest fix packs. Note : This issue applies to the following environment:. The following issues relating to the Agent for Microsoft Exchange Server are known to exist in this release:.

The r When you select Microsoft Exchange server directory as the backup source and perform file system backup with the client agent, please note the following: If the Exchange Information Store is running, the Exchange server files will be skipped during the backup. If you are restoring an old mailbox store session backed up with the MAPI 6. If Windows client agent and Exchange agent are installed at the Exchange server and Windows client agent is set to use the password security option, then the Exchange Doc level is unable to browse for backup and restore.

If you browse the Exchange Document level on two different Arcserve servers using different Windows domain accounts, then browsing at the Exchange Document level will fail. If you encounter this problem, UnivAgent service will need to be restarted in order to resolve this issue.

If you choose the Encryption option for a backup job to create a session, then perform a restore job of the backed up session, the session will fail.

If you do not choose the Encryption option for the backup job but perform a restore job of the backed up session anyway, the session will not fail. This scenario only happens in r For Microsoft Exchange Server , when you restore a mailbox database to a new Recovery Database and then fail, verify that the Event Log of the application specifies the following message: “Exchange Replication Service VSS Writer failed restoring a backup because the target database is online.

The message results to a known issue. Resubmit the restore job to an existing Recovery Database. The following issues relating to the Agent for Microsoft SharePoint Server are known to exist in this release:. Select the SPSO12 component and delete it. From the menu, click Options, Configuration. Update each field and check the box to Reset Credential. The Arcserve Backup Agent for SharePoint Server does not support restore operations of content databases that have multiple data files spanned across different disks.

To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started. This is a Microsoft requirement. To address this error, perform the following procedure: Locate the version of sqlvdi.

From a command prompt, change to the directory containing the selected sqlvdi. Starting with release When restoring a SQL session, the session size shown in the Restore Manager may be larger than the size of the actual session. The Arcserve Backup Agent for Microsoft SQL Server does not support backing up and restoring SQL Server databases where the sum of the characters representing the instance name, the database name, the file group name, and the data file name exceeds characters.

DLL file, which causes conflicts resulting in database backup job failures. DLL file or reboot the machine. When performing a database restore job that fails, the job continues after the error only if you are restoring by session.

If you are restoring by tree, subsequent sessions will not be restored. This is because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.

After upgrading Microsoft SQL Server or installing additional instances, you must run the Account Configuration utility to update the agent with the appropriate changes. If you do not run the Account Configuration utility, Arcserve Backup Agent for Microsoft SQL Server will be unaware of the new or changed instances, and you may not have access to additional instances or the additional features of the updated instance.

You should also perform your first backup of the upgraded or new instances immediately after running the Account Configuration utility. When you restore databases to an alternative location, the restore operation can fail and return the following messages: Failed to restore backup session. To prevent this behavior from occurring, perform one of the following actions and then resubmit the restore job:. When the next differential backup starts, SQL Server searches for and locates the most recent full backup data on the primary replica server.

At such time, SQL Server dumps the differential backup data to the most recent full backup data on the primary replica server. Therefore, when you need to restore data from differential sessions of secondary replica servers, restore the full backup from the primary replica server before you restore the differential backup from the secondary replica server.

If you are running eTrust Antivirus 7. Contact eTrust Antivirus Customer Support to obtain this patch. The Agent for Open Files does not provide the eTrust Real-Time scan engine with access to open files to prevent viruses from presenting the scan engine with a version of the infected file concealed as an uninfected file. When prompted to reboot your machine during remote installation, reboot the machine manually for the remote installation to be successful.

The agent may not start if it detects that an Open File Management product from another vendor is already running on the server. Multiple Open File Management products cannot function on the same server. To resolve this problem, remove the existing Open File Management product from your server and start the agent. Because of the way that Windows Server and Windows XP provides access to encrypted files for backup applications, access to open files is never prevented, so data integrity is not guaranteed.

Therefore, the Windows Server Engine does not support the use of encrypted files and their inclusion in a group specification is ignored. Ensure that all encrypted files are closed while your systems are backed up. If you install the Microsoft Cluster Service after you have installed the Agent for Open Files, you must restart the system to provide the agent with open file access to the shared storage resources of the cluster.

Before you perform backups, make sure you close all applications that have files open in a TxF context, such as installation programs. The Agent does not support reparse points other than mount points. All other kinds of reparse points including symbolic link files, junction points, or hard links, are treated as regular files. If you wish to add all files under a root volume to the Agent for Open Files configuration, you must use wildcards as shown in the following example.

When you remotely upgrade the Agent for Open Files on an English System with Chinese locale, you must do the following before you upgrade to ensure Unicode characters are properly displayed: Open the Control Panel and choose Regional and Language Options. Click Advanced. Choose the option, Apply all settings to the current user account and to the default user profile. Restart the machine. The following issues relating to Microsoft VSS are known to exist:. Retrying may work when the system is less busy.

After the backup is complete, return the shadow copy destination disk to an online status. Value: Set to a value greater than the number of database files you wish to exclude. For example, if there are DB files, a value of ensures all database files are excluded from the backup. To set this parameter to true, perform the following steps: Open a sqlplus prompt. Set the Number of Copies option to a value greater than 1. Submit the backup job. When you change the system time on the machine on which Oracle Server and the Agent for Oracle are installed, archive log backups will fail.

Put the database into MOUNT status before performing full database backups without control file restore, system tablespace restore, or undo tablespace restore.

For user tablespace restores, you do not need to do anything. Backup jobs fail if used. User Profile roles were introduced with the r This version of the Agent is case sensitive. If one modifies the previous job or loads a previous job script before upgrading the agent from earlier versions to the current release, the Oracle database instance may appear twice; once as uppercase and once as lowercase.

This issue affects only display, not performance. The current release of the Backup Server cannot back up r If you chose to back up directly to tape, note you will require more storage media when doing a multichannel backup. This release of Arcserve Backup supports one 1 password per Oracle encrypted backup. When different table spaces are backed up using different passwords, you must restore them in separate jobs by providing the correct passwords. Avoid changing passwords after a full backup is done.

When password must be changed, do so prior to performing a full backup. If you are running an earlier version of Oracle, set an incremental value between 0 and 4. If you enabled the control file autobackup feature for the target database before using the Agent for Oracle, use your own RMAN scripts to restore an autobackup of the control file. Compare Media to Disk is not supported on Agent for Oracle sessions.

Optimize Restore functionality is not supported for the Agent for Oracle. The Restore by Media and Restore by Session options are not supported for this release. Encryption Oracle data during the backup phase or the migration phase only supports encrypt data at Backup Server, encrypt data at Agent is not supported. The Agent can support session passwords if Encrypted data at server side is selected from Global Options during backup. You should reboot the machine whenever you install a new Oracle database to avoid problems loading a driver OCI.

If you experience problems expanding the Oracle database after providing the correct login credentials, collapse the machine and then re-expand the tree to refresh the cache. You must supply the correct host name when registering the Agent for Oracle nodes in the Arcserve Backup database.

The agent does not support table-level backup or restore operations. We recommend that you avoid canceling restore jobs. If you cancel a restore job, your database is marked Do Not Recover or Suspect.

If this happens, you must recreate the database before starting another restore job. Additionally, the Backup with Delete File option is not supported on agent sessions. When Sybase Adaptive Server devices are mirrored, only the actual device information the database on the device is backed up; data in the mirror device is not backed up. The agent does not support cluster environment backup or restore operations.

The agent supports only the Restore by Tree and Restore by Session options. If you restore the master database remotely and the Sybase source instance name is the same as the remote destination instance name, the job succeeds. However, when the Sybase source instance name is different from the remote destination instance name, the job fails. When you restore the master database, the contents of the sysservers system table of the master database in the destination instance is identical to the contents of that system table in the source instance and the row that records the Sybase backup server name is incorrect.

To address this issue, update the row using the following SQL statement:. Note: This name is case sensitive. You can find this name in the Windows registry.

If a source is missing in restore tree view, it may be a case-sensitive issue.

 
 
 
 

Documentation Changes The following documentation updates have been made since the last release of this documentation: Rebranded to CA Technologies. Licensing (see page 10)—This new topic describes the licensing requirements for the agent. A backup job fails with license errors when backing up open files on a virtual machine (see page 64)—This new topic . Core (x86, x64) (Arcserve Backup Member Server, Arcserve Backup Client Agent for Windows, Arcserve Backup Agent for Open Files, Arcserve Backup Agent for Virtual Machines) Failover Cluster support (only Windows Server Enterprise and Windows Server Standard). Install locally and follow the instructions for cluster environments.