Read-only snapshot comparison and Free WP-CLI backup, archive analysis, selective packaging, and migration planning tools.<\/li>\n<\/ul>\n\nOptional Pro edition<\/h4>\n\n
Automatic encrypted Google Drive and S3\/R2 uploads, authenticated delta package creation and advanced CLI staging-recovery commands are not included in this Free package. The dashboard shows small informational cards that link to https:\/\/indiatvdna.com\/ only when an administrator chooses to open them. No locked premium code, trial quotas, telemetry or license checks are included.<\/p>\n\n
Important security and scope<\/h4>\n\n
Archive size and record count have no artificial Free-edition paywall; provider\/server disk space, PHP, ZIP and database limits still apply. Backups can contain customer and credential data: store them securely, protect access, keep encryption passphrases offline and run a full test restore on staging before relying on disaster recovery. A local ZIP is not a complete server configuration snapshot. WordPress staging, multisite and WooCommerce restore compatibility depend on installation details and are not guaranteed without tests.<\/p>\n\n
External services<\/h3>\n\n
Local backup\/restore does not use any external service. External transfers are OFF unless the administrator explicitly configures and initiates them.<\/p>\n\n
Google Drive<\/h4>\n\n
When the administrator connects Google Drive, OAuth uses Google authorization and token services. A manually selected ZIP is locally AES-256-GCM encrypted before being sent over HTTPS to Google Drive under the administrator's account, with the limited drive.file scope. Google receives encrypted vault bytes and file metadata; the original ZIP remains on the WordPress server. OAuth credentials are stored with local encryption using WordPress salts. Disconnect stops new requests; previously uploaded files remain in the user's Google Drive. Google login may require a verified\/published OAuth client with allowed test users.\nService: https:\/\/drive.google.com\/\nPrivacy: https:\/\/policies.google.com\/privacy\nTerms: https:\/\/policies.google.com\/terms<\/p>\n\n
S3-compatible storage<\/h4>\n\n
An administrator may manually upload encrypted vault files to a chosen S3-compatible provider, whose identity, endpoint, privacy terms and cost are selected\/configured by the site owner. Encrypted vault content and object metadata go directly to that provider only when requested. The plugin itself is not a cloud-storage service.\nAmazon S3: https:\/\/aws.amazon.com\/s3\/ ; Privacy: https:\/\/aws.amazon.com\/privacy\/\nCloudflare R2: https:\/\/www.cloudflare.com\/developer-platform\/r2\/ ; Privacy: https:\/\/www.cloudflare.com\/privacypolicy\/<\/p>\n\n
IndiaTVDNA website<\/h4>\n\n
The plugin includes optional View Pro cards and a small Buy Pro Version link in the plugin-owned admin page header, pointing to https:\/\/indiatvdna.com\/. No information is sent to that site unless the administrator explicitly clicks a link.<\/p>\n\n
Source code and build instructions<\/h3>\n\n
The plugin is distributed as human-readable source code. All PHP is shipped in\nthis ZIP. assets\/admin.js is shipped as editable JavaScript, with a separately formatted\nhuman-readable equivalent at assets\/admin.source.js; assets\/admin.css is editable.\nNo transpiler, minifier or external build tools are needed. There is no hidden\nsource repository dependency and the distributed JavaScript can be edited directly.\nStandalone PHP CLI-only database\/disaster-recovery scripts are provided separately\nas optional offline tools and are not installed into a public web directory.<\/p>\n\n
Backup storage safety<\/h3>\n\n
New installations use a dedicated vault inside the WordPress uploads directory resolved via wp_upload_dir(), under indiatvdna-backup-restore. Before creating or transferring any unencrypted backup, the plugin checks that a direct HTTP request cannot read a random probe file from the vault. If a host ignores .htaccess (for example, many Nginx configurations), the plugin blocks new backups until the site administrator configures server-level access denial. Existing user-configured private vault paths and backups are retained. The plugin cannot guarantee every host's restore permissions. All core\/plugin\/theme filesystem restores must be explicitly initiated by an administrator and may fail on read-only hosts. Use a separate staging installation to verify restores. Never expose downloaded unencrypted backup ZIPs publicly.<\/p>\n\n\n
\n- Upload and activate the plugin. Open the Backup & Restore menu in WordPress admin.<\/li>\n
- Select components, make a local backup and run verification before depending on it.<\/li>\n
- Use Restore \/ Migrate to preview and restore on a separate staging site first.<\/li>\n
- Optionally configure Google Drive with your own Google Cloud OAuth Web application, correct HTTPS Redirect URI and a separate 16+ character offline-kept passphrase. Explicitly accept upload privacy notice, then initiate uploads manually.<\/li>\n
- For manual S3\/R2 operations you must configure your own S3-compatible credentials and encryption settings in private server configuration.<\/li>\n<\/ol>\n\n\n
\nCan I back up and restore without paying?<\/h3><\/dt>\nYes. Full and selective local backup and restore work without a license or cloud service.<\/p><\/dd>\n
Are there upload size limits in Free?<\/h3><\/dt>\nNo premium paywall quotas. Hosting, filesystem and third-party limits still apply.<\/p><\/dd>\n
Is Google Drive automatic in Free?<\/h3><\/dt>\nNo. Google Drive upload is manually initiated in Free after the administrator connects and consents.<\/p><\/dd>\n
Do I need a paid cloud account?<\/h3><\/dt>\nNo provider account is required for local backups. Remote storage accounts can have provider-imposed usage or charges.<\/p><\/dd>\n
Can I restore directly from Google Drive?<\/h3><\/dt>\nNo. Download the vault through Google Drive, import\/decrypt in Vault & Cloud, then verify and restore the ZIP. Keep the passphrase safe.<\/p><\/dd>\n
Is every server setting included?<\/h3><\/dt>\nNo. Back up wp-config.php, .htaccess and other sensitive server configuration separately.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.7<\/h4>\n\n\n- Resolve uploads, core, plugins and content directory paths centrally; use the actual configured uploads path during restore.<\/li>\n
- Default new vaults to a dedicated uploads\/indiatvdna-backup-restore directory and refuse unverified public backups.<\/li>\n
- Keep core-restore staging under the managed vault; stop generating IIS web.config files.<\/li>\n
- Preserve existing backups, legacy vault configuration and ZIP archive entry names.<\/li>\n<\/ul>\n\n
1.0.6<\/h4>\n\n\n- Use the WordPress core debug-reporting helper when available instead of the PHP error_log() function for a recoverable storage-metadata migration warning.<\/li>\n
- Keep WordPress 6.2\/6.3 compatibility, never report with debugging off, and avoid throwing during error reporting. Existing backup paths and file-storage behavior are unchanged.<\/li>\n<\/ul>\n\n
1.0.5<\/h4>\n\n\n- Make storage metadata migration deferred and fail-safe instead of running filesystem writes during WordPress plugin loading.<\/li>\n
- Preserve existing backups, signed storage metadata, and legacy upgrades.<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Store the signed recovery backup-location marker in a private plugin-specific uploads directory instead of writing to wp-content. Preserve and migrate older markers without moving existing backups.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Moved the durable storage-location marker to a non-executable file; safely reads and migrates the old PHP marker without changing the private backup path. Recovery job markers now commit atomically.<\/li>\n
- Escaped all dynamic diagnostic labels and server data in dashboard-generated HTML.<\/li>\n
- Removed obsolete edition-specific option filtering while preserving existing Google Drive consent, nonce and account requirements.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Removed the Google Drive Free\/Pro background-worker entitlement gate; encryption and administrator consent remain mandatory.<\/li>\n
- Switched legacy admin-menu compatibility CSS and JavaScript to WordPress enqueue and inline APIs.<\/li>\n
- Stopped creating executable PHP in mu-plugins during restore; private recovery markers and staged runtime isolation remain. High-risk restores require staging verification.<\/li>\n
- Moved independent offline-only CLI recovery scripts out of the public plugin archive into a separate optional package.<\/li>\n
- Documented readable JavaScript source and the no-build source workflow.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Corrected Google Drive permission-message translation domain and the Free edition privacy-policy title.<\/li>\n
- Improved direct-web-access protection for the then-bundled offline recovery scripts, explicit AJAX nonce checks, input validation and readme formatting.<\/li>\n
- Added a single, discreet Buy Pro Version link to the header of the plugin's own admin screens (including diagnostics). No outside requests are made without a click.<\/li>\n
- No changes to the backup, restore, security or cloud engines.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First Free release candidate. Functional local backup and restore, manual encrypted cloud tools and Google Drive OAuth kept. Premium-only automatic cloud scheduling, delta-package creation and staging CLI engine omitted.<\/li>\n<\/ul>","raw_excerpt":"Create full and selective WordPress backups, verify ZIP files, restore data, and optionally upload encrypted copies to Google Drive.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/392660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=392660"}],"author":[{"embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/indiatvdna"}],"wp:attachment":[{"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=392660"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=392660"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=392660"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=392660"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=392660"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/da.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=392660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}