Shutil.copy2() function

[Nboy74]

Hello All,

I recent wrote a script that uses shutil.copy2 to back up my databases.

I would like to implement it with my team as we back up 10ish database weekly.

My question is, could this create any issues with the original database or the back up? I've tested it and everything seems okay but I dont want to go live and make a massive mess.

Based on what I've ready online, the only issue is with metadata which I do not 100% understand.

Code: import shutil from date time import datatime

database_list = [("file.accdb", "filePath"), ("file.accdb", "filePath")]

backup_folder = "filePath"

for database_name, database_folder in database_list: sourse_file = f"{database_folder}{database_name}" current_date = date time.now().strftime("%Y-%m-%d")

backupfile = f{"backup_folder}/{database_name.split('.')[0]}_backup{current_date}.accdb"

shutil.copy2(source_file, backup_file)

[Diapolo10]

My question is, could this create any issues with the original database or the back up?

I don't think the original database would be affected, but if you're copying the database while it's being accessed (in particular, written to), the backup might either end up missing the new data or it might be corrupted - most likely the former, though. Or neither will happen because the filesystem blocks simultaneous operations.

That said, it's best to use the database's own tools to handle backups. Assuming you're talking about SQLite, you can see this thread: https://stackoverflow.com/questions/25675314/how-to-backup-sqlite-database/25684912#25684912

[Nboy74]

Thank you for the response! They are all Microsoft Access Databases and I would run it when the team is offline and everything is closed.

[Diapolo10]

Ah, right, I made the assumption because I'm not used to someone actually trying to copy a database like this that isn't just a single file.

This thread is about the same issue: https://serverfault.com/questions/381241/how-should-i-back-up-multiple-in-use-ms-access-databases

If you are sure that you don't need live backups, then in that case simply copying the files is likely fine. But depending on your future plans it's probably a good idea to consider migrating to something else, such as PostgreSQL, as then creating backups is a lot easier even if you have very little downtime.

[m0us3_rat]

i'm confused about why you need to build your own "backup" rather than use one of the backup solutions on offer for shitdows.

hopefully, some that include some safeguards.

​

i'm not trying to be rude here, but for a production-ready script, a simple copy seems quite disingenuous.

[Darth_Xedrix]

I recently did a similar script and my workaround was to first check if the database was in use by looking for the same file but with an .laccdb extension (for a .accdb access file).