Option	Details
Processing
Extraction Mode	Manual Archive Extraction Set the Extraction value to "Manual Archive Extraction" when the archive file has already been manually extracted on the server. This can be done through your host's control panel such as cPanel or by your host directly. This setting can be helpful if you have a large archive file or are having issues with the installer extracting the file due to timeout issues. PHP ZipArchive This extraction method will use the PHP ZipArchive code to extract the archive zip file. PHP ZipArchive Chunking This extraction method will use the PHP ZipArchive code with multiple execution threads to extract the archive zip file. Shell-Exec Unzip This extraction method will use the PHP shell_exec to call the system unzip command on the server. This is the default mode that is used if it's available on the server. DupArchive This extraction method will use the DupArchive extractor code to extract the daf-based archive file.
Server Throttling	If the current host is a budget host that monitors CPU usage, then users might want to consider checking this box to help slow down the process and not kick off any high-usage monitors.
Extraction Flow
Archive Action	Extract files over current files The existing site files will be overwritten with the contents of the archive.zip/daf. ^Pro Remove WordPress core and content and extract The existing WordPress core files and WordPress content directory will be removed, and then the archive will be extracted. ^Pro Remove all files except add-on sites and extract All files except an add-on site will be removed, and then the archive will be extracted. An add-on site is a site/domain that is stored in a directory off of your main site that has been "added on" to your main hosting account. For instance, when you purchased a hosting account it could be for a.com. Then after that, you decided to add b.com and c.com to the same hosting account. The structure of this setup is often the following although it can vary some: /public_html - contains files for a.com /public_html/b.com - contains files for b.com /public_html/c.com - contains files for c.com The directories /public_html/b.com and c.com contain the files for the add-on sites b.com and c.com (so the option above means that b.com and c.com would be preserved and not deleted when you installed to a.com)
Skip Files	Extract all files Extract all files from the package archive. This option is selected by default. ^Pro Skip extraction of WordPress core files Extract all files except WordPress core files. Choose this option to extract only the wp-content folder and other non-core WordPress files and directories. ^Pro Skip extraction of WordPress core files and plugins/themes existing on host Extract all files except WordPress core files and existing plugins/themes on the current host. ^Pro Extract only media files and new plugins and themes Extract all media files, new plugins, and new themes. The installer will not extract plugins and themes that already exist on the destination site.
File Times	When the archive is extracted it should show the current date-time or keep the original time it had when it was built. This setting will be applied to all files and directories. Note: Setting the Original time is currently only supported when using the ZipArchive Format.
File Permissions	Switch on and set permissions in either octal or symbolic values to assign permissions to files. This option is not available on Windows machines.
Directory Permissions	Switch on and set permissions in either octal or symbolic values to assign permissions to directories. This option is not available on Windows machines.
Configuration Files
WordPress wp-config	Do nothing This option simply does nothing. The wp-config file does not get backed up, renamed, or created. This advanced option assumes you already know how it should behave in the new environment. This option is for advanced technical persons. Modify original This is the default recommended option which will modify the original wp-config file. Create new from wp-config sample This option creates a new wp-config file by modifying the wp-config-sample.php file. The new wp-config.php file will behave as if it was created in a fresh, default WordPress installation.
Apache .htaccess	Do nothing This option simply does nothing. The .htaccess is not backed up, renamed, or created. This advanced option assumes you already have your .htaccess file set up and know how it should behave in the new environment. When the package is built it will always create an .htaccess file at this location: `/dup-installer/original_files_[HASH]/.htaccess` Since the file is already in the archive file it will show up when the archive is extracted. Retain original from Archive.zip/daf This option simply copies the /dup-installer/original_files_[HASH]/.htaccess file to the .htaccess file. Please note this option will cause issues with the install process if the .htaccess is not properly set up to handle the new server environment. This is an advanced option and should only be used if you know how to properly configure your .htaccess configuration. Create New This is the default recommended option which will create a new .htaccess file. The new .htaccess file is streamlined to help guarantee no conflicts are created during install. Notes: Inside the archive.zip or archive.daf will be a copy of the original .htaccess (Apache) file that was set up with your packaged site. The .htaccess file is copied to /dup-installer/original_files_[HASH]/source_site_htaccess. When using either "Create New" or "Retain original from Archive.zip/daf" an existing .htaccess file will be backed up to a /wp-content/backups-dup-lite/installer/original_files_[HASH]/source_site_htaccess. This change will not made until the final step is completed, to avoid any issues the .htaccess might cause during the install
General php.ini, .user.ini, web.config	OVERVIEW When the archive is built it will always create an original backup of the php.ini, .user.ini, and web.config files ("Config Files") if they exist. The backups will be in the following location within the archive file without an extension. `Original File Backups archive.zip\|daf/dup-installer/original_files_[HASH]/[location]_phpini archive.zip\|daf/dup-installer/original_files_[HASH]/[location]_userini archive.zip\|daf/dup-installer/original_files_[HASH]/[location]_webconfig` If there are "Config Files" on the new server, backups may also optionally be created. Backup [location] is defined by the following: source_site Backup of original file when the archive was created on the source host installer_host Backup of original file before the installer starts on active host ACTIONS Do nothing This option performs no actions and assumes you already have your configuration files set up properly; either on the server or in the archive. If the same "Config Files" exist in both the deploy directory and the archive, then the archive files will overwrite any configuration files that exist at the same location in the archive. Retain original from Archive.zip/daf Moves any existing "Config Files" on the new host to the following location: `/dup-installer/original_files_[HASH]/installer_host_[CONFIG-TYPE] An existing "Config File" resides on the server before the archive is extracted or step 1 is ran.` The installer last step copies all "Config Files" from the archive backups to the correct location on the new host. They are copied from this location: `/dup-installer/original_files_[HASH]/source_site_[CONFIG-TYPE]` Reset Moves any existing "Config Files" on the new host to the following location: `/dup-installer/original_files_[HASH]/installer_host_[CONFIG-TYPE] An existing "Config File" resides on the server before the archive is extracted or step 1 is ran.` If any "Config Files" already exist in the archive they will be deployed "as is" to the location that matches the archive file structure.
General
Logging	The level of detail that will be sent to the log file (installer-log.txt). The recommended setting for most installs should be "Light." Note if you use Debug the amount of data written can be very large. Debug is only recommended for support.
Cleanup	^Pro Remove disabled plugins/themes Remove all inactive plugins and themes when installing site. Inactive users will also be removed during subsite to standalone migrations. ^Pro Remove users without permissions Removes users that currently do not have any permissions associated with their accounts.
Safe Mode	Safe mode is designed to configure the site with specific options at install time to help overcome issues that may happen during the install where the site is having issues. These options should only be used if you run into issues after you have tried to run an install. Disabled This is the default. This option will not apply any additional settings at install time. Enabled When enabled the safe mode option will disable all the plugins at install time. Note: When this option is set you will need to manually re-enable the plugins that need to be enabled after the install from the WordPress admin plugins page.

Option

Details

Processing

Extraction
Mode

Manual Archive Extraction
Set the Extraction value to "Manual Archive Extraction" when the archive file has already been manually extracted on the server. This can be done through your host's control panel such as cPanel or by your host directly. This setting can be helpful if you have a large archive file or are having issues with the installer extracting the file due to timeout issues.

PHP ZipArchive
This extraction method will use the PHP ZipArchive code to extract the archive zip file.

PHP ZipArchive Chunking
This extraction method will use the PHP ZipArchive code with multiple execution threads to extract the archive zip file.

Shell-Exec Unzip
This extraction method will use the PHP shell_exec to call the system unzip command on the server. This is the default mode that is used if it's available on the server.

DupArchive
This extraction method will use the DupArchive extractor code to extract the daf-based archive file.

Server
Throttling

If the current host is a budget host that monitors CPU usage, then users might want to consider checking this box to help slow down the process and not kick off any high-usage monitors.

Extraction Flow

Archive Action

Extract files over current files
The existing site files will be overwritten with the contents of the archive.zip/daf.

^Pro Remove WordPress core and content and extract
The existing WordPress core files and WordPress content directory will be removed, and then the archive will be extracted.

^Pro Remove all files except add-on sites and extract
All files except an add-on site will be removed, and then the archive will be extracted. An add-on site is a site/domain that is stored in a directory off of your main site that has been "added on" to your main hosting account. For instance, when you purchased a hosting account it could be for a.com. Then after that, you decided to add b.com and c.com to the same hosting account. The structure of this setup is often the following although it can vary some:

/public_html - contains files for a.com
/public_html/b.com - contains files for b.com
/public_html/c.com - contains files for c.com

The directories /public_html/b.com and c.com contain the files for the add-on sites b.com and c.com (so the option above means that b.com and c.com would be preserved and not deleted when you installed to a.com)

Skip Files

Extract all files
Extract all files from the package archive. This option is selected by default.

^Pro Skip extraction of WordPress core files
Extract all files except WordPress core files. Choose this option to extract only the wp-content folder and other non-core WordPress files and directories.

^Pro Skip extraction of WordPress core files and plugins/themes existing on host
Extract all files except WordPress core files and existing plugins/themes on the current host.

^Pro Extract only media files and new plugins and themes
Extract all media files, new plugins, and new themes. The installer will not extract plugins and themes that already exist on the destination site.

File Times

When the archive is extracted it should show the current date-time or keep the original time it had when it was built. This setting will be applied to all files and directories. Note: Setting the Original time is currently only supported when using the ZipArchive Format.

File
Permissions

Switch on and set permissions in either octal or symbolic values to assign permissions to files. This option is not available on Windows machines.

Directory
Permissions

Switch on and set permissions in either octal or symbolic values to assign permissions to directories. This option is not available on Windows machines.

Configuration Files

WordPress
wp-config

Do nothing
This option simply does nothing. The wp-config file does not get backed up, renamed, or created. This advanced option assumes you already know how it should behave in the new environment. This option is for advanced technical persons.

Modify original
This is the default recommended option which will modify the original wp-config file.

Create new from wp-config sample
This option creates a new wp-config file by modifying the wp-config-sample.php file. The new wp-config.php file will behave as if it was created in a fresh, default WordPress installation.

Apache
.htaccess

Do nothing
This option simply does nothing. The .htaccess is not backed up, renamed, or created. This advanced option assumes you already have your .htaccess file set up and know how it should behave in the new environment. When the package is built it will always create an .htaccess file at this location:


                /dup-installer/original_files_[HASH]/.htaccess

Since the file is already in the archive file it will show up when the archive is extracted.

Retain original from Archive.zip/daf
This option simply copies the /dup-installer/original_files_[HASH]/.htaccess file to the .htaccess file. Please note this option will cause issues with the install process if the .htaccess is not properly set up to handle the new server environment. This is an advanced option and should only be used if you know how to properly configure your .htaccess configuration.

Create New
This is the default recommended option which will create a new .htaccess file. The new .htaccess file is streamlined to help guarantee no conflicts are created during install.

Notes: Inside the archive.zip or archive.daf will be a copy of the original .htaccess (Apache) file that was set up with your packaged site. The .htaccess file is copied to /dup-installer/original_files_[HASH]/source_site_htaccess. When using either "Create New" or "Retain original from Archive.zip/daf" an existing .htaccess file will be backed up to a /wp-content/backups-dup-lite/installer/original_files_[HASH]/source_site_htaccess. This change will not made until the final step is completed, to avoid any issues the .htaccess might cause during the install

General
php.ini, .user.ini,
web.config

OVERVIEW

When the archive is built it will always create an original backup of the php.ini, .user.ini, and web.config files ("Config Files") if they exist. The backups will be in the following location within the archive file without an extension.


                Original File Backups

                archive.zip|daf/dup-installer/original_files_[HASH]/[location]_phpini 

                archive.zip|daf/dup-installer/original_files_[HASH]/[location]_userini 

                archive.zip|daf/dup-installer/original_files_[HASH]/[location]_webconfig

If there are "Config Files" on the new server, backups may also optionally be created. Backup [location] is defined by the following:

source_site Backup of original file when the archive was created on the source host
installer_host Backup of original file before the installer starts on active host

ACTIONS

Do nothing
This option performs no actions and assumes you already have your configuration files set up properly; either on the server or in the archive. If the same "Config Files" exist in both the deploy directory and the archive, then the archive files will overwrite any configuration files that exist at the same location in the archive.

Retain original from Archive.zip/daf

Moves any existing "Config Files" on the new host to the following location: /dup-installer/original_files_[HASH]/installer_host_[CONFIG-TYPE] An existing "Config File" resides on the server before the archive is extracted or step 1 is ran.
The installer last step copies all "Config Files" from the archive backups to the correct location on the new host. They are copied from this location:
/dup-installer/original_files_[HASH]/source_site_[CONFIG-TYPE]

Reset

Moves any existing "Config Files" on the new host to the following location: /dup-installer/original_files_[HASH]/installer_host_[CONFIG-TYPE] An existing "Config File" resides on the server before the archive is extracted or step 1 is ran.
If any "Config Files" already exist in the archive they will be deployed "as is" to the location that matches the archive file structure.

General

Logging

The level of detail that will be sent to the log file (installer-log.txt). The recommended setting for most installs should be "Light." Note if you use Debug the amount of data written can be very large. Debug is only recommended for support.

Cleanup

^Pro Remove disabled plugins/themes
Remove all inactive plugins and themes when installing site. Inactive users will also be removed during subsite to standalone migrations.

^Pro Remove users without permissions
Removes users that currently do not have any permissions associated with their accounts.

Safe Mode

Safe mode is designed to configure the site with specific options at install time to help overcome issues that may happen during the install where the site is having issues. These options should only be used if you run into issues after you have tried to run an install.

Disabled
This is the default. This option will not apply any additional settings at install time.

Enabled
When enabled the safe mode option will disable all the plugins at install time. Note: When this option is set you will need to manually re-enable the plugins that need to be enabled after the install from the WordPress admin plugins page.

Option	Details
Table Prefix	^Pro This option allows changing the table prefix to other than the package creation site's table prefix. The table prefix is the value placed in the front of your database tables. It is possible to have multiple installations in one database if you give each WordPress site a unique prefix.
Mode	Modes affect the SQL syntax MySQL supports (and others such as MariaDB) . This setting performs various data validation checks. This makes it easier to use MySQL in different environments and to use MySQL together with other database servers. It is very useful when running into conversion issues. The following options are supported: Default: This is the recommended setting to use. It will use the current Database mode setting. Disable: This will prevent the database engine from running in any mode. Custom: This option will allow you to enter a custom set of mode commands. See the documentation link below for options. For a full overview please see the MySQL mode and MariaDB mode specific to your version. To add a custom setting enable the Custom radio button and enter in the mode(s) that needs to be applied.
Processing	Chunking mode Split the work of inserting data across several requests. If your host throttles requests or you're on a shared server that is being heavily utilized by other sites then you should choose this option. This is the default option. Single step Perform data insertion in a single request. This is typically a bit faster than chunking, however it is more susceptible to problems when the database is large or the host is constrained.
Create	Run all CREATE SQL statements at once. This option should be checked when source database tables have foreign key relationships. When choosing this option there might be a chance of a timeout error. Uncheck this option to split CREATE queries in chunks. This option is checked by default.
Objects	Allow or Ignore objects for "Views," "Stored Procedures," "Functions" and "DEFINER" statements. Typically the defaults for these settings should be used. In the event you see an error such as "'Access denied; you need (at least one of) the SUPER privilege(s) for this operation" then changing the value for each operation should be considered.

Option

Details

Table Prefix

^Pro This option allows changing the table prefix to other than the package creation site's table prefix. The table prefix is the value placed in the front of your database tables. It is possible to have multiple installations in one database if you give each WordPress site a unique prefix.

Mode

Modes affect the SQL syntax MySQL supports (and others such as MariaDB) . This setting performs various data validation checks. This makes it easier to use MySQL in different environments and to use MySQL together with other database servers. It is very useful when running into conversion issues. The following options are supported:

Default: This is the recommended setting to use. It will use the current Database mode setting.
Disable: This will prevent the database engine from running in any mode.
Custom: This option will allow you to enter a custom set of mode commands. See the documentation link below for options.

For a full overview please see the MySQL mode and MariaDB mode specific to your version. To add a custom setting enable the Custom radio button and enter in the mode(s) that needs to be applied.

Processing

Chunking mode
Split the work of inserting data across several requests. If your host throttles requests or you're on a shared server that is being heavily utilized by other sites then you should choose this option. This is the default option.

Single step
Perform data insertion in a single request. This is typically a bit faster than chunking, however it is more susceptible to problems when the database is large or the host is constrained.

Create

Run all CREATE SQL statements at once. This option should be checked when source database tables have foreign key relationships. When choosing this option there might be a chance of a timeout error. Uncheck this option to split CREATE queries in chunks. This option is checked by default.

Objects

Allow or Ignore objects for "Views," "Stored Procedures," "Functions" and "DEFINER" statements. Typically the defaults for these settings should be used. In the event you see an error such as "'Access denied; you need (at least one of) the SUPER privilege(s) for this operation" then changing the value for each operation should be considered.

Important Days

Vijay Diwas 2025: Remembering India’s Victory & Honouring Our Brave Soldiers

dailybees

December 13, 2025

1991

Introduction

For India, Vijay Diwas is a day of great pride and remembrance. It commemorates the Indian Armed Forces’ triumph over Pakistan in the 1971 conflict, which resulted in the establishment of Bangladesh. This day is celebrated nationwide with solemn ceremonies and patriotic fervour, paying tribute to the brave soldiers who fought valiantly and reaffirming the Indian people’s spirit of bravery and unity.

What is Vijay Diwas?

Observed on 16 December every year

Every year on December 16, Vijay Diwas is celebrated to mark the end of one of the most important wars in the history of the Indian subcontinent: the surrender of Pakistani forces to the Indian Army and Mukti Bahini (Bangladeshi freedom fighters) in 1971. The day represents triumph, selflessness, and patriotism.

Tribute to Brave Soldiers Who Protected the Nation

The day honors the Indian soldiers and officers who displayed exemplary valor, strategic brilliance, and unyielding determination. Vijay Diwas pays homage to their sacrifices, resilience, and dedication that ensured the protection and integrity of the nation while helping to liberate Bangladesh.

Historical Background

Reason Behind the 1971 Indo–Pak War

The 1971 Indo-Pak War was rooted in decades of political strife, ethnic tensions, and economic disparity between East Pakistan (now Bangladesh) and West Pakistan (now Pakistan). The immediate trigger was the violent crackdown by the Pakistani military on East Pakistani civilians following the latter’s demand for autonomy and independence.

Role of Indian Armed Forces

India played a crucial role by supporting the Mukti Bahini in their guerrilla warfare efforts and eventually entering the war to intervene directly against Pakistani forces. The Indian military’s coordinated campaign on land, air, and sea fronts decisively tilted the balance in favor of the liberation movement in East Pakistan.

Formation of Bangladesh

The war concluded with the signing of the Instrument of Surrender on 16 December 1971, leading to the birth of Bangladesh as an independent nation, ending East Pakistan’s subjugation and altering the geopolitical landscape of South Asia.

Major Operations and Turning Points

Operations like “Operation Jackpot” (guerrilla strikes by Mukti Bahini), and battlefronts such as the Eastern and Western theatres where Indian forces gained critical territorial advantages, were pivotal. The swift and coordinated military strategy led to the Pakistani army’s surrender in just 13 days.

Leadership & Strategy

Key Military Leaders and Their Contributions

Prominent leaders such as Field Marshal Sam Manekshaw, who was the Chief of Army Staff, and Admiral S.M. Nanda, who led the naval forces, were instrumental in achieving victory. Their strategic vision, clear command, and inspirational leadership motivated troops to execute complex operations flawlessly.

The Disciplined Strategy That Led to Victory

The military adopted a well-planned strategy combining conventional warfare and guerrilla tactics. The swift encirclement strategy and domination of key infrastructure ensured a rapid culmination of hostilities, minimizing casualties while maximizing impact.

International Perspective on India’s Success

Internationally, India’s role was widely acknowledged as a decisive and just intervention that ended humanitarian crises and supported self-determination. Despite Cold War tensions and global political complexities, India’s measured approach garnered respect worldwide.

Stories of Bravery

Acts of Courage by Indian Soldiers

Countless acts of extraordinary bravery emerged during the war—soldiers braving intense enemy fire, overcoming difficult terrains, and executing daring maneuvers. These stories highlight the courage and commitment inherent in India’s armed forces.

Inspirational Stories from the Battlefield

Many soldiers became national heroes due to their sacrifice and dedication. Tales of officers leading from the frontlines, extraordinary perseverance, and brotherhood among troops inspire generations to come.

Recognition of Soldiers Who Sacrificed Their Lives

Many soldiers were posthumously awarded gallantry medals, such as Param Vir Chakra and Maha Vir Chakra, underscoring their supreme sacrifice. Vijay Diwas also serves as a reminder to honor these martyrs and keep their memories alive.

National Celebrations & Tributes

How India Observes Vijay Diwas

Vijay Diwas is marked by official ceremonies, speeches by leaders, remembrance events across the country, and special programs highlighting the significance of the day.

Wreath-Laying Ceremonies

Wreaths are laid at war memorials such as the India Gate in New Delhi, and other prominent sites, paying homage to the soldiers who laid down their lives.

Speeches, Military Parades, Documentaries

Leaders, military officials, and veterans deliver speeches emphasizing patriotism and sacrifice, parades showcase India’s military strength, and documentaries narrate the heroic tales of the 1971 war to educate and inspire citizens.

Paying Respect to Our Armed Forces

Importance of Honouring Martyrs

Honouring martyrs on Vijay Diwas strengthens national morale and acknowledges the cost of freedom. Their sacrifice underpins the peace and security enjoyed by generations.

Respect for Families of Soldiers

The families of soldiers are an integral part of the nation’s defense fabric. Supporting and respecting them reminds us of the wider community involved in safeguarding the country.

Remembering Our Responsibility as Citizens

Vijay Diwas is also a call to all citizens to uphold the values fought for—peace, unity, and democracy—and to contribute positively to the nation’s progress.

Lessons from Vijay Diwas

Patriotism

The day rekindles a deep sense of love and loyalty toward the country, encouraging citizens to honor their heritage and contribute to national growth.

National Unity

The 1971 victory was a testament to India’s diversity coming together for a singular cause, reinforcing the idea that unity is India’s greatest strength.

Courage, Discipline, Sacrifice

The qualities exhibited by the armed forces during the war—discipline in strategy, courage in battle, and readiness to sacrifice—offer timeless lessons for both the military and civilians.

Conclusion

India’s Victory Was Not Just Military, but Moral

Beyond a tactical triumph, the 1971 war symbolized a moral victory upholding justice, humanity, and right to self-determination, values that continue to guide India.

Gratitude to Our Defence Forces

Vijay Diwas is an occasion to express profound gratitude to our defence forces for their unwavering commitment and valor, safeguarding the nation’s sovereignty.

Promise to Uphold the Pride of the Tricolour

Every Indian should take pride and vow to protect the nation’s honor and uphold the values symbolized by the tricolor flag, keeping alive the spirit and sacrifices of Vijay Diwas.