best practice for backup notes

Previous Member

Hi,

we are doing manual ziped database back-ups. I would like to save some text in the same zip file, so i can comment the recent backup.

 

Björn Reuber

Hi,

 

I assume you're doing the manual backups cause of some changes/new developement. If so I would use a different approach. Maybe it would be helpful to add something like a version Nr to your Zip File (like 1.3.4 etc) and having a seperate file/oneNote to write down the changes between those versions.

 

regards

Björn

Unknown

I agree Bjorn, we've just been taking the same approach with a client during a long development phase.  We backed up after each significant database change against a versioned folder and recorded the details of the change in an excel index.  Makes it easy to go back to the right version if you discover a problem with something.  You just have to make sure everyone involved in development is disciplined enough to keep record each time!  

Paul, if you wanted to automate it from BOARD you could build a procedure to extract a text cube each time you run a backup, but you'd probably then need to trigger a powershell script to zip the two together. If you're already doing this manually I guess that's probably not an option for you though and the above solution would be quicker and easier.

Björn Reuber

If your users/developers are not disciplined enough to keep record each time (or simpy forgot to), you also can use the standard BOARD Database Log and the Action Codes ED (Entity Defined), EM (Entity Modified), RD (Relation Defined), etc. So you can easily see if some certain actions have taken place and speak to the the develoers.

 

Regards

Björn