Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

DATA_DOMAIN_BOOST #892

Open
jmcbrat opened this issue Feb 10, 2025 · 1 comment
Open

DATA_DOMAIN_BOOST #892

jmcbrat opened this issue Feb 10, 2025 · 1 comment

Comments

@jmcbrat
Copy link

jmcbrat commented Feb 10, 2025

Looking to add support for the -N parameter on data domain. This populates the tables in SQL Server. Currently the feature uses the defaults of $:. I am trying to add in Locker in this description fields. When I run the command manually from DataDomain app agent I can add to the value.

Ideally, I would like to be able to populate this like other fields in MaintenanceSolution with @filename for example: {Description}{ServerName}${InstanceName}_{DatabaseName}. {Description} would have the Locker name in it (daily weekly and monthly).

Here is the manual command from DataDomain appagent, slightly redacted:
EXEC @returnCode = dbo.emc_run_backup ' -c <server> -l full -b "Daily" -y +2d -a "NSR_DFA_SI_DD_HOST=99.99.99.1" -a "NSR_DFA_SI_DD_USER=somename" -a "NSR_DFA_SI_DEVICE_PATH=/mssql-path" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" -a "PURGE_DEBUGLOG_DAYS=3" -N "Daily_DBNAME" MSSQL$DV:DBNAME'
In MSDB tables this is stored like:
select fam.media_set_id ,bset.name ,bset.description ,bset.expiration_date ,bset.backup_start_date ,bset.backup_finish_date FROM msdb.dbo.backupmediafamily fam inner join msdb.dbo.backupset bset on bset.media_set_id = fam.media_set_id where type = 'D' order by backup_start_date desc;

With the data looking like:
media_set_id, name, description, expiration_date, backup_start_date
11378, DDBMMSSQL, Daily_DBName1:DBName1, 2025-02-12 09:10:48.000, 2025-02-10 09:10:56.000
11377, DDBMMSSQL, MSSQL$DV:VDBName2, 2025-03-17 10:01:19.000, 2025-02-10 09:01:23.000

This name is good MSSQL$DV:VDBName2 but better would be Daily_MSSQL$DV:VDBName2

Why is this important? Having the locker stored in the name makes it easier to verify each Data Domain locker (Daily_ in above example data). I do restore tests on a jump server and being able to isolate the lockers helps this restore test to grab the correct backup type. Then the tests can be grouped by daily_ weekly_ and monthly_. Currently, I am using backup_start_date but that means weekly and monthly can get confused.

I read over the DatabaseBackup procedure (line 3710ish) and did not see a few of the DataDomain specific parameters being built yet.

Thanks for considering.

@olahallengren
Copy link
Owner

I did a change so that the backup set name is set when using Dell EMC Data Domain Boost, based on the parameter that I introduced some time ago.
#902

There is currently no support for tokens.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants