liulei_it

已更新

11 years ago

已解决!

前往解决方案
L

liulei_it

2 Intern

•

3209 帖子

0

3521

August 24th, 2015 01:00

有在MSSQL的always on模式下安装networker的Guide么?

有在MSSQL的always on模式下安装networker的Guide么?

我在MSSQL的always on中active和standby服务器都安装了networker和for MSSQL 的模块,添加客户端都很成功但是在执行备份的时候出错。

  • Fenglin1

    6 Operator

    •

    2074 帖子

    2621

    0

    已发布 August 24th, 2015 01:00

    这篇KB里面的方法试试看

    https://support.emc.com/kb/199614

  • liulei_it

    2 Intern

    •

    3209 帖子

    2621

    0

    已发布 August 24th, 2015 01:00

    谢谢,但是文档里说

    o perform backups of secondary replicas by using NMM 3.0 SP1, set the Readable Secondary option of SQL Server 2012 AlwaysOn configuration to “Yes.”

    我目前的配置是 两个active server一个passive server的always on且这个Passive server只是用于fail over不用于read only。难道一定要打开passive server的read only么?

  • liulei_it

    2 Intern

    •

    3209 帖子

    2621

    0

    已发布 August 24th, 2015 01:00

    错误如下没办法了都测试了就是不能使用模块备份

    43708:(pid 6184):Start time: Mon Aug 24 16:17:44 2015

    43621:(pid 6184):Computer Name: LCHDMESPNB41     User Name: SYSTEM

    97546:(pid 6184):Back up of MESP will be excluded as it is part of Availability group. It can be backed up using SQL federated workflow.

    29211:(pid 6184):At least 1 valid backup target is required

    43709:(pid 6184):Stop time: Mon Aug 24 16:19:48 2015

    Unable to find any full backups of the save set 'LCHDMESPNB41:MSSQL:MESP' in the media database. Performing a full backup.

    LCHDMESPNB41:MSSQL:MESP: retried 1 times.

  • Fenglin1

    6 Operator

    •

    2074 帖子

    2621

    0

    已发布 August 24th, 2015 06:00

    对的

  • liulei_it

    2 Intern

    •

    3209 帖子

    2621

    0

    已发布 August 24th, 2015 17:00

    really ? 如果是真的就惨了因为打开standby的readonly需要额外的许可的哦

  • liulei_it

    2 Intern

    •

    3209 帖子

    2621

    0

    已发布 August 24th, 2015 19:00

    dear ,

    偶这边MSSQL的always on环境是这个,应该不需要把standby的设置为read only吧

    PING TEST RESULT(10.42.68.56).jpg

  • Fenglin1

    6 Operator

    •

    2074 帖子

    2621

    0

    已发布 August 25th, 2015 00:00

    42是Secondary咯?选到42看看

  • liulei_it

    2 Intern

    •

    3209 帖子

    2621

    0

    已发布 August 25th, 2015 01:00

    您好

    那个LCHDMESPNB42是只用于fail over的standby没有read only耶

  • liulei_it

    2 Intern

    •

    3209 帖子

    2621

    0

    已发布 September 2nd, 2015 23:00

    dear 

      偶在软件的Help文档

    If using AlwaysOn configuration for SQL Server 2012

    NMM supports the SQL Server 2012 feature AlwaysOn. AlwaysOn allows a database to have multiple replicas. There can be a maximum number of four secondary replicas. These replicas can be configured to be in either synchronous or asynchronous mode.

    A database that is configured as AlwaysOn is treated by NMM as a normal database, and a backup of this database can be performed from the primary or secondary replica because the replicas are considered to be databases that are residing on separate instances. However, there are some restrictions on secondary replicas of the AlwaysOn database, and not all backup types are supported for secondary replicas.

    To perform backup of secondary replicas, the Readable Secondary option of SQL Server 2012 AlwaysOn configuration must be set to “Yes.” Enable this option for both primary and secondary replicas, because during the backup process, secondary replicas may become primary and vice versa.

    SQL Server 2012 has also introduced the new functionality Availability Group with AlwaysOn. Availability Group is a logical group of databases that have the AlwaysOn capability. The Availability Group is failed over to other nodes as a group, that is, all the databases which are part of the Availability group are failed over during the failure or manual failover.

    The Microsoft website describes the AlwaysOn Availability Group functionality in SQL Server 2012, and provides detailed information about how to configure your setup to utilize this support.

    If your setup contains an SQL Server with AlwaysOn configuration, then before recovery you must perform certain additional steps. You can either use the SQL Server Management Studio GUI or the query window.

    To perform the steps from the SQL Server Management Studio GUI:

    1. Open the SQL Server Management Studio and remove the content database from Availability Group. Right-click the content database and select Remove Database from Availability Group. 
    2. Perform recovery.
    3. After recovery is successful, go to the SQL Server Management Studio and add the content database back to Availability Group:
      • Right-click the Availability databases and select the Add Database to Availability Group option.

      • In the Add Database to Availability Group dialog box:
      • In the Select Databases page that appears, select WSS_Content_AO_webApp1 and click Next.
      • In the Select Initial Data Synchronization page that appears, select the Full option and specify the synchronization location, and click Next.

      The synchronization may fail with an error, in case a secondary replica copy with same name exists.

      • Delete the secondary replica copy that is in restoring mode.
      • Rerun the validation.

      The content database is added back to Availability Group.

    4. Return to the NMM GUI and click Continue in the dependency dialog box. Continue with the remaining steps.

    To perform the steps from the SQL Server Management Studio GUI:

    1. On the primary replica server, use the following command: 

      ALTER AVAILABILITY GROUP [Group9] REMOVE DATABASE [Weekly_test_weekly_data_backup_db9]

    2. On the secondary replica server, delete the AlwaysOn database, which is in restoring state.

    实际上不管是在active节点或者可以readonly的节点应该都是可以执行的

    还有一篇这个的help

    • In the Save Set attribute, specify the components to be backed up:
    • AlwaysOn Group referring SQL default instance — MSSQL#AG1
    • AlwaysOn Group referring SQL default instance — MSSQL#AG1:Database1
    • AlwaysOn Group referring SQL named instance — MSSQL$NamedInstance#AG2
    • AlwaysOn Group referring SQL named instance — MSSQL$NamedInstance#AG2:Database2

    但是 我不管是在命令行或者saveset 都出错。

    在客户端networker for MSSQL Module 打开准备选择备份数据库时发现,在always on环境中的recover model 为 simple 和 在always on的recover module为 full的数据库就不能被选中。是客户端软件的问题么

    客户端是 8.2.1 数据库模块是3.0.1

    h h.JPG.jpg

  • liulei_it

    2 Intern

    •

    3209 帖子

    317

    0

    已发布 September 3rd, 2015 23:00

    EMC

    ®

    NetWorker

    ®

    Module for Microsoft for SQL and

    SharePoint VSS

    上面说

    A database that is configured as AlwaysOn is treated by NMM as a normal database. A

    backup of the database can be performed from either the primary replica or secondary

    replica because NMM considers the replicas to be databases that are residing on separate

    instances. However, there are some restrictions on secondary replicas of an AlwaysOn

    database and not all backup types can be performed from the secondary replicas.

    按道理没啥区别呀