Have you tried backing up volumes individually i. This may give somes clues Communities View more. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:.
Sign In. Backups Failing - Cannot create recovery points for job. Go to solution. Smiffy85 Level 3. There are a group of servers that will not back up, the message they receive is as below taken from Event Log. Permissions are correct and I can copy backup files between the server and NAS and the other way too.
If you are able to help that would be excellent as I have been struggling with Symantec Support for about 6 weeks for various issues with regards this installation.
All forum topics Previous Topic Next Topic. Did this get resolved in any way? What does this message mean? Hello, If you are backing up multiple resources, split the job and check exactly on which resource does the job fail. Also check if the port is free not We apologise for the mistake in the previous reponse. NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool. As per our previous reply, marking the case as "assumed answered" and moving it to "answered questions" pool.
We're getting this same error at the end of our backup. No other errors in the job that I can see. Could this occur if you are using a tape library with two backup jobs running simultaneously, even if the jobs are backing up data from different servers? Error : efeb9 - The NDMP subsystem reports that a request cannot be processed because it is in the wrong state to service the request. For additional information regarding this error refer to link V I have the same problem occasionally and I have checked the account and port and still problem persists.
What is teh correct fix! Having this same problem with Backup Exec version 10 on windows server when backing up remote servers running both windows and windows If you install Backup Exec on a Veritas Cluster Server node that runs Microsoft Exchange, that node must be offline at the time of installation.
If you keep Exchange online during installation, services do not start properly. If you want to use the SQL Express database that is included with Backup Exec, you must switch the Exchange group to another node or take it offline. Otherwise the installation of SQL Express cannot complete successfully. An error error code 2 may occur when you install SQL Express in an environment with the following conditions: Active Directory is installed on a computer that is running Windows Server The computer belongs to a root domain that uses a short domain name such as "first.
To avoid this error, install SQL Express to a child domain such as "second. If the SQL Server instance is on the same server that you install Backup Exec on, the service account for the instance must have full permissions to the destination folder where Backup Exec is installed. If you perform a remote or push-install, and you specify a domain, you must enter an existing Backup Exec service account. New accounts are not granted proper rights for domains.
If you are creating a local account, you can specify a new service account. When you install Backup Exec, or when you install tape device drivers from Backup Exec, a Microsoft message may appear that indicates one of the following:. The software that you are about to install does not contain a Microsoft digital signature.
Symantec recommends that you choose the response on the Microsoft message dialog box that allows the Symantec driver software to continue being installed.
To prevent this message from appearing, you can change the policy setting. However, if you change the policy setting to 'silently succeed', it can allow other driver software to be installed without any warning.
User-created folders that are in the Backup Exec installation folder or subfolders are deleted when you install Backup Exec If you want to keep the folders, copy them to another location before you install Backup Exec These files can safely be deleted using Windows Explorer. Microsoft Exchange Server 5. Exchange mailbox-level backup legacy mailbox support is not supported for Exchange Backup Exec agents and options are no longer supported on Itanium-based computers with this release of Backup Exec.
Continued use of the Itanium Remote Agent for Windows from prior versions is at the user's own risk. If agents and options that are already installed on Itanium-based computers are used, the Backup Exec's Intelligent Disaster Recovery option is no longer supported.
Note that support for these agents and options will be provided on a best-effort basis only. Active Directory Application Mode and System State components now appear in the Backup Selections list directly under the computer name that appears under All Resources.
They no longer are listed under Shadow Copy Components. As a result, Backup Exec 10d jobs that back up these components are not automatically migrated to new backup jobs when you upgrade to Backup Exec You must manually edit the selection lists that contain these components, delete the existing references to them, and then add them again as new selections. Backup Exec versions You could view these stored images with the Crystal Reports module that was installed with Backup Exec.
The ReportViewer control is included with the. NET framework versions 2. Backup Exec versions 11d and later do not support the Crystal Reports format. Any existing report that needs to be saved must be rendered into PDF or another general format and saved independently before you upgrade to version 11d or later.
The compatibility lists contain the latest information about supported and unsupported hardware and software and is updated regularly. Before installing or upgrading Backup Exec, review the current compatibility list to confirm the compatibility of your hardware and software.
You can find the current compatibility list on the Symantec Support Web site at:. If you don't find your hardware or software listed, or if you have questions about the information in the compatibility list, please contact Symantec Support.
During startup, Microsoft. If no Internet connection is available, this activity significantly delays Backup Exec startup. To avoid this delay, you can disable digital signature verification from the Windows Control Panel. See Microsoft documentation for more information. This procedure turns off verification for all. NET applications. Symantec Best Practice documents detail the best ways to use Backup Exec in production environments.
When you browse remote restore selections, you may receive an informational message that the Backup Exec Remote Agent must be installed. This message may appear even though the agent is installed. You can ignore this message. Click OK to safely continue. When protecting a server running Veritas Cluster Server 4. Backup Exec reserves port For instructions on how to configure Backup Exec to use a port other than , refer to the following TechNote:.
For Windows , this job status is because the wins. For Windows , this job status is because the winstmp. Data encryption is not supported when you duplicate backup sets that were created with versions of Backup Exec prior to 11d.
To ensure backward compatibility with previous Windows platforms, the operating systems create special junctions. These junctions redirect access from one directory to another. Backup Exec must be able to back up and restore these junctions but it does not need to traverse them to back up the computer. Backup Exec version 11d and later detects the new junctions but does not cross them, even if you select the backup option, Back up files and directories by following junction points.
Change references to old directories to reflect the new directory structure. Doing so helps ensure that your data is backed up correctly. If you upgrade from Backup Exec 11d build Any LiveUpdate information or warning alerts that were generated before you upgraded Backup Exec are retained until you manually clear them. You configure the License Assessment Tool's language in one of three ways:.
Use a -Lang switch and a base language name parameter to launch the application in the language you specify. You can use any of the following base language name parameters:. Use a -Lang switch without a base language name parameter to prompt a dialog box that lets you select a language for the application.
Use the License Assessment Tool executable without a language switch. The application uses the same language as the computer's operating system. You must have the proper system fonts installed on a computer for the selected language to display correctly in the Backup Exec License Assessment Tool.
The Namespace technologies provide a virtual file system view of grouped shared folders from distributed servers. The Replication technologies provide scheduled replication, bandwidth throttling, compression, and conflict resolution. The Microsoft DFS feature requires protection of configuration settings and file system data for which Backup Exec uses different data protection methods.
In addition, target shares on remote servers must also be protected by a System State Registry backup. For configurations that do not use Microsoft replication technologies, the shared data must be protected by performing a file system volume backup of the data on the target server.
For configurations that use Microsoft replication technologies, see the following sections:. For configurations that use DFSR, you can protect the replicated data by running a Shadow Copy Components Distributed File System Replication backup of the replicated data on any server that is hosting the replicated data.
For configurations that use FRS, you can protect the replicated data by running a file system volume backup of the replicated data on any server that is hosting the replicated data. When you run an off-host backup of the following versions of Veritas Storage Foundation for Windows VSFW that are installed on a bit computer, the error code V appears. To resolve this issue, update your Storage Foundation for Windows software using the following link:. Backup performance can be seriously degraded if you use LUN libraries attached to a Windows Server Instead of a backup rate of hundreds of MB per minute, you could experience a backup rate of 3 to 4 MB per minute.
To resolve this issue, set the AutoRun registry key associated with both the tape drive and the associated library to 0 using the following link:. You can find detailed information about Backup Exec's Microsoft Windows Server Certification status at the following link:.
If a function is run on a Media Server Group that contains cluster nodes and contains the virtual Backup Exec server, Backup Exec Utility has problems when it tries to modify the virtual Backup Exec server. The operation then changes the previous primary server to a secondary server of the new primary server.
0コメント