Author: Chris Evans
Thank you!: https://github.com/fullenw1 and his blog where I found his AWESOME write-up on validating file/folder paths. Without this I never would've been able to figure out how to validate folder/file paths like I wanted.
Allows for restoring the same folder/file from multiple backups to a separate location (ie. 'Copy To' functionality)
Backup & Replication v9+ (possibly earlier, but haven't validated)
Tested with v10.0.1.4854 and v11.0.0.837
I had a client who had daily backups of a particular file that had to be retained indefinitely during a legal case. At one point the client was asked to restore a folder (including all files inside said folder) from every single day of the month for the months of September and October. That's 61 total File Level Restores that the client would've had to run via the GUI. I decided to create a PowerShell script that will allow you to input Job Name, Server Name, Source Folder/File Path, and Target Restore Path and it will display a numbered list of backup points. Simply choose the starting index and stopping index and the script will recover the same folder/file from every backup point between the Start/Stop indexes.
Execute Multi-FLR.ps1 and input the required details when prompted.
As long as the information is correct and backups are found, a numbered list will be displayed. Defaults to sorting from oldest to newest.
You will then be prompted if you would like to flip the sorting (ie. Newest to oldest)
Each backup point will have an index (number on the far left). Choose the starting point ($Start).
Then choose stopping point ($Stop).
Restores will begin starting from the point chosen and will end at the chosen stopping point. Total number of restores would be (($Stop - $Start) + 1)
Restored files will be named "RESTORED_%d-%b-%Y_%H-%M-%S <original filename>"
- Job Name: Name of the job which backs up the server you wish to restore files from.
- Server Name: Hostname of the server you wish to restore files from.
- Folder or File to Restore: Path to folder or file which you would like to restore. (Example: C:\temp\ or C:\temp\file.txt)
- Copy To: Drive path (or UNC path) where restored folder or file(s) will be copied to. (Example: C:\temp\ or \\servername\c$\temp\)
- Basic error handling. It's not hard to break it if you purposefully input bogus information, but it should account for most common stuff.
- Basic input validation. Should properly validate given paths to ensure it either exists already or can be created if necessary.
- Basic debugging included (Uncomment line #1 to see debug output)
- Implement an option to choose multiple folders/files rather than 1 at a time
- Improve error handling/validation
- Consolidate/Refactor code to make it look neater
- Probably should add better comments/debugging as well
Veeamhub projects are community driven projects, and are not created by Veeam R&D nor validated by Veeam Q&A. They are maintained by community members which might be or not be Veeam employees.
Copyright (c) 2020 VeeamHub
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
We welcome contributions from the community! We encourage you to create issues for Bugs & Feature Requests and submit Pull Requests. For more detailed information, refer to our Contributing Guide.
If you have any questions or something is unclear, please don't hesitate to create an issue and let us know!