You update an EA before the London session, restart MT4, and discover that the new version will not load. A snapshot can return the whole VPS to its earlier state quickly, while a separate backup can recover the original EA file without reversing every other server change. The safest VPS snapshot vs backup trading strategy uses both recovery methods for different failures.
Snapshots are designed for short-term rollback after a controlled change. Backups protect selected files or the complete system across a longer retention period and should remain available when the original VPS or storage fails.
This guide explains what each recovery method captures, when traders should use it, which MT4 files need protection, how to restore safely, and how to test a complete trading VPS recovery plan.
What Is the Difference Between a VPS Snapshot and a Backup?
A VPS snapshot is a point-in-time image of the entire server used to roll back quickly after a bad change, while a backup is a stored copy of your data for longer-term recovery. Traders benefit from snapshots before big changes and regular backups of MT4 data.
A point-in-time image records the virtual machine at a specific moment. Restoring it reverses the server to that earlier state, including applications, Windows settings, and local files covered by the snapshot.
A backup creates an independent recovery copy under a schedule and retention policy. It can support full-server recovery, file-level restoration, or both, depending on the backup product.
| Recovery feature | VPS snapshot | VPS backup |
| Main purpose | Fast rollback | Long-term recovery |
| Typical scope | Complete virtual machine state | Full server, volumes, folders, or files |
| Best timing | Before an update or major change | Daily, weekly, and long-term schedule |
| Restore target | Earlier server state | Original or replacement environment |
| Individual-file recovery | Often limited | Commonly supported |
| Retention | Usually short | Configurable for longer periods |
| Storage independence | Depends on provider design | Should use separate storage |
| Primary trading use | Reverse a failed change | Recover deleted or damaged trading data |
Microsoft states that a Hyper-V checkpoint, formerly called a snapshot, is not a full backup. Production checkpoints use Volume Shadow Copy Service to create a data-consistent point-in-time state, but they remain a rollback mechanism rather than a complete backup strategy. (Source: Microsoft Hyper-V Checkpoints, 2025).
What Does a VPS Snapshot Capture?
A VPS snapshot normally captures the virtual machine’s disks, configuration, and operating-system state at one moment. The exact contents depend on the virtualization platform, snapshot type, and hosting provider.
A full VPS snapshot can preserve Windows, installed trading platforms, local MetaTrader data, application settings, and system configuration. A standard Hyper-V checkpoint can also capture virtual-machine memory and device state, while a production checkpoint creates a data-consistent image without preserving running memory in the same way.
| Snapshot component | Usually captured? | Trading relevance |
| Windows installation | Yes | Restores the operating-system environment |
| Installed MT4 and MT5 terminals | Yes | Avoids reinstalling every platform |
| Platform data folders | Yes | Restores local charts, EAs, and settings |
| Windows registry | Yes | Preserves application and system configuration |
| Installed runtimes and DLLs | Yes | Restores software dependencies |
| Firewall rules | Yes | Preserves network-access settings |
| Scheduled tasks | Yes | Restores startup and maintenance tasks |
| Files created after the snapshot | No | Later changes are lost after rollback |
| Current broker-side position state | No | Broker records remain separate |
| External cloud data | No | It is outside the virtual machine |
The exact restore behavior must be confirmed with the provider. Some hosting services use the word snapshot for a disk image, while others include additional configuration or replication layers.
A practical guide to VPS backup solutions explains why full-server images are useful when a trader needs to recover the complete Windows and platform environment rather than reinstall each component manually.
Microsoft identifies standard checkpoints as captures of the virtual machine state, including memory, disk, and device state. Production checkpoints use backup technology inside the guest operating system to create a data-consistent point-in-time image. (Source: Microsoft Hyper-V Features, 2025).
What Does a VPS Backup Protect?
A VPS backup protects the files, folders, applications, volumes, or system image included in its backup policy. Its main value is retaining recoverable copies beyond the life of one snapshot or one physical storage system.
The backup scope should match the recovery objective. File backups are suitable for EA files and presets, while an image-level backup is required when the trader wants to restore the complete Windows environment.
| Backup type | What it protects | Suitable trading recovery |
| File backup | Selected files and folders | Deleted EA, preset, template, or log |
| Folder backup | Complete platform data folders | MT4 or MT5 configuration recovery |
| Volume backup | One Windows disk or partition | Platform and application data |
| System image | Windows and installed applications | Full-server reconstruction |
| Provider backup | VPS state under provider policy | Recovery after server failure |
| Offsite backup | Copy stored outside the VPS host | Recovery after infrastructure loss |
| Versioned backup | Several historical file versions | Restore before corruption occurred |
Windows Server Backup can protect and recover the operating system, volumes, applications, files, and folders. Its command-line tools also support selecting specific files or folders during recovery. (Source: Microsoft Wbadmin, 2022).
A backup should preserve older versions instead of overwriting the only usable copy. Immediate synchronization of a corrupted file to one destination is replication, not a complete versioned backup strategy.
How Do Snapshots and Backups Compare?
Snapshots provide faster whole-server rollback, while backups provide stronger retention, storage separation, and file-level recovery. Traders need both when they want quick change reversal and protection from larger failures.
The most important differences are restore scope and storage independence. A snapshot usually returns the whole VPS to one moment, while a backup can preserve several recovery points and allow selective restoration.
| Comparison | Snapshot | Backup |
| Recovery speed | Usually faster | Depends on backup size and storage tier |
| Restore scope | Complete server state | Full system or selected data |
| Retention period | Short | Short, medium, or long |
| File-level restore | Provider-dependent | Common |
| Storage location | Often close to source | Can be separate or offsite |
| Use before updates | Strong | Useful but slower to create or restore |
| Use after host failure | Limited if stored locally | Strong when stored separately |
| Protection from accidental deletion | Only if snapshot predates deletion | Strong with version history |
| Protection from ransomware | Limited if snapshot is accessible | Stronger with isolated or immutable storage |
Azure Backup documentation explains that snapshot-tier recovery is faster because the data is already stored with the disk. Vault recovery takes longer because data must be retrieved from separate backup storage. (Source: Microsoft Azure Backup Glossary, 2024).
Recovery Speed and Restore Scope
Snapshots usually restore a complete VPS faster, while backups offer more flexible recovery scope. The correct method depends on whether the trader needs one file or the entire server.
A snapshot is efficient after a failed Windows update, broker-platform upgrade, or configuration change. Rolling back the complete server for one deleted preset can reverse unrelated logs, settings, and files created after the snapshot.
A backup is more suitable when the trader needs to recover:
- One .set preset
- One EA or indicator
- A platform profile
- A template
- A log file
- One complete data folder
- A previous file version
Windows Server Backup supports recovery of specified files or folders to their original location or another target path. It can overwrite the existing item, create a copy, or skip the restore when the file already exists. (Source: Microsoft Wbadmin Start Recovery, 2022).
Storage Location and Retention
A backup should be stored separately from the production VPS, while a snapshot can remain dependent on the original virtualization and storage platform. Retention should preserve enough historical versions to recover from problems discovered late.
A snapshot stored on the same disk system can become unavailable when that storage fails. A provider can reduce this risk through replication, but the trader must confirm where the snapshot data resides.
| Storage design | Failure protected against |
| Snapshot on source storage | Bad software or configuration change |
| Backup on another host | Original server or disk failure |
| Backup in another data center | Site-level infrastructure failure |
| Offline or immutable copy | Ransomware and account compromise |
| Several dated versions | Delayed discovery of corruption |
| Long-term archive | Historical and compliance requirements |
Microsoft recommends a 3-2-1-1 backup strategy: three data copies, two storage types, one offsite copy, and one immutable or isolated copy. (Source: Microsoft Azure Backup Security Practices, 2026).
When Should You Create a VPS Snapshot?
Create a VPS snapshot immediately before a major change that could make the trading environment unstable. Keep the snapshot only long enough to validate the change and complete a safe rollback window.
Snapshots are most useful when the current VPS is known to work correctly. Capturing an already damaged platform produces a recovery point that contains the same problem.
Create a snapshot before:
- Installing a major Windows update
- Updating MT4, MT5, or another platform manually
- Replacing an EA or custom indicator
- Changing firewall or RDP settings
- Installing a new DLL or runtime
- Modifying automatic startup
- Changing broker connectors
- Updating a trade copier
- Migrating configuration files
- Testing a major registry or policy change
Do not create a snapshot while platform files are being copied or updated unless the provider confirms that the snapshot is application-consistent. Close nonessential tools and save platform profiles before capturing the recovery point.
A full VPS image can reduce recovery work because it preserves the complete trading environment. It should still be paired with separate file backups for selective restoration.
Which Trading Files Should You Back Up Regularly?
Back up platform profiles, templates, presets, EAs, indicators, configuration files, and logs that cannot be recreated quickly. The most important files are the custom components and settings that exist only on the VPS.
The safest method is to use File > Open Data Folder inside MT4 or MT5. This command identifies the active terminal data directory instead of relying on a guessed Windows path.
| Trading data | Why it matters |
| Profiles | Restore chart groups and workspaces |
| Templates | Restore chart settings and EA attachments |
| EA preset files | Restore tested input parameters |
| EAs | Restore strategy software |
| Custom indicators | Restore proprietary calculations |
| Scripts | Restore operational utilities |
| Configuration files | Restore platform and connection behavior |
| Logs | Support troubleshooting and audit review |
| Libraries | Restore required DLL or MQL dependencies |
| Custom sounds | Restore strategy alerts |
| Startup scripts | Restore automatic platform recovery |
| License records | Support reactivation where permitted |
MetaTrader templates can store chart settings, attached Expert Advisors, EA parameters, custom indicators, and their settings. Profiles store groups of charts and their workspace arrangement. (Source: MetaTrader 4 Templates and Profiles, 2026).
Platform Profiles, Templates, and Presets
Profiles restore groups of charts, templates restore individual chart configurations, and preset files restore EA input values. Backing up all three reduces the work required after reinstalling a terminal.
Profiles and templates serve different purposes. A profile can reopen several charts, while a template can recreate one chart’s indicators, appearance, and EA attachment.
Include these items:
- profiles folder
- templates folder
- EA .set preset files
- Saved chart objects
- Custom symbol files
- Broker-specific configuration files
- Screenshots of critical EA settings
Do not rely only on a profile to preserve important inputs. Save approved EA parameters as named .set files and record the strategy version used with each preset.
EAs, Indicators, Logs, and Configuration Files
EAs and indicators restore trading logic, while logs and configuration files preserve troubleshooting evidence and platform behavior. Back up both compiled files and source files when ownership and licensing permit it.
MT4 stores Expert Advisor operation logs in the MQL4\Logs directory. The platform creates dated log files that can show initialization errors, trade actions, and runtime failures. (Source: MetaTrader 4 Expert Logs, 2026).
Relevant folders can include:
- MQL4\Experts
- MQL4\Indicators
- MQL4\Scripts
- MQL4\Libraries
- MQL4\Files
- MQL4\Presets
- MQL4\Logs
- config
- history
- logs
License-protected software may not work after being copied to a different VPS. Keep activation instructions, vendor contact details, and proof of purchase with the recovery documentation.
Can a Snapshot Replace a Long-Term Backup?
No, a snapshot cannot replace a long-term backup because it can depend on the original VPS, storage chain, or provider account. Snapshots are temporary rollback tools rather than independent historical archives.
A checkpoint creates differencing files that track changes after the checkpoint. Leaving checkpoints active for extended periods can increase storage use and create a more complicated disk chain.
| Snapshot limitation | Backup response |
| Short retention | Keep scheduled historical versions |
| Same-host dependency | Store a copy on separate infrastructure |
| Whole-server rollback | Support selective file restoration |
| Limited version count | Retain daily, weekly, and monthly points |
| Storage growth | Use managed incremental backups |
| Provider account dependency | Keep an independent offsite copy |
| Vulnerable to source compromise | Use isolated or immutable storage |
| Difficult long-term management | Apply a documented retention policy |
Microsoft warns that Hyper-V checkpoints are not full backups. Checkpoint files must later merge into the parent virtual disk, and stale or failed differencing-disk chains can create operational problems. (Source: Microsoft Hyper-V Checkpoint Troubleshooting, 2026).
Delete or consolidate temporary snapshots through the provider’s approved process after the change has been validated. Do not delete snapshot files manually from the Windows or virtualization storage.
What Happens If the VPS Storage Fails?
A snapshot stored on the failed VPS storage can become unavailable with the original server. A backup stored on separate infrastructure can restore the trading environment to another disk, host, or VPS.
The level of protection depends on the provider’s architecture. A replicated snapshot can survive one disk failure, while a local snapshot on the same storage pool may not survive a wider storage incident.
| Recovery copy | Survives source-disk failure? | Survives host failure? | Survives site failure? |
| Local snapshot | Not guaranteed | Not guaranteed | No |
| Replicated provider snapshot | Often | Often | Provider-dependent |
| Backup on another host | Yes | Yes | No if same site fails |
| Backup in another region | Yes | Yes | Yes |
| Offline local copy | Yes | Yes | Yes if stored separately |
| Immutable cloud backup | Yes | Yes | Yes under policy |
Azure Backup can store recovery points in a vault outside the immediate snapshot tier. Microsoft also supports archived recovery points for long-term retention requirements. (Source: Microsoft Azure Backup Archive Tier, 2025).
Ask the provider where snapshots and backups reside. The labels “automatic backup” and “snapshot” do not confirm storage separation or geographic redundancy.
How Often Should Traders Create Snapshots and Backups?
Create snapshots before high-risk changes and create file backups on a regular schedule based on how much configuration work you can afford to lose. A practical trading plan uses daily file backups, weekly full backups, and change-based snapshots.
The recovery point objective, or RPO, is the maximum amount of data or configuration time that can be lost after an incident. A 24-hour RPO means the trader accepts losing changes made since the previous daily backup.
| Recovery item | Practical frequency | Retention example |
| Pre-change snapshot | Before each major change | Until validation is complete |
| MT4 data-folder backup | Daily | 7 to 14 daily copies |
| Full VPS backup | Weekly | 4 to 8 weekly copies |
| Monthly archive | Monthly | 3 to 12 months |
| EA preset backup | After every approved change | Keep each strategy version |
| Platform logs | Daily or weekly archive | Based on audit needs |
| Migration backup | Immediately before migration | Until the old server is retired |
| Disaster-recovery copy | Weekly or monthly | Stored outside the provider |
A documented Forex VPS backup strategy should link backup frequency to the rate of platform, EA, and configuration changes. A trader who changes presets every day needs more frequent protection than a stable server that remains unchanged for months.
Keep fewer snapshots than backups. Snapshots are operational rollback points, while backups are historical recovery copies.
How Do You Restore a VPS From a Snapshot?
Restore a snapshot through the hosting control panel or provider support process, then reconcile MT4 with the broker before enabling automated trading. The snapshot returns local server state, but it does not reverse broker-side orders or positions.
A rollback can restore an earlier account view, EA state, log set, and platform cache. The broker remains the source of truth for current balances, positions, orders, and executions.
| Restore step | Required action |
| 1 | Check current positions through the broker |
| 2 | Record working orders and account state |
| 3 | Disable or pause automatic trading where possible |
| 4 | Select the correct dated snapshot |
| 5 | Confirm that newer VPS changes will be lost |
| 6 | Start the provider restore operation |
| 7 | Wait for Windows and network services to return |
| 8 | Connect through Remote Desktop |
| 9 | Open each trading platform |
| 10 | Reconnect the correct broker accounts |
| 11 | Compare local positions with broker records |
| 12 | Review EA and platform logs |
| 13 | Enable automation only after reconciliation |
| 14 | Create a new backup after validation |
Do not submit replacement orders immediately after rollback. An order absent from the restored local history may still exist at the broker.
Snapshot-tier VM recovery can have infrastructure restrictions that do not apply to separately vaulted recovery points. Microsoft documents that snapshot-tier restoration can remain limited to the protected virtual machine subscription, while vault-tier recovery supports broader restore scenarios. (Source: Microsoft Azure VM Restore, 2026).
How Do You Recover Individual Trading Files From a Backup?
Restore the required file to a temporary folder, compare it with the current version, close the affected platform, and then place it in the correct data directory. Selective recovery avoids reversing unrelated VPS changes.
Do not overwrite the current file immediately. Keep a copy of both versions until the restored EA, preset, or profile has been tested.
| File type | Typical restore location | Post-restore check |
| EA | MQL4\Experts | Refresh Navigator or restart MT4 |
| Indicator | MQL4\Indicators | Apply it to a test chart |
| Preset | MQL4\Presets | Load and compare every input |
| Template | templates | Apply it to the correct chart |
| Profile | profiles | Confirm every chart and EA |
| Log | MQL4\Logs or terminal logs | Open it without replacing current logs |
| Library | MQL4\Libraries | Confirm EA dependency and trust |
| Configuration | config | Verify account and platform behavior |
Use this recovery sequence:
- Identify the last known good backup date.
- Restore the item to a temporary recovery folder.
- Compare file name, size, date, and version.
- Save a copy of the current production file.
- Close MT4 when the file can be locked or cached.
- Place the recovered item in the active data folder.
- Reopen MT4.
- Test on a demo account.
- Review the Experts and Journal logs.
- Return to live use only after validation.
Microsoft Azure Backup supports recovery of individual files and folders from Windows Server recovery points. Restored items can be copied to the original or another server location. (Source: Microsoft Azure File Recovery, 2025).
Should You Back Up Open Trades and Account History?
Back up local account history and trading logs for analysis, but use the broker as the authoritative source for open positions, working orders, balances, and executions. A VPS backup cannot preserve a live market position as if time had stopped.
Broker-side account state continues changing while the VPS is offline or being restored. A snapshot can contain an older local view that no longer matches the account.
| Trading record | Primary source | Why keep a local copy? |
| Open positions | Broker | Supports reconciliation |
| Working orders | Broker | Confirms current exposure |
| Executions | Broker | Provides official fill records |
| Account statements | Broker | Supports accounting and review |
| MT4 account history | Platform and broker | Speeds local analysis |
| EA logs | VPS | Shows strategy decisions and errors |
| Terminal logs | VPS | Shows connections and platform events |
| Copier logs | VPS | Links source and follower actions |
| Strategy state files | VPS | Supports controlled EA recovery |
Export broker statements regularly. Keep EA and platform logs because broker reports do not show every internal calculation, rejected local action, or software error.
After any restore, perform a three-way comparison:
- Broker positions and orders
- MT4 positions and orders
- EA internal strategy state
Do not enable new automated entries until all three states are understood.
How Can You Test Whether Your Recovery Files Work?
Test backups and snapshots by restoring them into a safe environment and confirming that platforms, charts, EAs, and files open correctly. An untested backup is only an assumption that recovery will work.
A restore test should avoid the active live server where possible. Use a temporary VPS, alternate directory, or demo terminal so the test cannot submit unintended trades.
| Recovery test | Passing result |
| Snapshot restore | Windows starts and accepts RDP |
| MT4 launch | Correct broker installation opens |
| Profile recovery | Required charts appear |
| EA restoration | EA loads without errors |
| Preset restoration | Inputs match the approved record |
| Indicator recovery | Custom study calculates normally |
| Broker login | Demo account reconnects |
| Log access | Historical records remain readable |
| File-level restore | One selected item can be recovered |
| Backup catalog | Expected recovery dates are present |
| External dependency | DLL, API, or license reconnects |
| Resource test | VPS remains stable under the restored workload |
Test at least one file-level recovery and one complete-server recovery. These procedures use different tools and can fail for different reasons.
Record:
- Backup date
- Snapshot date
- Restore duration
- Files tested
- Platform version
- Missing dependencies
- License reactivation steps
- Broker reconciliation steps
- Test result
- Next test date
A successful restore should produce a repeatable written procedure. The next recovery may happen when the original administrator is unavailable.
Which Snapshot and Backup Mistakes Put Trading Setups at Risk?
The most dangerous mistakes are storing every recovery copy with the VPS, keeping only one version, leaving snapshots indefinitely, and never testing restoration. These failures can turn a recoverable platform problem into a complete rebuild.
A backup plan must protect against accidental deletion, corruption, hardware failure, account compromise, and human error. One recovery method rarely covers every scenario.
| Mistake | Result | Corrective action |
| Treating a snapshot as a backup | Source failure removes both | Keep an offsite backup |
| Keeping one backup version | Corruption overwrites the good copy | Retain dated versions |
| Leaving checkpoints indefinitely | Storage and disk-chain complexity grow | Remove after validation |
| Backing up only program files | Profiles and custom data remain missing | Back up the active data folder |
| Ignoring EA presets | Strategy settings must be rebuilt | Save named .set files |
| Restoring without broker reconciliation | Duplicate or conflicting orders can occur | Verify broker state first |
| Keeping backups inside the VPS | VPS loss removes the recovery files | Copy them outside the server |
| Never testing restoration | Failure is discovered during an incident | Schedule restore tests |
| Using unclear file names | Wrong version is restored | Use dates and version labels |
| Forgetting license dependencies | EA cannot run after recovery | Document activation steps |
| Capturing a damaged server | Snapshot preserves the problem | Validate before capture |
| Manual deletion of checkpoint files | Virtual disk chain can break | Use provider tools |
A trading recovery plan is complete only when the backup is separate, current, and proven restorable.
Use access controls on the backup destination. A publicly exposed or broadly shared backup can reveal account records, proprietary EAs, API credentials, and platform configuration.
VPS Snapshots and Backups: Recovery Essentials for Traders
A reliable VPS snapshot vs backup trading plan uses snapshots for short-term rollback and backups for durable recovery. The plan must protect both the full Windows environment and the individual files needed to rebuild MT4 or MT5.
The recovery method should match the incident rather than applying a full rollback to every problem.
| Recovery need | Best method |
| Failed Windows update | Snapshot |
| Broken platform upgrade | Snapshot |
| Incorrect firewall change | Snapshot |
| Deleted EA preset | File backup |
| Corrupted template | File backup |
| Lost platform data folder | Folder backup |
| Failed VPS storage | Offsite full backup |
| Provider-level failure | Backup in another location |
| Ransomware or account compromise | Isolated or immutable backup |
| Complete migration | Snapshot plus file and image backups |
A complete recovery plan should include:
- Snapshots before major changes
- Daily platform-data backups
- Weekly full-server backups
- Separate offsite storage
- Dated retention points
- Broker statement exports
- Written restore procedures
- Quarterly recovery testing
- EA license documentation
- Position-reconciliation steps
A properly sized Forex VPS plan provides the Windows, CPU, RAM, and NVMe environment needed for MT4, MT5, and Expert Advisors. Backup and snapshot policies should be confirmed separately because resource specifications do not define recovery coverage.
TradingFXVPS uses Microsoft Hyper-V with guaranteed resource allocation and a no-overselling policy. Its documented 99.99% uptime SLA allows approximately 52.56 minutes of potential infrastructure downtime per year, but uptime does not replace recoverable copies of trading data.
Protect Your Trading VPS With a Reliable Recovery Plan
Protect the VPS with one current rollback snapshot, several retained backups, an offsite copy, and a tested restore procedure. Review the plan after every platform migration, EA update, account change, or major Windows modification.
The final recovery check should confirm both server restoration and safe trading resumption. Contact the TradingFXVPS team to review the snapshot, backup, and recovery options for your trading server.
Frequently Asked Questions About VPS Snapshots and Backups
Does a VPS snapshot include installed trading platforms?
Yes, a full VPS snapshot normally includes installed trading platforms and their local files at the time of capture. The exact scope depends on the provider and virtualization system.
Confirm whether the snapshot includes every virtual disk. Files stored on an excluded external volume will not return with the main server image.
Can you restore one MT4 file from a snapshot?
Not always, because many snapshot services restore the complete VPS rather than one file. A file-level backup is safer when you need one EA, preset, template, or log.
Some providers support mounting or browsing snapshot disks. Confirm that feature before relying on it for selective recovery.
Should backups be stored outside the VPS?
Yes, at least one backup copy should be stored outside the production VPS and its primary storage. A backup kept only inside the server can disappear with the original environment.
Use a separate provider location, cloud vault, secured local storage, or another independent destination. Restrict access because trading backups can contain proprietary software and account information.
How long should trading VPS backups be retained?
Retain daily copies for at least one to two weeks and weekly copies for one to two months as a practical starting point. Keep longer monthly archives when audit, tax, strategy, or compliance needs require them.
Retention should exceed the time it normally takes to discover a problem. A corruption found after three weeks cannot be repaired from seven days of recovery points.
Does creating a snapshot require shutting down the VPS?
No, many virtualization platforms can create a snapshot while the VPS is running. Production checkpoints use guest-aware backup technology to create a data-consistent state.
Provider behavior varies. Save platform settings and avoid major file changes during capture when consistency is critical.
What should you back up before reinstalling or migrating MT4?
Back up the complete active MT4 data folder, including profiles, templates, presets, EAs, indicators, scripts, libraries, logs, and configuration files. Export broker statements and document every installation path.
Save EA license and activation details separately. Test the copied files on a demo terminal before retiring the original VPS.