Backup Exec Error Connecting To The Remote Computer 24
But now: Microsoft Exchange 2010 database backup fails with V-79-57344-913 database was not found error. Windows Server 2008 To push-install Backup Exec to a computer that runs Windows Server 2008, you must enable certain items on the destination computer’s Windows Firewall Exceptions list. Solution Works - Nr. 2 s_hasslinger N/A Partner Accredited 08-02-2010 01:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall.
Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available
Domain account with full administrator rights. only those two (DC and ExcSrv2007) are still running with the old BE 12.5 agent RAWS, which one is the solution for this problem please ? 0 Kudos Reply Solution works Labels: 10.x and Earlier Agent for Microsoft Exchange Server Agents Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 10 Replies Hi, Check out the TN CraigV Join the community of 500,000 technology professionals and ask your questions.
- For IT career related questions, please visit /r/ITCareerQuestions Please check out our Frequently Asked Questions, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should
- We are a hosting company, so have multiple clients on different networks that require backing up.
- CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical
- You can then do like a GPO to apply any missed ports.
- Labels: 2010 Backup and Recovery Backup Exec Troubleshooting 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!
- No Yes How can we make this article more helpful?
- Add the User 'LOCAL SERVICE' to the Group or user names list and give Allow access for these permissions: Local Launch Remote Launch Local Activation Remote Activation Fig 7 Click
The first step is to acquire the necessary licen… Storage Software Windows Server 2008 VMware Disaster Recovery Configuring Storage Pools in Backup Exec 2012 Video by: Rodney To efficiently enable the for eg. 14,24,1603 ?? But Exec is very DenisFrolov Level 3 04-30-2013 05:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Instaled. Error Connecting To The Remote Registry Backup Exec Re-attempt the push installSystem account could be blocking the setup. If a push/local install of RAWS fails with the error 1603 still and is accompanied by the below event log
We are currently using BE2010 R3 with no issues. You may also refer to the English Version of this knowledge base article for up-to-date information. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec (BE) 2010 push install of the Backup Exec Remote Agent It is recommended that a complete backup of the registry and workstation be made prior tomaking any registry changes.Goto the following registry key: HKEY_CLASSES_ROOT\CLSID\ Locate the 'AppID' String Value key and
They are highly useful for migrations and disaster recovery. Error Connecting To The Remote Registry Backup Exec 2010 Create/Manage Case QUESTIONS? On German Server called: -Anpassen von Speicherkontingenten für einen Prozess -Ersetzen eines Tokens auf Prozessebene -> make a gpudate /force It Works fine since the changes, Thank You! 0 Kudos Reply No Yes Did this article save you the trouble of contacting technical support?
Backup Exec Cannot Connect To Remote Computer
Thank You! Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." Error Message Error connecting to the remote server. Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available I went with a manual install in the end and all currently appears well 0 LVL 29 Overall: Level 29 Storage Software 12 Message Active today Accepted Solution by:pgm5542013-01-23 FYI,Symantec The Backup Exec Server Could Not Connect To The Remote Computer A reboot may be needed. 0 Kudos Reply same problem here Symanticus Level 6 04-22-2010 07:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to
I tried instal with local administrator account and gave all sorts of rights, but to no avail. http://sovidi.com/backup-exec/backup-exec-error-connecting-to-the-remote-computer-14.php Would someone be able to assist? permalinkembedsavegive gold[–]Darth_NoahVMware Admin 0 points1 point2 points 2 years ago(0 children)Local installs allow the Windows Firewall to open up all the ports needed when the installation completes (cause its coming from inside the Create/Manage Case QUESTIONS? Backup Exec Cannot Connect To The Remote Computer Because A Trust Was Not Established
It is possible that updates have been made to the original version after this document was translated and published. Built around industry best-practice guidelines, the IT Cyber Security bundle consists of three in-depth courses. Click on Security button. have a peek here AndEvent ID 4672 for my "backup-user": SeCreateTokenPrivilege SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege 0 Kudos Reply I installedRAWS64(Local).
Right Click on the DCOM Object that matches and select 'Properties' and select the 'Security' tabFig 5 7. Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67 I've been asked to change this so that we push the agent out to it from another newer symantec install (backup exec 2010 r3) on an sbs2008 box. No Yes How can we make this article more helpful?
Reboot the remote server to apply changes. Learned this many,many years ago. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Solution Solution 1: Manually install the remote agent Copy the RAWS32/RAWS64 (from X:\Program Files\Symantec\Backup Exec\Agents) and the MSXML folders on the particular remote server where you want to install Remote Agent.On How To Install Backup Exec Remote Agent Manually Serves run with local system account.
I have installed the trial on a different server in the same backup network, but am having difficulty pushing out the Windows agent to any machines. Its DenisFrolov Level 3 04-29-2013 11:58 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content No, i have another id. My DB have size 50Gb 0 Kudos Reply ...check this CraigV Moderator Partner Trusted Advisor Accredited 04-30-2013 01:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Check This Out Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 20 Message Active 3 days ago Expert Comment by:Iamthecreator2013-01-23 Is there a number at the end of the
If I carry out the same task from our current BE2010 server (Windows Server 2003 R2), it works. Thank You! Check It Out Suggested Solutions Title # Comments Views Activity Mac Time Machine: Does my disk store password in Key Chain or have no password? 6 34 62d The disk signature VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer.
It is possible that updates have been made to the original version after this document was translated and published. Sorry, we couldn't post your feedback right now, please try again later.