2. Проект модернизации СРК и ВД …..
2
Результаты
• Внедрено 3х NetBackup Appliance 5330 458TБ
• Сокращено время РК для Oracle Exadata
• Оптимизирован уровень хранения резервных
копий (MSDP и AdvancedDisk пулы)
• Удовлетворены все требования по РК и ВД
виртуальной среды
Планы
• 2х NetBackup 5330 458 TB в 3-й ЦОД
• Расширение дискового уровня хранения
резервных копий
• Замена ленточных библиотек
• Аппаратная репликация резервных копий
между сайтами
Окружение
• Oracle Exadata
• Teradata
• VMware
• NetApp
• 3 ЦОДа
Исходное состояние
• NetBackup как ПО управления
СРК и ВД
• Физические ленточные
библиотеки IBM для хранения
резервных копий
• Суммарный объем данных 1 ПБ
Цели проекта
• Перевод на СРК и ВД на D2D2T
• Сократить окно резервного
копирования Oracle Exadata
• Стандартизировать подходы к РК и
ВД виртуальной среды
• Оптимизировать уровень хранения
резервных копий
3. Исходное состояние СКРиВД Oracle Exadata
Oracle Exadata
NBU Media Server
135TB
NBU Media Server
Infiniband
40Gb/s
Infiniband
40Gb/s
Fibre Channel
8Gb/s
Fibre Channel
8Gb/s
4. Целевая архитектура СКРиВД Oracle Exadata
РК на NetBackup Appliance MSDP
Oracle Exadata
NetBackup Appliance 5330
458TB
6x10 GbE
MSDP
NBU Media Server
135TB
NBU Media Server
Infiniband
40Gb/s
Infiniband
40Gb/s
6. Преимущества решения c использованием АПК РКиВД
Veritas NetBackup Appliance 5330
• Конвергентная платформа – интегрированное решение СРК «все в одном»
• Масштабируемость
– scale-up & scale-out
– построение всей схемы РКиВД на базе единой архитектуры (Oracle
Exadata, VMware, Teradata, NetApp, и т.п.)
• Надежность архитектуры
• Простота внедрения с минимальными рисками
• Дополнительные функциональные возможности (Copilot, MSDP 458TB)
• Глобальная дедупликация
• Снижение нагрузки на Oracle Exadata
• Поддержка от Veritas в построении решения под ключ
7. Результаты тестирования
Veritas NetBackup Appliance 5330
Различные сценарии тестирования NetBackup Appliance 5330
Время резервного
копирования, ч
Пропускная способность,
ТБ/ч
Библиотека IBM TS4500 Задействовано 10 LTO6 приводов
2 медиа сервера, 10 потоков 51 2.65
NBU Appliance 5330 MSDP Pool (Fingerprint load balancing media servers)
2 Fingerprint Media-сервера, 16 потоков (1-й прогон) 26 5.2
2 Fingerprint Media-сервера, 16 потоков (2-й прогон) 15 9.00
NBU Appliance 5330 MSDP Pool
16 потоков (1-й прогон) 22 6.1
16 потоков (2-й прогон) 20 6.75
NBU Appliance 5330 Advanced Disk Pool
16 потоков 21 6.43
Value Proposition:
NetBackup has always lead with flexibility and performance. By adding the “Dump and Sweep” capability backup admins are able to give Oracle DBAs the ability to maintain easy self-service access using the tools that they are most familiar with such as RMAN and OEM. With minimal training and setup both the Oracle DBA and the backup administrators are able to easily protect, monitor and report on backup disk usage and SLAs.
Copilot also delivers a reduction in primary secondary storage for the dump, reduced network hops (straight to appliance rather than 1) dump storage, 2) backup to appliance)
Technical:
The “dump and sweep” is a tradition method that allows the DBA to control when databases are backed up to the Appliance share. NetBackup Appliances provide the target for RMAN and then NetBackup backs up the dumped files to Advanced disk, MSDP or tape. Additionally the backup administrator can utilize Storage Lifecycle policies to then replicate the backup image using A.I.R. to an offsite DR appliance, to tape or cloud.
Step 1:
Copilot Oracle Shares(COS) are mounted/presented to an Oracle database server as NFS mounts.
Step2:
DBA initiates an RMAN backup of the Oracle instance at any time and sends the output to the Copilot Oracle Share on the appliance.
Step 3:
A NetBackup Oracle policy type is run that references the Oracle instance but has a new option in the Backup Selection tab called “Database Backup Shares”. When that option is selected another screen will open up allowing the backup admin to select the COS that was used by the DBA. All other options remain the same as a typical Oracle backup policy.
Step 4: (Replication Optional)
This backup image can be subsequently moved to MSDP storage or tape, or another advanced disk or to the cloud using Storage Life Cycle policies.
Recovery process:
With RMAN the Oracle DBA has the ability to recover the database using any of the Oracle backup images. They will all be available via RMAN and also appear in Oracle Enterprise Manager(OEM). All the recovery points are available, recovery can be made from wherever the backup image resides, including the Copilot Oracle Share, MSDP or Tape or any other OST connected storage that NetBackup utilizes as a storage target.
Retention:
Backup images that have been sent to the COS can be automatically expired using RMAN as needed. The Copilot Oracle Share is just like a directory on his Oracle server and he has full control of its contents.
Value Proposition:
NetBackup has always lead with flexibility and performance. By adding the “Dump and Sweep” capability backup admins are able to give Oracle DBAs the ability to maintain easy self-service access using the tools that they are most familiar with such as RMAN and OEM. With minimal training and setup both the Oracle DBA and the backup administrators are able to easily protect, monitor and report on backup disk usage and SLAs.
Copilot also delivers a reduction in primary secondary storage for the dump, reduced network hops (straight to appliance rather than 1) dump storage, 2) backup to appliance)
Technical:
The “dump and sweep” is a tradition method that allows the DBA to control when databases are backed up to the Appliance share. NetBackup Appliances provide the target for RMAN and then NetBackup backs up the dumped files to Advanced disk, MSDP or tape. Additionally the backup administrator can utilize Storage Lifecycle policies to then replicate the backup image using A.I.R. to an offsite DR appliance, to tape or cloud.
Step 1:
Copilot Oracle Shares(COS) are mounted/presented to an Oracle database server as NFS mounts.
Step2:
DBA initiates an RMAN backup of the Oracle instance at any time and sends the output to the Copilot Oracle Share on the appliance.
Step 3:
A NetBackup Oracle policy type is run that references the Oracle instance but has a new option in the Backup Selection tab called “Database Backup Shares”. When that option is selected another screen will open up allowing the backup admin to select the COS that was used by the DBA. All other options remain the same as a typical Oracle backup policy.
Step 4: (Replication Optional)
This backup image can be subsequently moved to MSDP storage or tape, or another advanced disk or to the cloud using Storage Life Cycle policies.
Recovery process:
With RMAN the Oracle DBA has the ability to recover the database using any of the Oracle backup images. They will all be available via RMAN and also appear in Oracle Enterprise Manager(OEM). All the recovery points are available, recovery can be made from wherever the backup image resides, including the Copilot Oracle Share, MSDP or Tape or any other OST connected storage that NetBackup utilizes as a storage target.
Retention:
Backup images that have been sent to the COS can be automatically expired using RMAN as needed. The Copilot Oracle Share is just like a directory on his Oracle server and he has full control of its contents.
Value Proposition:
NetBackup has always lead with flexibility and performance. By adding the “Dump and Sweep” capability backup admins are able to give Oracle DBAs the ability to maintain easy self-service access using the tools that they are most familiar with such as RMAN and OEM. With minimal training and setup both the Oracle DBA and the backup administrators are able to easily protect, monitor and report on backup disk usage and SLAs.
Copilot also delivers a reduction in primary secondary storage for the dump, reduced network hops (straight to appliance rather than 1) dump storage, 2) backup to appliance)
Technical:
The “dump and sweep” is a tradition method that allows the DBA to control when databases are backed up to the Appliance share. NetBackup Appliances provide the target for RMAN and then NetBackup backs up the dumped files to Advanced disk, MSDP or tape. Additionally the backup administrator can utilize Storage Lifecycle policies to then replicate the backup image using A.I.R. to an offsite DR appliance, to tape or cloud.
Step 1:
Copilot Oracle Shares(COS) are mounted/presented to an Oracle database server as NFS mounts.
Step2:
DBA initiates an RMAN backup of the Oracle instance at any time and sends the output to the Copilot Oracle Share on the appliance.
Step 3:
A NetBackup Oracle policy type is run that references the Oracle instance but has a new option in the Backup Selection tab called “Database Backup Shares”. When that option is selected another screen will open up allowing the backup admin to select the COS that was used by the DBA. All other options remain the same as a typical Oracle backup policy.
Step 4: (Replication Optional)
This backup image can be subsequently moved to MSDP storage or tape, or another advanced disk or to the cloud using Storage Life Cycle policies.
Recovery process:
With RMAN the Oracle DBA has the ability to recover the database using any of the Oracle backup images. They will all be available via RMAN and also appear in Oracle Enterprise Manager(OEM). All the recovery points are available, recovery can be made from wherever the backup image resides, including the Copilot Oracle Share, MSDP or Tape or any other OST connected storage that NetBackup utilizes as a storage target.
Retention:
Backup images that have been sent to the COS can be automatically expired using RMAN as needed. The Copilot Oracle Share is just like a directory on his Oracle server and he has full control of its contents.