Skip to content

More options in @DirectoryStructure #1174

Description

@Daan7777

Hey Ola,
We have in our company our own SQL Server backup strategy, but it is old and is not up to date anymore. I'm tasked with implementing your backup solution into our servers.
There is one feature in our current backup strategy that we find very useful, especially when performing restores.
When a FULL backup is created a new folder gets created and all the DIFF and LOG backups after the FULL backup gets put in that folder so when you need to restore a database on a new server without the original MSDB history to make a backup script for you, you can instantly see which backups you have to take to place the database back.
For example:
DatabaseName
├── 0001
│ ├── FULL backup
│ ├── DIFF backup
│ ├── DIFF backup
│ ├── DIFF backup
│ ├── LOG backup
│ ├── LOG backup
│ └── ...

├── 0002
│ ├── FULL backup
│ ├── DIFF backup
│ ├── LOG backup
│ └── ...
With your current way you can costumize the structure with @DirectoryStructure, but as far as i can see there is currently no token or option that represents the most recent FULL backup / current backup set.
Is there a way to make this possible or add something like this as een optional directory structure feature?
For example,
{DatabaseName}[BackupSet}
Where {BackupSet} is created when a successful FULL backup is performed and subsequent DIFF and LOG backups continue using that same backupset until the next FULL backup.

Thank you for your time.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions