Hello Forum,
We are using an older version of 7Zip to compress SQL backups in Server 2003. We then use VBS scripts to push the zipped files to a Windows 2019 shared folder.
The zipped archive files look totally different in the WS2019 share vs the native Server 2003 location when viewed with Windows file explorer. Source file sizes and compression % are totally different.
Maybe different zip files.
Look size of zip file.
Also one archive is big (file in archive is alrger than 4 GB) and can use zip64 extension of zip formart that can be unsupported by older systems.
Last edit: Igor Pavlov 2024-08-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Attached are two zip files of the same SQL TRN backup. One as found in the local drive of the WS2003 SQL server. The other as found in the remote WS2019 file share. The file in the remote share was copied from the local Ws2003 drive to the share by a scheduled vbs script.
I added the WS2003_ and the WS2019_ file name prefixes.
It is interesting that the ReportServer DB TRN backup files appear the same size in both zip files. That DB is static, no changes whereas the other DB is growing.
I see now that the two TRN files are not the same. The local one seems correct but the remote one has data foreign to the local SQL DB. Like our VBS script is replicating the files from the wrong SQL server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Never mind. We figured it out. We had cloned some Prod servers for Dev and did not clean them up properly. They were replacing the Prod DB backup zip files in our remote share.
Thanks for helping!
Juha
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Forum,
We are using an older version of 7Zip to compress SQL backups in Server 2003. We then use VBS scripts to push the zipped files to a Windows 2019 shared folder.
The zipped archive files look totally different in the WS2019 share vs the native Server 2003 location when viewed with Windows file explorer. Source file sizes and compression % are totally different.
Anybody ever seen this?
Thanks for helping!
Nut124
Maybe different zip files.
Look size of zip file.
Also one archive is big (file in archive is alrger than 4 GB) and can use zip64 extension of zip formart that can be unsupported by older systems.
Last edit: Igor Pavlov 2024-08-05
What version of 7-zip did you use?
You can create small example of starange archive,
and call:
So we can look correct sizes for files inside archive and we can detect what is correct size.
We are using version 9.20.00.
Attached are two zip files of the same SQL TRN backup. One as found in the local drive of the WS2003 SQL server. The other as found in the remote WS2019 file share. The file in the remote share was copied from the local Ws2003 drive to the share by a scheduled vbs script.
I added the WS2003_ and the WS2019_ file name prefixes.
It is interesting that the ReportServer DB TRN backup files appear the same size in both zip files. That DB is static, no changes whereas the other DB is growing.
I see now that the two TRN files are not the same. The local one seems correct but the remote one has data foreign to the local SQL DB. Like our VBS script is replicating the files from the wrong SQL server.
Never mind. We figured it out. We had cloned some Prod servers for Dev and did not clean them up properly. They were replacing the Prod DB backup zip files in our remote share.
Thanks for helping!
Juha