NetBackup™ for SQLite 管理指南: Windows 和Linux
nbsqlite.conf 配置文件 ................................................................... 13 使用 DataStore 策略配置 SQLite 备份 ............................................... 15 第 4 章 NetBackup for SQLite 备份和还原 Agent 安装 NetBackup for SQLite 代理 配置 NetBackup for SQLite 本章节包括下列主题: ■ nbsqlite.conf 配置文件 ■ 使用 DataStore 策略配置 SQLite 备份 nbsqlite.conf 配置文件 配置文件 (nbsqlite.conf) 包含必须为相应操作指定的参数。它位于客户端上并 包含预定义的设置。您可以在 nbsqlite 除。 指定用于 nbsqlite 操作的 NetBackup 主服务器。 MASTER_SERVER_NAME 此参数无默认值。 备份 指定 DataStore 策略名称。 POLICY_NAME 此参数无默认值。 备份 标识在创建 DataStore 策略时 配置的备份日程表。 SCHEDULE_NAME 如果未设置此参数,则默认 为 NetBackup 主服务器。 重定向还原和查询 定义具有代理的0 码力 | 34 页 | 777.04 KB | 1 年前3NetBackup™ for SQLite 管理指南: Windows 和 Linux - 版本:10.2
....... 7 第 2 章 配置 NetBackup for SQLite .............................................. 9 使用 DataStore 策略配置 SQLite 备份 ................................................ 9 第 3 章 NetBackup for SQLite 备份和还原 的前提条件 配置 NetBackup for SQLite 本章节包括下列主题: ■ 使用 DataStore 策略配置 SQLite 备份 使用 DataStore 策略配置 SQLite 备份 代理支持 DataStore 策略定义属性、日程表、客户端列表和备份选择。 使用 DataStore 策略配置 SQLite 数据库备份 1 以管理员身份 (Windows) 或 root 身份 (Linux) 管理控制台”中,展开“NetBackup 管理”,然后单击“策 略”。 3 在“所有策略”窗格中,右键单击“所有策略的摘要”,然后单击“新建策 略”。 4 在“添加新策略”对话框中,为策略输入一个唯一的名称。 5 在“更改策略”对话框中,从“策略类型”下拉列表中选择“DataStore 策 略”。 6 从“策略存储”下拉列表中,为存储选择基于磁盘的存储单元。 7 要选择日程表类型,请在“日0 码力 | 29 页 | 675.75 KB | 1 年前3VMware Greenplum 6 Documentation
Greenplum Database size discussed in the Planning section. You must verify that the free space in the datastore, the free memory in the cluster, and total amount of free processors in the cluster are enough build your own base virtual machine, you must have a running CentOS 7 virtual machine in the same datastore and cluster where you will deploy the Greenplum environment. You must have access to the Internet IP and Fully Qualified Domain Name (FQDN). VMware vSphere datacenter name. VMware vSphere vSAN datastore name. VMware vSphere compute cluster name. Network Request the following from your network administrator0 码力 | 2374 页 | 44.90 MB | 1 年前3VMware Tanzu Greenplum v6.23 Documentation
Greenplum Database size discussed in the Planning section. You must verify that the free space in the datastore, the free memory in the cluster, and total amount of free processors in the cluster are enough build your own base virtual machine, you must have a running CentOS 7 virtual machine in the same datastore and cluster where you will deploy the Greenplum environment. You must have access to the Internet IP and Fully Qualified Domain Name (FQDN). VMware vSphere datacenter name. VMware vSphere vSAN datastore name. VMware vSphere compute cluster name. Network Request the following from your network administrator0 码力 | 2298 页 | 40.94 MB | 1 年前3VMware Tanzu Greenplum 6 Documentation
Greenplum Database size discussed in the Planning section. You must verify that the free space in the datastore, the free memory in the cluster, and total amount of free processors in the cluster are enough build your own base virtual machine, you must have a running CentOS 7 virtual machine in the same datastore and cluster where you will deploy the Greenplum environment. You must have access to the Internet IP and Fully Qualified Domain Name (FQDN). VMware vSphere datacenter name. VMware vSphere vSAN datastore name. VMware vSphere compute cluster name. Network Request the following from your network administrator0 码力 | 2311 页 | 17.58 MB | 1 年前3VMware Greenplum 6 Documentation
storage (the Datastore Volume) is not dependent on the physical host. If high availability (HA) and RAID configuration are already configured at the external storage array, the Datastore Volume should the physical hosts. In the specifications below, 30% of the Datastore Volume is reserved for Greenplum operations and 30% of the Datastore Volume is reserved for vSphere operations. 10 TiB Database the operating system for the master host 1-9999 100 vSphere Datastore Operating Reservation (%) Percentage of free space in the datastore for DRS to rebalance master hosts and segment hosts across ESXi0 码力 | 2445 页 | 18.05 MB | 1 年前3VMware Tanzu Greenplum v6.21 Documentation
Greenplum Database size discussed in the Planning section. You must verify that the free space in the datastore, the free memory in the cluster, and total amount of free processors in the cluster are enough decide to build your own OVA template, you must have a running CentOS 7 virtual machine in the same datastore and cluster where you will deploy the Greenplum environment. You will need it to create the virtual IP and Fully Qualified Domain Name (FQDN). VMware vSphere datacenter name. VMware vSphere vSAN datastore name. VMware vSphere compute cluster name. Network Request the following from your network administrator0 码力 | 2025 页 | 33.54 MB | 1 年前3VMware Greenplum v6.25 Documentation
system for the coordinator virtual machine 1-9999 100 vSphere Datastore Operating Reservation (%) Percentage of free space in the datastore for DRS to rebalance virtual machines across ESXi hosts 1-100 for all the virtual machines. vSphere Datastore shows the total space used for all Greenplum virtual machines, and how much space is reserved for vSphere datastore operations. Recommended Storage Size Size is the total storage you must have available in your vSphere datastore for the values you provided. Prerequisites You must meet certain prerequisites and collect specific information from your existing0 码力 | 2400 页 | 18.02 MB | 1 年前3The Vitess 8.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow multiple indexes per table, and there are many types of indexes. Extending destination databases, while the application is still pointing to the source database as the primary datastore. • Create custom tools to backfill old data from the source to destination system. VReplication0 码力 | 331 页 | 1.35 MB | 1 年前3The Vitess 6.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow you to define multiple indexes per table, and there are many types0 码力 | 210 页 | 846.79 KB | 1 年前3
共 85 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9