Windows 7 with three laptops using home network. Problem - External backup drive connected to PC 2. After moving drive to PC 3 and changing backup job to reflect where drive is now located, history is no longer available. Name of drive and drive letter is the same. Only difference is where it is now located on network. Is this a functional limitation or a problem? Has anyone experienced this problem before and can offer a solution? Thanks Irvm
Are you using Backup My Computer {v2i files) or File and Folder Backup?
Both
I wouldn't waste my time with FIle and Folder Backup. You can read THIS POST by Allen M and decide for yourself. I'll bet I can recover any file or folder way faster from a v2i file using Recovery Point Browser than anyone using F & F Backup!
You can import F & F Backup by opening the Ghost GUI > Tasks > Recover My Files > under Search In, click 'File and Folder' > File > Import backup destination. Then browse to the folder the F & F Backups are in.
You cannot import v2i files into Ghost to show in the history file. However the files are still usable.
Thanks for your reply but I don't think you're understanding my problem.
The types of files whether FF or V2i are not really the issue. The thrust of my problem is that when I moved the external backup disk from the PC it was connected to on the network to another PC on the network, the status of the history backups (FF & V2i) were displayed as "not available" Yes, I know they are still physically there but if I were to run another incremental backup, it would not find any history of prior incremental backups and thus think that it must now run a base in order to start the process from day one. Which would mean that I would have to start manually deleting the oldest set every time the backups are scheduled until the physical number of backups catch up to the number of sets indicated in the backup job. Disk space is becoming tight and I don't have enough space to store twice as much as I need. As I stated above, the work around is to just keep deleting the oldest backups after every scheduled one until the physical backups catch up with the number of sets indicated in the job. Labor intensive!
My question is simply this, why are the history backup status showing "not available" when nothing else has changed other than the name of the PC where the backup disk was connected to on the network? Is there a better work around solution?