![data duplicacy data duplicacy](https://lyftron.com/wp-content/uploads/2020/05/Duplicacy.png)
To do this, we need to select the whole table and then need to join that with our duplicate records as below: 1. But now, we will try to fetch the entire record for each duplicate row.
![data duplicacy data duplicacy](https://www.girikon.com/wp-content/uploads/2020/06/image2-1.png)
In the previous step, we have seen that our query returned a list of duplicates records. I also had some permissions issues going on with my raid array that I think I have now fixed, so it is possible that caused the problem too. 02 Fetch All Duplicates Records In Database.
#Data duplicacy password
So I am not sure if the password was the problem and that just didn't get logged initially, or if there was something weird for me with doing the initialization automatically in the container. I have since removed and restarted the container a number of different times and it has worked properly each time now that the preferences file is initialized correctly in that directory. Once I changed the encryption key, the backup initialized correctly and began running. The first time I ran it, I got an error that my encryption key was too short because I initially had it as something like "test" and 8 characters is required. If /media/raid/test was uninitialized, all I would get was the failed to read preference file if I just ran the container as is.Įventually, I tried entering the container in interactive mode and ran backup.sh directly from in the container, and this produced a more meaningful output. e DUPLICACY_BACKUP_OPTIONS='-threads 4 -stats -limit-rate 200' \ The command I used to start my container was That error was the only thing the logs gave me initially, but I actually was able to get it working with a bit of tinkering.
![data duplicacy data duplicacy](https://forum.duplicacy.com/uploads/default/original/2X/e/e7d695dfacade0bbf2ab2081b517d84c973d4cf6.jpeg)
The logs did not provide too much info for me.