In the world of data migration, missing days' worth of data during the transition from one server to another can be a major headache. Cloud storage solutions like Box have become increasingly popular for businesses, but when it comes to migrating data, no one seems to have a foolproof solution. This article explores a potential scenario where missed days' data was encountered during a Box file migration using Robocopy as a rescue.
Background: Box Share File Migration
Box is a leading cloud content management platform that allows users to manage, share, and collaborate on files from anywhere. Businesses often use Box to store and manage large volumes of data, making it an essential part of their digital infrastructure. However, migrating data from an on-premises server to Box can be a complex and time-consuming process.
The Challenge: Missed Days' Data
During a recent Box file migration project, the IT team encountered a problem where some files from the previous three days were missing. The team had used Robocopy, a robust and flexible tool for synchronizing files and directories between servers, for the migration. Robocopy seemed like the perfect solution, but how could it have missed some critical data?
Robocopy: A Closer Look
Robocopy is a command-line tool that comes with the Windows Operating System. It is designed to copy files and directories from one location to another while maintaining the source file attributes, such as timestamps and access control lists. Robocopy offers several options to customize the migration process, making it an ideal choice for migrating data to Box.
Robocopy Switches Used
The IT team had used the following Robocopy switches for the migration:
- /M: Copy files with Millisecond timestamps.
- /SEC: Copy files with the same security information.
- /COPY: Copy files with all attributes, including timestamps.
- /LOG: Log the migration progress.
The Root Cause: Timestamps
After a thorough investigation, the IT team discovered that the root cause of the missing days' data was a timestamp issue. The source server's clock had been incorrect during the migration period, causing Robocopy to skip over some files that it thought had already been copied.
The Solution: Robocopy Rescue
To rescue the missing data, the IT team followed these steps:
- Checked the migration logs to identify the affected files.
- Corrected the source server's clock to the correct time.
- Used Robocopy to copy the missing files from the source server to the destination server.
By correcting the source server's clock and using Robocopy to copy the missing files, the IT team was able to recover the lost data.
Migrating data from one server to another, especially to a cloud storage solution like Box, can be a complex and time-consuming process. In this article, we explored a scenario where missed days' data was encountered during a Box file migration using Robocopy. We discovered that a timestamp issue was the root cause, and by correcting the source server's clock and using Robocopy to copy the missing files, the IT team was able to recover the lost data.
References
- Microsoft Docs: Robocopy
- Box Support: Migrating Data to Box