Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Some issues and ideas: Time, Post Command, User Message, Services

1. Time: In the main windows, it says 07:45:34 instead of 19:45:34

2. Post Command:

I added some (amateurish) vbs/bat stuff that was supposed to show a message with nircmd after end of backup. For some reason the backup never ended and was stuff at 99%. I think you should have a timeout to prevent this situation. I had to force close the application. 
Moreover, after force closing Hasleo, the service was also still stuck and when rebooting it would prevent a reboot (had to force reboot the computer!).

3. Perhaps it would be nice to have the option to show a custom user note at end of backup if it is successful "Backup successful." AND usernote: "Please xyz". For example "please remove backup drive from computer for sercurity reasons" -- just an idea.

4. I have another VSS using application. This application uses a service to trigger the backups. The service can be paused / started. It is important to pause/stop the service BEFORE hasleo backup, and to START the service again AFTER hasleo backup because it does vss backup every 15 minutes. changing the service status also requires admin rights. I was not able (as a amateur user) to do this with the pre/post command even though this seems to me like an important thing to be able to do. Perhaps you want to make it easier for users to start/stop services?
There should be no reason why more than one app can use VSS at the same time.  The System just picks another freeze point for the second app when it requests it.
I am going to quote ChatGPT (be aware ChatGPT makes mistakes):
When a program is said to be "VSS-aware," it means that the program is designed to interact properly with the Volume Shadow Copy Service (VSS) in Windows. VSS is a framework that allows applications to create consistent and point-in-time copies (snapshots) of data on a volume, even while the data is in use.

Being VSS-aware involves following specific guidelines and APIs (Application Programming Interfaces) provided by Microsoft for interacting with VSS. Here are some key aspects of VSS-awareness:

Coordination with VSS Writers: VSS-aware applications need to coordinate with VSS writers. VSS writers are components that ensure the consistency of data during a snapshot. For example, databases or file system writers can ensure that their data is in a consistent state when a snapshot is taken.

Freezing and Thawing of Applications: VSS-aware applications should freeze and thaw their activities when a snapshot is taken. This helps ensure that the data captured in the snapshot is in a consistent state.

Integration with VSS API Calls: VSS-aware applications use the VSS API calls to request and manage snapshots. These API calls include operations like querying for supported capabilities, requesting the creation of a snapshot, and releasing the snapshot when it's no longer needed.

If a program is not VSS-aware, it might not follow these guidelines, which could lead to issues such as:

Inconsistent snapshots: The captured snapshot might not represent a consistent state of the data.
Data corruption: Unaware applications may not handle freezing and thawing of data, leading to potential data corruption in the snapshot.
Conflicts with other VSS-aware applications: Multiple VSS-aware applications might interfere with each other if they are not properly coordinating their activities through VSS.

In the context of backup programs, being VSS-aware is crucial to ensure reliable and consistent backups, especially in scenarios where multiple backup applications might be running on the same system. It's always recommended to use applications that explicitly state their VSS-awareness and adhere to best practices for VSS integration.

I have seen issues with AllSync and Macrium Reflect, and AllSync and Hasleo. It might be that AllSync is not fully compliant with VSS-aware requirements. It might also be that Hasleo/Macrium are not fully compliant. (In any case I find it weird if a program that IS compliant can be disturbed by a NON-complient program, if this is indeed the case.)

In any case it seems to me that you cannot take it for granted that two VSS-using backup programs will work with no isssues.

By "issue" I mean: failure of backup (error message).

But it is good news that apparently it IS possible to program backup programs so they will work simultaneously!
I think you have something else going on...unrelated to VSS.

Check the Event Logs when you get errors for clues...

I think you would be better off using Windows File History for frequent personal data backups.

Forum Jump:

Users browsing this thread: 1 Guest(s)