2/28/2024 0 Comments Usb backup software ware![]() Then any attempt-to-backup a backup job (with these two setting configured) should always: ![]() and the backup job is configured for the conclusion of the attempt-to-backup sequence results in "eject removable media" as final step If attempt-to-backup sequence is actively in play. Means attempt-to-backup sequence is actively in play When veeam agent is determining "3 more hours need to transpire since the last backup. Means determining if enough time has passed since last backup Looking for the target means backup job logic processing procedures are underway. Now, if backup job did not enable the settings "backup when target is avail" then I would concede we would not expect Veeam agent to be looking for "is the target avail" or not. I hope I communicated my concept clearly enough. even if the job settings logic results in not backing up: please automatically eject removable media as a result of Veeam agent logic. If inserting media draws attn of the Veeam agent for Windows to begin process for considering (per job settings) to/not perform a backup. I was asking to automatically eject removable media even if backup job settings determine not to backup. My feature request was not to institute perceived higher level state of security. I am in 100% complete Agreement with you! Veeam Agent for Windows will automatically soft 'eject' the removable storage at the end of the attempt to see if it was time for the job to run or not run. because it has not been more than 24 hours since last backup. Step #5 = Even though the Job did not re-run. ![]() Step #4d = Job realizes it should not run for an additional "x" hours Step #4c = Job checks if it has been 24 hours since last backup Step #4a = plug back in the USB NVMe Enclosure I let backup job perform its first backup Using my FEATURE REQUEST, here is the sequence I envision: What is worse: if the USB backup target stays plugged in (avail to OS) long enough, the job will never run beause there is no schedule (only event driven triggers) and it will never again be soft ejected after the next job because the job will never occur again.įEATURE REQUEST: would you please give a check box option to enable "eject removable media even if job settings prevented writting any backup data" the USB backup target remained inserted and exposed for ransom ware attacks. and backup job settings recognized the drive and did not re-run the backup job because it was not enough time since last backup taken. during the 24 hour window since last backup, if the backup target get's re-inserted again. it has not been more than 24 hours since last backupįLAWLESS SO FAR awesome sausce kudos to Veeam! Step #4 = plug back in the USB NVMe Enclosure Step #3 = After backup job finished, USB was software 'ejected' 24 Hour = Backup no more often than every CHECKED = Eject removable storge once backup is completed (ransomware protection) CHECKED = When backup target is connected ![]() Thank you for SMARTLY designing the ability to 'rate limit' backups using the "Backup no more often than every" setting! Thank you for CLEVERLY designing the ability to software 'eject' USB storage devices after backup! Thank you for Veeam Agent for Windows (free)!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |