According to v5maint.exe's help option through command, running -E: -dlymaint should place a backup of all logs, journals, and the database and keys, into the root of an external hard drive. However, it does not do this when I run it from an elevated command prompt. Instead, it creates a corrupted zip file in E:\Archives that contains a single 3700d.log.0 file that only details the v5maint.exe that just ran. It doesn't back up any journals, nor does it backup the database and keys.
Running -E: -db does create a backup of the database and keys, but it places it in %resdbdir%\backup. I can't get it to create the backup in an external hard drive.
I went rooting around in registry and I found two strings titled "Primary backup path" and "Primary key backup path." Changing both of these to the external drive solves the second issue I'm having and does create a valid backup of the database and keys in the external hard drive. I'm still having issues getting -dlymaint to work correctly.
Is changing these two registry values safe? What can I do to get -dlymaint to run properly? I'm debating writing a script that will just copy and paste assorted logs into the external hard drive, and then scheduling that instead. But it would be nice to figure out the issues I'm having with v5maint, since we have loads of customers who are upgrading from 4.x to 5.5, or 5.x to 5.7 (once we hear from some other vendors that it doesn't suck ass). Thank you in advance.
Running -E: -db does create a backup of the database and keys, but it places it in %resdbdir%\backup. I can't get it to create the backup in an external hard drive.
I went rooting around in registry and I found two strings titled "Primary backup path" and "Primary key backup path." Changing both of these to the external drive solves the second issue I'm having and does create a valid backup of the database and keys in the external hard drive. I'm still having issues getting -dlymaint to work correctly.
Is changing these two registry values safe? What can I do to get -dlymaint to run properly? I'm debating writing a script that will just copy and paste assorted logs into the external hard drive, and then scheduling that instead. But it would be nice to figure out the issues I'm having with v5maint, since we have loads of customers who are upgrading from 4.x to 5.5, or 5.x to 5.7 (once we hear from some other vendors that it doesn't suck ass). Thank you in advance.