VMCE_V12 · Question #88
A Windows Server using the ReFS filesystem has been used as a standalone Veeam repository for several years and is due for replacement. A new Windows server using the ReFS filesystem has been…
The correct answer is C. Use the "Move backup..." function. To avoid running out of space when moving backups to a new repository, the "Move backup..." function in Veeam Backup & Replication should be used. This function allows you to relocate backup files to a new repository without duplicating data, which can save space. Unlike a…
Question
A Windows Server using the ReFS filesystem has been used as a standalone Veeam repository for several years and is due for replacement. A new Windows server using the ReFS filesystem has been created to replace the old server, with twice the capacity. Backup files need to be transferred to the new server with no disruptions to the existing backup chains. The Veeam engineer has begun to move backup files to the new repository but is now getting alerts that it is running out of space. How could the engineer have avoided this issue?
Options
- AUse a Backup Copy Job
- BUse the "Copy backup..." function
- CUse the "Move backup..." function
- DUse Robocopy with the /compress switch
How the community answered
(50 responses)- A6% (3)
- B16% (8)
- C74% (37)
- D4% (2)
Explanation
To avoid running out of space when moving backups to a new repository, the "Move backup..." function in Veeam Backup & Replication should be used. This function allows you to relocate backup files to a new repository without duplicating data, which can save space. Unlike a simple copy action, the move function ensures that the backup chain remains intact and does not require additional space for a copy of the backups during the transfer. When the move is initiated, Veeam will also automatically update the configuration to point to the new backup location, thus preventing any disruptions in the backup chain.
Topics
Community Discussion
No community discussion yet for this question.