![]() "C:\Program Files (x86)\FTR\ForTheRecord\" -trim -processrecordings -processlogsheets -UseTRSĭoes removing -add actually save any time or should I just leave it in for completion sake? Since the media is removed from the NAS when it is older I schedule a sync without -add: Is there a better way to do either part of that process? "C:\Program Files (x86)\FTR\ForTheRecord\" -add -trim -processrecordings -processlogsheets -UseTRS Then on the SAN Warehouse server I schedule a sync: So first it MOVES everything that is 180 days old, then it makes a COPY of everything else that is left. ![]() Robocopy \\NAS-Server\FTR_Recordings \\SAN-Server\FTR_Recordings /R:1 /W:1 /E Robocopy \\NAS-Server\FTR_Recordings \\SAN-Server\FTR_Recordings /R:1 /W:1 /E /MOV /MINAGE:180 /IS Is there a way to automate/schedule FTR Manager so that it will migrate 6 month old recordings from one warehouse to another? This is how we are doing it now (via scheduled nightly script): 1 is for the archived SAN media and lognotes. ![]() Warehouse enforced archiving sends recording to a NAS device that is located at each site.Įach night a script runs that copies media from each NAS to a SAN at the main site and if older than 6 months the media is removed from the NAS.Ģ Warehouse 5.6.1 servers running on server 2008. 1 main branch (29 recorders) and 4 remotes sites (23 recorders) totaling 52 recorders.Īll running Reporter 5.6.1 with warehouse client 5.6.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |