nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Test DB back up and restore

Nicoletta Landi

Hi, I am planning to use a de-duplicate tool to remove dups in our DB. IN order to fine tune the rules in the tool, I would like to plan a simply testing operation whereby: I would take a backup of the TEST DB, run my tests, check the results, and restore the backup back into TEST again. In case I need to fine tune and run a couple of times before I feel confident to go to production.

I struggle from Blackbaud support to identify the best course of action. It sounds like we must purchase some extra backup space just to be able to do a backup, but this sounds a little inconvenient. Is there no other solution for a hosted NXT DB ?

As the duplicates tool might affect many components of the constituent record, the option of exporting and re-importing might be inappropriate as I might have to export everything and re-import everything. And even so, is there a guide to do this apparently clunky process?

Any help would be very appreciated. Thanks!

Find more posts tagged with

Comments

Dariel Dixon

I'm not sure how Blackbaud handles the pricing situation with restores and test DBs, but I think you are on the right path. I don't think by default the test DB is backed up regularly, so that may be where an extra expense might lie.

I know it can take some time for the backups to take place, but it may be worth considering if you even need to restore the test DB after you get things the way you would like.