backup physical : file server 1.9TB
repository : data domain
network : san switch
When performing file restore, the restore speed is only 7MB
Could you please speed it up?
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 26, 2024 3:30 am
- Full Name: Allen Li
- Contact:
-
- Product Manager
- Posts: 10693
- Liked: 2894 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam Restore so long
Hello Allen,
Welcome to the forum.
Slower "restore speed" when using deduplication appliances compared to general disk storage is a common challenge, not only related to DataDomain. That's why we recommend deduplication appliances mainly as a backup copy target. For primary backup jobs, other backup storage should be considered.
However, the maximum recovery speed depends on many factors, including the exact model of the deduplication appliance, what you are trying to restore or how everything is connected by the network. It is important to follow the recommendations of the deduplication appliance vendor when deploying the appliance for Veeam Backup & Replication.
Logs will tell us if somehow some components are misconfigured or misplaced. For example, when doing File Level Restore, having a slow network connection between the mount server and the DataDomain gateway server could impact speed.
Best,
Fabian
Welcome to the forum.
Slower "restore speed" when using deduplication appliances compared to general disk storage is a common challenge, not only related to DataDomain. That's why we recommend deduplication appliances mainly as a backup copy target. For primary backup jobs, other backup storage should be considered.
However, the maximum recovery speed depends on many factors, including the exact model of the deduplication appliance, what you are trying to restore or how everything is connected by the network. It is important to follow the recommendations of the deduplication appliance vendor when deploying the appliance for Veeam Backup & Replication.
What I would recommend is to contact our customer support and let them investigate the log files and your configuration.Could you please speed it up?
Logs will tell us if somehow some components are misconfigured or misplaced. For example, when doing File Level Restore, having a slow network connection between the mount server and the DataDomain gateway server could impact speed.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 26, 2024 3:30 am
- Full Name: Allen Li
- Contact:
Re: Veeam Restore so long
Hi Fabian,
i can understand
Should it be so slow when I do a "file server restore"?
Because my network uses FC, the transmission shouldn’t be so slow?
Or is this an I/O issue?
i can understand
Should it be so slow when I do a "file server restore"?
Because my network uses FC, the transmission shouldn’t be so slow?
Or is this an I/O issue?
-
- Product Manager
- Posts: 10693
- Liked: 2894 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam Restore so long
For file level restore, the backup has to be mounted to the mount server. Traffic will follow this path:
- DataDomain > Gateway Server > Mount Server > Restore Target
FC is only used between Data Domain and Gateway Server. The other components will use your ip network to transfer the data blocks.
From my experience with similar scenarios you could see lower restore performance in different steps:
- rehydrating the backup file on the data domain
- having a slow network between gateway, mount server and restore target
- Restoring of thousands of small files will lead to a „slow restore speed“, restoring a single huge file can leverage the available bandwidth much better
Please check the logs with our customer support. Unfortunately we cannot investigate your environment over a forum post.
Best,
Fabian
- DataDomain > Gateway Server > Mount Server > Restore Target
FC is only used between Data Domain and Gateway Server. The other components will use your ip network to transfer the data blocks.
From my experience with similar scenarios you could see lower restore performance in different steps:
- rehydrating the backup file on the data domain
- having a slow network between gateway, mount server and restore target
- Restoring of thousands of small files will lead to a „slow restore speed“, restoring a single huge file can leverage the available bandwidth much better
Please check the logs with our customer support. Unfortunately we cannot investigate your environment over a forum post.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Bing [Bot] and 39 guests