BackUp device for local or colo storage
-
@scottalanmiller said:
@DustinB3403 said:
No 8 TB was to perform weekly fulls at the current infrastructure size.
Wait, if a full is 8TB, where did I get 22TB from?
Full Backup retention for an entire month.
-
@DustinB3403 said:
@scottalanmiller said:
@DustinB3403 said:
No 8 TB was to perform weekly fulls at the current infrastructure size.
Wait, if a full is 8TB, where did I get 22TB from?
Full Backup retention for an entire month.
That would be 32TB then.
-
Actually it's technically a 7 day swap cycle now for what we have.
Might have to keep the same process if I want to reduce IT's labor on the backup process. (Weekends count to computers)
-
@scottalanmiller said:
@DustinB3403 said:
@scottalanmiller said:
@DustinB3403 said:
No 8 TB was to perform weekly fulls at the current infrastructure size.
Wait, if a full is 8TB, where did I get 22TB from?
Full Backup retention for an entire month.
That would be 32TB then.
8 TB is with growth... currently he's at just over 6 TB.
so 24 TB for a month -
@scottalanmiller Only if we we're fully using all 8TB.
We have free space on the systems now and are only using approximately 6TB of total 8TB capacity in the infrastructure.
-
I'm really lost - why are you worrying about full backups when you have a StorageCraft backup solution?
-
@Dashrender So if something should happen to the vDISK on XS. That we have a way to simply import a 2TB file to the server, and turn it on.
Trying to K.I.S.S
-
@DustinB3403 said:
@Dashrender So if something should happen to the vDISK on XS. That we have a way to simply import a 2TB file to the server, and turn it on.
Trying to K.I.S.S
Can't you get that from the StorageCraft system?
-
Not effectively (at least with what we have).
Fulls currently take over 24 hours to generate when their needed. So fulls are almost never taken.
But our system partitions are ignored, besides 2 servers.
I want to include everything in the backup process. So everything is protected.
-
I'd say your two separate backup solutions aren't very simple. One extra thing that can fail. One extra thing to maintain/mange.
StorageCraft for daily incrementals
and home built solution for weekly fulls.Maybe StorageCraft can actually create the tapes for you?
I know when I was looking at Backup Exec it could. It would pull incrementals daily, then it could spin down full backups to tape on whatever schedule you wanted. It would create a virtual full backup at that given point in time and that is what was backed up to tape.
-
Incremental changes can be written to local onsite storage, but this doesn't include recovery options for "everything" just the system changes from the past 3 (but should be 7 days).
-
@Dashrender said:
and home built solution for weekly fulls.
I might be being mean to NAUBackup, calling it home built.
-
@DustinB3403 said:
Fulls currently take over 24 hours to generate when their needed. So fulls are almost never taken.
It takes 24 hours to generate a full backup from StorageCraft? Why? What's the hold up?
-
@Dashrender said:
@DustinB3403 said:
Fulls currently take over 24 hours to generate when their needed. So fulls are almost never taken.
It takes 24 hours to generate a full backup from StorageCraft? Why? What's the hold up?
Yeah, this seems like a major problem. If it takes that long to take a backup, what's the restore process look like?
-
@scottalanmiller We've never had to perform a full restore thank god.
But I'd imagine that it's awful.
-
This is also why we really only perform hourly incremental backups currently.
-
@DustinB3403 said:
@scottalanmiller We've never had to perform a full restore thank god.
But I'd imagine that it's awful.
And it is the reason that backups exist in the first place
If restoring a full is bad, imagine having to restore a full plus an incremental!
-
When you said it took 24 hours to generate - I thought you mean to do a restore, but after reading your comments, it takes 24 hours to take a backup?
Oh man - WHY? I'd look into fixing that problem, or ditching the StorageCraft all together. In keeping with your own desire to K.I.S.S. I don't see you have any other choice.
From here it looks like you're trying to solve one problem by throwing another solution at it instead of fixing the problem.
-
OK So dropping the idea of full backups.
What would you guys recommend? A single full backup of the XS VM's pre-data, and then use Storage Craft for the daily incremental backups?
-
If your OS's really don't matter, and they are only serving the purpose of file server - then that might work. Setup your main OS install, create all of your shares, then create images of the OS and boot drives. Then backup the data drives as desired.
But if you application settings that need to be backed up regularly that live on the OS drive, why not an incremental forever solution, once your StorageCraft performance problem is solved? Then you can replicate your StorageCraft to another site, only replicating the daily changes.
