Transfer Recording Schedule (not files) to New Hard Drive


#1

I want to replace my existing hard drive with a new larger one.
I would like the recording schedule saved, not the shows.

It the recording schedule stored on the HD or within the Tablo’s memory?

Note: I have the 4 Tuner model.


#2

I believe the schedule is in the Tablo. To verify, reboot the Tablo with no HD attached (when no recordings are scheduled to start), then see if you can view your upcoming schedule.


#3

I can verify eariler Tablo firmware versions stored recording schedules internally, not on the attached hard drive.
Easy to check to see if it’s still true.
Power off Tablo.
Disconnect currently attached hard drive.
Connect new hard drive.
Power on Tablo.


#4

I haven’t tried this myself, but believe the scheduled recordings might not display, cuz there isn’t an attached hard drive to record to.
It could be a false negative.


#5

There is no easy way or officially supported way to do this at this point in time (that I know of).


#6

Hey there, this isn’t currently possible at the moment - sorry! I’ve passed this along to our product team as a feature request.


#7

So if I upgrade my drive I have to make note of every scheduled show and create a new schedule.
That is not really a great feature!

So yes, please add the ability to backup the recording schedule for installation on a new drive. I cannot imagine why this is not yet available.


#8

Why - cause very few users upgrade their HDD. Tablo is a set it and forget it device, it just works.

But I agree, it would be a handy feature.


#9

Why?

  1. Hard drives fail.
  2. Larger faster drives are available every year. People may want larger drives to store more video.
  3. It is a basic feature of data processing - the ability to backup your data.

#10

I’m not in disagreement with your reasons for wanting such a feature.

But which other DVR on the market has this feature you claim is basic and absurd it doesn’t exist yesterday?


#11

Not a big time saver, but I screen print my scheduled recordings before any operation that could erase my schedules.

Obviously it takes some time to re-enter the schedules but at least I have a record of what was scheduled.


#12

Hey guys, I totally misinterpreted @Lysander’s original post. I thought you were looking to transfer the recordings along with the schedule (even though your explicitly stated this wasn’t necessary). My bad!

So to correct myself, this is possible; all you need to do is remove the existing drive, attach the new one, and you’ll receive a prompt to format. The schedules are stored on the Tablo itself, not the drive. Hope this helps.

So, your upcoming shows will simply be sent to the new drive. The only thing that may cause confusion is the recordings stored on the original drive will still appear in the Recordings menu, but will not be accessible as the original drive isn’t attached.


#13

THANKS. That is all I was asking for.

@theuser86. I guess Tablo has the feature I was asking for!

@TabloSupport - next logical step would be to have a way to back that up off the Table so when I Upgrade to my next new Tablo I could have my schedule restored on the new one!


#14

This is supported, too :slight_smile: if you reboot the Tablo with the reset button, it will back up the database to the externally attached drive. If you attach that drive to a new Tablo on the same firmware, it will restore that copy fo the database to the new Tablo.

The full process is available here :slight_smile:


#15

Great, thanks for that. Makes life a little more easy!


#16

Will the original recordings stored on the original drive ever be cleaned up aka deleted as the new drive doesn’t have such recordings on them?


#17

I upgraded my drive three weeks ago from 2 TB to 5 TB and the recordings schedule was retained. However I had to go through my old “recordings” (which actually were not on the new drive) and delete them one by one using the recordings panel. The delete worked despite the fact there was really no recording there. Tablo must have just deleted the index entry. That cleaned things up.


#18

@Lysander lol, which is what I stated early on. :slight_smile: