• NTT provides upstream DDoS mitigation through in-house scrubbing centers and partners like Arbor Networks.
• Mitigation Capacity: Typically, NTT scrubbing centers can handle 1–2 Tbps globally with regional capacity tailored for 300–500 Gbps depending on the deployment.
• PPS Tolerance: Up to 100+ million packets per second, depending on hardware and scrubbing policy.
• GRE-only protection is insufficient. Ensure you are subscribed to NTT’s DDoS Mitigation Service with inline scrubbing or upstream RTBH integration for true volumetric protection.

• IOPS Tiers: Depending on storage backend (e.g., NVMe or hybrid SAN), typical guarantees per VM can range:
  • Basic VMs: 2K–5K IOPS
  • High-performance VMs/GPUs: 10K–50K+ IOPS (configurable)
• Bandwidth Guarantees:
  • Per VM/NIC: 100 Mbps to 10 Gbps, depending on service tier. Enforced via hypervisor-level QoS and vSwitch policies.
• Enforcement: Resource limits are managed through vSphere DRS, or SDN QoS rules at the hypervisor/network layer.

• Default: 1 Gbps is often shared per physical host or per tenant.
• Dedicated Option: Available on request per VM or per VLAN/port group. Can be increased to 10/25 Gbps with proper NIC configuration.

• Yes, vSphere (vCenter) and NSX-T offer RESTful APIs for:
  • VM provisioning
  • Network setup
  • Storage management

• Terraform: Supported via VMware vSphere and NSX-T providers.
• Ansible: Yes, modules for VM provisioning, snapshotting, and network automation are available.
  • e.g., community.vmware collection in Ansible Galaxy, can be provided, though currently not in use.

• In-region multi-AZ is supported if you have workloads spread across:
  • Physically isolated data halls or zones within the NTT campus, or
  • NTT’s multiple Mumbai DCs (e.g., DC5 + DC3).
• Multi-AZ is viable with stretched clusters (vSAN) or replication across DC’s, with proper network and latency consideration.

• Integrated Tools:
  • Integration with Prometheus + Grafana or Zabbix.
• Customer View: Dashboards for performance metrics, alerts, and usage via customer portal.

• Frequency: Daily incremental + Weekly full (default); customizable up to hourly for critical workloads.
• Retention: 7 days to 1 year or more (based on policy).
• Encryption: AES-256 in transit and at rest.
• Location: Backups are stored in-region (same NTT DC or offsite near DR – 50Kms)
• Remote DR – Optional remote far DR 500Kms another seismic zone available

Yes, with VMware Tools, VSS integration, and custom scripts.

• Supported apps: MySQL, MSSQL, MongoDB, etc.
• Supports quiescing for app-aware consistence
• Veeam Backup & Replication with application aware

• Supported via:
  • Asynchronous replication between NTT DCs.
  • Tools: Veeam Backup & Replication
• DR Drill: Yes, simulations can be scheduled and tested non-disruptively.

• Recovery Time Objective (RTO): 1-24 hours (depending on your DR setup)
• Recovery Point Objective (RPO): As low as 15 minutes (with near-sync replication).
• SLAs vary from 99.9% to 99.99% uptime, with specific DR restoration SLA defined in your MSA.

• Typical Cap: Liability capped at monthly service charges for the impacted service.
• Check MSA for:
  • Exclusions (e.g., force majeure, client mis configuration)
  • SLA credit eligibility clauses.

• Each region typically has:
  • L1: 24×7 NOC team (~5–10 per shift per region)
  • L2/L3: On-call or scheduled experts (shared pool; 2-4 per DC or pooled across NTT India)
• Dedicated SRM often available for managed clients like yours.

• Refresh Cycle: Every 3–5 years, depending on SLAs and client requirements.
• Failure Handling:
  • Hot-swap: NVMe, SSDs, NICs, memory
  • Cold-spare: For GPUs, CPUs, full server nodes
  • 24×7 onsite engineers from NTT

• vSphere APIs, and OVF Export available.
• Full automation optional for :
  • VM image export (OVF/VMDK)
  • Metadata (VMX configs, logs, perf stats)
  • Scripted via API or CLI

• Low lock-in: VM images compatible with OVF, VMDK, VHD formats
• Cloud portability: Can migrate to/from AWS, Azure, GCP with minor customization
• No proprietary hypervisor constraints if using standard VMware or KVM Proxmox

• NTT typically carries cyber liability insurance globally.
  • Coverage: $5M to $50M depending on country and contract
  • Inclusions: Data breaches, business interruption, third-party liabilities
• Confirm specific coverage with your NTT/partner MSA, mostly clients need to take their insurance for their capacity and needs.

• Instant rollback (without detach) depends on the stack:
  • VMware: No native instant revert unless you clone from snapshot
  • Better managed via Veeam for crash-consistent restore on running disks

• Supported with:
  • Anycast DNS
  • Integration with Cloudflare, Cdnflare or DynDNS
• NTT provides DNS integration via the above options.
• 30s switchover depends on DNS TTL + health checks.