Install Backup Exec Remote Console Linux' title='Install Backup Exec Remote Console Linux' />Five common Backup Exec errors and how to resolve them.Symantec Backup Exec has been around in one form or another since the early 1.Even so, errors do occur.This tip discusses five of the most common Backup Exec errors and how to resolve them.By submitting your personal information, you agree that Tech.DBA Linux.Installing Oracle RAC 1f0g Release 2 on Linux x86.John Smiley.Learn the basics of installing Oracle RAC 10g Release 2 on Red Hat.Target and its partners may contact you regarding relevant content, products and special offers.You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.Backup Exec Error 1.The dependency group failed to start.This is probably the most common of all the Backup Exec error codes.It occurs when one or more Backup Exec services will not start.You can pinpoint the problem service by opening the Service Control Manager and checking to see which service failed to start.Download Bach Cello Suites Sheet Music there.BEoption.jpg' alt='Install Backup Exec Remote Console Linux' title='Install Backup Exec Remote Console Linux' />The following services need to be running SQL BkupexecBE Remote Agent.BE Device and Media.BE Server Service.BE Job Engine Service.BE Agent Browser.Oftentimes, you can force a service to start by right clicking on it and choosing the Start command from the shortcut menu.If that doesnt work, check the Application and System logs in the Event Viewer.Additional services may be required depending on how Backup Exec was installed.Oftentimes, you can force a service to start by right clicking on it and choosing the Start command from the shortcut menu.If that doesnt work, check the Application and System logs in the Event Viewer.The log entries should give you a hint as to the cause of the problem.In most of the cases I have seen, the problem is connected to a permissions issue related to the account being used to run the service.Backup Exec Error 1.Fatal error during installation.Error 1. . Backup Exec installation process rather than the backup process.You may see this error reported as Backup Exec agent install failed with error code 1.Backup Exec remote agent failed 1.This is one of the Backup Exec errors that occurs because another application on the system is sharing one of the following DLL files Eportmodeller.Schedu.Schedngrur.This error can usually be corrected by making a modification to the Windows Registry.Keep in mind that editing the Registry is dangerous a mistake can cripple Windows andor your applications.You should therefore make a full system backup before attempting a registry modification.After backing up the system, open the Registry Editor and navigate through the registry tree to HKEYCLASSESROOTType.Lib.Right click on the Type.Lib container and choose the Permissions command from the resulting shortcut menu.Give the Administrators group and SYSTEM Full Control.This should correct the problem.If not, you may have to manually associate the DLL file with Backup Exec.The instructions for doing so are beyond the scope of this article, but can be found here.Backup Exec Error E0.FED1 A failure occurred querying the writer status.This error message is related to the VSS writer for a particular application.Specifically, one of the VSS writers used to back up an application running on the server reported a status of failed, which caused Backup Exec to produce error E0.FED1.To troubleshoot this error, enter the command VSSADMIN LIST WRITERS in a Command Prompt window.Windows will display a list of each VSS writer and note if it is in an error state.You can usually clear a VSS writer error by rebooting the machine.However, VSS writer errors are tied to applications or the operating system, rather than to Backup Exec.If a reboot does not clear the error, you will have to troubleshoot the VSS writer itself and the underlying application rather than Backup Exec.The VSSADMIN command can be used to determine which VSS writer is causing your problem.Backup Exec Error 1.The service did not respond to the Start or Control Request in a timely fashion.This is one of the Backup Exec errors that can be caused by a variety of conditions.In some cases, it can be related to a problem with the Microsoft.NET Framework.The easiest way to correct this error is to remove and then reinstall the.NET Framework.The exact method to remove and reinstall the.NET Framework will vary depending on the operating system used.In Windows Server 2.R2, you can use the Server Manager to remove and reinstall the.NET Framework.However, other applications often depend on the.NET Framework and removing the framework can cause those applications to break.It is a good idea to initially check for updates to the.NET Framework.Applying an update often has the same effect as reinstalling the.NET Framework, but without the potential for breaking other applications.Not all occurrences of Symantec Backup Exec error 1.NET framework.Error 1.Backup Exec Management Services or a situation in which Backup Exec Services do not start.You may for example, see an error message stating Backup Exec Management Services could not be started.Backup Exec database is offline, turn it on and then restart the Backup Exec Services.Correcting this error can sometimes be as simple as entering Services.Run prompt and then checking to see if the SQL BKUPEXEC service is running.If the service is not running, you may be able to manually start the service by right clicking on it and selecting the Start command from the shortcut menu.Sometimes Error 1.Backup Exec Services from starting.You can check the permissions by entering Services.Run prompt.This causes Windows to launch the Service Control Manager, which can be used to view the properties for the various services.Any Backup Exec Services should be configured to start under the Local System Account.After making any changes, it is a good idea to reboot the server.You should also launch the Backup Exec Console and click on Tools Backup Exec Services Service Credentials Change Service Account Information to ensure Backup Exec is configured to use an account that has been granted Domain Admin permissions the actual location of this option may vary from one version of Backup Exec to the next.Again, restart the services after making any changes.Backup Exec Error E0.EC Error readingwriting data fromto the media.This is one of the Backup Exec errors that can be somewhat difficult to troubleshoot, as it corresponds to a read or write failure with the backup media.In many cases, the error is accompanied by a message indicating the tape drive needs to be cleaned.However, cleaning the tape drive rarely corrects the problem.You should also try a new tape, in case the current tape is defective.If replacing the tape doesnt work, the problem is most likely related to device drivers or the tape drive itself.I recommend downloading and installing the latest device drivers for your tape drive.This includes any available firmware updates.If you still have trouble after the device driver update, run a backup from Windows Server Backup.This will help you to determine whether or not a hardware problem exists.Installing Oracle RAC 1.Linux x.DBA Linux Installing Oracle RAC 1f.Release 2 on Linux x.John Smiley.Learn the basics of installing Oracle RAC 1.Release 2 on Red Hat Enterprise Linux or Novell SUSE Enterprise Linux, from the bare metal up for evaluation purposes only Contents.Overview.Background.Part I Install Linux.Part II Configure Linux for Oracle.Part III Prepare the Shared Disks.Part IV Install Oracle RAC Software.Conclusion.Overview.This guide provides a walkthrough of installing an Oracle Database 1.Release 2 RAC database on commodity hardware for the purpose of evaluation.If you are new to Linux andor Oracle, this guide is for you.It starts with the basics and walks you through an installation of Oracle Database 1.Release 2 RAC from the bare metal up.This guide will take the approach of offering the easiest paths, with the fewest number of steps, for accomplishing a task.This approach often means making configuration choices that would be inappropriate for anything other than an evaluation.For that reason, this guide is not appropriate for building production quality environments, nor does it reflect best practices.The three Linux distributions certified for Oracle 1.Release 2 RAC are Red Hat Enterprise Linux 4 RHEL4Red Hat Enterprise Linux 3 RHEL3Novell SUSE Linux Enterprise Server 9.We will cover both of the Linux 2.RHEL4 and SLES9.RHEL3 is not covered here.This guide is divided into four parts Part I covers the installation of the Linux operating system, Part II covers configuring Linux for Oracle, Part III discusses the essentials of partitioning shared disk, and Part IV covers installation of the Oracle software.A Release 1 version of this guide is also available.Background.The illustration below shows the major components of an Oracle RAC 1.Release 2 configuration.Nodes in the cluster are typically separate servers hosts.Hardware.At the hardware level, each node in a RAC cluster shares three things Access to shared disk storage.Connection to a private network.Access to a public network.Shared Disk Storage.Oracle RAC relies on a shared disk architecture.The database files, online redo logs, and control files for the database must be accessible to each node in the cluster.The shared disks also store the Oracle Cluster Registry and Voting Disk discussed later.There are a variety of ways to configure shared storage including direct attached disks typically SCSI over copper or fiber, Storage Area Networks SAN, and Network Attached Storage NAS.Private Network.Each cluster node is connected to all other nodes via a private high speed network, also known as the cluster interconnect or high speed interconnect HSI.This network is used by Oracles Cache Fusion technology to effectively combine the physical memory RAM in each host into a single cache.Oracle Cache Fusion allows data stored in the cache of one Oracle instance to be accessed by any other instance by transferring it across the private network.It also preserves data integrity and cache coherency by transmitting locking and other synchronization information across cluster nodes.The private network is typically built with Gigabit Ethernet, but for high volume environments, many vendors offer proprietary low latency, high bandwidth solutions specifically designed for Oracle RAC.Linux also offers a means of bonding multiple physical NICs into a single virtual NIC not covered here to provide increased bandwidth and availability.Public Network.To maintain high availability, each cluster node is assigned a virtual IP address VIP.In the event of node failure, the failed nodes IP address can be reassigned to a surviving node to allow applications to continue accessing the database through the same IP address.Configuring the Cluster Hardware.There are many different ways to configure the hardware for an Oracle RAC cluster.Our configuration here uses two servers with two CPUs, 1.GB RAM, two Gigabit Ethernet NICs, a dual channel SCSI host bus adapter HBA, and eight SCSI disks connected via copper to each host four disks per channel.The disks were configured as Just a Bunch Of Disks JBODthat is, with no hardware RAID controller.Software.At the software level, each node in a RAC cluster needs An operating system.Oracle Clusterware.Oracle RAC software.An Oracle Automatic Storage Management ASM instance optional.Operating System.Oracle RAC is supported on many different operating systems.This guide focuses on Linux.The operating system must be properly configured for the OS including installing the necessary software packages, setting kernel parameters, configuring the network, establishing an account with the proper security, configuring disk devices, and creating directory structures.All these tasks are described in this guide.Oracle Cluster Ready Services becomes Oracle Clusterware.Oracle RAC 1.Release 1 introduced Oracle Cluster Ready Services CRS, a platform independent set of system services for cluster environments.In Release 2, Oracle has renamed this product to Oracle Clusterware.Clusterware maintains two files the Oracle Cluster Registry OCR and the Voting Disk.The OCR and the Voting Disk must reside on shared disks as either raw partitions or files in a cluster filesystem.This guide describes creating the OCR and Voting Disks using a cluster filesystem OCFS2 and walks through the CRS installation.Oracle RAC Software.Oracle RAC 1.Release 2 software is the heart of the RAC database and must be installed on each cluster node.Fortunately, the Oracle Universal Installer OUI does most of the work of installing the RAC software on each node.You only have to install RAC on one nodeOUI does the rest.Oracle Automatic Storage Management ASMASM is a new feature in Oracle Database 1.RAID in a platform independent manner.Oracle ASM can stripe and mirror your disks, allow disks to be added or removed while the database is under load, and automatically balance IO to remove hot spots.It also supports direct and asynchronous IO and implements the Oracle Data Manager API simplified IO system call interface introduced in Oracle.Oracle ASM is not a general purpose filesystem and can be used only for Oracle data files, redo logs, control files, and the RMAN Flash Recovery Area.Files in ASM can be created and named automatically by the database by use of the Oracle Managed Files feature or manually by the DBA.Because the files stored in ASM are not accessible to the operating system, the only way to perform backup and recovery operations on databases that use ASM files is through Recovery Manager RMAN.ASM is implemented as a separate Oracle instance that must be up if other databases are to be able to access it.Memory requirements for ASM are light only 6.MB for most systems.In Oracle RAC environments, an ASM instance must be running on each cluster node.Part I Installing Linux.Install and Configure Linux as described in the first guide in this series.You will need three IP addresses for each server one for the private network, one for the public network, and one for the virtual IP address.Use the operating systems network configuration tools to assign the private and public network addresses.Do not assign the virtual IP address using the operating systems network configuration tools this will be done by the Oracle Virtual IP Configuration Assistant VIPCA during Oracle RAC software installation.Red Hat Enterprise Linux 4 RHEL4Required Kernel 2.EL or higher.Verify kernel version.Other required package versions or higher.EL4.EL4. gcc c 3. EL4.EL4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2018
Categories |