A staging site is a separate testing environment that mirrors your live multisite setup. It allows you to safely test updates, changes, or new features without affecting your live network.

Supported Multisite Configurations

WPvivid Staging Pro supports:

• 1. Entire Multisite Network Staging:
  Creates a staging copy of the full Multisite network (only subdirectory Multisite is supported).
• 2. Individual Subsite Staging:
  Creates a staging site for a specific network subsite. Subsites are supported in both subdomain and subdirectory multisite setups.

Before You Begin

Prior to creating a staging site:

• 1. Temporarily deactivate caching plugins to avoid conflicts during the staging process.
• 2. Ensure sufficient server resources (memory, execution time，disk space) to handle staging operations.
• 3. Create a backup of your live multisite before staging, especially on large networks.

Steps to Create a Staging Site for Multisite

1. Access the Staging Creation Interface

• 1. Log in to your WordPress admin dashboard.
• 2. Navigate to WPvivid Plugin > Staging Sites tab.
• 3. Click the Create A Staging Site button.

2. Configure Staging Target

Naming & Directory

• 1. Enter a folder name where the staging site will be installed under your WordPress installation.
• 2. This name also becomes part of the staging site’s URL.

Database Options

When choosing where to install the staging database:

• 1. Use the same database as live site (recommended)
• 2. Use a separate database (requires database credentials — database name, username, password, and host)

3. Select Content to Copy

Next, choose what content from the live multisite you want to copy:
Option A — Single Subsite Staging

• 1. Choose a specific subsite within the network.
• 2. You can search for the desired subsite if your network contains many.
• 3. After selecting a subsite, choose what to include:
  – Entire database and WordPress files by default
  – Customize by excluding specific tables or folders (e.g., themes, plugins, uploads)

To exclude content:

• 1. Expand Exclude Additional Files/Folders.
• 2. Choose a directory (e.g., /themes, /plugins), and select files/folders to exclude。

Option B — Entire Multisite Network Staging

• 1. Select to clone the entire WordPress multisite network.
• 2. This option is only available for Multisite networks using the subdirectory structure.
• 3. You can:
  – Copy the entire MU database
  – Exclude specific files/folders
  – Select specific subsites to include or copy all subsites

4. Create the Staging Site

When your selections are complete:

• 1. Click Create Now to begin the staging process.
• 2. Monitor progress via the dashboard — this can take time depending on site size and server performance.

Once the process is complete, a success message will be displayed.

Post-Creation Management

Once successful, your new environment will appear in the Staging Sites tab.

• 1. Accessing the Site:
  You will find the Staging Site URL and Admin URL. Your login credentials will match those of your live site.
• 2. Available Actions: From the management dashboard, you can:
  – Push to Live: Deploy your changes back to the production network.
  – Update Staging: Sync your staging site with the latest data from the live site.
  – Delete: Completely remove the staging site and its associated database tables.

Supported Multisite Restore Scope

Currently, WPvivid Backup & Migration Pro supports full multisite network restoration.

Supported Restore Type

WPvivid Backup & Migration Pro supports the following multisite restore operation:

• Full Network Restore
  Restores the entire multisite environment, including all subsites, database tables, plugins, themes, and uploads.

Unsupported Restore Scenarios (Current Limitation)

The following restore operations are not supported in the current version:

• Single Subsite Restore
  Restoring one subsite independently from a multisite backup is not supported.
• Cross-Type Restore
  Restoring backups of single-site WordPress installations to multisite is not supported.

What Gets Restored in Multisite Mode

When performing a multisite restore, WPvivid Backup & Migration Pro replaces the existing multisite environment with data from the selected backup.

The restore process includes:

• Network Database Tables
  All multisite database tables, including network settings and subsite data.
• All Subsites Content
  Posts, pages, media, users, and metadata from every site in the network.
• Plugins and Themes
  Network-activated and site-activated plugins and themes.
• Uploads and Media Files
  All media files stored across the multisite environment.
• Network Configuration
  Network settings, subsite configurations, and WordPress core files.

Restoring a WordPress Multisite Network Backup

WPvivid Backup & Migration Pro allows you to restore complete multisite network backups from the Network Admin dashboard. The restoration process replaces the entire multisite network with the backup data.

Step 1: Locate the Backup

• Navigate to My Sites → Network Admin → WPvivid Backup Pro → Backup Manager.
• Locate the multisite backup you want to restore in the backups list.
• Click the Restore icon (circular arrow) in the Actions column.

Step 2: Select Restore Content

• Review the Folders & Files section and select the file components you want to restore.
• Review the Database(s) section and select the database tables you want to restore.
• By default, all components are selected. Uncheck any components you do not want to restore.
• Click the dropdown arrows to view detailed file lists if needed.

Step 3: Execute the Restoration

• Click Restore Now to begin the restoration process.
• WPvivid will extract and restore the selected components to your multisite network.
• Monitor the progress bar as the restoration completes.
• Do not close the browser window or navigate away during the restore operation.

Step 4: Verify Restoration

• Once completed, you will see a success message confirming the restoration.
• Verify that all subsites are accessible and functioning correctly.
• Test critical network features and subsite functionality.

Known Limitations

Current multisite restore limitations include:

• Full Network Restore Only
  Restoring individual subsites from a multisite backup is not supported. The restore process applies to the entire network.
• Subdirectory Structure Required
  Restores are only supported for subdirectory-based multisite networks. Subdomain-based configurations cannot be restored using WPvivid Backup & Migration Pro.
• Network Admin Access Required
  Multisite restore operations must be performed from the Network Admin dashboard. Individual site administrators cannot initiate or manage network restores.
• Same Network Type Required
  The backup must be restored to a multisite environment with the same network structure (subdirectory-based) as the original backup source.

Best Practices for Multisite Restore

For safe and reliable multisite recovery, follow these best practices:

• Test restores in a staging environment before performing them on production networks.
• Keep multiple backup versions available for different recovery points.
• Store backups on remote cloud storage to protect against server failures.
• Verify all subsite functionality and network settings after restore completion.
• Clear all caches and check permalinks across all subsites after restoration.

What Is Multisite Childsite Migration

WPvivid Backup & Migration Pro supports migrating an individual site (childsite) within a WordPress Multisite network to a separate single-site WordPress installation.

This feature is useful when you want to extract a subsite from a multisite network and run it independently as a standalone WordPress site.

Before Migration

Before migrating a childsite, ensure the following requirements are met:

• Prepare Target Installation
  Ensure the target single site is a fresh WordPress installation ready to receive the childsite data.
• Install WPvivid on Both Sites
  WPvivid Backup & Migration Pro is installed and activated on both the source multisite network admin and the destination single-site installation.
• Deactivate Security Plugins
  Temporarily deactivate security and caching plugins on both sites, as they may write absolute paths that can interfere with migration.

How to Migrate a Multisite Childsite

Follow these steps to migrate a childsite from a multisite network to a standalone WordPress installation.

Step 1: Export the Childsite from Source Multisite

• Go to the source multisite’s Network Admin
• In WPvivid Plugin → Export Site, click Export to Localhost (Web Server).
• In the Backup Content section, select For the purpose of moving a subsite to a single install.
• Enter a subsite title in the search field, or click Search directly to display all available subsites.
• Select the childsite you want to migrate from the list.
• Optionally add a comment for identification purposes.
• Click Export Now.

Step 2: Download the Export Files

• After the export completes, you will see a successful message.
• Click the Download All Parts button to download the backup files to your computer.
• Keep all downloaded files together in the same location if the backup is split into multiple parts.

Step 3: Upload to Target Single Site

• Go to the target single site.
• In WPvivid Plugin → Import Site, click Import from Localhost (Web Server).
• Click Select Files or drag and drop all exported ZIP files into the upload field.
• Ensure all parts are uploaded at the same time if the backup is split into multiple files.
• Click Upload.

Step 4: Restore the Childsite

• After successful upload, you will see a successful message.
• Click Restore Now in the message to begin the restoration process.
• Wait for the restoration to complete.
• Verify the site is functioning correctly as a standalone WordPress installation.

What Gets Migrated

When migrating a childsite to a single install, WPvivid transfers:

• Childsite Database
  All posts, pages, users, settings, and metadata specific to the selected childsite.
• Childsite Content
  Media uploads, custom content, and site-specific data from the childsite.
• Themes and Plugins
  Active themes and plugins used by the childsite.
• Site Configuration
  Childsite-specific settings and configurations (wp-config.php is not overwritten on the target site).

After-Migration Steps

After completing the childsite migration:

• Verify Site Functionality
  Test all pages, posts, media, forms, and critical features to ensure they work correctly.
• Clear Caches
  Clear all caching plugins if any and server-level caches to ensure fresh content delivery.
• Reactivate Security Plugins
  If you deactivated security plugins before migration, reactivate them on the single-site installation.

Best Practices for Childsite Migration

For a successful childsite migration, follow these best practices:

• Perform a test migration in a staging environment before migrating to production when possible.
• Migrate to a fresh WordPress installation to avoid data conflicts and compatibility issues.
• Keep the source multisite network active until you have fully verified the migration was successful.
• Test all site functionality thoroughly after migration, including forms, media, plugins, and integrations.
• Ensure the target server has sufficient resources (disk space, memory, bandwidth) to handle the childsite independently.

Supported Multisite Migration Scope

Currently, WPvivid Backup & Migration Pro supports migration of full multisite network that uses a subdirectory structure, or migration of a subsite in a multisite network to a single-site WordPress installation.

Supported Migration Type

WPvivid Backup & Migration Pro supports the following multisite migration scenario:

• Full Network Migration
  Migrates the entire multisite environment, including all subsites, network settings, plugins, themes, uploads, and database tables.
• Multisite Subsite to Single-Site Migration
  Migrates a subsite in a multisite network to a standalone WordPress installation.

Unsupported Migration Scenarios (Current Limitation)

The following migration scenarios are not supported in the current version:

• Migration Between Subsites
  Migration between individual subsites in the same or different multisite networks is not supported.
• Subdomain Multisite Migration
  Multisite networks using subdomain structures are not supported.
• Single-Site to Multisite Migration
  Migrating a single-site WordPress installation to a multisite network is not supported.

Before Migration

Before starting a multisite migration, ensure the following conditions are met:

• Network Compatibility
  A fresh WordPress multisite installation that uses subdirectory structure is set up on the destination site
• WPvivid Activation
  WPvivid Backup & Migration Pro is installed and activated in Network Admin of both multisite networks

How to Migrate a WordPress Multisite Network

Follow these steps to migrate a complete WordPress Multisite networks.

Step 1: Export from Source Site

• Go to the source site’s Network Admin.
• In WPvivid Plugin → Export Site, choose Export to Localhost (Web Server).
• Select the content you want to migrate.
• Optionally add a comment for identification.
• Click Export Now.

Step 2: Download Export Files

• After the export completes, click Download Now to download all backup files to your computer.
• Keep all downloaded files together in the same location.

Step 3: Upload to Target Site

• Go to the target site’s Network Admin.
• In WPvivid Plugin → Import Site, choose Import from Localhost (Web Server).
• Click Select Files or drag and drop all exported ZIP files into the upload field.
• Ensure all parts are uploaded at the same time if the backup is split into multiple files.
• Click Upload.

Step 4: Restore the Multisite Network

• After successful upload, you will see a successful message.
• Click Restore Now in the successful message to complete the migration.
• Wait for the restoration to finish.

Best Practices for Multisite Migration

For a successful and safe multisite migration, follow these best practices:

• Keep Source Site Active
  Do not delete or modify the source site until you have fully verified the migration was successful and all subsites are functioning correctly on the target site.
• Ensure Sufficient Server Resources
  Verify the destination site has adequate disk space, memory, and bandwidth to handle the entire multisite network. Large networks require substantial storage for all subsites’ files and databases.
• Use Fresh Multisite Installation
  Always migrate to a fresh WordPress Multisite installation to avoid compatibility issues, conflicts, and data corruption. The target site should be a clean multisite setup with no existing subsites or content.
• Match Server Environments
  Ensure both source and destination sites use compatible versions of WordPress, PHP, and MySQL/MariaDB. Version mismatches can cause migration failures or functionality issues.
• Temporarily Disable Security Plugins
  Deactivate security plugins like Wordfence before migration, as they may write absolute paths that interfere with the migration process.

What Is Multisite Backup

WPvivid Backup & Migration Pro provides basic backup support for WordPress Multisite networks, enabling administrators to create full backups of the entire multisite network environment, including all subsites, network data, and shared resources.

This feature is designed to protect complete multisite installations and simplify disaster recovery for network administrators.

Supported Multisite Configuration

Currently, WPvivid Backup & Migration Pro supports specific multisite setups.

Supported Network Type

WPvivid Backup & Migration Pro supports multisite networks that use the following structure:

• Subdirectory-based Multisite
  Example format: example.com/site1

This configuration stores all subsites under the main domain using directory paths and is fully compatible with WPvivid’s multisite backup engine.

Unsupported Network Type (Current Limitation)

The following multisite configurations are not supported in the current version:

• Subdomain-based Multisite
  Example format: site1.example.com

Where WPvivid Backup & Migration Pro Works in Multisite

In WordPress Multisite environments, WPvivid Backup & Migration Pro operates exclusively at the network administration level.

To access WPvivid Backup & Migration Pro in a multisite environment:

• 1. Open WordPress Admin.
• 2. Click My Sites → Network Admin.
• 3. Open WPvivid Plugin.

What Gets Backed Up in Multisite Mode

When performing a multisite backup, WPvivid Backup & Migration Pro creates a complete network-wide backup package.

The backup includes:

• Network Database Tables
  All multisite database tables, including network settings and subsite data.
• All Subsites Content
  Posts, pages, media, users, and metadata from every site in the network.
• Plugins and Themes
  Network-activated and site-activated plugins and themes.
• Uploads and Media Files
  All media files stored across the multisite environment.
• Core Site Files
  Shared WordPress core files and configuration-related data.

Backing Up a WordPress Multisite Network

WPvivid Backup & Migration Pro processes multisite backups at the network level.

Step 1: Accessing Multisite Backup Features

• 1. Navigate to My Sites → Network Admin → WPvivid Plugin.
• 2. Access either Manual Backup or Backup Schedule to configure network-wide backups.

Step 2: Creating a Manual Multisite Backup

• 1. Go to Network Admin → WPvivid Plugin → Manual Backup.
• 2. Configure your backup settings including backup location and content type.
• 3. Optionally add a comment to identify the backup.
• 4. Click Backup Now to start the network backup process.

The backup will include all sites within the Multisite network along with their databases, themes, plugins, and uploaded content.

Step 3: Scheduling Multisite Backups

• 1. Go to Network Admin → WPvivid Plugin → Backup Schedule.
• 2. Choose between General Backup or Incremental Backup tabs.
• 3. Click Create a job to set up automated network backups.
• 4. Configure backup type, schedule frequency, and storage location.
• 5. Enable the schedule using the On/off toggle.

Scheduled backups will automatically back up your entire Multisite network according to the configured schedule.

Known Limitations

Current multisite backup limitations include:

• Subdirectory Structure Only
  Only subdirectory-based multisite networks are supported. Subdomain-based multisite configurations are not compatible.
• Network Admin Access Required
  Multisite operations must be managed from the Network Admin dashboard. Individual site administrators cannot access multisite backup features.
• Network-Level Backups Only
  Backing up individual subsites separately is not supported. All backups include the entire multisite network.
• Selective Subsite Restore
  Restoring a single subsite independently from a multisite backup is not supported. Restores apply to the entire network.

Best Practices for Multisite Backup

For reliable multisite protection, follow these best practices:

• Enable scheduled backups to maintain consistent recovery points.
• Store backups on remote cloud storage.
• Maintain multiple backup versions.
• Periodically test restore operations in a staging environment.
• Monitor backup logs for failed or incomplete tasks.

What Is Database Merging

WPvivid Database Merging Pro allows you to merge only the changes (uploads/media files and database) from a development site back to a live production site, without losing existing data on the production site.

This plugin is designed to solve a common development challenge: when you copy a live site to a development environment to make changes, the live site continues to receive new data (orders, form submissions, user registrations, content updates). Traditional migration methods would overwrite the live site and erase all new data that arrived while you were working on the development site.

Typical Usage Scenario

The most common use case for database merging involves e-commerce sites or any site where content is frequently updated:

• You copy your live WooCommerce site to a development environment.
• While you make design changes on the development site, the live site continues receiving new data: orders, contact form submissions, membership subscriptions, product updates, comments, etc.
• After finishing your development work, you need to push your changes to live without losing any of the new data that arrived on the live site.

WPvivid Database Merging Pro tracks all changes made on the development site and merges only those changes to the production site, preserving existing production data.

What Gets Recorded and Merged

WPvivid Database Merging Pro tracks specific types of changes:

Recorded Changes

• Database Changes
  All database queries and modifications made on the development site, including new posts, pages, settings, and custom data.
• Uploads and Media Files
  New media files added to the uploads folder during development.

Changes Not Recorded

• Theme Files
  Theme modifications are not tracked. Both sites must use the same theme version.
• Plugin Files
  Plugin changes are not tracked. Both sites must have identical plugins and versions.
• WordPress Core Files
  Core WordPress files are not tracked. Both sites must run the same WordPress version.

Prerequisites for Database Merging

Before using database merging, complete the following preparation steps:

1. Install WPvivid Database Merging Pro

• Install and activate WPvivid Database Merging Pro on both your development site and production site.
• Set each site’s role as either “Dev Site” or “Prod Site” in the plugin settings.

2. Connect Development Site to Production Site

• On the production site, go to WPvivid Merging and click Generate a key for creating connection with dev site.
• Copy the generated connection key.
• On the development site, go to WPvivid Merging, paste the key, and click Connect.

3. Install WPvivid Backup Plugin (Recommended)

• Install the free WPvivid Backup Plugin on both sites.
• This allows you to create snapshots before recording tasks or merging operations.
• Snapshots provide quick recovery options if something goes wrong during the merging process.

Initial Database Synchronization

Before starting database recording, perform an initial synchronization to ensure both sites have matching data.

Step 1: Migrate Production Files to Development Site

• Before syncing databases, migrate files from the production site to the development site.
• You can use WPvivid Backup Plugin (free version) for migration.
• Alternatively, copy the entire production site (files + database) to development to skip the initial database synchronization step.

Step 2: Synchronize Development Database with Production Database

• After files are copied to the development site, go to WPvivid Merging on the development site.
• Click Pull DB from Prod to Dev to start synchronization.
• Wait for the synchronization to complete.

This ensures both databases start from the same baseline before you begin recording changes.

Understanding Database Recording

What Is A Database Recorder?

A database recorder is automatically created and enabled when you create a database recording task. It tracks all changes including media files and database queries on the development site.

What Is A Database Recording Task?

A database recording task contains the full lifecycle of a database recording session. It allows you to merge all recorded changes (files + database queries) to the production site.

Key benefits of the task system:

• You don’t need to re-sync databases after every merge.
• You can perform multiple merges from a single recording task.
• You only need to sync databases after completing multiple merges, saving significant time.

A task is automatically terminated and marked as “Merged” after a successful merge. You can then create a new task as needed.

Creating A Database Recording Task

Once the development database is synchronized with the production database, you can start recording changes.

Step 1: Create the Task

• On the development site, go to WPvivid Merging.
• Click Create A Database Recording Task.
• Check the option Create a snapshot for dev site (highly recommended).
• This creates an automatic snapshot of the development site using WPvivid Backup Plugin.
• Wait for the task creation to complete (may take a few minutes depending on database size and number of plugins/themes).

Step 2: Monitor the Recording Task

Once created, the task will be automatically enabled and will appear in the Tasks section. You can:

• Enable or disable the task as needed.
• View the task start time and elapsed running time.
• See how many database queries have been recorded.
• See how many files have been added.
• Perform database merging operations.

Merging Changes to Production Site

When you’re ready to merge recorded changes from development to production:

Step 1: Prepare for Merge

• On the development site, go to WPvivid Merging → Tasks section.
• Locate your active recording task.
• In the Merge to dropdown, select Production Site.

Step 2: Configure Merge Options

• Choose what to merge: Database and Files, Files only, or Database only
• Check the option Create a snapshot for your production site before merging (highly recommended).

Step 3: Execute the Merge

• Click Merge Now to start the merging process.
• Wait for the merge to complete.
• Do not close or refresh the page during merging, as this will cause the merge to fail and may bring sites down.

Step 4: Verify Merge Success

• After the merge completes, verify that changes appear correctly on the production site.
• Check that existing production data remains intact.
• Test critical functionality to ensure everything works as expected.

Best Practices for Database Merging

For safe and effective database merging operations:

• Create Snapshots Before Major Operations
  Use WPvivid Backup Plugin to create snapshots before creating recording tasks or performing merges.
• Monitor Recording Tasks Regularly
  Check task statistics periodically to ensure recording is working correctly.
• Merge Changes Regularly
  Avoid running recording tasks for extended periods. Large volumes of accumulated changes increase the risk of merge failures and longer processing times.

Important Limitations

• Only Uploads and Database Changes Merged
  To avoid conflicts during merging, the plugin only records uploads (media files) and database changes. It does not record changes to themes and plugins.
• Environment Synchronization Required
  To prevent conflicts and ensure successful merging, the production and development sites must maintain identical environments for themes, plugins, and WordPress versions before a merging process.

What is the Debug Page

The Debug page in WPvivid Backup Pro provides a centralized view of your website’s environment, server configuration, and system runtime parameters. This information is primarily used for diagnostics, compatibility validation, and performance troubleshooting during backup, migration, and restore operations.

Common Use Cases

The Debug page is commonly used in the following scenarios:

• Investigating backup or migration failures
• Validating server environment compatibility
• Preparing diagnostic reports for technical support
• Auditing hosting resource limits before large backup operations

Accessing Debug Information

To access the Debug panel in WPvivid Backup Pro:

• Navigate to WPvivid Backup Pro → Debug
• The Debug Information table will be displayed automatically.

Understanding Debug Information

The Debug Information table is divided into multiple logical sections that reflect your WordPress installation, hosting environment, and runtime configuration.

Website Information

Displays core website and WPvivid plugin configuration details.

• version
  Shows the currently installed WPvivid Backup Plugin version.
• home_url
  Displays the website home URL configured in WordPress.
• abspath
  Shows the absolute path to the WordPress root directory.
• wp_content_path
  Displays the full server path to the wp-content directory.
• wp_plugin_path
  Shows the directory path where WordPress plugins are installed.
• wp_prefix
  Displays the database table prefix used by the WordPress installation.

Server Environment Information

Provides details about the hosting server and operating system environment.

• web_server
  Displays the web server software and version running on the host.
• OS
  Shows the operating system and kernel information of the server.
• fast_cgi
  Indicates whether FastCGI processing is enabled.

PHP Environment Configuration

Displays PHP runtime configuration values that affect backup and migration performance.

• php_version
  Shows the current PHP version running on the server.
• max_execution_time
  Displays the maximum allowed script execution time.
• max_input_vars
  Shows the maximum number of input variables PHP can process.
• upload_max_filesize
  Defines the maximum file upload size allowed by PHP.
• post_max_size
  Displays the maximum POST request size limit.
• allow_url_fopen
  Indicates whether remote file access is enabled.

Database Environment Information

Provides details about the database engine and database driver support.

• mysql_version
  Displays the MySQL or MariaDB server version.
• pdo_mysql
  Indicates whether the PDO MySQL extension is supported.
• mysql_mode
  Shows the active SQL operation mode configuration.

WordPress Environment Settings

Displays WordPress runtime configuration parameters.

• multisite
  Indicates whether WordPress Multisite mode is enabled.
• language
  Shows the site language setting.
• wp_debug
  Displays the WordPress debug mode status.
• timezone
  Shows the WordPress timezone configuration.

Active Plugins Information

Displays a list of all active plugins currently enabled on the website.

• active_plugins
  Lists plugin directories and main plugin files currently loaded by WordPress.

This information is useful when diagnosing compatibility issues or identifying plugin conflicts.

System Resource Usage

Displays PHP memory allocation and runtime usage information.

• memory_limit
  Shows the PHP memory limit assigned to the website.
• memory_current
  Displays the current memory usage.
• memory_peak
  Shows the highest memory usage reached during execution.

Server Extensions and Modules

Displays enabled PHP extensions and web server modules required for WPvivid operations.

• extensions
  Lists all active PHP extensions.
• apache_modules
  Displays enabled Apache server modules.
• PclZip
  Indicates availability of the ZIP compression fallback library.

Downloading Debug Information

WPvivid Backup Pro allows exporting Debug Information for support and diagnostics.

To download debug data:

• Scroll to the bottom of the Debug page.
• Click the Download button.
• A debug report file will be generated and saved locally.

This file can be provided to WPvivid support for further investigation.

Security and Privacy Considerations

The Debug page displays sensitive system information including server paths, environment configuration, and plugin lists.

For security reasons:

• Do not share debug exports publicly
• Only provide debug files to WPvivid official support
• Store downloaded debug files securely

Proper handling of debug information helps prevent unintended exposure of server configuration data.

What Is Logs Section of Staging Pro

The Logs section in WPvivid Staging Pro provides a centralized activity history for all staging-related operations, including staging site creation, updating, and deployment (pushing a staging site to live) actions. It helps administrators monitor staging task execution, identify errors, and verify successful operations.

Use Cases for Logs

Staging logs are useful for:

• Troubleshooting staging creation failures
• Debugging staging updates or deployment issues
• Providing diagnostic information to WPvivid support
• Auditing staging activity history

Accessing Logs

To view staging log records in WPvivid Staging Pro:

• Navigate to WPvivid Plugin → Staging Sites.
• Click the Staging Log tab.

The Logs interface displays all recorded staging operations in a structured table for easy review and management.

Log Information Displayed

Each staging log entry contains detailed operation metadata to help you understand what occurred during the staging process.

• Date
  Displays the timestamp when the staging operation started.
• Log File Name
  Shows the automatically generated log file associated with the staging task.
• View
  Provides quick access to view the staging log details directly in the browser.
• Download
  Allows you to download the complete staging log file for offline analysis or support troubleshooting.

Viewing Log Details

To view a staging log entry:

• Locate the desired staging log record.
• Click the Log icon under the Action column.

The system will display the full execution output, including staging progress steps, file operations, database processing status, warnings, and error messages.

Downloading Log Files

To download a staging log file:

• Find the staging log entry you want to export.
• Click the Download icon in the Download column.

Downloaded staging logs can be attached to support tickets or archived for auditing and troubleshooting purposes.

What Is Logs Section

The Logs section in WPvivid Backup & Migration Pro provides a centralized activity history for all backup, restore, and migration operations. It helps administrators monitor task execution, troubleshoot issues, and verify successful operations.

Use Cases for Logs

Logs are useful for:

• Debugging performance or timeout issues
• Providing diagnostic information to support teams
• Identifying failed backup or migration tasks
• Auditing site backup activity

Accessing Logs

To view log records in WPvivid Backup & Migration Pro:

• Navigate to WPvivid Backup Pro → Backup Manager.
• Click the Logs tab.

The Logs interface displays all recorded operations in a structured table for easy management and review.

Log Information Displayed

Each log entry contains detailed operation metadata to help you understand what occurred during the task.

• Date
  Displays the timestamp when the operation started.
• Log Type
  Indicates the operation category, including Backup, Restore, and Transfer (Migration).
• Log File Name
  Shows the automatically generated log file associated with the task.
• Action
  Provides quick access to view the log details directly in the browser.
• Download
  Allows you to download the full log file for offline analysis or technical support purposes.

Viewing Log Details

To view a log entry:

• Locate the desired log record.
• Click the Log icon under the Action column.

The system will display the complete execution output, including task progress, warnings, errors, and completion status.

Downloading Log Files

To download a log file:

• Find the log entry you want to export.
• Click the Download icon in the Download column.

Downloaded logs can be shared with WPvivid support or stored for auditing and troubleshooting purposes.

Filtering Logs

WPvivid Backup & Migration Pro includes built-in filtering tools to help manage large log histories efficiently.

Task Filter

The Task Filter allows you to narrow log results based on task type:

• Backup
  Displays logs of backup tasks
• Restore
  Display logs of restore tasks
• Transfer
  Displays logs of transfer (migration) tasks

Status Filter

The Status Filter allows you to narrow log results based on execution outcome:

• All
  Displays all logs
• Succeeded only
  Shows only successfully completed operations
• Failed only
  Displays failed tasks for troubleshooting

Search and Filter Bar

The Search bar enables quick filtering based on selected criteria.

To filter logs:

• 1. Select your preferred filter option
• 2. Click the Search button.

Only log entries matching your filter rules will be displayed.

Accessing Advanced Settings

To access the Advanced Settings panel in WPvivid Backup Pro:

• Navigate to WPvivid Backup Pro → Settings → Backup (Advanced)
• You will see advanced backup performance and behavior parameters ready for configuration.

Advanced Settings Explanation

Learning Mode

Optimize backup and migration processes for servers with limited resources.

• Learning Mode
  Automatically adjusts processing behavior to improve task success rates on restrictive hosting environments. Enabling this mode may increase overall backup or migration duration.

Auto Delete Backup Logs

Control automatic cleanup of backup log files.

• Auto Delete Backup Logs
  Automatically removes backup log files when the associated backup files are deleted, helping reduce server storage usage.

Large Database Mode

Optimize processing for websites with large databases.

• Large Database Mode
  Improves database export and import stability by adjusting processing parameters for large database tables.

Large Uploads Mode

Improve backup performance for sites with large media libraries.

• Large Uploads Mode
  Optimizes backup performance when processing large upload directories. This mode requires the ZipArchive PHP extension and does not support PclZip.

Database Access Method

Select how WPvivid accesses your WordPress database during backup and migration operations.

• WPDB (Default)
  Uses WordPress native database functions. Provides maximum compatibility but may be slower for large databases.
• PDO (Recommended)
  Uses the PHP PDO extension for faster database processing. Requires the pdo_mysql extension to be installed on your server.

Backup Compression Method

Configure how WPvivid compresses backup archives.

• ZipArchive (Default)
  Provides faster compression performance and better compatibility. Requires the PHP ZIP extension.
• PclZip
  A stable fallback compression method included in WordPress core. WPvivid automatically switches to this method if ZipArchive is unavailable.

Backup Performance Mode

Adjust how aggressively WPvivid uses server resources during backup creation.

• Low (Balanced)
  Minimizes server resource usage. Best for shared hosting or limited environments. Backup files are split into smaller parts for improved stability.
• Mid (Standard)
  Provides a balanced combination of speed and stability. Recommended for most hosting environments.
• High (Accelerated)
  Uses more server resources to reduce backup time. Recommended for VPS or dedicated servers. Backup files are split into larger parts.
• Custom (Advanced)
  Unlocks advanced backup processing parameters for manual configuration.

Custom Backup Processing Settings

Manually configure advanced backup parameters for complex hosting environments and large websites.

• The number of files compressed to the backup zip each time
  Defines how many files are compressed into the backup ZIP file during each processing cycle. The default value is 500. Lower values improve backup stability and success rate but increase overall backup duration. If backup timeouts occur, try reducing this value.
• Split a backup every this size
  Splits large backups into multiple parts to avoid hosting ZIP file size limitations. Setting this value to 0MB automatically splits backups every 4GB. Reducing this value can significantly improve success rates on servers with limited execution time or disk I/O performance.
• The number of database tables compressed to each zip
  Defines how many database tables are included in each ZIP segment during the backup process. The default value is 1000, which is suitable for most websites.
• Split a sql file every this size
  Splits large SQL export files into multiple parts to avoid hosting file size restrictions. The default value is 400. It is recommended not to set this value lower than 100. If database export timeouts occur, try adjusting this setting.
• Exclude files larger than this size
  Excludes files larger than the specified size from the backup process. Setting the value to 0 removes size restrictions and includes all files. This option is useful for skipping unnecessary large files such as videos or media that may cause backup or migration failures.
• Maximum PHP script execution time for a backup/migration task
  Defines the maximum execution time allowed for each backup or migration cycle. This timeout is managed internally by WPvivid and is independent of server PHP limits. The default value is 1800 seconds, which is suitable for most shared hosting environments. On VPS or dedicated servers, this value can be increased up to 3600 seconds if needed.
• Maximum PHP memory for a backup task
  Temporarily increases the PHP memory limit available to WPvivid during backup and migration operations. The default value is 256MB. If memory exhaustion errors occur, increase this value to 512MB or higher depending on database size and complexity. The memory limit is automatically released after task completion.
• Chunk size
  Controls how much data is processed and transmitted per request cycle. Some hosting providers impose strict data packet size limits. Reducing this value to 512KB or 256KB can improve compatibility when backup, migration, or remote storage upload operations fail.