AnsweredAssumed Answered

Handling Scheduled backup files:  switching paths, copying files, and remote container data

Question asked by disabled_JustinClose on Jan 26, 2013
Latest reply on Jan 27, 2013 by disabled_JustinClose


Handling Scheduled backup files:  switching paths, copying files, and remote container data

Your post

     I went through a process of trying to move our backup directory; the current one is on the same volume as the live file.  But, this might really be a problem with my understanding of hard links and remote container data.   FMS12.03, Mac OS X Server 10.6.8.  FMP client 12.01 (running on the server); live hosted file tested from FMPA client 12.03 running on Mac OS X 10.6.8.

     I made the new directory on the other volume, changed permissions, modified the path shown in the FM Server Admin console (hitting Validate to verify - it was good).  In order to try and keep things in the same place, I then COPIED all the current backups from vol1 to the new location in vol2.  No real problems there.  I then changed the schedules (rather, I created copies of the originals and edited the copies, giving them new names) to also point to the new path.  (Apparently the path defined in the console config is only a default?)  I also left both sets of schedules running (old path and new path backups) just to be sure I had the new ones going correctly before altering the old ones.

     So, this morning, I checked on things.  I have a variety of new backups in the new location.  I made a COPY of one of the new backedup files (including the entire RC_Data directory) and pasted that to a temp directory on the desktop of the server.  (So far, all of this has been done via screenshare to the server.)  The file opens OK, and there is plenty of data there.  However, when I go to a layout that shows some of this remote container data, it gives me a placeholder image saying "file missing:  filename.ext"

     I copied a different set of files/RCfolder from an earlier backup, same thing.  I copied a set of backup files from Vol1 volume (i.e. the original backup directory and schedules that I hadn't messed with) and got the same results:  no remote container data showing up.  I then copied the LIVE file and RC_Data, same result:  no RC data showing.  When I go to the hosted live file from my remote machine, I see RC_Data just fine for this same record (I have been checking the same record each time).  Whew!  :)

     So…instead of trying to unwind the various things I have done, perhaps it is just best to tell how to best MOVE a backup directory, or rather, switch the directory that the server is using for backups.  Or maybe the move part was fine, and it is merely my method of testing and verifying the move that is wrong.  I was thinking that it was a problem with the way the RC_Data hardlinks were being handled (or my perception of them - I thought if I made a COPY of the backups, that I would get a full real copy of the originals).

     Any suggestions would be appreciated.