Cloudsfer Backup
Micro Guides

Why Add a Backup If Autodesk or Egnyte Are Already Secure?

Autodesk Construction Cloud and Egnyte are secure platforms. They invest heavily in infrastructure, access controls, and availability.

But security and backup are not the same thing.

Security protects systems from unauthorized access. Backup protects your data when something goes wrong, even if the system itself is working exactly as designed.

The key difference

Autodesk and Egnyte follow a shared responsibility model:

• They keep the platform running and protected
• You are responsible for your data, its lifecycle, and its recovery.

This is where backup becomes essential. If a project manager deletes an entire folder by mistake — that is a human error, not a security breach.

Without a backup:

Recovery may be partial, limited, or impossible

With Cloudsfer Backup:

• The project can be restored from a known point in time
• Data is recovered cleanly, without impacting current work

The real role of backup

Backup doesn't replace Autodesk or Egnyte.
It adds a safety layer, ensuring you can recover data even when the platform behaves correctly.

How Cloudsfer Keeps My Backup Data Secure

Cloudsfer Backup is built with security at its core. All data is encrypted during transfer and while stored — protected both in motion and at rest.

Access is tightly controlled. Only authorized users can view or restore backups, and permissions are enforced at every step. Backups run quietly in the background without disrupting Autodesk, Egnyte, or daily work.

The bottom line

Cloudsfer Backup doesn't just back up your data.
It protects it, keeps it private, and ensures it's available when you need to recover.

Does Backup Replace Autodesk or Egnyte? Here's the Real Role of Backup

No. Backup does not replace Autodesk or Egnyte. Those platforms are where teams work, collaborate, and manage files — that's their job.

Cloudsfer's backup exists only to protect your data and help you recover it when something goes wrong.

The key idea

Backup does not replace your platforms.
It adds a safety layer behind them.

Do Backup Credits Expire? Understanding Cloudsfer's Credit Model

Cloudsfer Backup uses credits to cover backup and restore operations.

Credits are tied to usage, not time. They are consumed as backups run and when data is restored.

Credits do not disappear just because a project is quiet or inactive. You use them as long as backups and restores take place.

This makes it easier to plan, without worrying about losing credits simply because they weren’t used right away.

In short

You pay for what you use, when you use it.

What Is the Real Difference Between Cloud Storage, Sync, and True Backup in Cloudsfer?

Cloud Storage is where files live.

Sync keeps files the same across devices.

Cloudsfer’s Backup protects files over time

If a file is deleted or overwritten in cloud storage or sync, that change is usually permanent and spreads everywhere. True backup, like Cloudsfer’s, is different. It keeps historical copies so data can be restored from an earlier point. For example, if a synced project folder is deleted today, sync will remove it everywhere. Cloudsfer’s backup allows you to restore that folder as it existed yesterday.

Cloudsfer’s Backup focuses on recovery, not sharing or syncing.

How Does Data Restoration Work in Cloudsfer Backup, and What Recovery Scenarios Does It Support?

Restoration is simple and controlled.

You select the data you need and choose a point in time to restore from. Only the selected data is recovered, without affecting the current work.

Common recovery scenarios include:

• Accidental file or folder deletion
• Overwritten files
• Unwanted changes discovered days or weeks later

For example, if a project folder was deleted last Friday, it can be restored from a backup taken before the deletion.

Recover the right data, from the right moment, with minimal disruption.

What Level of Control Do Administrators Have Over What Is Backed Up and When?

Administrators stay in control of the backup process.

They decide which data is included in backups and when backups run, allowing protection to align with how a team actually works. This ensures that critical projects and folders are backed up without unnecessary data.

Backup schedules can be set to run automatically, so protection happens consistently without manual effort. Once configured, backups continue in the background without requiring daily attention.

Administrators can rely on backups running as planned while teams focus on their work. Control stays centralized, predictable, and easy to manage.

Administrators define the rules. Backup follows them.

Does My Data Ever Reside on Your Systems During Backup, and If So, For How Long Can It Be Accessed or Viewed?

During the backup process, data is securely transferred and stored so it can be restored when needed. This storage exists only to support backup and recovery.

Cloudsfer Backup uses secure, token-based authorization to access source platforms. This allows backups to run automatically without requiring usernames, passwords, or manual access to your data. Your content is not viewed, inspected, or used by Cloudsfer. Data access is handled programmatically, and no access is required as part of normal backup operations.

Backup data is kept based on your configuration and retention settings. It remains available only for recovery purposes and only for as long as you choose.

Your data stays private, protected, and under your control at all times.

Cloudsfer Backup exists to protect and recover your data, not to access, analyze, or use it.

Can Backup Be Safely Paused, Stopped, and Resumed Without Data Loss?

Yes. Backup jobs can be safely paused or stopped without losing already protected data.

When a backup is paused, Cloudsfer simply stops transferring new changes. Completed backup data remains intact at the destination. Nothing is deleted, overwritten, or rolled back.

When the job resumes, it continues incrementally. Only new or modified data is processed. This is useful during:

• Maintenance windows
• Bandwidth management
• Internal project freezes
• Platform-side updates

Note:Pausing a backup does not impact activity inside Autodesk Construction Cloud or Egnyte. Teams can continue working normally while the backup job is inactive.

Pausing will stop the process and not the protection that is already in place.

What Happens When New Projects or Folders Are Added After Backup Is Configured?

It depends on how the backup scope was defined.

If the backup was configured at a root or workspace level, newly created projects and folders are automatically included in the next scheduled run.

If the configuration was limited to specific projects or folders, administrators can update the scope to include new content. Cloudsfer does not require a full reconfiguration to expand protection. The backup job can simply be adjusted to reflect your evolving structure.

This flexibility ensures your backup grows alongside your organization.

In short:

When your environment expands, your backup can expand with it.

Can Backup Scope Be Safely Changed While a Backup Is Running?

Yes, and safely. If scope changes are made while a backup job is running, the current execution completes under the original configuration. Updates apply in the next cycle.

This prevents:

• Partial data capture
• Inconsistent backup states
• Interrupted transfers

Administrators can add or remove folders, projects, or filters without compromising backup integrity.

Cloudsfer maintains predictable behavior even during configuration updates.

Changes are controlled, and backup consistency remains intact.

Can Cloudsfer Restore Backup Data Directly Back Into Autodesk Construction Cloud or Egnyte?

Yes. Cloudsfer supports restoring backup data directly into working platforms such as Autodesk Construction Cloud and Egnyte.

Restore is not only a file download. It can push data back into the original environment or into an alternate location.

You can restore:

• Entire projects
• Specific folders
• Individual files

Historical versions (based on backup point)

This allows operational recovery without requiring manual re-upload or restructuring.

The goal of restoring is to return data to where teams actively work quickly and cleanly.

How Can Administrators Identify Deleted, Missing, or Failed Data for Recovery?

Administrators rely on backup reports and job logs. Cloudsfer provides visibility into:

• Successfully processed items
• Skipped files
• Failed transfers
• Source deletions

By reviewing these reports, administrators can identify discrepancies between the source environment and the backup.

If a folder is deleted or content is missing, administrators can reference previous backup runs and select an appropriate restore point.

Recovery decisions are based on documented backup history, not guesswork.

You see what changed. Then you decide what to recover.

How Does Selective Restore Work, and What Filters Can Be Applied During Recovery?

Selective restore allows administrators to recover only specific data rather than entire environments.

During recovery, you can choose:

• Individual files
• Specific folders
• Entire projects
• Data from a defined backup date

This prevents unnecessary overwrites and limits disruption to active work.

Selective restore is particularly useful when:

• Only one folder was deleted
• A file was overwritten
• Historical versions are required

The process is precise and controlled.

The goal is to restore exactly what is needed.

Why Use Cloudsfer’s Restore Feature If My Backup Already Exists on a Local System?

Local backups provide an additional layer of protection. However, they often require manual effort to restore content to cloud environments

Cloudsfer’s restore process is structured and environment-aware. It allows direct restoration into platforms like Autodesk Construction Cloud or Egnyte without rebuilding folder structures manually.

Additionally, Cloudsfer restore supports:

• Point-in-time recovery
• Incremental history
• Controlled re-insertion into live environments

Local storage holds copies. Cloudsfer restore re-integrates data into your working system.

A copy protects files.

Restore restores operations.

Can I Reset the Data Usage Count in Cloudsfer? Here’s How Data Usage Is Calculated

No. The data usage count in Cloudsfer cannot be manually reset.

Cloudsfer automatically calculates data usage based on the total amount of data transferred through migrations or backup operations associated with your account. Every time data is moved between platforms or included in a backup process, that transfer is counted toward the overall usage.

Because this value reflects the actual volume of processed data, it is designed to remain cumulative and cannot be cleared or restarted manually.

For example, if your account migrates from one cloud storage platform to another or runs recurring backup jobs, the transferred data size will be added to the total usage count.

How Long Does It Take to Receive My Recovery Email in Cloudsfer?

When you request a recovery in Cloudsfer, the system begins preparing your files right away. The time to receive the recovery email varies with the number of files and the total data size being restored.

For smaller recovery requests, the process is typically very quick. In many cases, the recovery email is sent within just a few minutes after the request is submitted.

If the recovery involves a larger amount of data or many files, it may take longer. The system needs time to securely gather the data, prepare it for delivery, and generate the recovery link before sending the email.

Most recovery emails arrive within minutes, but larger recoveries may take a bit longer. If your recovery email does not arrive within a reasonable timeframe, contact [email protected] so that the request can be checked and delivered as quickly as possible.

Can Backup Files Be Directly Accessed in the Repository?

No. The backup files stored in the repository cannot be directly accessed in the same structure as they appear in Autodesk Construction Cloud.

Cloudsfer stores backup data in a secure, encrypted format inside the backup repository.

The data is saved in a flat structure, which means it is not displayed in the same folder layout as the original ACC environment.

Because of this, the backed-up content is not meant to be opened or browsed directly from the repository. Instead, it is managed through the Cloudsfer platform.

To access your files, you need to use the Restore feature in Cloudsfer.

When a restore is performed:

• Cloudsfer prepares the backed-up data
• The restored content is generated as ZIP files
• After downloading and extracting the ZIP files, the data becomes available in its original structure and format, similar to how it appears in Autodesk Construction Cloud.

Backup files in the repository are secured and managed by Cloudsfer, not meant for direct browsing.

To access the actual files, you restore them through the Cloudsfer Backup & Restore dashboard.

Does Restoring Backup Data Affect the Monthly Data Allowance?

Yes. Restoring data from the backup does count toward your monthly data allowance.

When a restore is initiated, the system generates a ZIP file containing the restored data. This file is created so you can download and access the backed-up content.

If you download or approve the ZIP file, the system counts the restored data against your subscription credits. The amount counted is based on the size of the data being restored.

As a result, restore activity will be reflected in your monthly data allowance, even if the backup repository itself is stored on-premises.

Restoring data generates a ZIP file, and downloading or approving that file counts toward your monthly data allowance based on the restored data size.

Does “Skip Existing” or “Overwrite” Update Files During Migration?

Yes, but each option determines how existing files and folders in the destination are handled.

When usingAdvanced → “If a file already exists” → “Skip existing” the migration will skip all existing files and folders in the destination.

Only newly added files and folders will be migrated. Existing items will not be overwritten or updated, even if a newer version exists in the source.

When using“Overwrite existing”, the migration will overwrite all existing files and folders in the destination, regardless of whether changes have been made.

To ensure that only new and modified content is migrated, it is recommended to use the “Delta” option.

This will migrate new files and folders, as well as any files that have been updated.

Please note that each option directly affects whether existing data is skipped, replaced, or selectively updated during the migration process.