Maintain Date Modified between source (server) and destination (Azure)
As the title says, I would like the displayed date modified in Azure to be the same as the ione in the source, and not change it to the time the copy actually occurred.
Is this possible, or am I missing a setting somewhere.
The Modified Date in Azure will show the date the blob was created (the backup date). However, we maintain the actual modified date in metadata within the file. If you view Blob Properties, you'll see a property called "cbmodifiedtime" that contains the original modified date. However, CloudBerry tracks the real modified date in its database and if you view the Backup Storage, you will see the file's real modified date. But if you're viewing directly from the Azure Portal, you will see the date the file was created. I do not think there is any way around this.
That would be OK, BUT when restoring, is the date the original (metadata date, or the Azure one).
If it is the Azure one, can there be an option to make it the metadata one.
We use the metadata. In other words, the real modified date.
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
How to connect to my MS Azure RA-GRS storage account secondary location?
aws lifecycle creation date versus modified date
Cloudberry backup on One Drive - Searching modified files taking long time (3 day) and not completed
CB Listed Modified Date Does Not Match Directory
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2023 MSP360 Forum