Restore of backup wrong path

[resist]

I made a backup of my workspaces because I had to install NT 7 beta 16 totally new.

Backup function ok. File has been saved in /users/NT7 backup folder.

Restore is asking for backup file, than gives error message because searching path is something with NT 6.5 ...

I created this wanted NT 6.5 search path manually and copied backup file into this path, too, then restore function ok. (Don´t know if the restored file was take of the backup 6.5 or backup 7 folder because files have been identically).

Please check. Sorry for my worse English.

[NinjaTrader_Jason]

Hello resist,

Can you please clarify what you mean by 'Restore is asking for backup file'. When I go to File-->Utilities-->Restore it does not ask for a backup file. A Windows Explorer window will open up to select the backup file I like to restore. It will open up the following folder: (My) Documents-->NinjaTrader Backup.

[resist]

please make a backup
then restore
choose the just backuped file, click open
then you get an error message
(if not i ´ve to post screenshots)

[NinjaTrader_Jason]

I do not experience an error message - the backup file was sucessfully restored.

[RJay]

Resist,

I keep 6.5 backups in default folder. I keep 7.0 backups in a user created alternate folder called "NinjaTrader Backup7".

Once the explorer window opens up in the restore operation, maneuver to your alternate directory you created to restore from those backups located there..


RJay

[resist]

If there is a path "NinjaTrader 6.5" restore works.
If you remove (or rename) this path it´s not possible to restore.
So to test you have to rename the "NinjaTrader 6.5" path (it´s not important to costumers who install an update to NT 7 but if you install NT 7 on a new or cleaned computer this little error will occur).

[stisk47]

same exact problem

i had the same exact problem. i had a clean install of the 7 beta. i also had to create the path for it to find the correct folder.

[NinjaTrader_JoshP]

Thanks for the report. We will look into it.

[NinjaTrader_JoshP]

This has been fixed in the next version. Thank you for the report.