nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Y: Drive Backuping

Linio

Dear All,

I'm working on the backuping of the Y: Drive on a logical drive.
My client needs his data to be backuped and to access its files externally of Teamsite. A normal backup (NetBackup) doesn't work as the Y: drive emulated (IWFS) is not recognized by the Backup Tools.
We considered the possibility of backuping the whole content of the Y: drive on a logical drive, but as I'm testing (with a simple command line like xcopy), it takes about 25 minutes to copy 350Mb of data, and there is 36Gb of Data (so a estimate total of 40 hours to copy the whole thing).

I'm assuming those times are "normal" due to the fact that the disk is emulated, am I right?

If so, how can I manage to have those files backuped each day?

I'm working on Teamsite 6.0 on a Windows System.

Find more posts tagged with

Comments

ISCBorisB

Dear All,

I'm working on the backuping of the Y: Drive on a logical drive.
My client needs his data to be backuped and to access its files externally of Teamsite. A normal backup (NetBackup) doesn't work as the Y: drive emulated (IWFS) is not recognized by the Backup Tools.
We considered the possibility of backuping the whole content of the Y: drive on a logical drive, but as I'm testing (with a simple command line like xcopy), it takes about 25 minutes to copy 350Mb of data, and there is 36Gb of Data (so a estimate total of 40 hours to copy the whole thing).

I'm assuming those times are "normal" due to the fact that the disk is emulated, am I right?

If so, how can I manage to have those files backuped each day?

I'm working on Teamsite 6.0 on a Windows System.

You do not modify 36G of data daily, do you? So, bite the bullet once and create a back-up whatever time it takes.
Then find yourself a Tool capable of deploying only modified assets (Delta's). One of these Tools is IWOV Open Deploy
(OD), you may already have it if you are using TS

nipper

You do not modify 36G of data daily, do you? So, bite the bullet once and create a back-up whatever time it takes.
Then find yourself a Tool capable of deploying only modified assets (Delta's). One of these Tools is IWOV Open Deploy
(OD), you may already have it if you are using TS

Unless, of course, they create Editions, then each new edition will get backed up. This is really a dumb request and you need to tell the customer that.

Now it does make sense to back up workareas (esp if you have shared workareas) but not the whole Y drive

Adam Stoller

Dear All,

I'm working on the backuping of the Y: Drive on a logical drive.
My client needs his data to be backuped and to access its files externally of Teamsite. A normal backup (NetBackup) doesn't work as the Y: drive emulated (IWFS) is not recognized by the Backup Tools.
We considered the possibility of backuping the whole content of the Y: drive on a logical drive, but as I'm testing (with a simple command line like xcopy), it takes about 25 minutes to copy 350Mb of data, and there is 36Gb of Data (so a estimate total of 40 hours to copy the whole thing).

I'm assuming those times are "normal" due to the fact that the disk is emulated, am I right?

If so, how can I manage to have those files backuped each day?

I'm working on Teamsite 6.0 on a Windows System.

As Nipper indicated - you probably only want to backup the workareas through the Y drive - not the entire Y drive (you'll get tons of redundant data if you do that).

When you came up with 36Gb of data - were you just doing a Windows scan of the Y drive or were you looking at the actual contents of the workarea?

Linio

Actually I already know this request is ... how to say this... not really clever, still i'm not here to question the motives on this point, i'm (sadly) not paid for this.

To sum up and understand the motive of the request, it's mainly aimed at backuping data that is not effectively backuped by the Teamsite tool (mainly DCRs, and all the files that were not submitted at least once).

Still, even if i create a script to filter the uneeded files, it stills takes loads of time to go through all the directories on the Y: Drive.

Because even if I only backup the content of the Workareas I'm dividing the size of the data by about 2, so it will lead to the copying of about 15 to 20 Go, which is still to much...

I didn't though of the O.D. solution, still I never created a deployment to the teamsite main server, so let's hope this works.

Thanks.

Adam Stoller

Actually I already know this request is ... how to say this... not really clever, still i'm not here to question the motives on this point, i'm (sadly) not paid for this.

To sum up and understand the motive of the request, it's mainly aimed at backuping data that is not effectively backuped by the Teamsite tool (mainly DCRs, and all the files that were not submitted at least once).

Still, even if i create a script to filter the uneeded files, it stills takes loads of time to go through all the directories on the Y: Drive.

Because even if I only backup the content of the Workareas I'm dividing the size of the data by about 2, so it will lead to the copying of about 15 to 20 Go, which is still to much...

Are you sure? Did you verify that?

For each branch you encounter in the Y drive, there will be an EDITION folder, a STAGING folder and a WORKAREA folder. For each EDITION folder there will be folders for each edition created on that branch (named and unnamed) for each WORKAREA folder there will be a folder for each individual workarea.

The contents of the STAGING folder and each and every EDITION folder is virtual copies of the contents of the backing store - if version 1 of file foo is 10Mb, exists in staging, and has existed through 10 editions of that branch and there are 5 workareas on that branch in which nobody has modified this file - that would represent 160 Mb of data that your original method of trying to backup the Y drive would process (10Mb * (1 + 10 + 5)). If you only backup the workareas - then it comes down to 50Mb (10Mb * 5).

Hopefully you only have one workarea per branch. Probably you have more than 10 editions per branch - so if you use the above formula for differentiating the size of content in the branch versus the size of content in one workarea on the branch - you will probably see a dramatic difference in size (not 1/2 of the total size of the backing store - more like 1/20th or 1/200th or even smaller - it obviously varies on a lot of factors)

Writing a script to traverse the Y drive to find workareas and then copying the contents of the workarea to some other destination is not that difficult - but the exercise is for you to figure out how to do it - not me. If you like coding in Perl - consider taking a close look at TeamSite: Smiley Very Happy

irwalker and then whatever you want to do the actual data transfer.

Linio

I did verify the amount. I won't go into the specifics of how the application is used by my client, but not all the files are going through the staging.
Anyway it's not the important point here.

I've decided to try and copy those files with OpenDeploy, and I've managed to configure everything correctly.
First copy of the files takes some time but obviously after that it's taking only the time to copy the delta, so thanks, this was a good idea.