RPAM_Store.dat did not "Move" to new destination along with the .*v2i files

Archive
1

Using Ghost 15.0, I used the Move function within the Manage Backup Destination screen to move back-ups from one drive to another.  All of the .iv2i, .v2i and .sv2i backups moved as expected. 

Two issues and a few questions:

 

  1. Although all .*v2i backups were moved to the new destination, copies of three iv2i files remained in the original drive.  The file sizes match.  Is it OK to delete the three files in the original drive since they also appear in the new drive?

  2. The RPAM_Store.dat in the original drive did not move from the original drive to the new drive destination.  There is no RPAM_Store.dat in the new drive destination after the Move command was executed.  Should I just copy it from the original drive to the new drive using My Computer or Windows Explore?  Do I need RPAM_Store.dat, and if so, do I need to move or create a new one in any special manner such that it appears in the new drive destination along with the .*v2i files?
2

Using Ghost 15.0, I used the Move function within the Manage Backup Destination screen to move back-ups from one drive to another.  All of the .iv2i, .v2i and .sv2i backups moved as expected. 

Two issues and a few questions:

 

  1. Although all .*v2i backups were moved to the new destination, copies of three iv2i files remained in the original drive.  The file sizes match.  Is it OK to delete the three files in the original drive since they also appear in the new drive?

  2. The RPAM_Store.dat in the original drive did not move from the original drive to the new drive destination.  There is no RPAM_Store.dat in the new drive destination after the Move command was executed.  Should I just copy it from the original drive to the new drive using My Computer or Windows Explore?  Do I need RPAM_Store.dat, and if so, do I need to move or create a new one in any special manner such that it appears in the new drive destination along with the .*v2i files?
3

Thanks for the feedback.  The new location is indeed my new backup destination.  Since I wrote the original post, I see that a new RPAM_Store.dat was created in the new location along with the most recent backup, consistent with your feedback.  I have a few more questions:

 

1. Does the newly created RPAM_Store.dat also account for the older backups that now reside in the new location as a result of the "Move"?  Here's my concern:  the old RPAM_Store.dat that is only in the "old" destination has the info about the "old" backups.  But those old backups now reside in the new destination.  If I try to recover one of these old backups (out of the new destination), will the recovery fail because the new RPAM_Store.dat only keeps track of the new backups to that new destination?

 

2. You had menitioned that the history of the move still exists:

     -  Does that history exist in the new location and perhaps buried within the .*v2i files? 

     -  Can I delete the old RPAM_Store.dat in the old destination without affecting my ability to recover "old" backups that now reside in the new destination?  I would like to completely delete the old destination including the old RPAM-Store.dat, the folder name and the drive letter.

 

3. Is the RPAM_Store.dat file an integral part of the backup and recovery process, or is it just "information" for troubleshooting or some other purpose?

 

Best Regards,

TomSweazy

4

You can safely remove the RPAM file from that backup destination that is no longer used. It is not necessary for backup completion. The RPAM file is used by the Granular Restore Option, as well as during the mount process of an image file. So it is not necessary for succesful backups or restores, but please do not delete it if it exists with the active backups.

 

The history is stored in a separate location on C:\ drive, or where you installed the program to. The .V2i is a base image file, an .iv2i is in iincremental, and a .sv2i is an index file that is used when you choose the 'system' restore from the menu.