Backup Exec 2012功能调试文档
- 格式:docx
- 大小:3.05 MB
- 文档页数:28
Symantec Backup Exec™ 2012 Licensing GuideWho should read this paperUse this guide to learn how to license Symantec Backup Exec™ 2012,Symantec Backup Exec™ 2012 V-Ray Edition, Symantec Backup Exec™2012 Small Business Edition, Symantec Backup Exec™ 3600 Appliance,and Symantec Backup Exec.cloud™. Symantec reserves the right toreview and/or update the existing version without previous notice.ContentSymantec Backup Exec™ portfolio overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Important Backup Exec product, agent, option, and licensing updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Backup Exec portfolio licensing overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Backup Exec.cloud licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Backup Exec 3600 Appliance licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Backup Exec 2012 Small Business Edition licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Backup Exec 2012 licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Backup Exec 2012 V-Ray Edition licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Backup Exec Cloud Disaster Recovery Option licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Backup Exec 2012 Agents and Options licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Backup Exec 2012 Agent licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Backup Exec 2012 Option licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Backup Exec 2012 Add-on licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Entitlements, upgrades, and migration paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Upgrade eligibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Upgrade mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Cross-grade availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Further information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Symantec Backup Exec™ portfolio overviewSymantec Backup Exec™ powered by patented V-Ray technology unifies physical and virtual backups, and includes integrated disaster recovery, data deduplication, and replication technology while offering a choice among on-premise,appliance, or cloud-based solutions.The new, modern, and innovative range of Backup Exec solutions are designed to adapt for any business, large or small, to easily protect increasing amounts of data, in either virtual, physical, or combined environments and rapidly recover complete virtual machines, systems, applications, databases, files/folders, and even granular objects in minutes—all from a single pass backup. With a sleek and streamlined administration console, Backup Exec makes it easier than ever to efficiently manage backup and recovery operations across your physical and virtual infrastructure.Important Backup Exec product, agent, option, and licensing updates1Backup Exec portfolio licensing overviewBackup Exec.cloud licensing2Backup Exec 3600 Appliance licensingBackup Exec 2012 Small Business Edition licensing3Backup Exec 2012 licensingBackup Exec 2012 V-Ray Edition licensing4Backup Exec Cloud Disaster Recovery Option licensingPlease note: The Backup Exec Cloud Disaster Recovery Option is not available in all regions. Please check with your local Symantec Account representative for regional availability and release dates.5Backup Exec 2012 Agents and Options licensingBackup Exec Agents and Options enhance and extend platform and feature support for Backup Exec 2012 Small Business Edition, Backup Exec 2012, Backup Exec 2012 V-Ray Edition, and Backup Exec 3600 Appliance environments. Whether you need to protect VMware, Hyper-V, or Windows environments, critical Microsoft applications, or non-Microsoft operating systems, Backup Exec has an expansive portfolio ofhigh powered agents and options to scale and grow your Backup Exec environment.Backup Exec 2012 Agent licensingBackup Exec 2012 Agent licensing6Backup Exec 2012 Option licensing7Please note:With the release of Backup Exec 2012, the following Backup Exec Agents, Options, and Suites have been discontinued:•NetWare® Servers Open File Option•Agent for DB2® on Windows Servers•Agent for SAP® Applications•Remote Agent for NetWare Systems•Backup Exec Infrastructure Manager 12.5•Continuous Protection Server•Backup Exec Deduplication Suite•Backup Exec Deduplication and Archiving Suite•Backup Exec Suite for VMware•Backup Exec Suite for Hyper-VFor details on support expiration dates, please visit:/SearchServer/rosetta_view/viewer.asp.Backup Exec 2012 Add-on licensingEntitlements, upgrades, and migration pathsIf you are an existing Backup Exec customer, you can directly upgrade previously installed Backup Exec 12.5, and 2010 versions to Backup Exec 2012.Depending on the status of your maintenance contract with Symantec, you may be entitled to upgrade to Backup Exec 2012 freeof charge.See the tables below to determine if you are entitled to this no-cost upgrade.Upgrade eligibility yUpgrade eligibilit8Upgrade mechanismsss-grade av v ailabilitailability yCross-grade aCroFurther information•Evaluating Backup Exec 2012 free for 60 days—Backup Exec 2012 will run in evaluation mode free for 60 days when no license key is entered during the installation.During this 60 day period all features and options are available for evaluation apart from the Symantec Desktop and Laptop Option, Backup Exec File System Archiving Option, Backup Exec Exchange Mailbox Archiving Option, and the Enterprise Server Option. To try Backup Exec 2012 free for 60 days, visit .•Backup Exec 2012 Compatibility Information—Visit /compatibility for hardware and software compatibility documentation.•Need help?For licensing support, please visit:https://.9About SymantecSymantec is a global leader in providing security, storage, and systems management solutions to help consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks at more points, more completely and efficiently, enabling confidence wherever information is used or stored. Headquartered in Mountain View, Calif., Symantec has operations in 40 countries. More information is available at .For specific country offices and contact numbers, please visit our website.Symantec World Headquarters350 Ellis St.Mountain View, CA 94043 USA+1 (650) 527 80001 (800) 721 3934Symantec helps organizations secure and manage theirinformation-driven world with data backup andrecovery software.Copyright © 2012 Symantec Corporation. All rightsreserved. Symantec, the Symantec Logo, and theCheckmark Logo are trademarks or registeredtrademarks of Symantec Corporation or its affiliates inthe U.S. and other countries. Other names may betrademarks of their respective owners.3/201221223660。
长春工业大学Symantec Backup Exec 2012 备份管理系统设计方案长春恒信信息技术开发有限公司2012年7月2日目录一、项目概述 (3)二、系统需求分析 (4)2.1、系统现状分析 (4)2.2、备份系统需求分析 (4)三、备份系统设计方案 (5)3.1、系统设计指引 (5)3.1.1、系统设计原则 (5)3.1.2、数据保护技术选择 (5)3.1.3、备份管理系统组成 (7)3.2、系统结构设计 (9)3.2.1、整体系统架构设计 (9)3.3、备份架构的功能设计 (10)3.3.1、基于磁盘的数据保护系统设计 (10)3.3.2、文件服务器的备份设计 (12)3.3.3、活动目录(AD)服务器的备份和恢复 (14)3.3.4、SQL服务器的备份和恢复系统设计 (15)3.3.5、Oracle服务器备份方式 (17)3.4、灾难恢复计划 (19)3.4.1、灾难恢复计划概述 (19)3.4.2、灾难恢复的好处 (20)3.4.3、灾难恢复策略规划 (20)3.4.4、系统快速灾难恢复解决方案 (21)四、设计方案总结 (23)4.1、备份管理方案总结 (23)4.2、客户收益 (25)五、售后服务承诺 (26)5.1、Backup Exec系统维护服务 (26)5.2、Backup Exec系统培训服务 (26)5.3、具体服务明细 (27)5.3.1、日常维护明细 (27)5.3.2、巡检服务明细 (27)5.3.3、紧急上门服务 (27)5.3.4、现场培训服务 (28)一、项目概述随着企业信息化建设的不断完善,人们对信息的依赖性也就越来越强,目前企业数据都向着集中存储、集中管理方向发展,而大集中带来优化管理的同时也意味着数据的风险在集中,又让我们无法回避另一个话题——灾难备份。
追述2001年震惊世界的“9.11”事件,随着纽约世贸大厦的轰然倒塌,使1000多家公司蒙受毁灭性打击,造成的直接经济损失超过1000亿美元。
Symantec Backup exec 2012备份与恢复实施一、B E2012备份软件安装将备份软件安装介质放入光盘驱动器后,系统会自动运行安装程序;若系统并未自动运行,请打开光盘内容,双击Browser即可启动安装。
在弹出的安装界面内,选择“预安装”以对系统环境进行必要的检查。
选择需要进行环境检查的产品下一步,根据实际需要进行本地或远程环境检查环境检查结束后会弹出报告,浏览并确认环境就绪后可开始安装点击选择需要安装的部件,备份服务器选择Backup Exec,备份客户端选择Backup Exec Agent for Windows(这里环境为windows)选择同意授权后点击下一步继续根据实际需要选择典型安装或自定义安装后点击下一步,本系统选择自定义安装选择安装本地Backup Exec后点击下一步安装进程同样会进行安装环境监测,确认即可这是添加License的页面,为保护License信息,以下为未输入License状态由所输入License系统会自动勾选许可的选件选择安装语言选择安装路径输入具有administrators用户组权限的系统(域)用户名和密码,若该计算机并非域成员,则只需在域一栏下输入计算机主机名选择SQL Server实例安装路径,该实例由Backup Exec软件管理选择推荐设置,点击下一步继续确认安装摘要后点击安装开始安装进程安装过程备份软件服务器安装过程结束二、B E2012备份LINUX文件在备份服务器上添加linux备份客户机下一步,勾选允许Backup Exec与服务器建立信任添加linux客户端添加账户,用于建立信息关系,为linux系统root账户和密码完成即开始可对linux客户端设置备份作业,备份到磁带选择编辑设置备份作业,选择备份的文件选择确定,完成备份作业设置运行备份全备份作业完成备份三、B E2012恢复LINUX文件选择还原做文件的恢复选择还原的数据类型还原文件或者文件夹备份选择已备份的文件还原到其他位置下一步,默认即可下一步,默认下一步,完成设置还原作业运行验证还原结果,还原成功。
176[1].BackupExec12最佳实践:MicrosoftSQL数据库服务器Backup Exec 12 最佳实践:Microsoft SQL数据库服务器Best practices for Backup Exec 12 Agent for Microsoft SQL ServerDocument ID: 298297/doc/ef1b8f8d284ac850ac02420d.html /docs/298297 E-Mail this document to a colleagueBest practices for Backup Exec 12 Agent for Microsoft SQL ServerDetails:Best practices for Backup Exec 12 Agent for Microsoft SQL ServerBest practices include tips and recommendations to help you use Backup Exec 12 Agent for Microsoft SQL Server (SQL Agent) effectively. For more information about the SQL Agent, see the Backup Exec for Windows Servers Administrator’s Guide.The following best practices help you use the SQL Agent effectively:Back up the entire Microsoft SQL Server.Include the following in the backup job:o Full SQL database backupso Windows System Stateo System drive backups of the hard drive or drives where Microsoft SQL resideso System drive backups of the hard drive or drives where the Microsoft SQL databases resideExclude all database files from an anti-virus scan.Run a consistency check either before or after a SQL backup and after a SQL restore. If you back up a database, transaction log, or file group that contains errors, these errors still existwhen the backup is restored. In some cases, these errors can prevent a successful restore.Backup Exec lets you check the logical and physical consistency of the data before and after a backup. SQL reports any consistency check failures in the Backup Exec job log.Symantec recommends that you run regular database consistency checks to verify the integrity of the database.Use database, differential, and log backups to maximize your backup window. Combine these backup methods with backup strategies that address the following issues:o How much data loss can you accept if a failure happens between the time of the last backup and the time the loss occurred?o How many transactions are processed each day?o What are your users' expectations when a recovery is required? For example, do they expect a full recovery to the point at the time when the data loss occurred?o Use only the SQL Agent to perform SQL full, differential, and log backups. If you use a third-party application, Backup Exec fails the differential and log backup jobs until youmake a new full backup with the SQL Agent.The following best practices help you with security and database access with the SQL Agent:Ensure that the Windows user account that you use to back up the SQL instances has System Administrator privileges. Ensure that Backup Exec has rights to the following registry keys:o HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Servero HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLDo not apply the credentials that you use to make SQL backup and restore selections to an actual SQL instance. The credentials that you use to make SQL backup and restore selections must be applied to the Windows computer where SQL is installed.Note:If you use SQL-generated credentials, you must apply those credentials at the SQL instancelevel.Products Applied:Backup Exec for Windows Servers 12.0Last Updated: February 19 2008 10:37 PM GMTExpires on: 02-18-2009Subscribe to receive critical updates about this documentSubjects:Backup Exec for Windows ServersInformation Development: Best PracticesWindows 2000Information Development: Best PracticesWindows NT Small Business ServerInformation Development: Best PracticesWindows Server 2003Information Development: Best PracticesWindows Server 2008Information Development: Best PracticesWindows XPInformation Development: Best PracticesLanguages:English (US)Operating Systems:Windows 2000Professional, ServerWindows NT Small Business Server2000Windows XPPro 5.1, Pro 5.1 64 bit SP1, Pro 5.1 64 bit SP2, Pro 5.1 64-bit, Pro 5.1 SP1, Pro 5.1 SP2Windows Server 2003DataCenter, DataCenter (IA64), DataCenter (x64), DataCenter SP1, DataCenter SP1(IA64), DataCenter SP1(x64), DataCenter SP2, Datacenter SP2(x64), Enterprise (IA64), Enterprise (x64), EnterpriseSP1(IA64), Enterprise SP1(x64), Enterprise SP2, Enterprise SP2(x64), Enterprise Server, Enterprise ServerSP1, R2, Standard Server, Standard Server SP1, Standard Server SP1 (x64), Standard Server SP2, Standard Server SP2 (x64), Standard Server(x64), Storage Server, Storage Server SP1, Storage Server SP2, Web Server, Web Server SP1, Web Server SP2Windows Server 2008DataCenter (x64-64bit), DataCenter (x86-32bit), Enterprise (x64-64bit), Enterprise (x86-32bit), Itanium, Standard (x64-64bit), Standard (x86-32bit), Web Server (x64-64bit), Web Server (x86-32bit)Symantec World Headquarters:20330 Stevens Creek Blvd. Cupertino, CA 95014World Wide Web: /doc/ef1b8f8d284ac850ac02420d.html ,Tech Support Web: /doc/ef1b8f8d284ac850ac02420d.html ,E-Mail Support: /doc/ef1b8f8d284ac850ac02420d.html /email_forms,FTP: ftp:///doc/ef1b8f8d284ac850ac02420d.html or/doc/ef1b8f8d284ac850ac02420d.htmlTHE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SOTHE FOREGOING LIMITATION MAY NOT APPLY.。
一般设置步骤
1、将所需驱动分别装好!
2、将硬件布置实施完毕。
3、如果以上都没问题,那在backup_exec中就可以认到存储介质。
4、在media set中划分多个组(相当于pool)
5、先scan,将所有的磁带标签条码,都读出。
6、Catalog media
7、再inventory,将所有磁带所在的槽位,容量信息等详细列出来。
8、将这些磁带做一下label media,做上印记标签,此时磁带便可以使用。
故障分析
备份某些文件时,备了一些,便结束job,即失败!比如备份domino。
每次备份到某一文件时,便会停止。
尔后连续做四次都是会出现同样的错误报告。
后来分析得知,是因为/windows/servicepackfiles/i386/pscript.ntf是打印机驱动所需要的文件,每次备份到此文件,便会很容易出错。
后来将这个文件移出备份列时,再测试时,当即成功!。
Backup Exec 12.5 for Oracle RAC安装-配置-应用一.Oracle设置(注:如无特别说明,以下操作分别在RAC所有节点执行)由于BE备份Oracle时, 需要Oracle处于归档模式1. 配置Oracle归档模式SQL> alter system set log_archive_dest_1='LOCATION=/u01/app/oralog' scope=spfile; System altered.SQL> ! env | grep ORACLE_SIDORACLE_SID=orclSQL> create pfile='/u01/app/orabak/pfile orcl.ora' from spfile;File created.SQL> shutdown immediate;Database closed.Database dismounted.ORACLE instance shut down.SQL> startup mount;ORACLE instance started.Total System Global Area 167772160 bytesFixed Size 1218316 bytesVariable Size 79694068 bytesDatabase Buffers 83886080 bytesRedo Buffers 2973696 bytesDatabase mounted.SQL> alter database archivelog;Database altered.SQL> alter database open;Database altered.SQL> archive log list;Database log mode Archive ModeAutomatic archival EnabledArchive destination /u01/app/oralogOldest online log sequence 26Next log sequence to archive 28Current log sequence 28二.安装RALUS注意: 在root用户下执行建立解压目录[root@popgo-tsdb ~]#mkdir /opt/ralus解压到/opt/ralus[root@popgo-tsdb ~]# tar –zxvf/mnt/hgfs/share/BackupExec/BEWS_12.5.2213_LINUX-UNIX-MAC-SAP_AGENTS.tar.gz -C /opt/ralus安装RALUS[root@popgo-tsdb ~]# /opt/ralus/installralusERROR: VXIF_HOME is invalid. It must point to the root of VxIF. Exiting ...[root@popgo-tsdb ~]# cd /opt/ralus[root@popgo-tsdb ralus]# ./installralus设置安装RALUS的主机, 即为popgo-tsdbSymantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers 12.5.2213Enter the system names separated by spaces on which to install RALUS: (popgo-tsdb)Checking system communication:Checking OS version on popgo-tsdb ................ Linux 2.6.9-55.ELsmpChecking system support for popgo-tsdb ... Linux 2.6.9-55.ELsmp supported by RALUSInitial system check completed successfully.Press [Return] to continue:备份的通信端口检查, 一定要先确认端口是否有被占用Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers 12.5.2213Checking system installation requirements:Checking RALUS installation requirements on Linux target systems: popgo-tsdbChecking RALUS installation requirements on popgo-tsdb:Checking file system space ................ required space is availableInstallation requirements checks completed successfully.Press [Return] to continue:Checking for prerequistes ........................................ DoneChecking for Port 10000 .......................................... Done设置介质服务器, 即为BE12.5主机名和IP, 此步一定要设置正确Remote Agent Media Server ConfigurationTo display the Remote Agent as a selection in a media server's backup selection tree, and to be able to specify a local network for use between the Remote Agent and a media server, enter the names or IP addresses of the media servers that you want the Remote Agent to communicate with.An IP Address: XXX.XXX.XXX.XXXA Host Name: COMPUTERNAMEEnter a directory host:192.168.40.13Do you want to add another name or address for this agent? [y, n] (n)n再次确认, 如果有错可以直接改. 最好把BE主机名/IP写入/etc/hostsRemote Agent Media Server ConfigurationHostnames and/or IP addresses verification:Address: 192.168.40.13Is this information correct? [y, n] (y)y设置beoper组及组内用户, 一定把oracle用户加入此组Remote Agent User Group SetupTo perform backups, you must have a 'beoper' user group. This user group can be created only if you are not using NIS server. Your system will be scanned to detect a NIS server, group and membership.Press [Return] to continue:Checking if system uses NIS server: ............................... NoThe installer will now check your system for the 'beoper' user group and root membership.Press [Return] to continue:Checking for 'beoper' user group: ........................... Not FoundChecking for 'root' user membership in 'beoper' user group: ... Not FoundYou can create 'beoper' user group manually or you can choose to have it created automatically.Do you want installer to create 'beoper' user group? [y, n] (y)yDo you want to use specific group ID when creating 'beoper' user group? [y, n] (n) Creating group 'beoper': ......................................... DoneDo you want to add the 'root' user to 'beoper' user group? [y, n] (y)yAdding 'root' user to 'beoper' user group: ...................... DonePress [Return] to continue:安装RALUS所需的包Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers 12.5.2213Checking Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers on popgo-tsdb:Checking VRTSralus package .............................. not installedPress [Return] to continue:Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers 12.5.2213Installing Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers on popgo-tsdb:Installing VRTSralus 12.5.2213 on popgo-tsdb ........ done 1 of 1 stepsSymantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers installation completed successfully.Press [Return] to continue:Copying new initialization scripts ............................... DoneCreating RALUS linkedname in rc2.d ............................... DoneCreating RALUS linkedname in rc3.d ............................... DoneCreating RALUS linkedname in rc5.d ............................... DoneUpdating RALUS files for beoper .................................. Done安装成功, 并确认RALUS配置参数文件/etc/VRTSralus/ralus.cfg是否生成Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers 12.5.2213 Configuring Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers:Creating configuration files ..................................... DoneSymantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers configured successfully.Press [Return] to continue:The response file is saved at:/var/tmp/vxif/installralus1117215008/installralus1117215008.responseThe installralus log is saved at:/var/tmp/vxif/installralus1117215008/installralus.log[root@popgo-tsdb ralus]# id oracleuid=500(oracle) gid=500(oinstall) groups=500(oinstall),501(dba)使用以下命令将用户oracle添加到beoper组:[root@popgo-tsdb ralus]# usermod -G dba,beoper oracle在每一个节点上复制/etc/oratab到/etc/VRTSralus/beoratab,并使用vi对/etc/VRTSralus/beoratab进行编辑。
Backup Exec备份运维手册目录1.用户登录和服务启动 (3)1.1用户登录和创建用户 (3)1.2启动服务 (3)2.设备(存储) (4)2.1带库(带机) (4)2.2磁盘 (6)3.介质(策略) (7)3.1介质集 (7)3.2关于介质的移动 (8)4.选项(事前准备) (9)4.1预选项 (9)4.2关于将作业报告发送邮件 (11)5.备份和恢复 (12)5.1.1文件备份(Windows) (12)5.1.2文件恢复(Windows) (18)5.1.3文件备份(Linux & Unix) (19)5.1.4文件恢复(Linux & Unix) (20)5.1.3卸载客户端(Linux & Unix) (21)5.2.1 MSSQL备份 (22)5.2.2 MSSQL恢复 (23)5.3.1 Exchange备份 (23)5.3.2 Exchange恢复 (25)5.4.1 Oracle备份(Windows) (26)5.4.2 Oracle备份(Linux) (28)5.4.3 Oracle恢复 (31)5.5.1 Active Directory备份 (33)5.5.2 Active Directory恢复 (34)6.台式机和笔记本文件保护(Desktop and Laptop Option) (34)6.2 DLO安装注意事项与登录 (34)6.2 DLO配置与备份 (35)6.3 DLO恢复 (45)7.管理性选件 (47)7.1中央管理服务选件Central Admin Server Option (CASO) (47)7.1.1 CASO的安装 (47)7.1.2中央管理服务器的配置 (49)7.1.3 CASO的使用 (50)7.2共享存储设备选件SAN Shared Storage Option(SSO) (51)7.2.1 SSO的安装 (51)7.1.2共享设备服务器的配置 (53)7.1.3共享设备服务器的使用 (55)8.问题集 (56)1.用户登录和服务启动1.1用户登录和创建用户在菜单栏选择“网络”→“登录账户”→“新建”或者“编辑”,弹出“登录凭证”对话框。
文件名称: Backup Exec 2012 管理员手册目录一、系统需求 (1)1.1软硬件需求 (1)1.2安装前检查 (2)二、开始安装BACKUP EXEC (3)2.1以自定义方式安装 B ACKUP E XEC (3)三、管理配置BACKUP EXEC (11)3.1配置存储 (11)3.2B ACKUP E XEC 代理安装 (1)83.2.1Linux代理安装 (25)3.2.2配置Oracle服务器用于备份Oracle数据库 (29)3.3建立备份作业 (3)93.3.1AD备份 (41)3.3.2AD恢复 (48)3.3.3Windows 文件服务器备份 (55)3.3.4Windows文件服务器恢复 (57)四、备份还原OS (82)4.1备份 OS (82)4.2异机还原 OS (85)1.1软硬件需求1.操作系统要求:●Windows Server 2003 系列●Windows Server 2008\2008 R2 系列如果需要备份Exchange 2010,则必须使用64 位系统,建议使用Windows Server 2008 64bit 或者Windows Server 2008 R2。
如果需要使用重复数据删除模块,则必须使用64 位系统,且内存至少6GB,且备份数据每增加1TB,内存增加1.5GB。
不能在运行 Windows Server 2008 的 Windows Server Core 安装选项的计算机上安装 Backup Exec 服务器。
在 Server Core 计算机上只能安装 Backup Exec Agent for Windows。
不能在以“只读域控制器”(RODC) 角色配臵的 Windows Server 2008 计算机上安装 SQLExpress 或 SQL Server 2005。
“只读域控制器”角色不允许您使用 SQL Express 和 SQL Server 2005 需要的本地帐户。
您在存储数据时可能会遇到的典型问题:1)业务数据都是非常重要的,一旦发生了意外,重要数据丢失,如何在最快时间内恢复?2)SQL 、Exchange、Active Directory ,还有很多应用都自带备份功能,但无法实现统一的管理,需要编写脚本文件,同时无法备份操作系统。
如果应用服务器较多,通过自带的备份工具进行备份是一件非常繁琐的工作……3)除了业务数据的快速恢复, 我们的操作系统是否也能恢复?4)我们采用了VMware,Microsoft Hyper-V, 备份时如果每个虚机装Agent,性能是否会受到影响?可以进行颗粒级的数据恢复吗?例如Exchange中的某个邮件?5)我们公司的邮件服务器是Exchange, 每次备份的时间很长,不得已就给员工设置限额,以免数据量太大。
但是性能又不好,而且备份还困难……6)我单位既有物理环境,又有虚拟环境,让独立的团队分别负责虚拟和物理环境,在备份和恢复上缺乏信心,对可靠性也不是十分满意……7)有太多的历史邮件,需要长期保留,但对存储空间的消耗又过大?Symantec Backup Exec概述Symantec Backup Exec™ 2012 是业界领先的Windows数据保护解决方案,是一套为虚拟环境和物理环境提供保护的集成产品,实现了备份和灾难恢复的简化,并可以恢复任意规模的数据或系统,从单独的项目到完整的服务器,无所不包。
借助于强大的 Symantec™ V-Ray 技术,通过无以伦比的恢复功能减少业务停机,实现了完整服务器、关键 Microsoft 应用程序以及 VMware 或 Microsoft Hyper-V 访客虚拟机的恢复。
通过独立于硬件的裸机灾难恢复集成功能、虚拟环境中的“无硬件灾难恢复”、应用程序恢复以及高效全面地恢复个人电子邮件、文件和文件夹,满足您的恢复点目标和恢复时间目标要求。
同时,该产品还具备重复数据删除和归档功能,能够减少存储成本并提高备份速度。
Backup Exec 2012功能调试文档
一.远程安装Backup Exec 2012
实验环境:一台PC(IP:192.168.1.11),一台VMware(IP:192.168.118.128),网络模式NAT 实验目的:从物理机启动BE2012的安装程序,远程安装到VM
运行Browser.exe
初次安装建议点击“预安装”—“Backup Exec”
提示欢迎界面下一步继续
检查本地或远程计算机环境此处是远程所以选择“远程环境检查”
添加远程计算机并输入凭据
输入序列号,这里是测试环境,所以直接下一步,试用版本60天
勾选服务器端的Agent(代理)
输入密码“下一步”工作组环境则填写计算机名
使用本地Backup Exec SQL Express
测试过程没有磁带设备,此处选择“不使用Symantec 设备驱动程序”
已经创建好用于安装的远程计算机的列表,下一步
输入本地X86安装介质,我的安装文件在【D:\ 】所以路径选择OK后,让它自己去D盘找
点击“安装”耐心等待远程安装完毕
完成远程安装
现在,来验证一下是否已经成功完成了远程安装,转到虚拟机上查看
运行Backup exec 2012并且输入服务器相应凭据后点击连接
提示正在加载数据
加载完数据之后自动进入主页。
OK 这样的话,远程安装的检验全部完成,现在就可以使用了。
二.Backup Exec 2012策略配置
备份D盘至网络磁盘,目标URL:\\192.168.1.30\beshare
备份完成正在检验备份数据
提示完全备份全部完成
为了验证此备份数据可以正常实用,我们现在来检测一下
用SDR测试是不是可以将D盘的数据还原到以前的样子,见下图:
这是已经备份的数据:
现在将这些数据全部删除,用来测试刚才的备份是否可以正常恢复数据点击“还原”
选择想要恢复的目标项下一步
设置将恢复数据恢复至何处
选择维护数据的完整性、安全性
列出恢复摘要
还原正在运行
显示恢复结果
查看D盘中的数据是否恢复成功
恢复成功 ok .
三.Backup Exec 2012 SDR功能测试
手动制作Simplified Disaster Recovery(SDR)引导光盘及如何使用Backup Exec 2012 进行系统灾难恢复
灾难备份过程在此不再赘述,注意:灾备的时候记得将系统盘和系统状态同时选中,灾备完成后会有蓝色警报提示,如下图:
下面我们讨论一下使用BE2012如何做系统灾难恢复
挂载恢复介质,插入将计算机重启至U盘启动
选择语言
正在加载文件
Windows正在启动
接受许可协议
如下图看到的是SDR界面
先来配置网络,保持网络畅通
根据设置,PING一下远程计算机网络是否连通
映射网络驱动器—输入凭据—提示“已经成功映射网络驱动器”
然后点击“恢复”按钮,转入“恢复磁盘主页”点击“恢复此计算机”
问:备份数据放到哪里了?根据情况选择对应选项此处数据是在另外一台计算机上放置所以我选择第二项
选择使用哪个备份集的时间点来恢复计算机
选择浏览备份存储的路径
下一步,继续
列出恢复摘要,点击“恢复”继续
恢复向导正在还原数据等待完成之后提示“灾难恢复过程已经完成”
这样,BE2012的灾难恢复就完成了。
你可以重启计算机试试!。