免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 8152 | 回复: 13
打印 上一主题 下一主题

[备份软件] nbu oracle rac 备份 问题 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2011-04-06 17:23 |只看该作者 |倒序浏览
本帖最后由 zhangmq 于 2011-04-06 17:48 编辑

各位好,小弟将要实施一个nbu备份,备份aix平台下的oracle 11g rac,特意在rhel5.1下搭建环境测试,安装oracle 10.2(本应安装11g的,不过感觉11g对服务器性能要求很高)测试。
以下是一些信息,请各位帮忙确认这样做有没问题,在一个节点在发起备份,另一节点的归档日志有没有备份成功?

描述:
1.测试环境均在vmware esxi虚拟机下完成;
2.安装一部win2003做nbu server,版本7.0;两部rhel5.1使用共享磁盘安装oracle 10.2 rac,两部(node1、node2)都安装nbu 6.5 client和oracle option(本想安装nbu7.0 client,实属无奈,我的rhel是32位的,nbu 7.0不支持) 。
3.采用lan备份。

论坛徽章:
0
2 [报告]
发表于 2011-04-06 17:26 |只看该作者
二、数据库配置:
1.归档均在asm上:
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            +RAC_DISK
Oldest online log sequence     10
Next log sequence to archive   11
Current log sequence           11
SQL>

论坛徽章:
0
3 [报告]
发表于 2011-04-06 17:30 |只看该作者
创建策略,只添加一个节点(备份在一个节点在完成),如附件,发现再添加另一个节点执行时有会报错。

未命名.JPG (19.73 KB, 下载次数: 46)

未命名.JPG

论坛徽章:
0
4 [报告]
发表于 2011-04-06 17:32 |只看该作者
以下是备份脚本,在node1下的,套用模板做的修改:
  1. [root@node1 /]# cat hot_database_backup.sh
  2. #!/bin/sh
  3. # $Header: hot_database_backup.sh,v 1.2 2002/08/06 23:51:42 $
  4. #
  5. #bcpyrght
  6. #***************************************************************************
  7. #* $VRTScprght: Copyright 1993 - 2007 Symantec Corporation, All Rights Reserved $ *
  8. #***************************************************************************
  9. #ecpyrght
  10. #
  11. # ---------------------------------------------------------------------------
  12. #                       hot_database_backup.sh
  13. # ---------------------------------------------------------------------------
  14. #  This script uses Recovery Manager to take a hot (inconsistent) database
  15. #  backup. A hot backup is inconsistent because portions of the database are
  16. #  being modified and written to the disk while the backup is progressing.
  17. #  You must run your database in ARCHIVELOG mode to make hot backups. It is
  18. #  assumed that this script will be executed by user root. In order for RMAN
  19. #  to work properly we switch user (su -) to the oracle dba account before
  20. #  execution. If this script runs under a user account that has Oracle dba
  21. #  privilege, it will be executed using this user's account.
  22. # ---------------------------------------------------------------------------

  23. # ---------------------------------------------------------------------------
  24. # Determine the user which is executing this script.
  25. # ---------------------------------------------------------------------------

  26. CUSER=`id |cut -d"(" -f2 | cut -d ")" -f1`

  27. # ---------------------------------------------------------------------------
  28. # Put output in <this file name>.out. Change as desired.
  29. # Note: output directory requires write permission.
  30. # ---------------------------------------------------------------------------

  31. RMAN_LOG_FILE=${0}.out

  32. # ---------------------------------------------------------------------------
  33. # You may want to delete the output file so that backup information does
  34. # not accumulate.  If not, delete the following lines.
  35. # ---------------------------------------------------------------------------

  36. if [ -f "$RMAN_LOG_FILE" ]
  37. then
  38.         rm -f "$RMAN_LOG_FILE"
  39. fi

  40. # -----------------------------------------------------------------
  41. # Initialize the log file.
  42. # -----------------------------------------------------------------

  43. echo >> $RMAN_LOG_FILE
  44. chmod 666 $RMAN_LOG_FILE

  45. # ---------------------------------------------------------------------------
  46. # Log the start of this script.
  47. # ---------------------------------------------------------------------------

  48. echo Script $0 >> $RMAN_LOG_FILE
  49. echo ==== started on `date` ==== >> $RMAN_LOG_FILE
  50. echo >> $RMAN_LOG_FILE

  51. # ---------------------------------------------------------------------------
  52. # Replace /db/oracle/product/ora81, below, with the Oracle home path.
  53. # ---------------------------------------------------------------------------

  54. ORACLE_HOME=/opt/ora10g/product/10.2.0/db_1
  55. export ORACLE_HOME

  56. # ---------------------------------------------------------------------------
  57. # Replace ora81, below, with the Oracle SID of the target database.
  58. # ---------------------------------------------------------------------------

  59. ORACLE_SID=RACDB1
  60. export ORACLE_SID

  61. # ---------------------------------------------------------------------------
  62. # Replace ora81, below, with the Oracle DBA user id (account).
  63. # ---------------------------------------------------------------------------

  64. ORACLE_USER=oracle

  65. # ---------------------------------------------------------------------------
  66. # Set the target connect string.
  67. # Replace "sys/manager", below, with the target connect string.
  68. # ---------------------------------------------------------------------------

  69. TARGET_CONNECT_STR=system/root1234

  70. # ---------------------------------------------------------------------------
  71. # Set the Oracle Recovery Manager name.
  72. # ---------------------------------------------------------------------------

  73. RMAN=$ORACLE_HOME/bin/rman

  74. # ---------------------------------------------------------------------------
  75. # Print out the value of the variables set by this script.
  76. # ---------------------------------------------------------------------------

  77. echo >> $RMAN_LOG_FILE
  78. echo   "RMAN: $RMAN" >> $RMAN_LOG_FILE
  79. echo   "ORACLE_SID: $ORACLE_SID" >> $RMAN_LOG_FILE
  80. echo   "ORACLE_USER: $ORACLE_USER" >> $RMAN_LOG_FILE
  81. echo   "ORACLE_HOME: $ORACLE_HOME" >> $RMAN_LOG_FILE

  82. # ---------------------------------------------------------------------------
  83. # Print out the value of the variables set by bphdb.
  84. # ---------------------------------------------------------------------------

  85. echo  >> $RMAN_LOG_FILE
  86. echo   "NB_ORA_FULL: $NB_ORA_FULL" >> $RMAN_LOG_FILE
  87. echo   "NB_ORA_INCR: $NB_ORA_INCR" >> $RMAN_LOG_FILE
  88. echo   "NB_ORA_CINC: $NB_ORA_CINC" >> $RMAN_LOG_FILE
  89. echo   "NB_ORA_SERV: $NB_ORA_SERV" >> $RMAN_LOG_FILE
  90. echo   "NB_ORA_POLICY: $NB_ORA_POLICY" >> $RMAN_LOG_FILE

  91. # ---------------------------------------------------------------------------
  92. # NOTE: This script assumes that the database is properly opened. If desired,
  93. # this would be the place to verify that.
  94. # ---------------------------------------------------------------------------

  95. echo >> $RMAN_LOG_FILE
  96. # ---------------------------------------------------------------------------
  97. # If this script is executed from a NetBackup schedule, NetBackup
  98. # sets an NB_ORA environment variable based on the schedule type.
  99. # The NB_ORA variable is then used to dynamically set BACKUP_TYPE
  100. # For example, when:
  101. #     schedule type is                BACKUP_TYPE is
  102. #     ----------------                --------------
  103. # Automatic Full                     INCREMENTAL LEVEL=0
  104. # Automatic Differential Incremental INCREMENTAL LEVEL=1
  105. # Automatic Cumulative Incremental   INCREMENTAL LEVEL=1 CUMULATIVE
  106. #
  107. # For user initiated backups, BACKUP_TYPE defaults to incremental
  108. # level 0 (full).  To change the default for a user initiated
  109. # backup to incremental or incremental cumulative, uncomment
  110. # one of the following two lines.
  111. # BACKUP_TYPE="INCREMENTAL LEVEL=1"
  112. # BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"
  113. #
  114. # Note that we use incremental level 0 to specify full backups.
  115. # That is because, although they are identical in content, only
  116. # the incremental level 0 backup can have incremental backups of
  117. # level > 0 applied to it.
  118. # ---------------------------------------------------------------------------

  119. if [ "$NB_ORA_FULL" = "1" ]
  120. then
  121.         echo "Full backup requested" >> $RMAN_LOG_FILE
  122.         BACKUP_TYPE="INCREMENTAL LEVEL=0"

  123. elif [ "$NB_ORA_INCR" = "1" ]
  124. then
  125.         echo "Differential incremental backup requested" >> $RMAN_LOG_FILE
  126.         BACKUP_TYPE="INCREMENTAL LEVEL=1"

  127. elif [ "$NB_ORA_CINC" = "1" ]
  128. then
  129.         echo "Cumulative incremental backup requested" >> $RMAN_LOG_FILE
  130.         BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"

  131. elif [ "$BACKUP_TYPE" = "" ]
  132. then
  133.         echo "Default - Full backup requested" >> $RMAN_LOG_FILE
  134.         BACKUP_TYPE="INCREMENTAL LEVEL=0"
  135. fi


  136. # ---------------------------------------------------------------------------
  137. # Call Recovery Manager to initiate the backup. This example does not use a
  138. # Recovery Catalog. If you choose to use one, replace the option 'nocatalog'
  139. # from the rman command line below with the
  140. # 'rcvcat <userid>/<passwd>@<tns alias>' statement.
  141. #
  142. # Note: Any environment variables needed at run time by RMAN
  143. #       must be set and exported within the switch user (su) command.
  144. # ---------------------------------------------------------------------------
  145. #  Backs up the whole database.  This backup is part of the incremental
  146. #  strategy (this means it can have incremental backups of levels > 0
  147. #  applied to it).
  148. #
  149. #  We do not need to explicitly request the control file to be included
  150. #  in this backup, as it is automatically included each time file 1 of
  151. #  the system tablespace is backed up (the inference: as it is a whole
  152. #  database backup, file 1 of the system tablespace will be backed up,
  153. #  hence the controlfile will also be included automatically).
  154. #
  155. #  Typically, a level 0 backup would be done at least once a week.
  156. #
  157. #  The scenario assumes:
  158. #     o you are backing your database up to two tape drives
  159. #     o you want each backup set to include a maximum of 5 files
  160. #     o you wish to include offline datafiles, and read-only tablespaces,
  161. #       in the backup
  162. #     o you want the backup to continue if any files are inaccessible.
  163. #     o you are not using a Recovery Catalog
  164. #     o you are explicitly backing up the control file.  Since you are
  165. #       specifying nocatalog, the controlfile backup that occurs
  166. #       automatically as the result of backing up the system file is
  167. #       not sufficient; it will not contain records for the backup that
  168. #       is currently in progress.
  169. #     o you want to archive the current log, back up all the
  170. #       archive logs using two channels, putting a maximum of 20 logs
  171. #       in a backup set, and deleting them once the backup is complete.
  172. #
  173. #  Note that the format string is constructed to guarantee uniqueness and
  174. #  to enhance NetBackup for Oracle backup and restore performance.
  175. #
  176. #
  177. #  NOTE WHEN USING TNS ALIAS: When connecting to a database
  178. #  using a TNS alias, you must use a send command or a parms operand to
  179. #  specify environment variables.  In other words, when accessing a database
  180. #  through a listener, the environment variables set at the system level are not
  181. #  visible when RMAN is running.  For more information on the environment
  182. #  variables, please refer to the NetBackup for Oracle Admin. Guide.
  183. #
  184. # ---------------------------------------------------------------------------

  185. CMD_STR="
  186. ORACLE_HOME=$ORACLE_HOME
  187. export ORACLE_HOME
  188. ORACLE_SID=$ORACLE_SID
  189. export ORACLE_SID
  190. $RMAN target $TARGET_CONNECT_STR nocatalog msglog $RMAN_LOG_FILE append << EOF
  191. RUN {
  192. ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  193. ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
  194. BACKUP
  195.     $BACKUP_TYPE
  196.     SKIP INACCESSIBLE
  197.     TAG hot_db_bk_level0
  198.     FILESPERSET 5
  199.     # recommended format
  200.     FORMAT 'bk_%s_%p_%t'
  201.     DATABASE;
  202.     sql 'alter system archive log current';
  203. RELEASE CHANNEL ch00;
  204. RELEASE CHANNEL ch01;
  205. # backup all archive logs
  206. ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  207. ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
  208. BACKUP
  209.    filesperset 20
  210.    FORMAT 'al_%s_%p_%t'
  211.    ARCHIVELOG ALL DELETE INPUT;
  212. RELEASE CHANNEL ch00;
  213. RELEASE CHANNEL ch01;
  214. #
  215. # Note: During the process of backing up the database, RMAN also backs up the
  216. # control file.  This version of the control file does not contain the
  217. # information about the current backup because "nocatalog" has been specified.
  218. # To include the information about the current backup, the control file should
  219. # be backed up as the last step of the RMAN section.  This step would not be
  220. # necessary if we were using a recovery catalog.
  221. #
  222. ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
  223. BACKUP
  224.     # recommended format
  225.     FORMAT 'cntrl_%s_%p_%t'
  226.     CURRENT CONTROLFILE;
  227. RELEASE CHANNEL ch00;
  228. }
  229. EOF
  230. "
  231. # Initiate the command string

  232. if [ "$CUSER" = "root" ]
  233. then
  234.     su - $ORACLE_USER -c "$CMD_STR" >> $RMAN_LOG_FILE
  235.     RSTAT=$?
  236. else
  237.     /usr/bin/sh -c "$CMD_STR" >> $RMAN_LOG_FILE
  238.     RSTAT=$?
  239. fi

  240. # ---------------------------------------------------------------------------
  241. # Log the completion of this script.
  242. # ---------------------------------------------------------------------------

  243. if [ "$RSTAT" = "0" ]
  244. then
  245.     LOGMSG="ended successfully"
  246. else
  247.     LOGMSG="ended in error"
  248. fi

  249. echo >> $RMAN_LOG_FILE
  250. echo Script $0 >> $RMAN_LOG_FILE
  251. echo ==== $LOGMSG on `date` ==== >> $RMAN_LOG_FILE
  252. echo >> $RMAN_LOG_FILE

  253. exit $RSTAT
复制代码

论坛徽章:
0
5 [报告]
发表于 2011-04-06 17:34 |只看该作者
备份日志输出没有报错,就是不确定是否成功,node2的archivelog有没备成功。
  1. [root@node1 /]# cat hot_database_backup.sh.out

  2. Script /hot_database_backup.sh
  3. ==== started on Thu Apr 7 00:46:32 CST 2011 ====


  4. RMAN: /opt/ora10g/product/10.2.0/db_1/bin/rman
  5. ORACLE_SID: RACDB1
  6. ORACLE_USER: oracle
  7. ORACLE_HOME: /opt/ora10g/product/10.2.0/db_1

  8. NB_ORA_FULL: 1
  9. NB_ORA_INCR: 0
  10. NB_ORA_CINC: 0
  11. NB_ORA_SERV: nbuserver
  12. NB_ORA_POLICY: racdb

  13. Full backup requested

  14. Recovery Manager: Release 10.2.0.1.0 - Production on Thu Apr 7 00:46:36 2011

  15. Copyright (c) 1982, 2005, Oracle.  All rights reserved.

  16. connected to target database: RACDB (DBID=744895673)
  17. using target database control file instead of recovery catalog

  18. RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38>
  19. allocated channel: ch00
  20. channel ch00: sid=148 instance=RACDB1 devtype=SBT_TAPE
  21. channel ch00: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

  22. allocated channel: ch01
  23. channel ch01: sid=146 instance=RACDB1 devtype=SBT_TAPE
  24. channel ch01: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

  25. Starting backup at 07-APR-11
  26. channel ch00: starting incremental level 0 datafile backupset
  27. channel ch00: specifying datafile(s) in backupset
  28. input datafile fno=00001 name=+RAC_DISK/racdb/datafile/system.259.747278925
  29. input datafile fno=00004 name=+RAC_DISK/racdb/datafile/undotbs2.263.747278985
  30. channel ch00: starting piece 1 at 07-APR-11
  31. channel ch01: starting incremental level 0 datafile backupset
  32. channel ch01: specifying datafile(s) in backupset
  33. input datafile fno=00003 name=+RAC_DISK/racdb/datafile/sysaux.261.747278963
  34. input datafile fno=00002 name=+RAC_DISK/racdb/datafile/undotbs1.260.747278955
  35. input datafile fno=00005 name=+RAC_DISK/racdb/datafile/users.264.747278995
  36. channel ch01: starting piece 1 at 07-APR-11
  37. channel ch00: finished piece 1 at 07-APR-11
  38. piece handle=bk_21_1_747794816 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0
  39. channel ch00: backup set complete, elapsed time: 00:07:42
  40. channel ch01: finished piece 1 at 07-APR-11
  41. piece handle=bk_22_1_747794817 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0
  42. channel ch01: backup set complete, elapsed time: 00:13:40
  43. Finished backup at 07-APR-11

  44. Starting Control File and SPFILE Autobackup at 07-APR-11
  45. piece handle=c-744895673-20110407-04 comment=API Version 2.0,MMS Version 5.0.0.0
  46. Finished Control File and SPFILE Autobackup at 07-APR-11

  47. sql statement: alter system archive log current

  48. released channel: ch00

  49. released channel: ch01

  50. allocated channel: ch00
  51. channel ch00: sid=148 instance=RACDB1 devtype=SBT_TAPE
  52. channel ch00: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

  53. allocated channel: ch01
  54. channel ch01: sid=146 instance=RACDB1 devtype=SBT_TAPE
  55. channel ch01: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

  56. Starting backup at 07-APR-11
  57. current log archived
  58. channel ch00: starting archive log backupset
  59. channel ch00: specifying archive log(s) in backup set
  60. input archive log thread=1 sequence=35 recid=8 stamp=747795749
  61. channel ch00: starting piece 1 at 07-APR-11
  62. channel ch01: starting archive log backupset
  63. channel ch01: specifying archive log(s) in backup set
  64. input archive log thread=1 sequence=36 recid=11 stamp=747795767
  65. input archive log thread=2 sequence=9 recid=9 stamp=747795751
  66. channel ch01: starting piece 1 at 07-APR-11
  67. channel ch00: finished piece 1 at 07-APR-11
  68. piece handle=al_24_1_747795768 tag=TAG20110407T010247 comment=API Version 2.0,MMS Version 5.0.0.0
  69. channel ch00: backup set complete, elapsed time: 00:00:57
  70. channel ch00: deleting archive log(s)
  71. archive log filename=+RAC_DISK/racdb/archivelog/2011_04_07/thread_1_seq_35.274.747795749 recid=8 stamp=747795749
  72. channel ch00: starting archive log backupset
  73. channel ch00: specifying archive log(s) in backup set
  74. input archive log thread=2 sequence=10 recid=10 stamp=747795767
  75. channel ch00: starting piece 1 at 07-APR-11
  76. channel ch01: finished piece 1 at 07-APR-11
  77. piece handle=al_25_1_747795769 tag=TAG20110407T010247 comment=API Version 2.0,MMS Version 5.0.0.0
  78. channel ch01: backup set complete, elapsed time: 00:01:23
  79. channel ch01: deleting archive log(s)
  80. archive log filename=+RAC_DISK/racdb/archivelog/2011_04_07/thread_1_seq_36.272.747795765 recid=11 stamp=747795767
  81. archive log filename=+RAC_DISK/racdb/archivelog/2011_04_07/thread_2_seq_9.271.747795751 recid=9 stamp=747795751
  82. channel ch00: finished piece 1 at 07-APR-11
  83. piece handle=al_26_1_747795825 tag=TAG20110407T010247 comment=API Version 2.0,MMS Version 5.0.0.0
  84. channel ch00: backup set complete, elapsed time: 00:00:55
  85. channel ch00: deleting archive log(s)
  86. archive log filename=+RAC_DISK/racdb/archivelog/2011_04_07/thread_2_seq_10.273.747795765 recid=10 stamp=747795767
  87. Finished backup at 07-APR-11

  88. Starting Control File and SPFILE Autobackup at 07-APR-11
  89. piece handle=c-744895673-20110407-05 comment=API Version 2.0,MMS Version 5.0.0.0
  90. Finished Control File and SPFILE Autobackup at 07-APR-11

  91. released channel: ch00

  92. released channel: ch01

  93. allocated channel: ch00
  94. channel ch00: sid=148 instance=RACDB1 devtype=SBT_TAPE
  95. channel ch00: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

  96. Starting backup at 07-APR-11
  97. channel ch00: starting full datafile backupset
  98. channel ch00: specifying datafile(s) in backupset
  99. including current control file in backupset
  100. channel ch00: starting piece 1 at 07-APR-11
  101. channel ch00: finished piece 1 at 07-APR-11
  102. piece handle=cntrl_28_1_747795976 tag=TAG20110407T010615 comment=API Version 2.0,MMS Version 5.0.0.0
  103. channel ch00: backup set complete, elapsed time: 00:01:08
  104. Finished backup at 07-APR-11

  105. Starting Control File and SPFILE Autobackup at 07-APR-11
  106. piece handle=c-744895673-20110407-06 comment=API Version 2.0,MMS Version 5.0.0.0
  107. Finished Control File and SPFILE Autobackup at 07-APR-11

  108. released channel: ch00

  109. RMAN> RMAN>

  110. Recovery Manager complete.

  111. Script /hot_database_backup.sh
  112. ==== ended successfully on Thu Apr 7 01:09:08 CST 2011 ====
复制代码

论坛徽章:
0
6 [报告]
发表于 2011-04-06 17:59 |只看该作者
rac备份就备份一台机器,将另一台归档nfs挂载在备份机上会自动备份归档的,楼主看看nbu备份rac部分吧。

论坛徽章:
0
7 [报告]
发表于 2011-04-06 18:19 |只看该作者
你的RAC的归档日志放在共享磁盘阵列上吗,还是说放在本地磁盘呢

论坛徽章:
0
8 [报告]
发表于 2011-04-06 20:17 |只看该作者
如果归档都存储在ASM存储上,应该没有问题,否则需要在allocate时使用parms指定备份策略、客户端等。

论坛徽章:
0
9 [报告]
发表于 2011-04-06 22:23 |只看该作者
rac备份就备份一台机器,将另一台归档nfs挂载在备份机上会自动备份归档的,楼主看看nbu备份rac部分吧。
heroesray 发表于 2011-04-06 17:59



    归档是在共享存储上的

论坛徽章:
0
10 [报告]
发表于 2011-04-06 22:24 |只看该作者
如果归档都存储在ASM存储上,应该没有问题,否则需要在allocate时使用parms指定备份策略、客户端等。
jcbut 发表于 2011-04-06 20:17



    改天做恢复测试,验证下。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP